If view-through conversions in a Demand Gen campaign move while spend, clicks, and downstream sales or leads look ordinary, do not assume the campaign suddenly became more or less effective. The reporting method itself may have changed underneath your benchmark.
Google has lowered the threshold that a Display ad within Demand Gen must meet before a later conversion can receive view-through credit. That distinction matters whenever you evaluate creative, calculate performance, move budget, or report results across the transition.
Key takeaways
- The change is limited to Display ads within Demand Gen campaigns. It is not a blanket redefinition of every Demand Gen ad view.
- The qualifying event is moving from an Active View-based view to a rendered ad impression.
- Under the new definition, an impression can qualify when at least one pixel of the ad appears onscreen, even momentarily.
- The conversion event is not being redefined. Google is changing which preceding ad views can receive credit for it.
- A rise in view-through conversions may reflect broader attribution eligibility rather than stronger advertising performance.
- Keep pre-change and post-change benchmarks separate, and require corroborating evidence before changing budgets or performance targets.
The attribution gate changed, not the conversion event
A view-through conversion, or VTC, connects a conversion to an eligible ad impression rather than to a click on that ad. Two events therefore matter: a person converts, and an earlier impression qualifies to receive view-through credit.
Google is changing the second event for Display ads inside Demand Gen. The old method used Active View and its viewability standards to decide whether an impression was sufficiently viewable. The new method uses a rendered ad impression, which has a lower qualification threshold.
| Measurement question | Active View method | Rendered-impression method |
|---|---|---|
| What qualifies the preceding ad exposure? | An impression that satisfies Active View viewability criteria | An impression with at least one pixel onscreen for any amount of time |
| How demanding is the qualification gate? | Higher | Lower |
| What happens to the conversion event itself? | No change from this update | No change from this update |
| Which campaign inventory is covered? | Display ads within Demand Gen campaigns | |
Do not fill in the missing Active View criteria from memory or apply a familiar viewability threshold from another report. You do not need a percentage or duration to interpret this update correctly. The decision-relevant fact is that one onscreen pixel, however briefly displayed, can now make the impression eligible under the rendered-impression definition.
Google’s stated reason is measurement consistency across Demand Gen inventory. That may make reporting conventions more uniform inside the campaign type, but consistency across inventory does not create continuity across time. A VTC reported under the old rule is not methodologically identical to one reported under the new rule.
The announced transition is automatic for eligible campaigns, with no campaign-setting change required from advertisers. Your immediate job is therefore to protect reporting continuity, not to reconfigure campaign delivery.
Why the same campaign can report more view-through conversions
Think of VTC attribution as a gate. Under the earlier method, an impression had to pass Active View’s viewability test before it could participate in view-through attribution. Under the new method, merely rendering one pixel onscreen can open that gate.
Lowering the gate can enlarge the pool of impressions eligible to receive credit. If people in that larger pool later convert, more conversions may be classified as view-through conversions even when the campaign did not generate additional purchases, form submissions, or other underlying conversion events.
This does not mean every affected campaign will report an increase. Delivery, audience mix, spend, conversion lag, and actual customer behavior can all move at the same time. The update supplies a plausible measurement explanation for a change in VTCs; it does not predict the size or direction of every account’s result.
The more important distinction is between attribution and incrementality. A VTC tells you that the platform connected an eligible impression with a later conversion under its rules. It does not, by itself, prove that the impression caused a conversion that would otherwise never have happened. A broader eligibility rule makes that distinction more important, not less.
The definition can also change calculated KPIs. If an internal cost-per-acquisition calculation divides spend by a platform-attributed conversion count, additional VTC credit can make CPA appear lower. If a return calculation includes value assigned to those VTCs, reported return can rise. The arithmetic may be correct while the apparent improvement is methodological rather than commercial.
Use corroborating signals before changing budget

