Trackers and service providers: what is each component doing?

“Tracker” covers several different mechanisms. One component counts article visits, another records player failures, another selects marketing messages. A consent or subscription provider can also exchange necessary service data alongside optional metrics. Understanding the role makes a patch's effect and tradeoffs easier to assess.

An SDK is a reusable package of code embedded in an app. An event is a record of something that happened, usually with named details. An identifier is a value used to associate records with the same installation, session or account. Telemetry is data software sends about its operation or use. None of these terms alone proves that data is anonymous or identifies a particular person by name.

Which tools measure behaviour and interactions?

• Snowplow: structured screen, action and publisher events, with identifiers and context.
• Contentsquare and Heap: screen/component interactions, recording and identity/instrumentation boundaries.
• Usabilla/GetFeedback: manual feedback alongside automatic event-triggered surveys and telemetry.
• Matomo and Eventor: first-party collection in FTM's embedded website.

Which tools measure audiences, content and video?

• Kantar/NMO: audience counts and the concrete Snowplow-ID connection in Buienradar.
• Bitmovin: player quality and viewing analytics, separate from playback/licensing.
• Comscore and Gemius: audience-measurement integrations, including native code.
• Chartbeat, Parse.ly and Smartocto: reading, engagement and video-play measurement.
• Blue Billywig, JWPlayer and DPG media: media telemetry, retained Catsure state and the independent audio coverage gap.

Which components diagnose problems?

• Firebase: Analytics, Crashlytics, Performance and Sessions have different jobs from installation identity, configuration and push delivery.
• The additional-service profiles also explain why player quality measurements overlap with behavioural records.

Which tools support marketing and targeting?

• Meta/Facebook: App Events and Audience Network, with separate startup and identifier paths.
• Swrve: profiles/campaigns plus Buienradar's weather-alert dependency. It remains enabled by default.
• Insider: events, profiles and geofencing suppressed in Flitsmeister; live CITS location remains.
• BrandMetrics and VWO: advertising-effectiveness surveys and experiments.

Which services manage consent and subscriptions?

• OneTrust: privacy UI, configuration and consent-related interactions.
• Didomi: consent state and optional service metrics, with different per-app boundaries.
• RevenueCat: genuine purchases/entitlements alongside optional attributes and diagnostics.

How should I read the evidence?

Each profile separates documented product capability, traced app code, configured destinations, web-policy coverage and runtime observations. A hypothetical example explains a mechanism; it is not a captured user session. The linked app pages identify exact supported versions and controls. Provider documentation describes what a product can do, not everything an inspected app did.

Independent resources help identify systems and their wider context: Exodus's tracker catalogue, DuckDuckGo Tracker Radar and the historical 2017 Cracked Labs report. Tracker Radar explicitly supplies a dataset rather than a ready-made blocklist. These sources do not replace app-specific evidence or establish current transfers in these versions.

Evidence reviewed 28 October 2026. No new decrypted packet capture was added. These findings do not establish retention, resale, legal violations or zero remaining traffic. Start with how tracking works, then identifiers, location, consent and our methodology. The source guide explains the source types.