Understand your Monthly Unique Visitors (MUVs)

Didomi SDK Behavior

For the MUV, Didomi's SDK works as follows:

  1. Didomi’s SDK is called on each web page/app opening.
  2. Collects pageview/app session events. 
  3. Checks if the user is known and has given consent or not.
  4. Checks if the consent needs to be asked again based on the notice’s update or settings. 
  5. If required, the notice is displayed. 
  6. Collects consent asked event.
  7. Collects the user consent.
  8. Transfers the consent information to the vendor integrations or the tag management system (TMS).

👉 Didomi’s SDK verifies all visitors' consent, on all the pageviews/app sessions.

👉 As a result, Didomi’s SDK is called each time a web page is loaded and performs verifications for all the visitors, even visitors who already have given consent.

👉 Whatever is the number of pageviews/app sessions generated by a visitor (adid*,uuid**), he will always be counted as one.

Why the MUV?

  • MUV is an approximation of the monthly volume of visitors generated by an account. They are estimated thanks to the pageview / app session events.
  • Standard MUVs are calculated following this formula: user IDs (adid,uuid)/ pageview or app session event sampling rate.
  • Sampling rate:

    • Web: 3% sampling (on users)
    • App/CTV: 10% sampling (on users)

    MUV ≠ total consents given

    👉 The MUV metric covers all the traffic whereas the consents given only covers the users that have given a consent during the period.

Impacted Features

Cross-domain

Cross-domain feature enables for a same user to share the same user ID across multiple domains. Therefore the user consent can be kept and used in multiple websites (same browser).

👉 The MUVs are calculated by domain, therefore the user with a same ID on multiple domains will still be counted once by domain.

Cross-device MUV

Cross-device MUVs are calculated in the same way as standard MUVs.

👉 They allow to have an estimation on several different devices, for the same user_organization_id.

Cross-device MUV are provided in three groups: 

  • Opt-in MUV
  • Opt-out MUV
  • No Choice MUV

Webviews

Webviews are used in the context of a hybrid app. A hybrid app is an application with two distinct environments: a native environment and a web environment. Webviews transfer the consent from the native environment to the web environment. Despite the two different environments, the consent is only asked once to the user.

👉 In this context, the user has an app env. ID and a web env. ID. As a consequence, the user  will be counted twice.

setUserStatus (“external” consents)

For all custom user consent collection, not done through the notice itself and using the SDK’s function setUserStatus, we collect a different type of consent, labeled “external”.

👉 Triggering external consents (or not) does not impact the volume of MUV because the MUV metric is calculated with the pageview/app sessions events (triggered when the SDK loads, not when the notice load or is displayed).

Enabling Collection of Consent for Different Pages

Customizing the consent collection by changing the names of Didomi’s cookies with the web SDK will have an impact on the counting of the unique visitors. For a same domain, a user who visits pages or subdomains where different cookie names have been set, will be counted multiple times.

Notice Geographic Behavior

The option Only Apply GDPR to EU Visitors can be selected. This option enables to not display a banner for the visitors that are located outside of EU.

Even if this option is selected the SDK is still called on all the pageviews, whatever is the user’s country. Didomi's CMP is communicating with the vendors to specify that the GDPR regulation is not applied.

GDPR

Therefore, Didomi still collects pageviews/app sessions events and none-EU visitors are integrated into your MUVs.

👉If you don’t want to be billed for users outside of the EU, you have to condition the triggering of the CMP SDK.

Possible discrepancies

Please note that they are potential gaps and differences between your MUV and Didomi's MUV:

  • Difference of scope: The scope of domains/apps covered by your analytics tool and the CMP might differ.
  • MUV calculus: If your analytics tool is logged-in users or different ways to count users (e.g. cross-domain), the comparison won’t be relevant.
  • Positive Consent Visitors vs All Visitors: In most cases, your analytics tool is triggered when a visitor gives consent. Didomi also provides this follow-up, but it may vary from one domain to another.
  • Sampling impact: The calculation of the MUV remains an estimation. The exact number of MUV's may vary by + or - 10%