Publishers with direct demand
Publishers running direct deals through GAM gain a higher-performing video unit as part of their Sponsorship-priority line items.
For publishers running their own Google Ad Manager, we deliver the Pub Clarity player as a third-party custom creative on a Sponsorship-priority line item targeting your existing ad units. The publisher's ad server stays in full control.
Tag-in-creative is the standard distribution model for player products that integrate with the publisher's ad server. The publisher's GAM serves the Pub Clarity player as a custom creative on a Sponsorship-priority line item — first-look delivery without a separate page tag.
Sponsorship priority guarantees the player serves first when the ad unit is called. Your GAM records the impression alongside Pub Clarity's reconciled numbers — no double-counting.
Tag-in-creative delivery is built for publishers who already run their own Google Ad Manager and want to keep ad-server control. The Pub Clarity player serves as a third-party custom creative through their existing line items.
Publishers running direct deals through GAM gain a higher-performing video unit as part of their Sponsorship-priority line items.
Network operators with multiple sites trafficked through one GAM instance can deploy the player across all properties from a single creative update.
Sites that report up through corporate ad operations teams keep all delivery and reporting inside GAM, with the Pub Clarity dashboard as the parallel reconciliation view.
For publishers running header bidding in GAM alongside direct sales, the player fits as one more line item — no new auction logic, no new tag on the page.
Publishers with their own content libraries and CDN keep video hosting in-house. The player loads, fetches video metadata from the publisher's feed, and runs the auction.
Agency-led monetization teams operating GAM on behalf of multiple publishers traffic the player through standard ad-server workflows.
The publisher's GAM remains the ad server. Pub Clarity registers as a third-party demand source delivered through a custom creative attached to a Sponsorship-priority line item. The line item targets the publisher's existing ad units — typically an in-content video placement.
When the page calls GPT to load that ad unit, GAM's standard auction logic runs. The Sponsorship line item has the highest priority tier and serves first, delivering Pub Clarity's creative tag. The tag loads the player into the GAM-controlled iframe, fetches its configuration from Pub Clarity's backend, and begins ad delivery.
Every impression fires both into GAM's reporting (as a normal Sponsorship line-item impression) and into Pub Clarity's reconciled reporting (via the beacon collector). The publisher sees the same number reflected in both systems, with Pub Clarity's side adding viewability, video event tracking, and demand-partner attribution.
Setup takes roughly fifteen minutes in GAM: create a Sponsorship line item, paste the Pub Clarity creative tag as a third-party creative, target your existing video ad unit, set goal type to Sponsorship 100% delivery, save. The first impression typically renders within a few minutes of GAM's standard creative-cache refresh.
For tag-in-creative delivery, the two systems must agree. Discrepancies above 1–2% indicate a configuration issue we investigate with the publisher.
Benchmark ranges reflect Pub Clarity's South & Southeast Asia publisher cohort. Individual publisher results vary with traffic source, vertical, and demand mix.
GAM publishers have specific questions about how the player integrates with their existing ad server.
No. Tag-in-creative complements header bidding. The Pub Clarity player serves through a Sponsorship line item which sits above standard header-bidding line items in GAM's priority tree. Your header bidding still runs for non-video inventory.
Sponsorship-priority line items deliver against booked goals; if the goal is 100% delivery, the line item serves every available impression on the targeted ad unit. Pub Clarity does not unsold inventory through this path — for that, use the standard SSP integration with our pc.js loader.
Yes. Create two Sponsorship line items targeting the same ad unit — one with our creative, one with your current creative. Use GAM's rotation settings to split traffic. Pub Clarity's reporting will show our half of the data; your existing reporting captures the other half.
The creative reads GAM's consent macros at load time and gates the ad request accordingly. If consent is rejected, no ad request fires and a non-personalized fallback shows. The same TCF v2 logic that runs in our direct SSP path applies here.
The line item, creative, and impression counts appear in GAM Query Tool exactly like any third-party creative. Pub Clarity's reconciliation runs alongside and provides per-event detail (start, quartiles, complete, click) that GAM's default reporting does not surface.
Yes. Duplicate the line item targeting different ad units, or use one line item with multiple targeted ad units. The creative reads which ad unit it served into at runtime and behaves accordingly.
The tag-in-creative delivery path, step by step. This is what happens between a page-side ad call and the Pub Clarity player rendering inside the publisher's GAM-controlled ad slot.
GAM stays the ad server. Trafficking, line item priorities, delivery rules — all controlled in GAM. Pub Clarity is one creative on one line item.
Roughly fifteen minutes in GAM. Sponsorship line item, custom creative paste, target your ad unit, save. First impression on next GAM creative cache cycle.
GAM Query Tool sees the line item as a Sponsorship impression. Pub Clarity dashboard surfaces viewability, video events, and reconciled revenue.