Skip to content
All field notes
Publisher measurement
Published
Oct 31, 2026
Reading time
10 min read

GAM Ad Refresh: Audit Declarations Against Runtime

Audit GAM refresh declarations against real slot behavior. Check targeted inventory, trigger types, timer intervals and request cycles before changing rates.

AP
AdProof Research
Independent measurement desk
A refresh declaration folder and a separate runtime ad-slot sequence meet under a magnifying glass to compare trigger and timing evidence.
Declared inventory, trigger type and minimum interval must be checked against the refresh behavior that actually runs. Conceptual illustration.
In this guide (10 sections)

A GAM refresh declaration and a page's refresh code are separate controls. Audit whether the targeted inventory, trigger and minimum interval match what actually runs. Do not assume that saving a declaration implements a timer, that a visible ad proves the declaration is accurate, or that an average loading delay safely extends a shorter interval.

A real ad-operations question about sub-30-second refresh rates asks whether requesting after roughly 25 seconds can compensate for creative loading time. Replies mix opinions, commercial claims and platform behavior. The question is older and archived; its useful unresolved task is how to compare a declared minimum with the fastest actual behavior of the deployed implementation.

Start with current documentation for the demand and environment you use, then capture a small authorized test. This guide is a declaration-and-runtime audit, not a recommendation to increase refresh volume or a substitute for other demand partners' requirements.

Establish which rules govern this inventory#

Google's publisher declaration guidance applies to Open Auctions, Private Auctions, First Look and Open Bidding. It distinguishes user-action, event-driven and time-based triggers. For web inventory, event/time-based refreshes have a 30-second minimum; qualifying user action has no minimum in that table. Mere activity, gameplay clicks and scrolling without substantial new content do not qualify as user-action refreshes. Declarations disclose behavior rather than execute it; wrong or missing declarations can violate Google's policy.

Keep that scope explicit. A declaration does not establish compliance with every advertiser agreement, SSP rule, creative requirement or user-experience obligation. Ask the owners of the actual demand paths which additional requirements apply. Do not import a forum contributor's claimed platform threshold into another system without evidence.

Record the source URL, retrieval date, inventory type and implementation version in the audit. If a provider manages both your tags and declarations, ask for the mapping between them. A statement that refresh is “handled by the wrapper” needs a configured rule and a runtime observation behind it.

For your campaign

Compare the declaration with runtime behavior

A GAM refresh declaration and page code are separate controls. Discuss which inventory, trigger and interval evidence is available.

Discuss delivery measurement

A short inquiry to scope relevant options; no campaign access is needed.

Inventory the slots that really refresh#

Make a list of page templates, slots and environments before reviewing one timer setting. A desktop sidebar, mobile sticky position and dynamically inserted article slot can have different lifecycles even when they share a familiar ad-unit name.

Use a worksheet like this:

Inventory fieldEvidence to capture
Page template and environmentApproved test URL or equivalent fixture, desktop/mobile/app context
Slot identityAd-unit path, element reference and page placement
Refresh ownerPublisher code, wrapper, SDK or another documented component
Trigger sourceTimer, navigation, content event or multiple paths
Effective declarationTargeted inventory, selected trigger and declared minimum
Runtime versionCode/configuration version and effective timestamp
LifecycleInitial load, subsequent cycles, route changes and cleanup

Compare the worksheet to the declaration's actual targeting. Google's guidance warns that buyer restrictions apply to matching requests even when a targeted slot does not refresh. Broad targeting is therefore not a harmless substitute for an inventory map. Include genuinely refreshing placements and identify unintentionally included static inventory.

When an ad-unit path represents several page positions, retain the supported targeting detail that distinguishes them. Do not assume a declaration with the right ad-unit name covers only the position the yield team had in mind.

Identify the event that causes replacement#

Observe the trigger rather than choosing the label that offers the most convenient interval. Ask what must actually happen before a new request is allowed. Then compare the documented trigger category with that event.

For a content-driven integration, retain the content transition reference and whether it represents a meaningful change for the user. For a timer, retain its start point, condition checks and reset behavior. For a mixed implementation, inspect each route separately. A page can have several ways to refresh a slot; validating one does not validate the others.

Runtime observationInvestigation question
A countdown expires while the page is unchangedWhich declaration describes this scheduled path?
A new article or result set appearsWhat content transition caused the ad request?
Pointer movement repeatedly resets a timerIs activity merely gating a timed refresh?
A route change recreates the slotIs this a new lifecycle or another cycle of the same placement?
A wrapper and publisher timer both runWhich component is authorized to request replacement?

These are diagnostic questions, not universal classifications of every implementation. Preserve enough evidence for the platform and inventory owners to apply the current contract. A variable named userActive or contentChanged does not establish what the page actually did.

Record the relevant clocks without treating them as equivalent#

A refresh audit needs more than the scheduled interval. Capture the previous creative's insertion, trigger eligibility, refresh call, outgoing request, response and next creative insertion. Also record page visibility and supported slot-visibility observations where available. Each timestamp answers a different question.

The GPT reference describes slot events and their boundaries. A render-ended event indicates creative code injection, not a completed resource load or a human exposure. Use the supported later observations separately; do not rename every event “impression” in the worksheet.

A useful per-cycle record contains:

Page session reference and slot reference:
Cycle reference and runtime version:
Previous creative insertion:
Trigger became eligible:
Refresh call and explicit slot set:
Outgoing request / response:
Next creative insertion / later supported load evidence:
Declared trigger and minimum interval:
Page/slot state and unavailable observations:

