Governance
One consent decision, enforced where data leaves for a network.
Two systems with their own idea of consent eventually disagree, and the disagreement surfaces in an audit rather than a dashboard. Realvertising runs no second policy engine. Your consent platform holds the configured state per region and purpose; this connection reads it and decides, per outcome, whether an identifier may be matched to a network, hashed first, or not used at all. A withdrawal is propagated to every network that received that identifier, and the propagation is tracked until each one answers.
In short: Your consent platform decides privacy policy and holds the configured state; Realvertising reads that state and enforces it at the point where outcomes and audiences are sent to Google, Meta, TikTok, LinkedIn and Microsoft. Withdrawals propagate outward as deletion and opt-out requests, and every hand-off is logged against the permission it ran under.
What it is
A consent platform collects visitor privacy choices, holds the configured policy per region and purpose, and publishes the resulting state to every system that must honour it. Policy is decided there, by your organisation and its advisers.
What Realvertising receives
- Configured consent and privacy state per site, region and purpose, as your consent platform publishes it.
- Activation permission per identifier: whether it may be matched to an ad network at all, and in what form.
- Regional privacy mode, including restricted modes that permit measurement but not audience matching.
- Withdrawal events as they occur, with the identifiers and purposes each one covers.
What it sends back
- A deletion or opt-out request to every network that received an identifier once a withdrawal arrives, tracked until the network confirms it.
- An enforcement log: which outcomes went where, under which permission and mode, and which were withheld.
- The destination map — every network and audience that depends on a given purpose — so a policy change shows its reach before it is made.
What this lets you ask
Questions this connection makes answerable.
- Which regions are in restricted mode right now, and what can advertising still do in them?
- When this customer withdrew consent, which networks were told, and did they confirm?
- How many of yesterday's outcomes were withheld from a network, and for which purpose?
How it connects
- 1Authorise your consent platform and select the sites and regions whose state Realvertising follows.
- 2Map each consent purpose to an activation mode: full matching, hashed matching only, measurement only, or nothing.
- 3Set the mode for visitors who have not yet chosen, then apply. Enforcement starts at the next hand-off; nothing queued is released under the old state.
Where it stops
- What the law requires in a region is not decided here. Your consent platform holds the policy, and Realvertising enforces the state it publishes faithfully — including a state configured wrongly.
- Restricted modes cost match rates. The drop is reported as a measured percentage instead of the missing conversions being modelled back in.
- Propagation depends on each network's own interface. Realvertising issues the request, records the response, and shows the ones still outstanding.
Integrations
Everything the Growth Brain can read.
One goal. Every channel. Real business truth.
Connect your ad accounts, say what a good customer is worth, and let the Growth Brain work the objective inside limits you set.
No ad spend commitment · Connect one channel to start · [email protected]