Google App campaigns gain ad-group scope for seasonality adjustments

What changed

The control changes the conversion-rate expectation used by bidding during a defined period. It does not change the campaign budget. Google’s interface distinguishes campaign type, specific campaigns and specific ad groups, with the last option labelled for App campaigns only.

The practical difference is scope. An advertiser expecting a short-lived conversion-rate change in a particular part of an App campaign can assess whether an ad-group adjustment better represents that event than a campaign-wide assumption. The screenshot does not establish universal account availability, and the documentation does not supply a verified introduction date.

What to review

Separate a forecast of conversion rate from a forecast of traffic or spending. A promotion expected to bring more visits does not automatically justify telling bidding that each visit is more likely to convert. Base any adjustment on a specific event and a defensible estimate, then record which ad groups it covers and when it ends.

Check the conversion action and reporting delay before evaluating the result. A short window with incomplete conversions can make an adjustment look more or less effective than it was. Keep a record of the previous setup and the assumptions behind the estimate so later comparisons remain interpretable.

This report is distinct from the earlier Demand Gen seasonality guidance: it concerns the App campaign scope selector. The image is Thomas’s original screenshot, cropped to remove the promotional footer while preserving the interface and embedded credit.

Date note: 27 October 2026 is the coverage date. The precise documentation revision, first introduction and wider rollout schedule remain unconfirmed.