Your biggest Google Ads risk is no longer a lack of automation. It is allowing the platform to make a wider range of decisions while your reporting still collapses those decisions into one campaign total.
If you run Standard Shopping campaigns or maintain a Google Ads integration, you now have two different changes to prepare for. AI Max functionality in Standard Shopping remains an unconfirmed test, while Google Ads API v25 is a released engineering change. In both cases, the practical goal is the same: define what Google may decide, record what it actually does, and connect each decision to a business outcome.
Automation and measurement are changing at the same time
Standard Shopping has traditionally appealed to advertisers who want more direct control than Performance Max provides. That distinction could become less clear. A reported AI Max test in Standard Shopping includes conversational query matching, feed-based ad copy, Final URL Expansion, and the ability to choose between a Shopping ad and a text ad based on the query.
The reported implementation would preserve existing bidding and targeting settings while adding campaign-level controls for asset optimization, brand exclusions, and Final URL Expansion. Advertisers could reportedly disable URL expansion when they want traffic to remain tied to Shopping ads. That combination matters: it suggests Google may expand the decisions made inside Standard Shopping without forcing advertisers to migrate the campaign into Performance Max.
Do not treat those capabilities as settled product behavior. Google has not formally announced the Standard Shopping test, so availability, controls, and final functionality could change. Treat it as a scenario for which you can prepare, not a feature you should promise to a client or build into a forecast.
Google Ads API v25 is different. It adds new YouTube reporting, Shorts engagement metrics, creator insights, a loyalty retention goal, and a revised implementation of new customer acquisition goals. It also requires developers to update client libraries and code to use the new functionality, while the removal of legacy resources can affect compatibility. The API v25 changes therefore belong in an engineering release plan, not on a product-watch list.
Key takeaways
- Prepare for AI Max in Standard Shopping, but preserve the distinction between a reported test and a released feature.
- Treat query matching, message generation, destination selection, and ad-format selection as separate automation permissions.
- Record feature settings alongside campaign results so you can explain why performance changed.
- Use API v25 to deepen YouTube and lifecycle reporting rather than adding new metrics to an undifferentiated dashboard.
- Upgrade integrations through staging and regression checks because legacy lifecycle resources have changed.
Write an automation contract before enabling AI Max
An automation contract is a short operating document that states which decisions the platform may make and which boundaries it must respect. You do not need legal language or a lengthy policy. You need an explicit answer for each decision layer before a campaign starts spending under new rules.
| Decision layer | Potential automated behavior | What you should decide first |
|---|---|---|
| Query | Match Shopping inventory to conversational and long-tail searches | Which brand, intent, and relevance boundaries must be protected |
| Message | Create ad language from Merchant Center attributes | Which attributes are accurate, current, and safe to present as claims |
| Destination | Send a visitor to a page selected through Final URL Expansion | Which page types are eligible and whether expanded routing should be enabled |
| Format | Choose between a Shopping ad and a text ad | How each format will be identified and evaluated in reporting |
Start with the feed. Materials, fit, durability, and other Merchant Center attributes may become inputs to generated ad copy. A feed value that was previously visible only in a product listing can therefore become a prominent advertising claim. Check those attributes for accuracy, consistency, and substantiation. Do not use automation to amplify language that merchandising or legal reviewers would reject on the landing page.
Then decide how much routing authority the campaign should receive. Final URL Expansion is not merely a media setting; it is permission to select a different part of your site as the destination. A technically valid page can still be commercially wrong if it shows the wrong product set, weak availability, conflicting prices, or a conversion path that was not built for paid traffic.
- Verify that eligible pages show the same material product facts used in the feed.
- Confirm that price, availability, promotional language, and conversion tracking remain correct on every likely destination type.
- Use brand exclusions where matching or generated messaging could cross a brand boundary.
- Keep Final URL Expansion disabled until broader destinations have passed the same review as product pages.
- Document who may approve a wider set of destinations after the initial validation.
The downside of skipping this work is direct: budget can move to a page or message that does not represent the offer you intended to advertise. If you cannot verify destination eligibility, keep traffic constrained to the known Shopping path until you can.
Make every automated decision observable
Aggregate campaign performance cannot tell you whether a change came from broader query matching, generated messaging, a different destination, a different ad format, or the bid strategy already in place. You need a record that separates inputs, permissions, delivery, and outcomes.
| Measurement layer | What to record | Question it answers |
|---|---|---|
| Inputs | Feed revisions, attribute changes, landing-page changes, and tracking changes | Did the campaign receive different information? |
| Permissions | Asset optimization state, brand exclusions, Final URL Expansion state, bidding settings, and targeting settings | What was Google allowed to change or select? |
| Delivery | Available search-query detail, served ad format, selected destination, product coverage, and traffic mix | What did the system actually do? |
| Outcomes | Spend, conversions, conversion value, engagement, acquisition outcomes, and retention outcomes relevant to the campaign | Did the behavior produce the intended business result? |
Capture the current state before changing a setting. Screenshots can help during a preliminary rollout, but a structured change record is more useful because it can be joined to reporting later. At minimum, store the account, campaign, setting name, previous state, new state, approval owner, deployment point, expected effect, and rollback condition.
Next, write a falsifiable hypothesis. Broader conversational matching, for example, is not a complete hypothesis. A usable version identifies the eligible product group, the type of demand you expect to reach, the outcome you expect that traffic to produce, and the signal that would show the expansion is commercially irrelevant.
- Snapshot campaign settings, feed state, destination rules, and baseline reporting dimensions.
- Choose the specific automation permission being evaluated.
- Predefine the primary outcome and the business guardrails.
- Change one permission at a time where the platform and campaign structure allow it.
- Inspect query, format, and destination behavior before relying on the aggregate result.
- Keep, constrain, or reverse the change based on the predefined outcome and guardrails.
Do not copy a universal efficiency threshold from another account. A defensible guardrail comes from your margins, sales cycle, conversion quality, inventory constraints, and tolerance for exploratory demand. The important discipline is to set it before seeing the result. A threshold invented after the test becomes a justification, not a decision rule.
Use API v25 to separate YouTube signals from business outcomes
Segment non-skippable ads by sub-format
API v25 introduces the ad_sub_format_type segment for non-skippable in-stream YouTube ads. It can distinguish standard duration, ads up to 30 seconds, and ads up to 60 seconds. That dimension prevents materially different creative experiences from disappearing inside one format total.
Add the segment where it answers a real creative or delivery question. Compare performance within a consistent campaign objective and audience context. If duration, targeting, bidding, and creative concept all change at once, the new field gives you a cleaner label but not a causal explanation.
Keep Shorts engagement diagnostic
Comments, likes, and shares are now available for Shorts ad reporting. These metrics can show how viewers respond socially to a creative, but they are not substitutes for conversions, revenue, qualified acquisition, or retention. Use them to diagnose resonance and participation, then read them beside the outcome the campaign was funded to produce.
A practical Shorts view should keep delivery, engagement, and business results in separate groups. That structure stops a highly interactive ad from being declared successful when it misses the commercial objective, while still preserving the engagement data that can guide creative development.
Treat creator insights as conditional data
API v25 can expose creator-channel information including average views, engagement rates, likes, comments, and audience attributes. Non-public details depend on creators opting to share them. Build reports that make missing or unavailable creator data explicit rather than treating absent values as zero performance.
Creator metrics are best used to improve selection and contextual interpretation. They do not remove the need to measure the actual ad, audience, offer, and conversion path used in your campaign.
Separate retention optimization from customer acquisition
API v25 adds a loyalty retention goal with campaign- and account-level settings. It also supports bid adjustments and loyalty-member benefits in Product Listing Ads. This gives advertisers a way to optimize for keeping loyalty members rather than treating every valuable action as another acquisition event.
That distinction should survive all the way into your dashboard. Acquisition asks whether you gained the intended new customer. Retention asks whether an existing loyalty member stayed active or received an experience designed for that relationship. Combining them can make campaign efficiency look healthy while concealing which lifecycle objective produced the value.
New customer acquisition goals have also moved to Google’s unified goals framework, replacing legacy lifecycle goal resources. Before upgrading, map each existing resource, field, report, and internal label to its intended counterpart. Do not let an engineering migration silently redefine the business meaning of a goal.
- Give acquisition and retention goals distinct names in campaign documentation and reporting.
- Identify the first-party data and membership logic on which each goal depends.
- Assign an owner to validate member benefits shown in Product Listing Ads.
- Keep bid adjustments visible in the same change record as the lifecycle goal.
- Check that executive dashboards do not merge retained members with newly acquired customers.
This is where media, analytics, customer relationship management, and engineering teams need one shared definition. The API can transport the goal, but it cannot resolve a disagreement about who counts as new, retained, or eligible for a member benefit.
Put API and campaign changes into production safely
Begin the API v25 migration with an inventory of affected client libraries, queries, resources, report schemas, calculated fields, dashboards, and downstream exports. Pay particular attention to code that depends on legacy lifecycle goal resources. New reporting fields are useful only after the existing integration remains trustworthy.
- Map current dependencies and identify removed or replaced lifecycle resources.
- Upgrade the supported client library and update code in a non-production environment.
- Add the YouTube sub-format, Shorts engagement, creator, and loyalty fields only where a defined use case exists.
- Run unchanged reports through regression checks and compare row structure, totals, null handling, and field meaning.
- Test reports with and without the new optional dimensions so downstream users understand how segmentation changes the output.
- Deploy with monitoring and a documented recovery path for failed jobs or incompatible consumers.
Use the same release discipline for campaign automation. A campaign ticket should state the setting before and after the change, eligible products and brands, permitted destination types, expected query behavior, primary outcome, guardrail, data location, approval owner, and rollback condition. This turns an AI feature from an opaque switch into a governed campaign change.
Your first move should be simple: capture the current state of the campaigns and integrations that would be affected. If the Standard Shopping test never reaches your account in its reported form, that record still improves your control over existing automation. If it does arrive, you will be ready to test it without sacrificing the ability to explain where an ad appeared, what it said, where it sent the visitor, and whether that decision helped the business.
References
- Search Engine Land – AI Max spotted in Google Standard Shopping campaigns
- Search Engine Land – Google Ads API v25 adds YouTube metrics and loyalty campaign goals
Leave a Reply