Google Ads
Your Sale Changes Conversion Rate for Three Days. Demand Gen Still Needs the Right Channel Scope.

Updated: November 12, 2026
Google Ads API v26.2 expands beta support for BiddingSeasonalityAdjustment to Demand Gen campaigns. The control is appropriate when a short event is expected to change conversion rate, not when tracking is broken or demand merely increases. Write the expected dates, affected campaigns and conversion-rate shift before creating the adjustment. If the team cannot state the expected rate change, the intervention is not ready.
The control is for expected rate changes
Google Ads API v26.2 expands beta support for BiddingSeasonalityAdjustment to Demand Gen campaigns. The control is appropriate when a short event is expected to change conversion rate, not when tracking is broken or demand merely increases.
Write the expected dates, affected campaigns and conversion-rate shift before creating the adjustment. If the team cannot state the expected rate change, the intervention is not ready.
Inventory coverage is not uniform
Google says Demand Gen seasonality adjustments apply to YouTube, Display, Gmail and Maps inventory, but have no effect on Discover. A campaign-level adjustment therefore does not imply uniform behavior across every surface.
Document the Discover exception in the launch brief and reporting annotation. Do not interpret blended results as if all inventory received the same bidding signal.
Operating control table
| Control | Evidence | Failure prevented |
|---|---|---|
| Owner | Named reviewer and decision | Unclaimed change |
| Configuration | Saved source state | Cannot reproduce |
| Validation | End-to-end fixture | Partial success accepted |
| Threshold | Success and rollback rule | Result reinterpreted |
| Evidence | Public or reporting read-back | Configured mistaken for delivered |
Keep the window narrow
Use the shortest date and time range that matches the event, and avoid stacking overlapping adjustments without a clear precedence rule. Long windows can teach bidding systems to expect a temporary condition as normal.
Record the baseline conversion rate, expected uplift and rollback threshold. Review the setting before the event begins and again after it expires.
Test the request and the business meaning
Validate campaign resource names, channel scope, timestamps and account permissions in a nonproduction fixture. Then inspect the saved resource rather than trusting only the mutation response.
Keep creative, audience and budget changes stable during the test so the seasonality effect remains interpretable.
Reconcile by inventory after the event
Compare delivery, conversions, conversion rate and value by the inventory dimensions available to the team. Separate Discover where possible and retain the limitation where it is not possible.
Do not call the adjustment successful from aggregate CPA alone. Confirm that the expected short-term pattern appeared without degrading the post-event baseline.
Connect the control to the wider system
Use this process alongside the seasonality-versus-data-exclusion decision guide. The platform setting, creative promise, measurement rule and downstream experience should describe the same decision.
Pre-launch checklist
- Write the decision and owner in plain language.
- Capture the source configuration and evidence.
- Test one realistic customer or reporting path end to end.
- Verify mobile presentation, links and accessibility.
- Record the success threshold and rollback trigger.
- Schedule the next review before material spend accumulates.
Run a cross-functional release review
Ask the channel owner, creative lead, analyst and conversion owner to inspect the same case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation.
Repeat the test on mobile and with one adverse condition. Resolve differences in the campaign brief and measurement plan before launch.
Set the review cadence before launch
Assign a monitoring owner, review frequency and evidence threshold before the change is released. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.
At the first review, reconcile the source platform, public experience and one downstream business system. Close the change only when all three support the same conclusion, and record any limitation that future analysts must preserve.
Frequently asked questions
Should this be automated?
Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.
What evidence should be preserved?
Keep the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.
When should the team roll back?
Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.
