DoubleVerify (incl. Meetrics)
How to configure DoubleVerify (incl. Meetrics) at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics
Overview
This guide explains how DoubleVerify ad verification is used on websites and how to reflect it in the Consenter Manager. It also covers the index entry "Meetrics", which DoubleVerify acquired in 2021.
- Configure the third-party service.
- Map the configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configuration is a comparative example, not a guarantee of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. DoubleVerify (DV) verification tags that measure ad impressions (viewability, brand safety, invalid traffic) on a website, either deployed by the publisher or delivered with ads. DoubleVerify, Inc. is a US company.
What the service does in this scope. DV states that its technology "does not leverage cookies and does not create profiles or audiences" and measures each ad impression individually without tracking user activity over time. Under DV's data privacy addendum, DV processes personal data as processor for the client, while the fraud-elimination part of the solutions is operated by DV as controller; DV's processing is limited to pseudonymous information.
Simplified format. DV offers no privacy settings for the website operator. The guide uses a single fixed-behaviour configuration.
Consent. Verification tags run in the visitor's browser alongside ads. Load publisher-side DV tags together with the advertising they measure, i.e. after advertising consent.
Step 1 — Configure DoubleVerify
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Support marketing analytics (ad measurement and verification) |
| Cookies / profiles | None, per DV |
| Roles | Processor; Controller for fraud elimination |
| Loading | With advertising, after consent |
| DPA | DV Data Privacy Addendum |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Support marketing analytics | Ad verification. |
| Tracking method | No tracking | No cookies, no tracking over time. |
| Identifier | IP address | Pseudonymous information for invalid-traffic detection. |
| Data categories | IP address, Device characteristics, Browsing and interaction data | Impression context and device signals. |
| Legal role of data recipient | Processor; Individual Controller for fraud elimination | Consider a second entry. |
| Personalisation model | No personalisation | No profiles or audiences. |
| Maximum storage duration | Not documented | — |
| Processing location | United States | DoubleVerify, Inc. is subject to the US CLOUD Act. |
Privacy-policy follow-up
- DoubleVerify as processor and, for fraud detection, controller; ad verification; US transfer and potential access by US authorities.
Verification checklist
- DV tags load only with consented advertising.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on