Google is consolidating how Local Inventory Ads are controlled in eligible Standard Shopping campaigns. The practical issue is not merely that a setting is moving: local inventory may become active by default where the linked Merchant Center account has the relevant add-on enabled.
Advertisers should use the change as a prompt to verify which inventory each campaign can serve, especially when online and in-store products have separate budgets or strategies.
What Google is changing in Shopping campaigns
According to Search Engine Land, Google notified advertisers that Local Inventory Ads will be enabled by default beginning Aug. 31 for Shopping campaigns connected to Merchant Center accounts with the Local Inventory Ads add-on enabled.
Google is also removing the legacy “Local products” control found under Other settings. Campaign-level management will shift to the Inventory filter, where an advertiser can select Channel = Local or Channel = Online.
The reported rationale is simplification. The old arrangement included overlapping controls for local inventory, while the revised setup places channel selection in one filtering mechanism.
Why a default change can affect campaign planning
A default determines what happens when an eligible campaign is left without an explicit restriction. That makes this update particularly relevant to advertisers who have intentionally divided online and store inventory into different campaigns.
If those boundaries are reflected only in the setting Google plans to remove, the campaign may no longer behave as intended after the transition. The concern is operational: inventory eligibility and budget allocation can become misaligned even when product data and campaign structure remain otherwise unchanged.
This does not mean every Shopping advertiser needs to redesign an account. The reported change applies to eligible campaigns associated with Merchant Center accounts that have the Local Inventory Ads add-on enabled. Accounts outside that description are not identified in the source as affected.
Organic visibility, paid media and artificial intelligence merge into one connected search ecosystem, where vivid data streams link a creative website with a powerful analytics dashboard.
Key takeaways
Local Inventory Ads are set to become the default for eligible Shopping campaigns beginning Aug. 31.
The existing “Local products” option under Other settings will be removed.
Local and online inventory will instead be controlled through the Inventory filter.
Advertisers separating store and ecommerce budgets should confirm that each campaign uses the intended channel filter.
A focused campaign review before the transition
The most useful review starts with scope. Advertisers can identify Standard Shopping campaigns linked to Merchant Center accounts where the Local Inventory Ads add-on is active, then determine whether those campaigns are intended to advertise store inventory, online inventory or both.
For campaigns meant to remain channel-specific, the Inventory filter should express that choice directly: Channel = Local for local inventory or Channel = Online for ecommerce inventory. This is especially important when separate campaigns carry separate budgets, because an unintended expansion of eligible inventory could blur the purpose of that structure.
Advertisers should also document the intended role of each affected campaign before making changes. A simple record of campaign purpose, budget ownership and selected channel can make later troubleshooting easier without introducing assumptions about performance.
What is known, and what still requires account-level verification
Search Engine Land attributes the initial public identification of the update to PPC specialist Arpan Banerjee, who shared a notification email sent to affected Google Ads manager accounts on LinkedIn. The available report establishes the new default, the removal of the old setting and the replacement filter options.
It does not provide account-specific forecasts or performance outcomes. Advertisers therefore should not assume the update will help or hurt results on its own. Its significance depends on existing campaign structure and whether local and online inventory are supposed to share targeting and budget.
The durable approach is to make channel intent explicit in the Inventory filter. That leaves less room for a platform default to determine how a carefully separated retail strategy operates.
I’m seeing an important shift for Standard Shopping campaigns: Google is bringing Maximize Conversion Value bidding to these campaigns without requiring a Target ROAS. That gives advertisers more room to pursue value-based optimization without immediately being locked into a specific return target.
What’s happening. Google is rolling out Maximize Conversion Value bidding for Standard Shopping campaigns, and advertisers no longer have to set a Target ROAS to use it.
Before this update, if I wanted to optimize around conversion value in Standard Shopping, I generally had to use a Target ROAS bidding strategy. Now, this new option lets campaigns focus on maximizing conversion value while giving Google’s bidding system more flexibility to find the highest-value opportunities.
Why I care. This matters because I can now use Google’s value-based bidding in Standard Shopping without being constrained by a Target ROAS goal. That gives me more flexibility while preserving the control and transparency that many advertisers still prefer in Standard Shopping campaigns.
It may also reduce the need to run feed-only Performance Max campaigns just to access Maximize Conversion Value bidding. For advertisers who prefer tighter campaign control, that is a meaningful change.
Between the lines. I know many advertisers have continued to favour Standard Shopping because it offers more visibility and control than Performance Max. But when they wanted flexible value-based bidding, they often created feed-only Performance Max campaigns as a workaround.
With this update, that workaround may no longer be necessary for some accounts.
Why advertisers should care. I can now combine the structure and transparency of Standard Shopping with a more flexible automated bidding strategy. In practical terms, this could simplify campaign setups, reduce unnecessary Performance Max usage, and make account management cleaner.
The bottom line. Google is narrowing one of the biggest feature gaps between Standard Shopping and Performance Max. For me, this gives advertisers another reason to keep using Standard Shopping while still benefiting from automated value-based bidding.
First spotted. Performance marketer Yash Mandlesha spotted the update and shared the option on LinkedIn.
If your Shopping or Performance Max campaigns rely on an API-fed catalog, the Merchant API migration is a delivery dependency, not routine backend maintenance. Letting a legacy Content API connection reach its cutoff can interrupt campaigns that depend on its product feed.
The dangerous version of this failure is not always an obvious API error. Products may arrive through the new connection while feed labels, campaign structure, or bidding logic no longer match. Your migration is complete only when the new API writes the right product data and the campaigns consuming that data still behave as intended.
Confirm whether your account is exposed
Start in Merchant Center Next. Open Settings > Data sources and inspect the type shown for every product source. Any source marked Content API belongs in your migration inventory. Do not assume that an ecommerce app, scheduled file, or newer integration elsewhere in the account means the legacy connection has already been replaced.
For each Content API source, record:
The Merchant Center account and data source name.
The application, connector, platform, or custom code that writes the product data.
The person or provider able to change and deploy that integration.
How updates are triggered, including scheduled jobs and manual runs.
The Shopping and Performance Max campaigns that consume the products.
Every feed label associated with the source and what that label controls.
The evidence you will require before declaring the migration complete.
If a third-party platform manages the connection, ask for more than a general confirmation that it supports Merchant API. You need four explicit answers: which connection will be replaced, when the change will reach your account, whether feed labels will be recreated or mapped, and whether you must reconnect anything inside Merchant Center Next. The provider may own the deployment, but you still own campaign validation.
The transition began in mid-2024, and the communicated migration path cited February 28 for beta participants and August 18 for other Content API users. Those month-and-day references are not safe planning dates without the applicable year and account context. Use the dated notice attached to your own account as the operative cutoff. If nobody can produce that notice, treat the connection as an active risk rather than assuming you have more time.
Preserve feed labels before moving product data
Feed labels can be part of your campaign architecture. They may separate inventory or support bidding decisions, yet they do not transfer seamlessly during this migration. That creates a misleading success state: the new connection works, products appear, and the technical ticket closes, but a label-dependent campaign no longer addresses the same inventory.
Build a label map before changing the connection. For each existing label, capture:
The exact current value, including spelling and capitalization.
A small set of representative products that should carry it.
The campaign structure or bidding rule that depends on it.
The value expected after migration.
The person responsible for checking it in the advertising account.
Include products from every label and at least one product that intentionally has no label. That last case helps you distinguish a valid blank value from a failed transfer. Compare the same products before and after cutover instead of checking whichever items happen to be easiest to find.
Do not rename, consolidate, or reorganize labels during the API migration unless the old structure makes the cutover impossible. Combining cleanup with migration destroys your baseline: when inventory changes, you will not know whether the API, the new label design, or the campaign edit caused it. Move the existing behavior first, prove parity, and schedule cleanup as a separate change.
Run the migration as a controlled cutover
A useful migration plan separates preparation, technical cutover, and advertising validation. It also names the person who can stop or reverse the change. Use this sequence:
Assign two owners. The technical owner changes the integration. The paid media owner verifies labels, inventory coverage, and campaign behavior.
Freeze unrelated changes. Avoid simultaneous feed restructures, label renaming, and major campaign edits from baseline capture through validation.
Capture the baseline. Save the current data source type, label map, representative products, update process, and dependent campaigns.
Configure the Merchant API connection. Update the system that actually writes product data, then reconnect the data feed where the migration flow requires it. A code deployment alone does not prove that Merchant Center is receiving the new writes.
Preserve rollback material. Keep the previous configuration, mappings, and baseline evidence until validation finishes. Do not allow two uncontrolled connections to write conflicting versions of the same products.
Send a controlled update. If the integration permits it, change a representative product through the real production path. Choose a field whose before-and-after state is easy to verify.
Check every label path. Compare the representative products against the label map and confirm that dependent campaign structures still include the intended inventory.
Observe a scheduled run. A successful manual request does not prove that the recurring job, connector, or automation has been migrated.
Retire the legacy connection only after sign-off. Require approval from both the technical owner and the paid media owner.
Define rollback triggers before cutover. Missing labels, a test update that never reaches Merchant Center, or a campaign structure that loses its intended inventory are reasons to stop and investigate. A rollback should restore a known configuration, not blindly reactivate every old process.
Validate business behavior, not just API success
An authenticated request proves only that one request was accepted. End-to-end validation has three layers: the connection, the product data, and the campaign consuming that data.
Connection validation
Confirm that Merchant Center Next shows the intended new data-source connection rather than the legacy Content API source.
Verify that a deliberately changed product value arrives through the new path.
Run or observe the normal scheduled process and confirm that it uses the same path.
Record the time, product tested, expected result, actual result, and validator.
Product and label validation
Check the same representative products captured in the baseline.
Compare each expected label character for character.
Confirm that intentionally unlabeled products remain unlabeled.
Test an ordinary product update after the initial migration so you know the connection handles ongoing changes, not only the first import.
Campaign validation
Inspect every Shopping or Performance Max structure that relies on a migrated feed label.
Confirm that each label still selects the intended inventory and that no expected subset has become empty.
Check that bidding logic tied to those labels still points to the right product group.
Have the paid media owner sign off independently of the developer or integration provider.
Do not use immediate spend or revenue as your only acceptance test. Auction results vary, and business metrics can lag behind a configuration error. Structural checks – the right products, labels, and campaign relationships – reveal migration mistakes sooner. Performance monitoring should follow, but it cannot replace those checks.
Keep the validation record with the integration documentation. It should show the old and new connection, the label mapping, the test products, the scheduled-run result, the dependent campaigns, and both approvals. That evidence gives you a precise starting point if a later feed or campaign problem appears.
Key takeaways
A data source marked Content API in Merchant Center Next is a migration dependency that needs a named owner.
Moving products is not enough. Feed labels require an explicit before-and-after mapping because they may not transfer cleanly.
Separate the API cutover from feed cleanup and campaign restructuring so you retain a useful baseline.
Validate the new connection, a normal scheduled update, representative products, labels, and every dependent Shopping or Performance Max structure.
Use the dated notice for your own account to determine the applicable cutoff rather than relying on an unqualified calendar date.
Open Merchant Center Next and inspect Data sources now. If Content API appears, assign a technical owner and a paid media validator in the same work item. Close that item only after a scheduled product update reaches the new connection and the label-dependent campaigns still address the inventory you intended.
If your Performance Max build keeps stalling while someone finds, exports, labels, and re-uploads the right product video, Google has removed part of that handoff. Product-associated videos in Merchant Center can now appear during campaign setup, giving you a shorter route from catalog creative to an eligible PMax asset.
Treat this as a creative-operations improvement, not an automatic performance win. The useful question is not simply whether Google can find your videos. It is whether the surfaced video matches the product, communicates something useful, and can be measured without attributing every campaign change to one new asset source.
The benefit becomes more important as your catalog grows. A team managing a small, stable product range can usually locate the correct creative manually. With an extensive SKU catalog, that manual lookup turns into a recurring reconciliation exercise: which video belongs to which product, whether it is current, and whether the campaign builder selected the right version.
What it solves
Asset discovery: campaign builders can find product-related videos through the Merchant Center connection instead of starting another search through shared drives or separate libraries.
Product-to-creative alignment: an existing product association gives the setup process a stronger signal than a filename or a campaign builder’s memory.
Catalog coverage: reusable associations make it more practical to bring relevant video into campaigns covering many products.
Workflow duplication: retail, feed, and paid-media teams have less reason to recreate the same asset mapping at every campaign build.
What it does not solve
It does not turn a generic brand video into product-specific creative.
It does not correct an inaccurate product-video association.
It does not prove that a surfaced video was selected, delivered, or responsible for a change in results.
It does not replace creative review. Automation can scale a good mapping, but it can also repeat a bad one across more of the catalog.
This distinction should shape your rollout. First make the Merchant Center relationship trustworthy. Then use the PMax setup screen as a second validation point. If you reverse that order, the campaign builder becomes responsible for repairing catalog data under launch pressure.
Prepare the product-video relationship before campaign setup
A video can be professionally produced and still be wrong for a product. The common failure is not poor production quality; it is a mismatch in identity, variant, feature, or promise. A family-level demonstration may be appropriate for several related products, for example, but only if everything shown and claimed applies to every product receiving that association.
Use an internal relationship classification before you expand coverage. This is a planning framework, not a Merchant Center setting:
Relationship
What the video shows
Approval rule
Typical failure
Exact product
One identifiable product or variant
The depicted product and the associated item agree on every visible or stated attribute
The video shows a different color, size, model, bundle, or generation
Product family
A shared use case or feature across related products
Every claim remains true for every associated item
A feature available on one model is implied for the entire family
Contextual
A scene, category, or collection containing several products
The associated product is relevant and understandable without a forced interpretation
A broad lifestyle scene is attached to products that are barely visible or unrelated
Do not chase raw coverage by attaching the nearest available video to every product. Define approved video coverage instead:
Approved video coverage = products with a reviewed, relevant video association / products in campaign scope
That denominator matters. If a campaign contains only part of your catalog, measure the products that can actually enter that campaign rather than celebrating coverage across unrelated inventory. The metric also prevents a misleading shortcut: one broadly associated video may raise nominal coverage while doing little to improve product relevance.
Prioritize associations by confidence
Start with products that already have an exact, current video and an unambiguous association.
Move to product families only after documenting which claims and visual attributes are shared across the family.
Use contextual creative where the product relationship is clear, not merely because the video is available.
Leave uncertain matches out of the rollout until a reviewer can resolve them. Missing video is easier to diagnose than misleading video.
This order gives you a clean first implementation. It also makes later troubleshooting easier because the initial group contains the associations most likely to be correct.
Use a two-checkpoint QA workflow
The first checkpoint belongs in Merchant Center, where the product-video relationship lives. The second belongs in PMax setup, where you confirm what Google actually surfaced for the campaign. Neither checkpoint should be treated as a substitute for the other.
Define the campaign product scope. Record the products or product groups you intend to promote before reviewing creative. Otherwise, reviewers waste time validating assets that cannot affect the build.
Review the existing associations. Confirm that the video depicts the intended product, family, or legitimate context. Check visible attributes, spoken or written claims, and any offer information that could become outdated.
Record an approval decision. Keep the product identifier, video identifier or filename, relationship class, reviewer, status, and reason for rejection. A simple shared sheet is enough if those fields remain consistent.
Inspect the videos surfaced during PMax setup. Confirm that the expected approved assets appear and that an unexpected near-match has not entered the candidate set.
Review the final campaign selection. Surfaced means available during setup; it should not be treated as proof that the asset was intentionally selected or will receive meaningful delivery.
Log the launch state. Save the campaign scope, approved coverage, relevant asset decisions, launch date, and any simultaneous changes to budget, bidding, feed data, pricing, or promotions.
Give reviewers a compact acceptance checklist. A video is ready only when you can answer yes to the applicable questions:
Does the video show the same product, or a clearly valid product family or context?
Do visible attributes agree with the associated item?
Are every feature and benefit shown applicable to that item?
Will the main product and message remain understandable on a small screen?
Does the video still make sense without relying entirely on audio?
Are displayed prices, promotions, bundles, availability statements, and seasonal messages still current?
Is the destination experience consistent with what the video leads a shopper to expect?
The checklist is also a responsibility boundary. Feed specialists can validate product identity and association. Creative owners can validate the footage and claims. Paid-media owners can validate campaign scope and final selection. Without those boundaries, every mismatch becomes the campaign manager’s problem at the last possible moment.
Review changes by exception
A full manual review at every build will eventually recreate the bottleneck this connection is meant to reduce. Preserve approved mappings and reopen them when something material changes: the video is replaced, the product is revised, variants are consolidated, a family gains or loses a feature, an offer expires, or the campaign scope changes.
This exception-based process lets stable mappings pass through quickly while sending genuinely risky changes back to a person. The goal is not less control. It is to place control where a decision has changed.
Measure workflow gains separately from ad performance
The Merchant Center connection can deliver value even before you see a commercial lift. It may reduce campaign preparation, increase approved video coverage, and cut mapping rework. Those are operational outcomes. Return on ad spend, cost per acquisition, conversion value, and profit are commercial outcomes. Combining the two creates an evaluation that cannot tell you what improved.
Track the operational outcome
Approved coverage: reviewed, relevant product-video associations divided by products in campaign scope.
Mapping accuracy: associations approved without correction divided by associations reviewed.
Rework rate: associations changed after campaign setup divided by associations reviewed.
Build effort: time spent locating, transferring, mapping, and validating video assets for a comparable campaign build.
Exception volume: new or changed mappings that require human review.
Measure the same definitions before and after adopting the workflow. Do not quietly change the denominator from all in-scope products to only products that already have video. That would make coverage look better without improving the catalog.
Evaluate commercial movement cautiously
Performance Max uses automated delivery, so a campaign-level change after adding Merchant Center videos does not establish that the videos caused it. Demand, bids, budget, product mix, feed quality, price, promotions, and other creative can move at the same time.
Choose the business metric first. Use the metric that governs the campaign, such as conversion value, return on ad spend, cost per acquisition, or another internally approved profitability measure.
Record a baseline. Capture the campaign and product scope before the new video workflow enters the build.
Log concurrent changes. Note feed edits, price changes, promotions, budget shifts, bidding changes, assortment changes, and other creative updates.
Stage the rollout where practical. Begin with a bounded product group whose associations have been reviewed. Expand after the mapping and workflow hold up.
Separate diagnosis from attribution. Asset delivery and engagement can help you investigate what happened, but they do not by themselves prove incremental business value.
If several major inputs changed at once, label the result directional rather than causal. That wording is not excessive caution. It keeps a convenient creative feature from receiving credit or blame for changes that the campaign design cannot isolate.
Set decision rules before launch. Expand when associations remain accurate, operational effort falls, and the primary business metric stays acceptable or improves. Revise when coverage rises but mappings or claims fail review. Pause expansion when errors multiply faster than the team can correct them. Your thresholds should come from the economics and risk tolerance of the account, not from an invented universal benchmark.
Key takeaways
Merchant Center videos can now surface during Performance Max setup, reducing the manual handoff between product data and campaign creative.
The product-video association is the control point. Validate identity, variant, feature claims, offer details, and destination consistency before scaling.
Measure approved, relevant coverage rather than the number of products attached to any video.
Use Merchant Center review and PMax setup review as separate checkpoints, then keep a decision log so later corrections are traceable.
Track workflow improvement separately from commercial performance, and do not treat a campaign-level before-and-after change as proof of video impact.
For your next PMax build, choose one bounded part of the catalog. Classify its product-video relationships, approve the strong matches, check what setup surfaces, and record both the operational baseline and the campaign baseline. Expand only when the mapping stays trustworthy. That is how this small integration becomes a repeatable system instead of another source of automated ambiguity.
You’re deciding which Google changes deserve engineering time, which belong in your Shopping plan, and which are still too speculative to enter a forecast. The answer isn’t to treat every announcement, test, and rumor as equally actionable.
The clearest opportunity is first-party data infrastructure. Local Shopping labels deserve feed preparation and controlled observation. Gemini advertising belongs on a watchlist, not in a committed media plan. That order will help you improve what is available without budgeting against a product that doesn’t exist.
Key takeaways for advertisers
Prioritize the Data Manager API when separate integrations are creating duplicated work or inconsistent first-party data flows.
Treat merchant city and town labels in Shopping ads as an observed test. Prepare accurate local inventory data, but don’t forecast an uplift or assume every eligible impression will show the label.
Keep Gemini separate from AI Mode in your planning. Google’s stated position is that the Gemini app has no ads and there are no plans to add them.
Classify every platform change as available, experimental, or unconfirmed before assigning budget, engineering effort, or performance targets.
First-party data deserves the engineering time
Google’s Data Manager API is the most concrete change because it solves an operational problem you may already have: audience data, offline conversions, and other first-party signals reaching Google through separate connections. The API is designed to provide one integration point across Google Ads, Google Analytics, and Display & Video 360.
That consolidation matters when your team maintains one job for customer lists, another for offline conversion uploads, and additional platform-specific logic for authentication, retries, or refreshes. A shared route can reduce that maintenance burden. It can also make ownership clearer when a data flow fails.
Use a bounded migration sequence rather than moving every data flow at once:
Inventory the current routes. Record which process sends each audience or conversion type, how often it runs, who owns it, and what happens when records fail.
Choose one well-understood flow. Start with an audience list or offline conversion type whose current volume, update pattern, and business meaning are already known. A familiar baseline makes discrepancies easier to find.
Define the data contract before building the endpoint. Agree on identifiers, event names, time fields, refresh frequency, correction handling, and ownership. A unified API won’t reconcile two teams using different meanings for the same conversion.
Validate the new and existing routes side by side. Compare submitted, accepted, rejected, and delayed records where those measures are available. Do not send the same event through both routes unless you have verified how duplicates are prevented.
Check reporting before changing bidding. Confirm that conversion totals, audience freshness, and processing delays behave as expected. Only then should you evaluate whether richer signals help automated bidding.
Retire an old connection only after reconciliation. Keep a rollback path until the new route has completed its normal refresh and correction cycles without unexplained gaps.
This sequence protects the part of the account with financial consequences: measurement. If an integration drops conversions, submits duplicates, or changes event meaning, bidding can optimize against a distorted picture. Parallel validation is less expensive than discovering the problem after an automated campaign has reacted to it.
The strongest adoption case is a team already maintaining several Google connections. If you have one stable data flow and little engineering overhead, consolidation may be less urgent. Start with the operational cost you can document, not the assumption that a new API automatically creates incremental revenue.
Local Shopping labels make feed accuracy visible
Some Shopping ads using local inventory data have displayed the merchant’s city or town above the product title. The placement gives shoppers a proximity cue without requiring a separate local ad format. It is distinct from fulfillment labels such as In-store, Pickup later, and Curbside pickup.
That distinction is important. A city label tells the shopper where the merchant is located. By itself, it doesn’t promise immediate availability, same-day collection, or a particular fulfillment method. Your inventory and pickup information still need to carry those meanings accurately.
Google has not published rollout, eligibility, or technical requirements for the location-label test. You therefore shouldn’t look for an undocumented switch, promise the placement to stores, or build a performance forecast around it. The practical move is to make the local inventory setup reliable enough to benefit if the label appears.
Check store and product coverage. Confirm that the intended locations and locally available products are present in the systems supplying your local inventory data.
Standardize location names. Resolve inconsistent city or town naming across store records before those differences become visible to shoppers or fragment your analysis.
Audit location and fulfillment separately. A correct city label cannot compensate for stale availability or pickup information, and a pickup label does not confirm that the displayed city is the location you intended to promote.
Record observed appearances. When your team sees the label, capture the market, store, query context, device, and date. That record will help you distinguish a limited test from a broader change.
Measure at the local level. Compare results by store or market where activity is sufficient, rather than blending exposed and unexposed locations into an account-wide average.
A recognizable or nearby location could make a merchant feel more relevant than a distant seller. That is a plausible shopper response, not a guaranteed click-through or store-visit lift. Let observed exposure and local results establish the value before you change budgets.
That doesn’t settle how every Google AI experience will be monetized indefinitely. It does settle what belongs in a responsible plan based on the information available: no Gemini inventory, targeting assumptions, pricing model, creative specification, eligibility rule, or measurement framework should appear as a committed line item.
Keep Gemini and AI Mode in separate rows of your channel plan. Ads associated with AI Mode do not prove that the Gemini app will use the same inventory or commercial model. Product names, interfaces, and user behavior may look related while their advertising availability remains different.
A useful planning boundary is simple:
Available inventory can receive budget when your account is eligible and its economics fit the campaign.
An observed test can receive monitoring, data preparation, and a measurement plan, but not assumed reach or revenue.
A denied or unconfirmed product stays on a watchlist until Google supplies an official product path, eligibility details, and reporting expectations.
You can still prepare strategically. Decide which customer questions, product attributes, and conversion events would matter in a conversational ad environment. Do not assume, however, that current Google Ads audiences, Shopping feeds, or Data Manager integrations will automatically transfer to a future Gemini product. No documented product connection supports that implementation decision.
Use one evidence rule for every platform change
The three developments require different actions because their evidence states are different. Put them in a change register that your paid media, ecommerce, analytics, and engineering teams can read without translating headlines into strategy on their own.
Platform change
Documented status
Action now
Do not assume
Data Manager API
Available across Google Ads, Google Analytics, and Display & Video 360
Pilot one audience or offline conversion flow and reconcile it before consolidation
That a new connection fixes weak data or guarantees a performance gain
Shopping merchant location label
Observed test using local inventory data; rollout and requirements are unannounced
Audit local feeds, standardize locations, and prepare store-level measurement
Universal exposure, a configuration switch, or an automatic traffic lift
Gemini app ads
Google denied that ads are present or planned
Keep the possibility on a monitored watchlist
2026 inventory, pricing, formats, targeting, or compatibility with AI Mode
For each entry, record the affected surface, evidence status, business dependency, owner, next action, and condition that would justify changing the status. An official availability notice could move a test into implementation. Repeated sightings without documentation may justify broader measurement, but not a guaranteed forecast. A rumor should not advance because it has been repeated.
Start with the first-party data inventory because it can improve infrastructure you already use. Then audit local feeds so your stores are ready for location-led Shopping presentation. Remove Gemini placements from committed projections unless Google replaces its denial with a real product announcement. That gives you a plan based on executable changes rather than imagined inventory.
Your shopping campaigns can keep spending while your products become harder to find. When that happens, the failure may sit upstream of the ads: weak catalog language, inconsistent offer data, a landing page that cannot honor a regional price, or reporting that hides what each SKU actually earns.
If you are deciding where the next dollar should go, do not begin with the channel budget. Build one reliable product truth layer, give each channel a specific job, and find the earliest point where visibility turns into waste. That sequence makes your paid shopping, marketplace, social, and AI discovery work reinforce one another.
Build a product truth layer before adding campaigns
Treat every SKU as a bundle of claims that must agree wherever the product appears. The title should identify the same item as the landing page. The advertised price should match the price a qualified shopper can obtain. Availability, variants, regional eligibility, and member conditions should not change unexpectedly between the listing and the destination.
Audit each product family against five requirements:
Unambiguous identity: A shopper should be able to distinguish the product, brand, model, variant, size, or other meaningful option without opening several nearly identical listings.
Useful discovery language: Titles and descriptions should use the terms a buyer would recognize while remaining readable. Repeating keywords is not a substitute for identifying the product precisely.
Offer truth: Price, availability, promotion, region, and membership conditions should agree across the feed, visible page content, checkout path, and structured product data.
Decision detail: The page should explain who the product is for, what differentiates it from nearby alternatives, which options are available, and any limitation that could change the buying decision.
Destination continuity: The landing page should open the correct product and preserve the offer presented before the click. Do not make the shopper search again for the advertised variant or price.
The same discipline supports discovery outside conventional ads. A shopper using Perplexity Shopping is still trying to identify, compare, and choose products. Your goal is to make each offer understandable without requiring an AI system or a person to reconstruct essential facts from vague category copy.
Write product content for comparison, not merely description. Explain the meaningful difference between adjacent models. State what is included and what is not. Connect technical features to the decision they affect. Keep structured data aligned with what the shopper can see instead of using markup to introduce a second version of the offer.
Give every commerce channel one job in the buying journey
An ecommerce visibility strategy becomes expensive when every channel is expected to produce the same kind of result. Google, Amazon, social platforms, and AI shopping interfaces meet the buyer in different contexts. Your measurement and budget decisions should reflect those differences.
Channel
Primary job
First lever to inspect
Misleading conclusion to avoid
Google Performance Max
Capture and expand shopping demand through automated placements
Feed quality, conversion tracking, and actionable campaign segments
More budget will compensate for weak product data
Amazon
Convert marketplace demand close to the transaction
Offer quality plus keyword- and market-level performance
Strong conversion proves Amazon created all of the demand
Social platforms
Build awareness, customer lists, and remarketing audiences
Audience quality, creative response, and downstream engagement
Last-click sales reveal the channel’s entire contribution
AI shopping discovery
Help shoppers discover and compare relevant products
Clear product facts, differentiated offers, and useful destination pages
Referral clicks represent total visibility in answer-led journeys
Social activity often earns its place by creating future demand rather than closing every sale immediately. Giveaways can help build customer lists, awareness campaigns can introduce an unfamiliar product, and remarketing can bring interested shoppers back. If you judge all three solely by direct conversion, you may cut the activity that supplies later demand to Google, Amazon, or your own store.
Use channel roles as budget hypotheses, not permanent labels. When high-intent traffic exists but efficiency is poor, inspect product data, tracking, and offer continuity before funding more awareness. When conversion is healthy but discovery is thin, improve social reach, comparison content, and AI-readable product information. When Amazon performs but your direct store does not, compare the offer and landing experience before blaming the audience.
Make Performance Max accountable to decisions you can make
Performance Max becomes easier to manage when campaign boundaries correspond to real business decisions. A segment is useful only if you would change a budget, bid objective, creative approach, geography, or landing experience because of what it reveals.
Verify the conversion signal before trusting automation
Automated bidding optimizes toward the data it receives, not the business result you intended to send. Confirm that a completed order and its value are recorded correctly. If more than one integration can report the same order, verify that the purchase is not counted twice. Keep browsing actions and shopping-cart activity distinct from completed revenue so the campaign is not rewarded equally for unequal outcomes.
For stores using Shopify, synchronizing commerce data with Google Ads can support automated bidding and campaign experiments. The important part is not merely connecting the systems. Run a test order, follow it through the reporting path, and compare the recorded value with the actual transaction before increasing spend. Scaling against inflated or incomplete conversion data can direct more budget toward false revenue.
Segment the feed around controllable differences
Merchant Center default and custom labels let you group products for more precise campaign control. Useful labels can represent a product family, inventory condition, margin band, promotion, season, or region when you possess reliable data for that distinction.
Before creating a separate campaign, finish this sentence: “If this segment behaves differently, we will change ___.” A clear answer might be its budget, return objective, geographic reach, creative, or destination. If there is no different action to take, keep the reporting distinction without necessarily creating another campaign boundary.
Do not split a modest sales base simply because a granular dashboard looks tidy. PMax benefits from conversion volume. Excessive segmentation can leave each campaign with too little feedback to distinguish a real pattern from ordinary variation.
Improve query fit at the product level
Start with the products receiving meaningful exposure or spend. Read each title as if you know nothing about the store. Put the most distinguishing information where it can be understood quickly. Remove generic promotional language that displaces product identity. Use the description to clarify selection criteria rather than repeating the title in a longer form.
Then compare the feed record with the destination page. A well-formed listing cannot rescue a landing page that hides the selected variant, changes the price, or buries the information that justified the click. Conversely, an excellent page may never receive qualified traffic if the feed describes the product too vaguely.
Use this order for a PMax audit:
Validate the purchase event and transaction value.
Resolve feed eligibility, identity, price, and availability problems.
Check whether campaign segments correspond to different business actions.
Improve the product title, description, imagery, offer, and destination continuity.
Increase budget only after the earlier layers can convert additional demand accurately.
Use regional loyalty pricing only when the page can keep the promise
Regional member pricing can make a national catalog more locally relevant, but it also creates a strict continuity requirement. The shopper must see the appropriate member offer in the ad and on the page reached after the click.
Google is testing this capability as a beta with limited visibility. It is available only where both regional availability and pricing, or RAAP, and loyalty programs are supported. Eligible merchants must participate in Google’s loyalty add-on, define regional settings in Merchant Center, and add the program label, tier, and price through loyalty program attributes in regional inventory feeds.
The click is the critical handoff. Google adds a region ID to the URL, and the merchant’s landing page must use it to display the corresponding member price. If the page falls back to a national price or presents an unexplained amount, the shopper encounters a broken promise after a paid click.
Implement the beta as a controlled offer system:
Confirm eligibility first. Verify that the intended market supports both RAAP and loyalty programs before designing a campaign around the feature.
Define the commercial rules. Record which regions, program labels, tiers, products, and prices belong together. Decide what a shopper sees when regional or membership status cannot be established.
Configure Merchant Center and the feed. Set the regional definitions and populate the required loyalty program attributes in the regional inventory data.
Make the landing page region-aware. Read the region ID from the click and render the matching member offer. Clearly distinguish the regular price from a price that requires membership.
Test every handoff. Open representative ad URLs for each configured region, test signed-out and eligible-member states, and confirm that page caching does not inadvertently reuse one region’s price for another.
Measure the incremental outcome. Separate ordinary purchases, purchases using the member price, and loyalty registrations where your systems support those distinctions.
Localized loyalty incentives could improve conversion or program enrollment, but a limited beta does not establish that result for every merchant. Treat it as an experiment with a dependable fallback, not as the foundation of your shopping strategy. The durable advantage is the infrastructure: reliable regional data, explicit eligibility, and a landing page that can honor the offer it receives.
Key takeaways: diagnose the layer that failed
A blended return figure can tell you that performance changed without telling you why. Diagnose ecommerce visibility in the order a shopper and a commerce system encounter it:
No eligible visibility: Inspect feed approval, product identity, availability, price, region, and loyalty eligibility before changing bids.
Impressions without qualified clicks: Rework the title, primary image, visible offer, and product differentiation. The listing may be eligible but unconvincing or poorly matched.
Clicks without shopping progress: Check whether the page preserves the product, variant, price, region, and member conditions presented before the click.
Shopping activity without purchases: Inspect the transition from product selection to checkout and identify any condition or cost that appears later than the original offer.
Revenue without acceptable economics: Move from campaign-level return to SKU-level revenue and costs. Do not let profitable products conceal products that lose money as spend grows.
Direct sales without broader discovery: Review whether social and AI shopping activity is expanding the audience, customer list, comparisons, and later demand rather than judging it only by last-click orders.
Your dashboard should preserve those layers. Keep eligibility and visibility metrics separate from conversion and profit metrics. Break the useful views down by SKU or product family, channel, campaign, and region where the data supports that detail. A tool such as Sellerboard can connect revenue and costs at the SKU level, but the tool matters less than the decision the dashboard exposes.
Do not force all platforms into an identical attribution story. Amazon can provide keyword- and market-level transaction reporting. Google PMax depends on the conversions your store sends back. Social may contribute through awareness, audience building, and remarketing. AI shopping may influence product discovery and comparison without receiving the final click. Keep a visibility diagnostic for those channel-specific signals and a separate economic scorecard for orders, revenue, and trusted costs.
Choose one commercially important product family this week. Trace it through the feed, visible page content, structured data, PMax segmentation, marketplace offer, regional rules, and SKU dashboard. Fix the earliest inconsistency you find. Once that layer is dependable, the next budget decision becomes much easier to defend.
