Other measurement services: which similar names have different roles?

The profiles below explain additional systems in the supported apps. An event is a record of an action; an SDK is a reusable code library; an identifier connects records to an installation, session or account. A destination found in code is not automatically a captured transfer. Examples marked hypothetical explain mechanisms rather than actual user behaviour.

What do Comscore and Gemius count?

Comscore supplies audience and advertising measurement. Gemius also measures audiences, combining tagged-service data with panel-based information in its documented methodology. Their purposes can resemble Kantar/NMO, but they are distinct providers and implementations. Comscore SDK description, Gemius methodology.

Hypothetical example: article-open and periodic activity records let a measurement system estimate use over time. A repeated ID may distinguish a return visit from a new installation; the resulting totals do not tell us which fields were collected before aggregation.

NU.nl, NRC, AD, de Volkskrant, Trouw and Parool have separately traced Comscore integrations. scorecardresearch.com destinations belong to this evidence, including native-library capability in some apps. Parool's actual configuration also selects gabe.hit.gemius.pl. The controls stop the inventoried initialization, events, queues and relevant native boundaries; a packaged native library can remain without its identified entry points running. Do not infer active Gemius collection in AD merely from bundled types: its audit did not establish a reachable integration. Destination evidence, AD boundary.

What do Chartbeat, Parse.ly and Smartocto learn about content use?

These tools support editorial measurement: which content is used and how people engage. Chartbeat documents interaction/engagement tracking. Parse.ly documents periodic heartbeats, requests used to report engaged time. Smartocto documents video events with content identifiers. These capabilities do not establish identical collection in every integration. Chartbeat Android SDK, Parse.ly engagement, Smartocto video tracking.

Hypothetical example: “article opened” followed by activity pings lets an editor distinguish opening a page from continuing to use it. That can inform editorial decisions while also recording reading behaviour.

NRC 5.12.24 has Chartbeat and Parse.ly integrations and destinations including ping.chartbeat.net, pong.chartbeat.net and p1.parsely.com. The patch stops their audited setup/event paths and web beacons. Functional Parse.ly recommendations remain allowed: content recommendation and measurement are not interchangeable just because one provider supplies both. NRC audit.

Buienradar 7.4.8 has a separate video-play sender to ingestion.smartocto.com/v?t=videoPlay; Disable tracking stops that listener. It is separate from Bitmovin analytics. Buienradar audit.

Why distinguish Blue Billywig, JWPlayer and DPG media telemetry from playback?

A player can fetch media and separately report playback events. JWPlayer's documentation explains periodic pings and calculating time watched from them. This is a mechanism description, not evidence of every field in NU.nl. JWPlayer analytics reference.

Hypothetical example: “play”, “seek” and “stop” describe interaction with a clip. They are different from retrieving the bytes needed to play it. Audio player telemetry likewise does not imply microphone recording.

Weeronline traces Blue Billywig statistics to stats.bluebillywig.com and stops the statistics sender while keeping playback. NU.nl stops an identified JWPlayer image-pixel sender and known web telemetry while retaining player assets and media requests. Weeronline audit, NU.nl audit.

DPG's video telemetry includes psti.prd.dpge.be; its independent Amalia audio events use tracker.prd.dpge.be/track. Parool stops collection through the independent audio event methods. AD, Trouw and de Volkskrant have an explicit remaining audio-coverage gap. Their video controls should not be taken as proof that every audio event is stopped. Across these apps, functional Catsure device ID, ordered queue/media IDs, playback position and playing/paused/stopped synchronization remain. The server's functional role is not fully classified. Current pinned coverage and residual data, Parool audio finding.

What do Matomo and Eventor show about first-party collection?

Matomo supports pageview and event requests, including optional user and pageview IDs. A publisher's own hostname can host a collector; first-party does not mean “no measurement”. Matomo tracking API.

Hypothetical example: a request to the same organisation's insight host may report a reading event while its main host supplies the article. Ownership and purpose answer different questions.

FTM 2.6.8 has insight.ftm.nl Matomo instrumentation and eventor.ftm.nl event/ID updates. The patch filters those collectors and clears five specific Eventor browser-storage keys after page completion. Temporary local ID creation before that cleanup remains possible. It also blocks the exact comments-visibility telemetry route on the production sites. Account state, comments functionality and ordinary browser storage are not globally replaced. FTM audit.

How do BrandMetrics and VWO differ from a general event logger?

BrandMetrics concerns advertising effectiveness and survey measurement; VWO concerns experiments. Their own descriptions explain survey-based brand measurement and visitor conditions for showing a variant. BrandMetrics measurement, VWO targeting settings.

Hypothetical example: an experiment compares two presentations by assigning a visitor to a variant and counting outcomes. An ad survey asks a different question, but either can involve identifiers and response context. The example is not an assertion that a particular experiment ran.

Parool's actual ad configuration selects phx.bmtrcs.com with DMOI identity and survey placeholders. That is configured evidence, not a captured completed survey. Its policy therefore covers bmtrcs.com; brandmetrics.com alone would miss that hostname. Several news-app web policies cover dev.visualwebsiteoptimizer.com, but policy coverage does not prove which experiment loaded. Parool audit, destination distinctions.

Evidence reviewed 28 October 2026. No new packet capture, retention or resale finding follows from this page. Read how tracking works, identifiers and methodology.