Whether your organization chooses to use functions included in the Didomi SDKs or display a fully customized consent notice, customizing custom notice behavior will likely impact the standard CMP analytics available to your organization.
The most common behavior implemented by organizations that will impact CMP analytics are functions that either use the API to programatically set the end-user's consent status or sharing consent with a webview. Depending on the functions used, the end-user's consent choice (opt-in or opt-out) will be record as either:
- external
- webview
external
If your organization leverages the Didomi API to set the end-user's consent then the end-user's consent choice (opt-in or opt out) will programmatically include an external flag and be record as an external opt-in or external opt-out in your organization's CMP analytics.
The common API functions that will trigger the external flag include:
Note: Consent choices that are flagged as external (e.g. external opt-in, external opt-out) are not included in the calculation for opt-in rates and opt-out rates. In order to retrieve this aggregrated data, your organization can utilize the Didomi Analytics Data Export premium feature to compute rates on your end.
webview
An end-user's consent choices (opt-in or opt out) will programmatically include a webview flag and be recorded as an webview opt-in or webview opt-out if your organization performs one of the following customizations:
| Mobile SDK | Your organization shares consent from an app to a webview and utilizes the getJavaScriptForWebView function. |
| Web SDK |
Your organization leverages the Didomi API to set the end-user's consent by passing |