What to expect from your analytics when setting a custom behavior for your consent notice?

Customizing your consent notice behavior, whether you choose to use our SDK functions or display a fully customized consent notice, will likely impact your out-of-the-box analytics and metrics.

Which consent notice customization will impact my analytics?

Any consent notice customization in all environments, not done through the notice out-of-the-box options, will result in a positive or negative consent (consent.given event) measured as custom.

The main use case is the use of our SDKs' setUserStatus function(s).

How will my analytics be impacted by said customization?

First, here is a bit of context about how our SDKs determine what triggers a positive or negative consent (consent.given event):

  1. click
    For all SDKs:
    An end-user interacts by clicking on the consent notice to provide their consent
    👉 A positive or negative consent with a click parameter will turn out to be a positive or negative consent in your analytics and will be taken into account in the different metrics and rates
  2. external
    For all SDKs:
    Consent is set programmatically via our functions (such as setUserAgreeToAll) without the action being specified as a parameter
    👉
    A positive or negative consent with an external parameter will turn out to be an external positive or external negative consent in your analytics and will not be taken into account in the different metrics and rates
  3. webview
    Either via:
    1/ Mobile SDK
    Programatically through our mobile app SDKs, when sharing consent from an app to a webview and using the getJavaScriptForWebView function (with a parameter or not)
    2/ Web SDK
    Programatically with the action being specified as a parameter in the function
    For instance, using our JS functions like setUserAgreeToAll(action='webview')
    👉
    A positive or negative consent with a webview parameter will turn out to be a webview positive or webview negative consent in your analytics, it will be available under the "App Session dashboard"
    And it will not be taken into account in the different metrics and rates

P.S:
There can also be navigation and scroll parameters for the user to interact with the notice (just like (1) click)
Those options will result in positive or negative consent given and would be taken into account into the metrics and rates
However, those options are now not compliant in most countries

In summary; the customization described above will likely result in external consents. And they are not taken into account in the rates calculation.

What are the options to use my analytics and measure my rates?

As detailed above, external consents are not taken into account in the metrics calculations.
However, there are still options to retrieve this data and aggregate it to compute the metrics and rates on your own:

1/ Use the custom report in the Analytics section

Our Custom Report allows you to extract raw data (external consents, total notices, etc.) so that you can compute the rates on your end with the granularity and details you wish.


2/ Subscribe to the Analytics Data Export 

The Analytics Data Export provides a way to access analytics data (aggregated data) collected through the Didomi platform at once, through the export of said data on a cloud bucket.

Analytics Data Export is a premium feature. 


You can read more about our Analytics Data Export feature by clicking here.


Moreover, you will find details of how our rates are computed in this file. This would help compute the metrics on your own using our calculation methods.