We’ve migrated our documentation to a new site, which means some URLs have changed. If you hit a broken link, submit a support ticket.
Analytics
English French
Analytics
English French
Breadcrumbs

Why do I have differences between my Piano Analytics and ACPM data?

The ACPM certification is specific to the French market.

It is completely normal for your Piano Analytics and ACPM statistics to differ each month. ACPM processing is part of a separate processing chain from standard Piano Analytics data and relies on different rules. The main sources of discrepancy are detailed below.

Configuration differences

  • Domains rather than site numbers. The ACPM works by domain, not by site number, for fixed and mobile scopes. Several visits from distinct level 1 sites on the Piano Analytics side may therefore add up to a single visit on the ACPM side, if they took place on the same domain.

  • Visit inactivity timeout. It is fixed on the ACPM side (30 minutes) but configurable on the Piano Analytics side. Visits are therefore recalculated by the ACPM processing chain.

Traffic exclusions

  • AMP traffic. It is excluded from the web and mobile scopes and must have its own scope to be taken into account.

  • Events other than page views. All events that are not page views (Clicks, AV Insights, Sales Insights, and so on) are excluded from the ACPM data, whereas a visit can exist without any page.display event in Piano Analytics.

  • Responsive rules. They affect what is taken into account in an ACPM scope. They are based on the device type (the Device - Type property), which can be empty if the User-Agent or Client Hints are forced by the publisher with unrecognized values.

The "no referrer" case

From the ACPM's point of view, "no referrer" cases are pages with no current URL associated with them. Only some of these pages are taken into account for certification, since it is not possible to verify that they come from the domains to be certified.

The Piano Analytics SDKs collect this information natively, except in "exempt" mode for clients using exempt tagging. In that case, you need to exempt the page_url property to collect it systematically.

The SmartTag collects the information natively through the request headers, which can be limited by browsers or by your hosting server's Referrer-Policy. A dedicated article explains how to obtain the full URLs of pages. Here too, you'll then need to exempt the page_url property.

Getting closer to the ACPM data

Comparing the two sources remains difficult. To get as close as possible to the ACPM data:

Web scopes

  • Select all of your sites (for mobile web, select only the sites declared in your DSH).

  • Filter on the domains declared in the relevant ACPM scope.

  • Filter on page.display events.

Mobile apps and AMP

  • Select the sites declared in the relevant ACPM scope.

  • Filter on page.display events.

Last updated: