Shopify and GA4: what's new for server-side tracking?

The relationship between Shopify and GA4 has changed considerably over the past few months.

Shopify has progressively deprecated some of the older methods used to add scripts to checkout and post-purchase pages, while Google has strengthened its native integration through the Google & YouTube app.

The result is a more centralised setup, where ecommerce events, Google Ads conversions and data coming from Shopify can be managed through an integration that is more stable than older implementations based on manually added scripts.

This is where server-side tracking comes in.

Some purchase signals can now travel directly between Shopify’s infrastructure and Google’s, reducing reliance on the browser.

At the same time, GA4 continues to collect the events needed to reconstruct the ecommerce customer journey through the native integration.

For ecommerce teams, the useful question is therefore understanding which data is arriving, where it comes from and how to avoid overlaps.

What changes with Google & YouTube on Shopify

To configure Shopify with Google Analytics 4, Google currently recommends the Google & YouTube app as the preferred implementation.

Once the GA4 property is connected, Shopify automatically sends several ecommerce events. Alongside existing events such as view_item, add_to_cart, begin_checkout and purchase, Google has expanded the set with events including view_item_list, remove_from_cart, view_cart and add_shipping_info.

This gives GA4 a more complete view of the journey between product discovery and purchase.

For Google Ads, there is also a second layer: Shopify’s integration with Google Ads Data Manager uses direct server-to-server communication to recover conversion signals linked to completed checkouts.

The distinction matters because "native Google integration" and "server-side tracking" describe different layers of the same ecosystem.

What server-side really means in this setup

With traditional tracking, a large proportion of events originate in the user’s browser.

This makes collection more exposed to browser restrictions, ad blockers, loading problems and other factors that can interrupt tag execution.

With the Data Manager integration, Shopify can send the completed checkout conversion directly to Google Ads alongside the signal collected by the Google tag. Google then deduplicates the two events before attribution.

This makes purchase data more resilient.

A dedicated server-side tracking setup through GTM Server has a different scope. In that scenario, the business manages its own server endpoint and decides which events to collect, transform and forward to GA4, Google Ads, Meta or other platforms.

The Shopify-Google integration is managed by the two providers and operates within a predefined framework. A dedicated server-side architecture provides a higher level of control over data flows.

GA4 and purchase: why transaction ID remains essential

When multiple systems can send information about the same order, deduplication becomes essential.

In GA4, the key parameter is transaction_id.

Google Analytics uses this identifier to recognise purchase events associated with the same transaction and reduce the risk of counting the same purchase twice.

Each order should therefore have a unique and consistent ID.

This is a technical detail with very practical consequences: if an old pixel, a GTM tag, a new integration and a third-party app continue sending the same event with different configurations, the data can diverge or become duplicated.

After any change to a Shopify GA4 setup, it is therefore worth checking the transaction_id, order value, currency and items being sent.

The issue with legacy Shopify tags

2026 has also marked the end of many legacy implementations.

Google has recommended moving tags to Google & YouTube following Shopify’s new checkout experience.

For Shopify Plus merchants, the deadline to upgrade the Thank you and Order status pages was 28 August 2025; for non-Plus stores, it was 26 August 2026.

That second deadline has just passed.

Scripts added through older methods such as checkout.liquid or Additional Scripts on post-checkout pages can therefore no longer be considered a reliable long-term solution.

This makes September a particularly useful time to review accounts that have accumulated several layers of tracking over the years.

An old integration left active alongside Google & YouTube can create duplicate measurement. A legacy configuration that has stopped working can instead leave gaps in the data.

Both scenarios lead to the same place: reporting that becomes harder to interpret.

Does server-side mean perfect data?

Server-side tracking improves the reliability of certain signals, particularly when the event comes directly from the system that records the order.

Attribution remains a separate issue.

Knowing with certainty that a purchase occurred does not automatically tell us which touchpoint generated the sale.

Accurate attribution still relies on information about the session, source, campaign, advertising identifiers, consent and the user’s previous journey.

This is where browser-side and server-side signals need to be read together.

The browser still plays an important role in understanding how the user reached the store and what they did before purchasing.

The server provides a strong signal that the transaction itself actually took place.

An effective setup connects these two parts clearly.

What to check in a Shopify GA4 setup today

For an existing ecommerce store, I would start with a few essential checks:

• make sure Google & YouTube is connected to the correct GA4 property;
• identify legacy tags, custom pixels or apps that still send purchase events;
• compare transaction_id, revenue and order volume between Shopify and GA4;
• review consent and Consent Mode configuration;
• check separately which conversions Google Ads uses for bidding.

The objective is to create a simple map: which system sends which event, and to which platform.

This is far more useful than trying to make Shopify and GA4 match down to the last penny. The two platforms use different logic, windows and purposes, so some discrepancy is normal.

Deduplication and double tracking: where the risk begins

Google itself recommends removing legacy tags when migrating to Google & YouTube and checking for duplicate conversion measurement.

This matters particularly for stores that have added GTM, custom pixels, analytics apps or scripts directly into checkout over the years.

The issue often comes from implementations that work correctly on their own.

When they coexist, they can send the same order more than once or use different parameters for the same transaction.

Moving to the new setup is therefore also an opportunity to simplify the tracking architecture.

Fewer redundant tags mean easier debugging, clearer responsibilities and a better understanding of where discrepancies originate.

When a dedicated server-side setup still makes sense

For many stores, the native Shopify-Google integration already provides a strong foundation for GA4 and Google Ads.

A dedicated server-side project becomes valuable when tracking needs to cover multiple platforms, markets or custom requirements.

It can be useful when the same framework needs to connect GA4, Google Ads, Meta Ads, CRM and other first-party sources, or when greater control is required over the parameters being sent, data transformations and consent governance.

In these cases, working with a dedicated server-side tracking architecture makes it possible to design data flows around the ecommerce business’s measurement objectives.

For a Shopify store, the question is therefore how much the native integration can cover and where a more advanced configuration becomes necessary.

Shopify, GA4 and attribution: which data should you look at?

One of the most interesting consequences of this change concerns the relationship between analytics data and advertising data.

Shopify is the transactional source: it records the order.

GA4 reconstructs user behaviour and the journey according to its analytics model.

Google Ads attributes conversions to advertising interactions according to its own rules and uses those signals for bidding.

These numbers can be close without matching perfectly.

A good setup aims for data that is consistent enough to support reliable decisions, while also making the main differences between platforms understandable.

Server-side signals help reduce part of the signal loss.

The final quality still depends on implementation, consent, tagging and conversion configuration.

Shopify and GA4 need a cleaner tracking setup

In 2026, the integration between Shopify and Google Analytics 4 has become more centralised, while server-side signals are playing a growing role in purchase measurement across the wider Google ecosystem.

For ecommerce businesses, the main advantage is greater data resilience.

The priority now is to bring order to the setup: review Google & YouTube, remove redundant legacy implementations, check transaction_id, and understand which events travel through the browser and which rely on server-side integrations.

From there, the business can assess whether the native setup is sufficient or whether a more advanced infrastructure is required.

Because tracking quality increasingly depends on the consistency of the system connecting the data, rather than on how many tags have been installed.