A network operator managing 12 publisher properties through one GAM instance rolls out the Pub Clarity instream player as a Sponsorship-priority custom creative across all properties in four working days. The case study documents the line-item template, per-property targeting, rollback path tested during deployment, and reconciliation cadence used to verify per-property revenue against GAM Query Tool.
The network operates twelve publisher properties across three verticals (regional news, lifestyle, and sports) serving readers across India and Singapore. All twelve sites are trafficked through one GAM 360 instance. The network's ad operations team is four people. Monthly combined network pageviews are approximately 47 million.
The constraint that shaped the rollout approach: the network team could not afford a multi-week deployment. Any rollout that required per-site manual configuration would compete with the team's existing operational workload. The proposal was for a deployment that could complete in less than a working week and that would not require touching individual publisher sites.
GAM Creative delivery was the right fit for these constraints. The Pub Clarity player ships as a third-party custom creative attached to a Sponsorship-priority line item targeting each property's existing ad units. No code change to publisher sites; the existing GPT tag continues to call the existing ad units, and GAM serves the Pub Clarity creative through the new line item.
The first day was spent constructing a line-item template that could be replicated across the network with per-property targeting overrides. The template specified: Sponsorship priority, 100% delivery goal, Pub Clarity custom creative as the only creative on the line item, and a key-value targeting profile that could be parameterized per property.
Per-property targeting was parameterized on three axes: GAM ad unit (each property has its own ad unit hierarchy), property key-value (a unique siteKey per property in the network's targeting structure), and Pub Clarity siteKey (the unique identifier in the Pub Clarity dashboard that maps the creative to the property's configuration).
The template was reviewed against GAM 360's line-item validation rules and against the network's internal ad-server quality standards. One minor adjustment was made: the dayparting field was left empty (rather than 24/7) to inherit the network's default dayparting rules; the original template had specified 24/7 explicitly, which would have overridden the network's nightly maintenance windows.
Days 2 and 3 deployed the line items across the twelve properties at a cadence of three properties per half-day. The deployment process per property: clone the template line item, apply per-property targeting overrides, set the Pub Clarity siteKey in the creative tag, activate the line item, wait for the next GAM creative cache refresh (typically 30 minutes), verify first impression on a test page.
Per-property validation captured five data points before moving to the next property: first impression timestamp (verifying delivery), reconciliation hash (verifying the creative loaded the correct configuration), GAM Query Tool revenue (verifying GAM-side reporting), Pub Clarity dashboard revenue (verifying Pub Clarity-side reporting), and the discrepancy percentage between the two (expected within 1–2%).
Two properties hit minor configuration issues during deployment. Property #4 had a legacy ad unit name that did not match the targeting expression and required manual targeting adjustment. Property #9 had a creative-cache TTL configured at 4 hours rather than the network default 30 minutes, which delayed the first-impression verification by 3.5 hours. Both issues were resolved in-day; neither required rolling back any deployed properties.
Day 4 ran full-network reconciliation across all twelve properties. Each property's GAM Query Tool revenue was compared against its Pub Clarity dashboard revenue for the prior 24 hours. Eleven properties showed discrepancies under 1%. One property (the property with the previously-noted 4-hour creative-cache TTL) showed a 4% discrepancy that resolved by the second day reconciliation cycle once the cache TTL was adjusted to match the network default.
The same day, the rollback path was tested on one property. The Sponsorship line item was paused, causing GAM to fall back to the standard auction stack (header bidding + AdSense backfill) for the targeted ad units. The fallback served within 30 minutes (matching the GAM creative-cache refresh cycle), with no measurable revenue loss during the test window. The line item was re-activated and the property returned to the Pub Clarity creative delivery.
The rollback test was performed against the network's contractual requirement to maintain a documented rollback path for any third-party creative deployment. The test result was documented in the network's ad-operations runbook and shared with the network's ad-operations team for future reference.
The network has been operating with full GAM Creative delivery across all twelve properties since the four-day rollout completed. Monthly reconciliation across the network has held within 1.2% discrepancy between GAM Query Tool and Pub Clarity dashboard reporting; the discrepancy is consistent with the publisher cohort baseline for GAM Creative delivery.
Network-wide instream video yield has lifted approximately 18% over the network's previous video monetization, with property-by-property variance between 11% and 28%. The publisher properties that lifted most are the sports and lifestyle properties where reader dwell-time on video content is highest; the news properties (where video clips are shorter and reader behavior is more bounce-prone) lifted least.
The network has indicated interest in extending the GAM Creative deployment to a Pub Clarity Native delivery in the same model. We will publish that case study when the deployment completes.
Apply as a Pub Clarity publisher. After 90 days we offer to write up your monetization journey — anonymised or attributed, your call.
Apply as a publisher →