Monthly unique visitors (MUVs) is an estimate of the total number of distinct users who visit your organization's website and/or application within a given month. In this article, we will cover:
- MUVs sampling rate
- MUVs calculation
- MUVS calculation by features
- MUVs discrepencies
MUVs does not equate to total number of consent decisions made by end-users. MUVs covers all traffic to your website and/or application regardless of whether the end-user provided a consent decision during the period.
MUVs sampling rate
Sampling refers to the collection of events from random end-users and then extrapolating the analytics data in your organization's CMP dashboards. The Didomi sampling strategy ensures that the sample is representative of the entire end-use base by selecting purely random end-users and logging all events for those end-users (which ensures that we capture the full behavior of those end-users).
The MUV sampling rate is as follows:
| Platform | Sampling rate |
| Web |
3% of end-users |
| Mobile |
10% of end-users |
| CTV |
10% of end-users |
MUVs calculation
MUVs is determined by counting unique end-user IDs recorded during pageviews or app sessions and then extrapolating the total visitor count based on a predefined sampling rate.
Didomi SDKs is called every time a page is loaded or an app is initialized (this is how Didomi generates the pageview and app session metrics, respectively). Upon loading, the Didomi SDK will perform verification for all visitors to check if user is known, their consent status, and if the consent notice needs to be displayed (or displayed again). Regardless of how many times a known end-user loads a webpage or application their unique identifier (uuid) will always be the same and be counted as a single unique user in the MUVs.
- Didomi SDK is called on each webpage/app load
- Collects pageview/app session events
- Checks if the end-user is known and whether they have given consent or not
- Checks if consent needs to be requested again based on the consent notice's update or settings
- If required, the notice is displayed
- Collects consent asked event
- Collects the end-user consent
- Transfers the end-user consent information to the vendor integrations or the tag management system (TMS)
MUVS calculation by features
Since Didomi provides a variety of tools and methods to collect and share consents across properties your organization owns, the way MUVs is calculated for certain end-user behavior can also vary slightly. In this section, we will cover the impact (if any) on MUVs calculations for some popular features:
- Cross-domain
- Cross-device
- Webview
setUserStatus("external" consents)- Collection of consent on different pages
- Country/Region configured for regulation
Cross-domain
The cross-domain feature enables an end-user to share the same user ID across multiple domains and therefore end-user consent choice can be kept and used on multiple websites (same browser).
The MUVs are calculated by domain, therefore the end-user with the same ID on multiple domains will still be counted once by domain.
Cross-device
Cross-device MUVs are calculated in the same way as standard MUVs and leverages the user_organization_id across multiple devices tie an end-user to a single person.
Cross-device MUVs are provided in three groups:
-
Opt-in MUV
-
Opt-out MUV
-
No Choice MUV
Webview
In this context, the end-user has an app env. ID and a web env. ID and as a result will be counted twice.
setUserStatus ("external" consents)
For all custom end-user consent collection not done through the notice itself but via the SDK’s setUserStatus function, Didomi collects a different type of consent, labeled “external”.
Triggering external consents choices 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 loaded or is displayed).
Collection of consent on different pages
Customizing the consent collection by changing the names of Didomi cookies with the web SDK will have an impact on the counting of the unique visitors. For the same domain, an end-user who visits pages or subdomains where different cookie names have been set, will be counted multiple times.
Country/Region configured for regulation
When your organization configures its consent notice you will need to set the countries/regions for which the regulation applies.
However, since the Didomi SDK is initialized globally for every pageview and app session, including regions where your regulation does apply, this means that all visitors are included in the your MUVs.
To avoid being billed for end-users outside regions with applicable regulations, you should condition the call to our initialization tag so that the Didomi SDK is not initialized if no regulation applies.
MUVs discrepencies
It can be the case the the MUVs generated by Didomi does not match the MUVs generated by your organization. The reason for this can be due to:
| Reason | Description |
| Scope difference |
The scope of domains/apps covered by your analytics tool and the CMP might differ. |
| MUVs calculation |
Your analytics tool calculates logged-in users or when consent is shared across domains differently than Didomi |
|
Opt-in visitors vs All visitors |
In most cases, your analytics tool is triggered when an end-user gives consent instead of when the webpage or app is loaded |
|
Sampling |
The calculation of the MUVs is an estimation. The exact number of MUVs may vary by +/- 10%. |