[ ← All guides ]Tracking · Privacy

root@ecombender:~$ cat guides/23-shopify-consent-mode-server-side-tracking

Shopify Consent Mode v2 + Server-Side Tracking (and Why Conversions Drop After a Checkout Change)

Two Shopify changes tend to collide. You add a consent banner, or Google asks for Consent Mode v2, and conversion volume moves. Then you upgrade checkout or the thank-you page, and purchase tags quietly stop firing. The fix is not a new bid strategy. It is a consent signal that reaches Google, a purchase event that still fires after checkout, and a server-side setup that does not invent consent it never received.

Reading time: 17 min · Tools: Shopify Customer privacy, Customer events, Google tag / Tag Manager, optional server-side tagging, Tag Assistant

The short version

What Consent Mode v2 actually sends

Google’s Consent Mode lets tags adjust their behavior based on the visitor’s choice in your banner. The November 2023 update, which Google documents as Consent Mode v2, added two parameters: ad_user_data for sending user data to Google for advertising purposes, and ad_personalization for personalized advertising. You still also send ad_storage and analytics_storage.

Google’s EEA consent-mode update says advertisers who receive data from end users in the European Economic Area need to collect consent and share those signals in order to keep using applicable tags and SDKs for measurement, ad personalization and remarketing. Check Google’s current EU user consent policy for the exact regions and products that apply to your account. Do not assume a banner that only blocks cookies is enough if it never updates the Google tag.

ad_storage Ad cookies Storage for advertising analytics_storage Analytics Storage for analytics ad_user_data User data Added in v2 for ads data ad_personalization Personalization Added in v2 for remarketing
Figure 1: If your banner only sends the two older signals, you are not on Consent Mode v2 yet.

A Shopify-friendly setup

  1. In Shopify, review Customer privacy and the cookie banner or your CMP. The banner has to collect the choices you need, and those choices have to be written into Google’s consent API — either by a Google-certified CMP, Shopify’s consent tools if they are connected to your tags, or a carefully maintained custom integration.
  2. Set a default consent state before any Google tag sends measurement data, then update it when the shopper chooses. Google’s developer guide stresses that order. A default of denied with no later update looks like “almost nobody consents,” even when people clicked Accept.
  3. Prefer region-specific defaults where you actually show a banner, so you do not apply an EEA default to traffic that never sees the prompt. Google documents region-specific consent defaults for this reason.
  4. Confirm the four v2 parameters in Tag Assistant or Ads conversion diagnostics. Google surfaces consent-mode status in conversion diagnostics after it is implemented.
  5. If you use server-side tagging or a first-party tag gateway, pass the same consent state to the server container. Do not have the browser honor a denial and the server fire a full purchase hit anyway.

Google describes basic and advanced implementations. In a basic setup, tags wait until the visitor chooses. In an advanced setup, tags can load in a denied state and send more limited pings, which Google can use for modeled measurement. The right choice is a legal and company-policy decision, not a trick to recover a number. If you use modeled conversions, treat them as a modeled estimate, not as a second set of real checkout receipts.

Server-side does not mean “no consent”

Moving the Google tag behind your domain, or through a server container, can make delivery more reliable and keep more measurement in a first-party context. It does not let you ignore a denied signal. Build the server path so consent is an input, then test both an accepted and a declined journey.

Banner / CMP Shopper choice Web tag / pixel Consent update Server / Ads Same state
Figure 2: The chain is only as strong as the step that drops the signal. A polished server container cannot fix a banner that never updates the tag.

When conversions drop after a checkout change

Shopify has moved checkout, thank-you and order-status customizations toward Checkout Extensibility and Customer events. Older “additional scripts,” theme checkout code and some app hooks can stop running when you upgrade those pages. The store still takes orders. Google Ads simply never hears about them.

Work the diagnosis in this order so you do not rebuild tracking twice:

  1. Prove the gap. Compare paid-ad conversions in Google Ads with paid-channel orders in Shopify for the same dates. If Shopify still has the orders and Ads does not, it is a measurement break, not a demand break.
  2. Check the page that used to fire the tag. Place a test order and watch the thank-you and order-status pages with Tag Assistant. If the Google tag never loads, the checkout change likely removed the old script.
  3. Move purchase tracking to Customer events. Shopify’s pixels and custom-pixel help is the official replacement path: a custom or app pixel that subscribes to events such as checkout_completed, rather than leftover additional scripts. Shopify also documents pixel migration for this reason. Remove the old script so you do not later get duplicates.
  4. Recheck consent on the new checkout. A new checkout or thank-you domain can drop the banner’s update, default everything to denied, or load the tag before the update runs. Google warns that updates must happen on the page where the choice is made, and that an update fired during unload can be lost.
  5. Only then debug server-side. Look at whether the server container received the event, whether the conversion ID is still correct, and whether consent arrived with the event. A container that was pointed at the old checkout path will go quiet after an upgrade even if the web pixel looks fine in preview on the homepage.
Orders still arrive in Shopify, not in Ads? 1. Compare order counts for the same day 2. Test purchase: does the Google tag load after checkout? 3. Is the pixel on Customer events, not old checkout scripts? 4. Does consent update on the new page, then reach the server? 5. Only after that, rewrite the server container or gateway
Figure 3: Most “the algorithm broke” tickets after a checkout upgrade are a tag that never fired. Illustration, not a live screenshot.

Do not change the bid strategy, the consent default and the server endpoint on the same afternoon. Fix the purchase event first, confirm a test order appears in Ads (allowing for processing delay), then tighten consent and server-side delivery. If you sell into the EEA, keep a declined-consent test in the regular QA, not only an accept-all test from the store’s home country.

FAQ

What is new in Consent Mode v2?

Google added two parameters on top of ad_storage and analytics_storage: ad_user_data (consent to send user data to Google for advertising) and ad_personalization (consent for personalized advertising). For EEA traffic, Google says you need to collect consent and pass those signals if you want to keep using applicable tags for measurement, ad personalization and remarketing.

Will server-side tracking replace the need for consent?

No. A server container still has to honor the visitor’s consent. If the web pixel or tag does not send a consent state, or always sends granted, you can both under-count and over-collect. Server-side tagging can improve first-party delivery and resilience; it does not bypass Consent Mode or your privacy obligations.

We upgraded Shopify checkout and Google conversions fell. What should we check first?

Compare Shopify orders to Google Ads conversions for the same days, then look at the thank-you and order-status pages. Additional checkout scripts and older checkout customizations often stop running after Checkout Extensibility. Move purchase tracking into Customer events (custom or app pixels) on checkout_completed, confirm the consent banner still updates Google tags, and test a real order with Tag Assistant before you rewrite the whole server setup.

Go deeper

Tracking & Analytics: Server-Side 2026

The course covers first-party and server-side measurement for Shopify, including how to keep Google conversions accurate when checkout and consent tools change.

[ Open the course ]