Your revenue depends on consent.So does your exposure.
ConsentCenter records what each reader agreed to, per purpose and per vendor, and passes that decision to the partners that need it.
- ePrivacy Directive Article 5(3)
- GDPR Article 4(11)
- GDPR Article 26
You are not running one tracker. You are running someone else’s supply chain.
Each partner brings their own.
A reader clicks accept once, and that single click is asked to justify dozens of vendors doing different things for different reasons. When a regulator asks which vendor relied on which purpose, "they accepted" is not an answer.
Where this goes wrong first.
The vendor list is longer than anyone thinks
Partners bring sub-partners. The list on the banner and the list of scripts actually loading drift apart quietly, and the banner is the one you can prove.
One click, many purposes
Advertising, measurement and personalisation are different purposes with different justifications. Collapsing them into a single accept is convenient right up to the point someone asks you to separate them.
The signal stops at your edge
You captured the choice. Whether every downstream partner received it, and acted on it, is something you currently take on trust.
What you are actually buying.
Record consent per purpose and per vendor, not as one undifferentiated yes.
Keep the disclosed vendor list and the loaded scripts in step.
Pass the reader’s decision to partners in a form they can act on.
How it works
Enumerate
Build the real vendor and purpose list from what loads, not from what was once documented.
Separate
Ask for advertising, measurement and personalisation as the distinct purposes they are.
Transmit
Pass each reader’s decision downstream and keep the record of what was sent.
What the text actually says.
- ePrivacy Directive Article 5(3)
- Storing or accessing information on a reader’s device requires prior consent unless it is strictly necessary for the service they requested.
- GDPR Article 4(11)
- Consent must be freely given, specific, informed and unambiguous — "specific" meaning tied to particular purposes.
- GDPR Article 26
- Where two parties jointly determine the purposes of processing, they must set out their respective responsibilities in an arrangement between them.
Paraphrased for brevity and provided for orientation, not as legal advice. Which obligations apply to your organisation is a question for your own counsel, and ConsentCenter does not determine it for you.
The products that apply
Cookie Consent
Hold advertising and measurement scripts until the purpose they need is granted.
View productUniversal Consent & Preference Management
Keep per-purpose decisions for logged-in and newsletter audiences in one record.
View productData Mapping
Keep track of which vendors receive what, and for which purpose.
View product
Frequently asked questions
ConsentCenter is designed to capture and store the reader’s decision and make it available to the systems that need it. Which partners you pass it to, and how, depends on your stack — that is the part worth walking through on a call rather than guessing at here.
Yes, and you generally should. Consent has to be specific to a purpose, so one combined toggle is the harder position to defend.
They still get the article. What changes is which optional technologies run. Treating refusal as a supported outcome rather than a failure state is the whole point of asking.
Bring us the publishers & media version of this problem.
Show us the consent question you cannot currently answer — the choice that did not propagate, the record you could not reproduce — and we will walk through exactly how ConsentCenter handles it.