Tag: GA4 attribution

For years, shopping on Google followed a familiar path: a search, a click, a visit to your store, a purchase. Your analytics were built around it. In late September 2026, part of that path moved. Eligible US Shopify merchants can now sell directly inside Google’s AI Mode and the Gemini app, where a shopper taps Buy and pays without ever opening the merchant’s website.

For merchants, the change is both an opportunity and a measurement problem. Sales can arrive from a surface where your tracking does not run. This piece sets out what was announced, who is affected, how to opt out, what the checkout supports and what it does not, and a decision framework for whether to leave it switched on. We have kept to what documentation and reputable reporting confirm, and flagged what is unclear.

What changed

On September 22, 2026, Search Engine Land reported that Google is notifying eligible Shopify merchants that their products can be bought directly in AI Mode in Google Search and in the Gemini app. The checkout runs on the Universal Commerce Protocol, an open standard Google developed with other companies, including Shopify, that lets AI agents interact with merchants and payment systems during shopping.

Two details deserve attention. First, merchants did not have to apply. Search Engine Land reports that eligible products are included automatically once a Shopify store is matched with its Google Merchant Center account, and Shopify’s help center confirms that direct checkout is on by default for eligible stores. Second, the rollout is gradual. Shopify says direct checkout is still rolling out to Google users and may not yet be available in every store, and Google’s own documentation, as quoted by ContentGrip, describes the program as “a phased program for select participating merchants”.

Who is eligible

Shopify’s help center lists the requirements. Your store must be based in the United States and sell to US customers. You need a valid Google Merchant Center account and must meet Google’s requirements, including its free listing eligibility and return policy rules. Your products must be available in Merchant Center, either through Shopify’s Google and YouTube sales channel with product and shipping sync turned on, or through a third-party feed provider or manual upload. Products must also be eligible for Shopify Catalog, you must agree to the Shopify Agentic Storefronts Supplemental Terms of Service, and your terms of service, privacy policy and refund policy must be completed in your Shopify settings.

Direct checkout is shown only to US-based shoppers.

There is no extra fee. Shopify states that you pay only your standard payment processing fees. Merchants also keep the underlying customer and order relationship, according to Search Engine Land, and the retailer remains the seller of record, according to Google’s documentation as cited by ContentGrip.

How to opt out

If you want shoppers to complete purchases on your own site, Shopify’s help center gives these steps. In the Shopify admin, go to Sales channels, then Agentic. Deactivate the setting called Allow Shopify to manage for me. Click Google AI Mode and Gemini. Switch Direct checkout off, then click Save.

Opting out does not remove you from AI Mode. Your products can still appear in results, but shoppers are redirected to your online store to complete the purchase.

What direct checkout supports, and what it does not

The in-AI checkout is not an exact copy of your store’s checkout. Shopify’s documentation sets out the gaps.

Supported: automatic discounts and discount codes, and Shopify Functions for shipping, discounts and cart and checkout validation.

Not supported: subscriptions, product bundles, customizable products and B2B-only products. Local delivery, in-store pickup and pickup points. Requiring customers to sign in before checkout. Only a subset of accelerated checkout options. Many checkout blocks, including upsells, loyalty and rewards blocks, consent collection blocks, chat blocks and trust badges, may not display, so the checkout can look different from your own. Shopify also asks that required legal disclosures appear within the first 6,000 characters of a product description.

Why this is a measurement problem

Shopify’s help page states plainly that “Google Analytics and custom pixels won’t fire” in direct checkout. Only server-to-server pixel events fire, and only two of them: checkout started and checkout completed.

Your analytics tag, ad platform pixels and attribution tools all depend on code running in the shopper’s browser on your site. When the purchase happens inside Google’s surface, that code never loads. The sale is real, but the session your tools normally record does not exist on your side.

Three practical consequences follow.

Revenue can be undercounted in tools that rely on client-side tracking. If you compare Google Analytics revenue with Shopify order totals, a widening gap may be this checkout, not a tracking bug.

Channel reporting can shift. Because the journey no longer includes a visit to your site, orders may not be credited the way you expect. Shopify’s page does not describe how these orders are labeled in your admin or reports, and we found no authoritative source that does, so treat any confident claim about it with caution.

Funnel analysis loses steps. These buyers generate no product page views, add-to-cart events or checkout steps on your site, so a shift in conversion rate could reflect where people buy, not how well your pages convert.

The practical answer is to reconcile against Shopify’s own order data, which records the purchase wherever it happens, and to stop treating the browser-side analytics tag as the only source of truth for revenue.

What is still unclear

Some claims in circulation should stay out of your planning until they are confirmed. Some coverage repeats specific review thresholds, such as a minimum number of reviews and a minimum star rating. Those figures relate to Merchant Center’s store ratings rules for showing ratings with ads, and we could not confirm that they are conditions for this checkout. Shopify’s eligibility list above does not include them.

