A quick primer
There's a key officially documented property worth establishing up front, since it directly shapes what's even possible to measure. Google explicitly documents that the automatic text updates that happen when a customizer fires don't reset or fragment an ad's performance data — all the stats keep accumulating on the same ad, regardless of which specific dynamic value was shown at any given moment. That's convenient in that reporting doesn't "multiply," but it also means there's no way to see directly, in the interface, how a specific countdown value or price actually affected clicks and conversions — standard reports don't break results down by which version of the dynamic text rendered at the time of a given impression.
The dynamic elements officially available for RSAs include: ad customizers (parameters that automatically change based on a selected attribute — a product, category, or price), the countdown function, keyword insertion, and location insertion; the conditional "IF" function is officially not supported for RSAs. Countdown works on a specific, documented logic: the timer counts down first in days, then hours, then minutes — meaning the ad's text changes in real time as the end date approaches, so a single countdown element can render dozens of different text states over its lifetime, none of which are broken out separately in reporting.
What to check before you touch anything
- Whether you understand that a standard ad-level or asset-level report will only show the aggregate performance of an ad with a customizer/countdown as a whole, not the performance of a specific dynamic value — that's an architectural limitation, not a reporting gap.
- Whether you have a clean "before" and "after" comparison period for adding the dynamic element, with everything else held equal (same targeting, same budget, same semantics) — this is the minimal way to get any read on the effect without a dedicated experiment.
- Whether adding the customizer/countdown coincided with other changes (seasonality, a bid change, shifts in the competitive landscape) — without ruling those out, any observed effect can't be confidently attributed to the dynamic element alone.
- Whether default values are configured for the customizer in case the feed is missing data — without them, some impressions may serve with blank or irrelevant text, skewing the overall performance picture.
- Whether the ad group has enough traffic for a meaningful read on a specific period of the countdown's run (for example, the final hours before expiry versus the first few days) — on a low-frequency group, this kind of within-cycle comparison can be statistically unreliable.
Possible approaches
- For a basic read on the effect — compare the ad group's metrics (CTR, conversions) over a comparable period before and after adding the dynamic element, with everything else stable.
- For a more honest, controlled read — run a Custom experiment where the control version of the campaign uses static text and the test version uses the same text with the customizer/countdown added, splitting traffic and comparing incremental results.
- If specifically testing a countdown — evaluate the effect not just as a single average across the whole run, but separately by phase of the countdown (days/hours/minutes before expiry), since the message — and likely the audience response — shifts as the deadline nears, and an averaged figure hides that dynamic.
- If using ad customizers for product attributes (price, availability) — evaluate the effect not through direct attribute-level reporting (which doesn't exist), but indirectly, by comparing ad groups with the customizer enabled against those without it, on comparable semantics and traffic.
- Don't draw conclusions about a dynamic element's effectiveness from a single cycle (one promotion, one countdown) — repeat the observation across several independent cycles before treating the effect as systematic rather than a coincidence tied to one particular period.