1. Help Center
  2. Analytics
  3. Consent Management Platform (CMP) Analytics

Paywall integration impact on CMP analytics

The analytics functionality of the the Didomi CMP are closely tied with consent notices. Replacing the Didomi consent notice with an alternative notice to deploy a paywall will significantly impact data collection since Didomi does not provide tracking capabilities for other services that could be a substitute for the primary end-user interface.

The event responsible for counting the displayed notice (consent.asked event) will not be triggered, rendering indicators relying on this metric inaccurate. Metrics such as total notices displayed, no choice rate, and opt-in rate will no longer provide reliable information.

If your organization must integrate a paywall option into a consent notice Didomi strongly recommends to customize an existing Didomi notice for optimal analytics. Below are two examples that your organization could configure to preserve analytics accuracy:
  • No opt-out option 
  • Consent change incentive
No opt-out option

Didomi recommends implementing the no-opt-out option by utilizing a Didomi consent notice that does not incorporate an opt-out option (neither button nor link). Instead, customize the consent notice by adding a second button, directing users to the pay option.

Upon end-user subscription (or micro-payment), we suggest triggering an opt-out using the setUserDisagreeToAll function of the SDK.

This implementation ensures the continuity of CMP analytics. Additionally, end-users who have subscribed to the paid option will be registered as an external opt-out. This metric is available in the main table of Domains & Apps dashboard, as well as in the analytics export.

Consent change incentive

Your organization can also implement a consent notice where there is a preference to initially allow opt-out, but when it happens, there is a recommendation to change the consent status or encourage a subscription to a paid option.

Didomi suggests that your organization deploys a standard consent notice with a decline option of your choice (button, link, or cross). Subsequently, you would need to condition the deployment of the consent change request banner to those who opt-out. Regarding the consent change option (from opt-out to opt-in), we recommend using the setCurrentUserStatus function. These changes will be registered as external opt-ins in your analytics data.

You will then be able to have the consent rate of the first layer (standard banner). With the external opt-ins, you will also be able to measure how many opt-outs have been changed to opt-in and recalculate the final consent rate (and opt-in rate), especially with the analytics export.