When Google Ads makes automation easier to deploy, your reporting has to get stricter. AI Max can expand targeting and apply brand or location-related controls, while Direct Offers can put a context-selected incentive in front of a shopper inside AI Mode. Those capabilities can help, but they also blend media optimization with commercial policy.
Your job is to answer two separate questions: what was the automation allowed to do, and did it create profitable demand that would not otherwise have existed? A campaign can improve on an in-platform metric while quietly reaching a different audience, relaxing a targeting boundary, or discounting orders you could have won at full price. The control plan below is designed to expose those differences before you scale them.
Start with permission reporting, not performance reporting
Google Ads is adding AI Max reporting columns for Locations of interest, Optimized targeting and Brand inclusions. Add them to the campaign-level view before investigating a performance change. They tell you which controls are present, which is the first layer of any useful audit.
Think of these fields as permission reporting. They describe what a campaign is configured to use; they do not prove that a setting caused an outcome. A conversion increase beside an enabled setting is a lead for investigation, not a causal conclusion.
| Reporting column | What it makes visible | What you should check |
|---|---|---|
| Locations of interest | Which campaigns use location-of-interest settings | Whether campaigns being compared use the same geographic-intent configuration |
| Optimized targeting | Where automated audience expansion is enabled | Whether broader reach is intentional and whether it coincides with a change in traffic quality |
| Brand inclusions | Where brand inclusion settings are applied | Whether each campaign has the brand scope your strategy requires |
The columns are still rolling out and may not be visible in every account. If you cannot find one, do not treat its absence from the interface as evidence that the underlying behavior is disabled. Confirm the campaign settings directly until the reporting fields reach your account.
Once the columns are available, build a repeatable campaign view:
- Add all three AI Max columns to the same view as the outcome metrics your team actually uses.
- Keep campaign identity, status and commercial objective visible so campaigns with different jobs are not compared as if they were interchangeable.
- Save a dated export or configuration record. That gives you a snapshot of the permissions in place when results were measured.
- Flag unexpected combinations, such as an expansion setting enabled on one campaign but not on otherwise comparable campaigns.
- Resolve configuration mistakes before interpreting performance. Analysis built on unintended settings only explains the wrong experiment more precisely.
This view should let you scan from configuration to outcome in one row. If an analyst has to open every campaign individually to discover the relevant settings, setup differences are too easy to miss and too slow to audit.
Compare configuration cohorts before explaining a performance gap

Campaign averages become misleading when they combine different automation permissions. Create configuration cohorts instead. One cohort might contain campaigns with Optimized targeting enabled; another might contain campaigns without it. You can then subdivide them by Locations of interest and Brand inclusions when those distinctions matter to the question.
Do not automatically call one cohort a control group. A credible comparison also needs a similar commercial objective, market, offer, audience opportunity and measurement setup. A branded campaign and a prospecting campaign remain different even if their three AI Max columns match exactly.
Use this sequence when a campaign begins outperforming or underperforming its peers:
- Define the business symptom. State whether the issue is lead quality, sales volume, acquisition cost, conversion value or profit. Avoid the vague diagnosis that performance changed.
- Map the permission state. Record the values of Locations of interest, Optimized targeting and Brand inclusions for the affected campaign and its intended comparators.
- Separate mismatched campaigns. Compare like configurations first. If the difference disappears, the blended average was hiding a setup distinction.
- Check timing. Place the first visible performance change beside the dated configuration record and other campaign changes. A setting that was already stable before the change is a weaker explanation than one altered at the same time.
- Change one decision at a time where practical. If targeting, bidding, creative and promotion all change together, you may improve the result but lose the ability to explain why.
- Write down the interpretation. Record the setting, expected mechanism, primary metric and condition that would disprove your explanation.
The last step is important. A statement such as “Optimized targeting improved the campaign” is too broad to test. A useful interpretation is narrower: enabling expansion was followed by more qualified conversions in comparable campaigns while cost and downstream quality stayed within the team’s accepted limits. That claim can be monitored and challenged.
Also look for configuration drift. Two campaigns that were launched from the same template can stop being comparable after later edits. The new columns make that drift easier to spot, but only if somebody owns the exception review. Assign that check to a named role and run it on the same cadence as your normal campaign review.
Build Direct Offers as governed promotions
Direct Offers add a second kind of automation: Google can decide not only when an offer is relevant, but also which incentive to present. The beta-labeled asset can be created at the account or campaign level, and it is limited to campaigns using AI Max or text customization.
The setup asks for an internal offer name, final URL and short description. Google AI uses the description to judge relevance and can generate the customer-facing offer text. If you provide multiple incentives, the system can select among them using the shopper’s behavior and context. That makes the description and incentive set part of your targeting logic, not just administrative copy.
Start with a campaign-level pilot unless you have a clear reason to expose the offer across the account. A campaign-level asset narrows the commercial blast radius and makes it easier to connect claims and redemptions to a defined test population.
Use the following launch checklist:
- Name the offer for analysis. Include the campaign or product scope, incentive and intended run period in the internal name. Someone reviewing an export later should not have to decode Offer 1.
- Send traffic to the exact destination. The final URL should land where the promoted product, service or eligibility conditions can be understood and the incentive can actually be redeemed.
- Write the description as an AI instruction. State what is being offered and the context in which it is relevant. Do not rely on clever promotional language to carry eligibility rules.
- Begin with one incentive. Multiple incentives are supported, but allowing AI to choose among them immediately makes the first result harder to interpret. Establish a baseline before testing an incentive set.
- Use a dedicated code batch. Single-use promotional codes can be uploaded by CSV. Keep the pilot’s codes separate so a redemption can be reconciled to the offer rather than mixed with codes from email, affiliates or customer support.
- Set the contractual boundaries. Add the applicable terms and conditions, terms URL, start date and end date. Make sure the landing page and checkout enforce the same promise the shopper sees.
- Cap the exposure. Direct Offers support daily limits based on total offer value or number of claims. Select the type that controls your real constraint, then set it before activation.
A claim-count limit is useful when code inventory or fulfillment capacity is scarce. A total-value limit gives you a closer control on financial exposure, especially when incentives have different values. Neither replaces a complete promotional budget because a claim is not necessarily a redemption and a redemption is not necessarily an incremental sale.
The shopper can see an eligible promotion beneath a sponsored result in AI Mode as a Claim one-time code option. Opening it reveals the offer details and code, along with a button to visit the advertiser’s website. Review the entire handoff from that promise to the landing page and checkout. If the displayed terms and the site experience disagree, pause the offer rather than asking support staff to repair the mismatch after purchase.
Promotional terms can also create financial and legal exposure. If eligibility, expiry, exclusions or consumer rights require formal review in your market, put the Direct Offer through the same legal and operational approval process as any other public promotion. AI-selected delivery does not make the underlying promise less binding.
Measure discount economics beyond claims and conversions

