Macro and Consent Passthrough
Standard macros for click, impression, viewability, placement ID, and consent strings (GDPR, US privacy, GPP) so offsite tags respect the destination's consent state.
Macros carry the buyer's tracking values and the viewer's consent strings into each offsite tag. Genuin reads the consent state at the destination and personalizes only where consent allows. The device ID passes only when consent allows it.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. It's part of Offsite, and Privacy and VPPA: the two-channel data flow explains how Genuin keeps viewing and identity apart.
When to use it
Use it on every offsite tag, whatever its format or content source. That covers the VAST Video Tag, the JavaScript Display Tag, the Dynamic Feed Tag, and the Audience Extension Tag.
How it works
- You add macros when you create the tag, and Brand Control Center validates the destination's macro syntax.
- Click, impression, viewability, and placement ID macros let the buyer track the tag in its own tools.
- Consent macros carry the destination's GDPR, US privacy, and GPP strings into the tag.
- Without consent, the tag renders without personalization.
- Genuin keeps what a viewer watched in one channel and who the viewer is in another. It joins them only under your agreement and the viewer's consent.
- Consent is honored per viewer and per purpose, including in your audience segments.
- Conversions can report back to the buyer through macros, as Offsite Attribution Postbacks describes.
Set it up
Octo proposes the macros with these steps already done. You review the result and confirm it.
- Add macros when you create the tag under Offsite > Tags. Brand Control Center validates the destination's macro syntax. The Ad tag reference: VAST, IAB sizes, and macros lists every macro.
- Map the consent macros. Without consent, the tag renders without personalization. Privacy and VPPA explains what consent unlocks.
Settings
| Macro | What it carries |
|---|---|
| Click | The buyer's click tracker |
| Cache buster | A random number |
| GDPR, GDPR consent, US privacy, and GPP | Consent strings |
| Placement ID | The buyer's placement identifier |
| Device ID | Passed only when consent allows |
The ad tag reference gives the exact syntax for each macro. You set the consent source and its default per property: auto, granted, or denied.
What it reports
Reports > Offsite shows these for each destination. Unified identity: auto login, SSO, and the ID graph explains the consent sources Genuin reads, such as a CMP string or your own consent flag.
- Consent state distribution: how impressions at each destination split across consent states.
- Impressions without personalization: impressions served without personalization because consent wasn't given.
Build on it
The macros are set on the tag in Brand Control Center and need no code. In your own apps and pages, these live pages cover consent and events today.
- Serve your first ad covers the declarations personalized ads need: the advertising ID permission on Android and tracking authorization on iOS.
- Integrate the Genuin iOS SDK covers embeds, placements, single sign-on, deep links, and push notifications in an iOS app.
- Embed the Genuin Web SDK on your website covers loading the script, sign-in, page context, and events.
- Receive engagement events in your own analytics sends what viewers do in Genuin views to your analytics tool and warehouse.
The tag and consent calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