Reports of a separate, wider default-on rollout of agent checkout across Shopify, including a figure of about one million merchants, rest on thin sourcing, so we have not relied on them.

Finally, there are open questions on reporting: how these orders are labeled, what Google will offer in Merchant Center for AI surface performance, and how consent settings apply. Recheck the documentation before committing.

Opt in or opt out: a decision framework

There is no single right answer. It depends on what you sell and how you measure it. Use these questions.

Do you sell subscriptions, bundles, customizable items or B2B-only products? If these make up a large share of revenue, the AI checkout cannot handle them, and keeping the feature on mainly matters for your simpler products.

How much of your profit comes from checkout upsells or loyalty features? If the answer is a lot, redirecting shoppers to your own checkout protects that revenue.

How dependent is your reporting on client-side tracking? If your team, or your agency, cannot trust revenue numbers without it, you may prefer to opt out until your reporting is ready.

Do you want to learn? Some merchants will reasonably leave it on for a few weeks and compare Shopify order data with previous periods, as long as they set a review date.

For most stores, a good default is to keep the feature on for a defined trial period if your product mix is mostly simple, one-time purchases, and to switch it off if subscriptions, bundles or upsells drive revenue.

What to do this week

Open the Agentic section in Shopify and see whether direct checkout is on for your store.

Review your Merchant Center feed and your Shopify policies. Product discovery in AI Mode is powered by Merchant Center, so missing attributes, mismatched prices or incomplete return policies can limit what shows up.

Check product descriptions for legal disclosures in the first 6,000 characters.

Place a test order if possible and see how it appears in Shopify and in your analytics.

Reconcile weekly. Compare Shopify order totals with analytics revenue.

Why this matters for visibility

This checkout sits at the end of a discovery path, and the path begins with product data. Shopify’s documentation says product discovery in AI Mode is powered by Google Merchant Center, so a store whose data is complete and consistent has a better chance of being shown. That is where search engine optimization, generative engine optimization and answer engine optimization meet ecommerce: accurate titles, complete attributes, clear policies, authentic reviews and consistent information across your site and your feed.

The checkout does not change the basics. It raises the stakes on them, because a recommendation in an AI answer can now turn into a sale without a visit to your site. For brands that want to understand how they appear in these answers before deciding how to respond, an AI Visibility Audit is a sensible starting point, because you cannot manage what you have not measured.

Where this leaves you

The confirmed facts are these. Google and Shopify have enabled a native checkout in AI Mode and the Gemini app for eligible US Shopify merchants, powered by the Universal Commerce Protocol. It is on by default for eligible stores and can be turned off in the Agentic settings. Merchants keep the customer and order relationship. Google Analytics and custom pixels do not fire, and only server-to-server started and completed events are sent. Several features, including subscriptions and bundles, are unsupported.

The response is a decision, not a panic. Check your setting, choose deliberately, protect what depends on your own checkout, and measure through Shopify’s order data while your reporting catches up. Strong search engine optimization, generative engine optimization and answer engine optimization all start with clean product data, either way.

Frequently Asked Questions

1. Is Google’s AI Mode checkout turned on for my Shopify store?
If your store is based in the US, sells to US customers and is matched with a valid Merchant Center account, it is likely eligible, and Shopify says direct checkout is on by default for eligible stores. The rollout is gradual, so check Sales channels, then Agentic, in your Shopify admin.

2. How do I opt out of direct checkout in AI Mode?
In Shopify admin, go to Sales channels, then Agentic. Deactivate Allow Shopify to manage for me, click Google AI Mode and Gemini, switch Direct checkout off and save. Your products can still appear, but shoppers are sent to your online store to buy.

3. Do I still own the customer and the order?
Search Engine Land reports that merchants keep the underlying customer and order relationship, and Google’s documentation, as cited by ContentGrip, says the retailer remains the seller of record. Shopify charges no extra fee beyond standard payment processing.

4. Will Google Analytics track these purchases?
No. Shopify’s help page says Google Analytics and custom pixels do not fire in direct checkout. Only server-to-server started and completed events are sent. Use Shopify’s order data to reconcile revenue.

5. Which products and features does the AI checkout not support?
Subscriptions, bundles, customizable products and B2B-only products are not supported, nor are local delivery, pickup or required sign-in. Many checkout blocks, such as upsells, loyalty and consent blocks, may not display.

6. Do I need 100 reviews and a 3.5 star rating?
We could not confirm that. Those figures relate to Merchant Center store ratings for ads and are not on Shopify’s eligibility list.

7. Should I leave it on or switch it off?
It depends on your product mix and your reporting. Stores with mostly simple, one-time purchases may reasonably test it for a defined period. Stores that rely on subscriptions, bundles, upsells or client-side tracking may prefer to opt out.