Do not judge the transition from the VTC column alone. Compare that movement with signals that do not depend on the revised view definition: clicks, conversion paths involving clicks where separately available, qualified leads, completed orders, revenue, and other outcomes recorded in your own business systems.
| Pattern you observe | What it can mean | What to do next |
|---|---|---|
| VTCs rise while clicks and independently recorded outcomes stay flat | The broader view definition is a strong candidate for at least part of the increase. | Do not increase budget from the VTC movement alone. Annotate the methodology break and inspect the affected Display inventory. |
| VTCs, click-associated results, and independently recorded outcomes all improve | There may be a real performance gain, although the definition change can still contribute to the VTC increase. | Base the decision on the corroborating outcomes and a post-change benchmark, not on the full VTC difference. |
| VTCs stay broadly stable | The practical effect may be small for this campaign or masked by other changes. | Keep the reporting annotation. Stability does not make the pre-change and post-change methods identical. |
| VTCs decline | The lower eligibility threshold does not explain the decline by itself. | Investigate delivery, spend, audience mix, conversion lag, tracking, and business outcomes before assigning a cause. |
This check is especially important for automated spreadsheets, dashboards, scorecards, and budget rules that consume an attributed conversion total. A methodology-driven increase can silently trigger a recommendation to scale, make a target appear easier to reach, or make a post-change creative look stronger than a pre-change control.
Pause those conclusions, not necessarily the campaign. The campaign may be performing well; the point is that this particular before-and-after comparison can no longer establish why.
Build a clean reporting bridge across the rollout

You cannot recover comparability by pretending the definition stayed constant. You can preserve decision quality by treating the rollout as a measurement break and documenting it explicitly.
- Identify the affected slice. List the Demand Gen campaigns containing Display ads. Do not apply the same warning indiscriminately to unrelated campaign types or to every format inside Demand Gen.
- Preserve the old baseline. Save the last available pre-change reports with spend, impressions, clicks, VTCs, attributed conversion value where used, and independently observed leads or sales. Keep the raw export rather than only a chart or percentage change.
- Mark the methodology break. Add the change to dashboards, recurring reports, experiment logs, and client or leadership notes. If you do not have a confirmed account-level cutover date, label it as an estimated transition period instead of inventing a precise date.
- Separate the reporting eras. Calculate post-change VTC rates, CPA, return, and targets from post-change data. Retain the earlier benchmark for historical context, but do not blend the two periods into one continuous trend line without a visible warning.
- Keep the comparison conditions honest. When reviewing periods on either side of the change, account for spend, delivery, audience mix, campaign edits, conversion lag, and changes in the underlying business. The definition shift is one variable, not permission to ignore the others.
- Require an independent decision signal. Before increasing budget or declaring a winning creative, look for support from clicks, qualified leads, orders, revenue, or an appropriately designed experiment. The corroborating metric should not rely on the newly broadened view threshold.
Suggested reporting note: View-through attribution eligibility for Display ads in Demand Gen changed from an Active View-based definition to a rendered-impression definition. Post-change VTC results are not directly comparable with the earlier baseline.
Avoid creating a blanket adjustment factor to make old and new VTC totals look comparable. No universal uplift amount is provided, and the effect can vary with each campaign’s delivery and conversion behavior. Multiplying historical results by an assumed correction would replace a known methodology break with an invented one.
The rollout was described as automatic over a period of weeks, so do not assume every account changed on the same day. For agencies or teams combining several accounts, keep the transition status at the account or campaign level until you can justify a shared post-change baseline.
Make the next performance decision on the new baseline
The safest immediate move is simple: add the methodology note to your recurring Demand Gen report, split the VTC trend at the transition, and check every budget recommendation against at least one outcome that does not depend on view-through eligibility.
Once you have enough post-change data for your normal buying and conversion cycle, set fresh benchmarks under the rendered-impression definition. You can still use VTCs as an attribution signal. Just stop asking the old baseline to answer a question measured under a new rule.
References


Leave a Reply