Use a consistent monotonic clock for within-page intervals, with a corresponding wall-clock reference for joining external evidence. A browser trace and a server export can use different timebases; state how they were aligned. If a timestamp is unavailable, keep it unknown rather than filling it with the request time.

This is an observation plan. Do not generate large quantities of commercial traffic to test it, and do not click live ads. Use an approved QA setup or bounded observation of ordinary serving, with test traffic handled according to the integration's supported process.

A hypothetical short-timer failure#

Hypothetical example. Assume a particular web placement declares a time-based minimum of 30 seconds. The implementation arms a 25-second timer after the previous creative is inserted. The following invented trace is from an illustrative fast response, not a customer account:

EventTime from the first request
Initial ad request0 seconds
First creative inserted2 seconds
Timer expires and replacement request is sent27 seconds
Replacement creative inserted28 seconds

The first request-to-replacement-request gap is 27 seconds. The interval between creative insertions is 28 - 2 = 26 seconds. Neither becomes 30 seconds because another connection might respond more slowly. Adding an assumed five-second load delay to a 25-second timer does not constrain the fastest observed replacement.

The corrective investigation is to identify the clock and gate that must meet the intended minimum, then verify the implementation against it with its owner. Do not copy this example into production as a timing recipe, or decide that a single slow test proves the minimum is respected.

Test a second, separate risk: two active timers. If a route re-entry leaves an earlier timer alive, each timer can appear correctly configured while their combined calls are too close together. Group observations by slot and lifecycle; inspect the interval between consecutive actual calls, not only the delay programmed into each timer independently.

For a minimum-based requirement, an average is insufficient. Preserve the shortest relevant observed interval, the conditions that produced it and the sample's coverage. A small test can demonstrate a specific violation of the intended behavior; it cannot prove every production session is correct.

Verify the refresh call and lifecycle#

Google's ad-loading and refresh guide distinguishes slot registration from initial loading. A later refresh() can perform the first fetch, so do not classify every call to that method as replacement of an existing creative. Calls without a slot array affect all registered slots; explicit arrays limit the selected slots. The guide also advises against excessive refreshes and unnecessary clear() calls.

Record whether the cycle is first load or replacement and which slots the call actually includes. An unrelated placement's event should not reset the timer for every slot. On route or component teardown, confirm that the implementation's own observers and scheduled work are cleaned up through its supported lifecycle.

If the page uses Prebid, keep the auction and targeting evidence for the same cycle. The Prebid/GPT lazy-loading audit covers auction, targeting and request timing. It does not replace the separate declaration check, and a new auction does not automatically make a refresh policy correct.

SRA and roadblocking also affect the page-level delivery contract. Google's ad-slot best practices explains their relationship. Do not remove grouping or broadly refresh every slot solely to make one timer easier to reason about.

Separate declarations from performance conclusions#

After the behavior matches the intended declaration, evaluate delivery and user experience with comparable populations. Track requests, counted impressions, measured/viewable populations where supported, and the explicitly defined revenue measure. More requests do not by themselves establish more useful exposures or better monetization.

Use the viewability discrepancy guide when systems disagree about measurability or viewability. A thirty-second timing check does not certify viewability or invalid-traffic quality. Use the publisher revenue diagnostic to distinguish request volume, delivery and price changes.

Do not label the reduction after a timing change as recovered waste or a fraud repair without the provider's actual finding. Equally, do not interpret a falling count as proof that a correct declaration harmed the business: traffic mix, report maturity and the counting definition still matter.

Close the audit with a reviewable finding#

Retain the declaration before and after the change, targeted inventory list, runtime version, trigger evidence, per-slot trace and unresolved cases. Give each proposed change an owner, expected observation, approved test scope and rollback condition.

Useful findings are specific: an unchanged page followed a timed path while its declaration described another trigger; a static slot was included in broad targeting; or two lifecycle timers produced overlapping calls. “Refresh is broken” is too broad to verify.

Recheck the smallest affected scope after correction, then assess broader production coverage through supported aggregates and operational evidence. Save exceptions rather than silently excluding hard-to-test templates. If an integration exposes too little detail, record that limitation and request a supported trace from its owner.

Frequently asked questions#

Does saving a publisher declaration start refreshes?

No. The declaration describes the inventory's behavior to buyers. Runtime implementation is separate, and both need to agree.

Can a 25-second timer be treated as 30 seconds because ads load slowly?

Do not assume that. Faster responses can shorten the replacement interval. Measure actual calls and creative boundaries for the affected slot against the applicable requirement.

Does an active or scrolling user make every refresh user-action based?

No. The actual content/navigation behavior must meet the applicable trigger definition. Activity checks or a variable name do not change the underlying trigger.

Does a correct declaration prove viewability or revenue improvement?

No. Declaration accuracy, measured exposure and commercial performance are different checks. Use defined populations and evidence for each.

Bring the measured delivery scope to the review#

The anonymized fashion retail display case shows why a documented delivery baseline matters before interpreting performance. It does not validate a refresh implementation or prove that a particular rate improved results.

Where a campaign is measured by AdProof, compare its available event or aggregate export with publisher delivery records over the same dates, timezone and supported filters. Keep that measured delivery comparison separate from the declaration and runtime trace. Discuss the AdProof comparison workflow with those artifacts; it does not automatically inspect every publisher timer or configure GAM declarations.

Your next step

Compare the declaration with runtime behavior

A GAM refresh declaration and page code are separate controls. Discuss which inventory, trigger and interval evidence is available.

Discuss delivery measurement

A short inquiry to scope relevant options; no campaign access is needed.

Back to all field notes