If you want to know how your brand and products show up across Google and AI answer engines, that is exactly what we look at in a free AI Visibility Audit.

On August 26, a Google spokesperson confirmed what SEOs had already been spotting in the wild since late June. Search result links are being rewritten to route through google.com/goto before landing on the actual destination page. Google’s stated reason was procedural: it said it regularly deploys technical measures to protect its services and users from evolving abuse. This sits alongside a separate legal fight, Google’s suit against SerpAPI, first filed in July and amended in August, over how that company accesses Google’s search results.

That much is confirmed. What happens after that point, in coverage of this story, splits into two very different camps, and it is worth being precise about which claims are actually settled and which ones are not before you act on either.

What actually changed, mechanically

Instead of a result linking straight to a destination page, the link now points to google.com/goto, with the destination URL encoded using Protocol Buffers, Google’s own binary data format. A server-side redirect on Google’s end then forwards the visitor to the real page. For a person clicking a result, nothing looks different. They click, they land where they expected. What changed sits entirely underneath that click, in a URL structure that any tool reading destination links now has to parse differently than before.

Third-party tools that read destination URLs directly took the first hit, and here the evidence is solid because the vendors themselves reported it. SerpAPI confirmed impact across several of its products. Ahrefs confirmed what it called a temporary inconsistency in its data. One rank-tracking vendor documented a real six-day window, August 26 through September 2, where its Share of Voice reporting misattributed clicks because its parser was not reading the new format correctly. That has since been fixed, with the affected data being backfilled for customers.

Not every tool broke the same way, and this is worth sitting with for a moment. SE Ranking and Semrush both confirmed no impact on their own position tracking data at all. So the blanket claim that the /goto redirect broke SEO tools is not quite accurate. Some tools broke. Others, reading the exact same search results pages, did not, which suggests the difference has more to do with how each vendor’s parser was originally built than with the redirect itself being universally disruptive.

Where the coverage actually splits

Here is where a real divide appears. Several sources treat GA4 organic-to-direct misattribution as an established, active problem, describing what one piece called “massive organic attribution data loss” and sudden, unexplained spikes in Direct traffic. That framing has spread fast, because it is the scariest possible read of a genuinely technical, genuinely unresolved situation, and alarming framing tends to travel faster online than careful, hedged framing ever does.

Now look at what the more carefully sourced coverage actually says. As of late August, one detailed technical write-up stated plainly that nobody had reported confirmed organic undercounting inside GA4. A separate analysis went further and ran an actual test across ten device and browser combinations, checking whether referrer data survived the redirect chain. It found the referrer stayed intact in every case, and GA4 correctly classified those sessions as Organic Search each time. Multiple outlets, working independently of each other, land on the same conclusion. Google has not confirmed a GA4 attribution impact, and the direct evidence gathered so far does not show one either.

None of that means the concern is baseless. The mechanism Google’s own documentation describes makes an attribution gap plausible in principle. If a redirect chain ever strips referrer data before it reaches your site, GA4’s fallback logic would file that session as Direct rather than Organic Search, silently, with no alert generated anywhere in your dashboard. That is a real risk worth watching closely. It is not the same thing as a confirmed, ongoing problem, and treating it as something that has already happened is exactly the kind of overstatement that risks needing a correction once more data actually comes in, one way or the other.

Why the distinction actually matters

It would be easy to read the last two sections and conclude the difference between disputed and confirmed is mostly semantic. It is not, and the practical stakes are worth spelling out.

If a team reacts to this as a confirmed GA4 problem, the natural response is to start second-guessing every organic traffic number reported for the past month, which burns real time reconciling data against a theory that current testing does not support. Budget conversations get harder to have with confidence when the underlying numbers are being treated as suspect without evidence. Reporting to a client or a leadership team gets shakier too, since telling a room that your organic numbers might be wrong because of a redirect Google has not confirmed affects attribution is not a comfortable thing to say out loud in a review meeting.

If a team instead treats this as a plausible, unconfirmed risk worth monitoring, the response looks completely different. You set a baseline, you watch two specific ratios over the following weeks, and you keep operating normally in the meantime rather than freezing decisions around a risk that has not actually materialized in the testing done so far. That is the more defensible position given what is currently known, and it is also simply less exhausting to maintain.

A second, less-discussed layer

There is a second angle here that is easy to miss if you are only thinking about traditional search engine optimization reporting. Reports say /goto-wrapped URLs are starting to show up as cited sources inside ChatGPT, Perplexity, and Claude, wherever those systems pull from Google’s search results as part of answering a query. If a citation-tracking tool has the same blind spot rank trackers had in late August, before their parsers caught up, the same kind of silent misattribution could in theory apply to AI citation counts, not only to GA4 sessions.