A Direct Offer has at least six commercially distinct events: the offer is shown, its details are opened, a code is claimed, the shopper reaches the site, the code is redeemed and an order is completed. Do not collapse that chain into a single conversion number. Each transition answers a different question.
| Decision | Measurement | What a problem can mean |
|---|---|---|
| Is the offer attracting attention? | Claims or detail opens relative to observable offer exposure | The incentive, relevance decision or presentation is not compelling enough to prompt action |
| Can shoppers use it? | Redeemed codes relative to claimed codes | The site journey, eligibility rules, expiry or checkout process is creating friction |
| Does it produce completed business? | Completed orders and revenue tied to redeemed codes | Claims are not progressing to purchases, or order tracking is incomplete |
| Is the promotion affordable? | Realized discount cost and contribution after the discount | Additional sales may still be eroding margin |
| Is the result incremental? | Difference versus a credible unoffered comparison | The offer may be subsidizing orders that would have occurred at full price |
Use the denominator you can actually observe, and label it precisely. Claims divided by offer views is not the same metric as claims divided by sponsored-result impressions. If a required exposure event is not available in your account, report the narrower metric rather than manufacturing a rate from incompatible events.
Reconcile the advertising record with your commerce or lead system. The promotional code is the bridge: it lets you distinguish a code that was claimed from one that was redeemed, and a redemption from an order that remained valid after returns, cancellations or lead qualification. Do not assume the Google Ads interface contains every downstream business outcome you need.
Track the realized discount separately from media spend. A promotion can improve conversion efficiency inside an ad platform while the associated margin reduction appears only in the order system. Your decision table should therefore place ad cost, discount cost and contribution in the same review, even if the data originates in different systems.
Redemption alone cannot establish incrementality. Some shoppers who use a code would have purchased without one. The cleanest test is a randomized unoffered group when your setup supports it. If it does not, use the closest comparable campaign or audience cohort you can maintain, keep other meaningful changes stable and document the limitations. A simple before-and-after comparison is weaker because seasonality, demand shifts and other campaign edits can move at the same time.
Set decision rules before the pilot starts:
- The maximum daily offer value or claim count you will permit.
- The minimum contribution the promoted orders must retain.
- The comparison you will use to judge incremental orders or leads.
- The code redemption and completed-order events that must reconcile.
- The conditions that trigger a pause, such as exhausted code inventory, a checkout failure, incorrect terms or unacceptable margin.
- The evidence required before you add more incentives or move from campaign-level to account-level deployment.
Read the failure pattern, not just the final total. Many claims with few redemptions points toward a broken or confusing handoff. Many redemptions without incremental growth points toward cannibalization. Few claims followed by strong purchase quality may indicate narrow relevance or limited exposure; it does not automatically justify a larger discount. Each pattern calls for a different response.
Key takeaways
- The new AI Max columns expose campaign permissions; they do not prove why performance changed.
- Compare campaigns in configuration cohorts before attributing a result to Locations of interest, Optimized targeting or Brand inclusions.
- Start a Direct Offer at campaign level with one incentive when you need a test that is easier to interpret and contain.
- Treat the offer description as an input to AI relevance and generated copy, not as a private note.
- Use claim limits for operational scarcity and value limits for financial exposure, then track the full promotional budget outside the asset.
- Judge success through redemptions, completed outcomes, realized discount cost, contribution and incrementality – not claim volume alone.
When the new columns appear in your account, export the current permission state before changing anything. Then choose one eligible campaign, document its baseline, connect a dedicated code batch to completed-order data and launch only with a hard exposure limit. That gives Google room to optimize while preserving your ability to explain what happened and decide whether it deserves to scale.
References
- Search Engine Land – Google Ads adds new AI Max columns for deeper campaign analysis
- Search Engine Land – Google Ads tests new Direct Offer asset for AI Mode promotions


Leave a Reply