Insider: how do events and location become marketing inputs?

What does this SDK do?

Insider, now documented as Insider One, provides tools for customer profiles, segmentation and messaging. Its SDK is a reusable code package embedded in an app. An event records an action with its context; an attribute describes a profile property, such as a current preference. The provider explains that some default fields need explicit app integration while device attributes can be populated through SDK setup. A feature appearing in documentation does not establish that an app sends it. Insider events and attributes.

The service also supports geofencing: checking whether a device enters or leaves a defined geographic area. Its instructions describe location permissions and a separate location opt-in. This is product capability; a geofence library's presence is not proof of a particular fence, location history or campaign. Insider geofencing documentation.

Why distinguish navigation from a marketing location feature?

Hypothetical example: a navigation app needs the current position to display a map. A separate marketing component might use entry into an area to select a message. Both involve location, but their triggers, receivers and purpose differ. Stopping the marketing component need not mean turning off the GPS functionality required to drive with the app.

An ID can connect successive events to one installation or profile. Finding profile and event APIs tells us which collection boundaries deserve inspection; the exact profile fields and transmitted payload still require app-specific evidence.

What did we find in Flitsmeister?

For Flitsmeister 14.17, Disable tracking covers Insider initialization, event/profile attributes, geofencing, persisted jobs and its SDK-only transport. A persisted job is work saved to run later, so stopping only visible screens would miss that route. The published audit does not pin an exact Insider upload hostname or a complete captured payload. Pinned Flitsmeister audit.

What location exchange remains?

The same patch separately suppresses identified first-party footprint, floating-car-data, usage and optional sensor/monitoring telemetry. However, live CITS GPS exchange remains. CITS is the connected traffic-warning service described in the audit. Essential map/routing, explicit hazard reports and operational account/push registration also remain. These can receive functional location and identifiers.

All six Flitsmeister controls are enabled by default in the supported release. User-confirmed device acceptance does not prove complete network silence or establish provider retention. Removing Insider is one bounded result within a larger location-dependent application.

Evidence reviewed 28 October 2026. Read location, identifiers and methodology.