Nobody has published confirmed data on this specifically yet either. It follows the same underlying mechanism, and the same caution about calling something confirmed before the evidence is actually in applies here just as much. This is precisely the kind of gap that generative engine optimization and answer engine optimization work now has to account for. Visibility inside an AI answer is only useful if you can actually measure it, and a measurement tool with an unpatched blind spot will quietly undercount exposure it should be reporting, in exactly the way several rank trackers briefly did in late August.

Setting a baseline instead of guessing

The sensible response to a disputed, plausible-but-unconfirmed risk is not to panic and it is not to ignore it. It is to set a baseline now, so that if this ever does show up in your own data, you catch it immediately instead of noticing it months later as an unexplained trend with no starting point to compare against.

Record this week’s ratio of Search Console clicks to GA4 organic sessions for your key properties, and write the number down somewhere you will actually revisit. Do the same for your current organic-to-direct traffic split. These two figures are your tripwire. If either one moves meaningfully in the weeks ahead with nothing else in your setup changing, that is your signal to look closer, rather than reacting to someone else’s alarmed blog post as though it were your own data.

Reconcile Search Console against GA4 weekly for the next month, instead of your usual monthly cadence. A real attribution gap, if one exists, would show up as a widening divergence between the two figures over time, not as a single dramatic jump you would notice immediately anyway.

Check your GA4 referral exclusion list for any new entries appearing as google.com/goto. If Google’s own redirect domain starts showing up there as a distinct referral source, rather than resolving cleanly through to Organic Search, add it to your exclusions so it does not fragment your organic channel into two separate, harder-to-reconcile pieces.

Hold off on reacting to a rank-tracker alert this week unless you have confirmed that specific tool already adjusted its parser to read the new /goto format correctly. Given that SE Ranking and Semrush reported no impact while SerpAPI and Ahrefs did, an alert from a tool that has not caught up yet is more likely a parsing problem on their end than an actual ranking change on your site.

And if you are already doing any AI visibility tracking, apply the same caution to what you see there. A cited source appearing as a raw /goto link rather than a resolved domain in your reporting is a sign your tool needs to catch up, not evidence that your underlying citation count has actually changed.

Where this leaves you

Google confirmed the redirect itself on August 26. It has not been confirmed, and the direct testing done so far does not support a GA4 attribution problem. Some SEO tools broke, others did not, and the ones that did have mostly already fixed their parsers by now. The plausible risk to your own analytics is real enough to baseline and monitor closely. It is not, as of this writing, a confirmed, active problem serious enough to justify the level of alarm some coverage is giving it, and treating an unconfirmed risk as settled fact is its own kind of mistake, one that tends to send teams chasing a problem that is not actually there yet while a genuinely useful baselining exercise gets skipped entirely.

Frequently Asked Questions

1. Is Google’s /goto redirect confirmed?
Answer: Yes. A Google spokesperson confirmed the rollout on August 26 and described it as a technical measure to protect Google’s services and users from evolving abuse. The rollout itself is not in dispute anywhere in the coverage. What remains unsettled is how far its effects reach.

2. Is my GA4 organic traffic being misattributed because of it?
Answer: Not as far as anyone has confirmed. Google has not acknowledged a GA4 attribution impact, and one technical test across ten device and browser combinations found referrer data stayed intact, with sessions classified as Organic Search. The risk is plausible in principle, so it is worth monitoring, but it is not a confirmed problem.

3. Why is my rank tracker showing odd data?
Answer: It depends on the tool. SerpAPI and Ahrefs confirmed some impact, with Ahrefs calling it a temporary inconsistency, while SE Ranking and Semrush confirmed none. Check whether your vendor has published a statement or a fix before assuming your rankings actually moved.

4. Does this affect AI citation tracking?
Answer: Possibly, but nothing is confirmed. /goto-wrapped links are reportedly appearing as cited sources in ChatGPT, Perplexity, and Claude. A tool that cannot parse them could undercount your citations. Treat any sudden citation drop as a possible tracking issue first, and verify it manually.

5. What should I check first?
Answer: Record this week’s ratio of Search Console clicks to GA4 organic sessions, plus your organic-to-direct traffic split. These two numbers are your baseline. If either shifts meaningfully with nothing else changing, investigate then.

6. How often should I reconcile Search Console and GA4?
Answer: Weekly for the next month, instead of monthly. A genuine attribution gap would show up as a widening divergence between the two over several weeks, not as a single sudden jump.

7. Should I change my SEO strategy because of this?
Answer: No. Nothing about the redirect changes how rankings are earned. Keep your strategy as it is, baseline your data, and update only if a confirmed impact emerges.

If you want a second set of eyes on whether your own reporting, or your AI visibility specifically, is being affected, that is exactly what we check in a free AI Visibility Audit.