How to Set Up Google Ads Dynamic Remarketing on Shopify When Your Events Run Server-Side

TL;DR

On a store running WeltPixel Conversion Tracking, Google Ads gets each order's total and nothing about the products in it, and the app loads no Google Ads tag on your storefront. The product side of remarketing has to come from somewhere else, and there are two candidates. The Google & YouTube channel's tag sends product IDs with product views and adds to cart, by Google's own reference [6]. GA4 gets the same kinds of events from the app's server, tagged with the shopper's own GA4 browser ID, and Google says GA4 can pass product IDs to Google Ads [1]. Google documents each part of that second route and not the joint between them, so treat it as a set of switches plus a check.

Key Takeaways

• If the Google & YouTube channel's tracking is on your storefront, use its tag; Google lists the product IDs it sends with view_item and add_to_cart [6].
• If you removed the channel's tracking, the GA4 route needs four switches: product events on in the app, Google Ads linked with Enable Personalized Advertising, Google signals on, and a Merchant Center feed [1][5].
• Event IDs must equal the feed's id, item_group_id or display_ads_id [4]. On the free plan, GA4 gets variant IDs.
• A visitor whose consent denies ad_personalization adds no remarketing data on either route [8].
• Keep one purchase action counting in Google Ads and one sender per GA4 property.
• Finish tag and app changes by about November 13, and allow up to two days for GA4 lists to reach Google Ads [1].

What reaches Google from a store whose events run server-side?

Two Google products get two very different things. This is how the app delivers them today:

The Google Ads column is why "does dynamic remarketing work with your app?" is a question we see in support, and why it has no one-line answer. The upload the app sends Google Ads is built for conversions, with fields such as value, currency, order ID and click IDs. Google's dynamic remarketing reference asks for events such as view_item and add_to_cart that carry item objects, with id marked Required [4]. An order total can't supply that.

The GA4 column is different. Product views and adds to cart travel from the app's server through GA4's Measurement Protocol, but each one is tagged with the client ID the shopper's Google tag set in their browser, so it lands on the same visitor the tag built. That's the setup Google describes for the protocol: it exists "to augment automatic collection through gtag", and "Same device remarketing is supported when Google signals is turned on" [2]. So the old line that server-side tracking can't do remarketing doesn't hold on this store. What's still open is the product detail.

Route 1: the Google & YouTube channel's tag

Google keeps a reference page for exactly this tag, last updated July 28, 2026: "The Google & YouTube app helps automatically send important events and parameters for Google tags" [6]. On view_item it lists items[].id, items[].variant_id, ecomm_prodid and ecomm_pagetype set to "product"; on add_to_cart, ecomm_prodid and ecomm_pagetype set to "cart" [6]. That's the shape Google's dynamic remarketing page asks for, which says "You should always pass at least one item object" [4]. Google's parameters page never uses the words "dynamic remarketing", though, so treat it as a list of what the tag sends, and confirm the rest in Google Ads.

Shopify's side is thin. Shopify's channel pages we read on October 13, 2026, including the overview [11], don't mention remarketing, and the overview says "The Google & YouTube sales channel is managed by Google" [11]. Google's documentation is the only source here.

Linking Google Ads through the channel also creates conversion actions. Google says "a purchase conversion action is created automatically in Google Ads, and set as the account default", while Add to cart, View item and four others are "secondary conversion actions, which are included for observation only and don't affect bidding" [7]. Leave those secondary actions alone. The purchase is the one to watch: if the app also uploads purchases to Google Ads, two actions now count the same order, and only one should be primary. Running a tracking app alongside the Google & YouTube channel covers that choice, and which Google Ads conversion action should count as primary covers why it matters for bidding.

Route 2: GA4, documented in two parts

The first part is on Google Analytics' remarketing page. "This feature allows advertisers to transfer dynamic attributes, such as product IDs or price values, directly to Google Ads for dynamic remarketing campaigns", which "eliminates the need to manually define and map parameters" [1]. The second part is the Measurement Protocol sentence above: server-sent events can take part in same-device remarketing when Google signals is on, and "For cross-device remarketing, a User ID is required" [2].

The joint between them is missing. We read Google's GA4 remarketing page and both Measurement Protocol pages on October 13, 2026, and none of them says whether the item IDs on an event sent through the protocol are among the dynamic attributes GA4 passes to Google Ads. Nobody outside Google can tell you that from the documentation, so switch the route on and test it. Switching it on costs nothing: GA4 is on every plan of the app.

The switches, in the order you'd flip them:

1. Product events on in the app. Keep product views and add to cart switched on for GA4. A store that picked the Minimal event tracking preset during setup sends GA4 only checkout and purchase events, so there's nothing to remarket on.
2. Google Ads linked to GA4. In GA4 Admin, link the Google Ads account and select Enable Personalized Advertising. Google adds: "You must enable ads personalization to share web event data to the linked Google Ads account" [1].
3. Google signals. Google's setup page asks for "Google Signals" or "User-provided data collection" [1], so switch one on, and since the protocol page names Signals for server-sent events [2], Signals is the one to pick here. Since June 15, 2026, Signals no longer gates ads identifiers on its own; Consent Mode does [9], as the June 2026 GA4 consent change explains. User-provided data collection is Google's other listed option.
4. A Merchant Center feed Google Ads can use. Google: "data passed via retail events and parameters can only be used in conjunction with a Merchant Center product feed" [4]. The campaign itself runs on responsive display ads [5].

Which Google Ads dynamic remarketing route fits your store?

Lead with the route whose product IDs Google documents. The GA4 route earns its place on stores where the channel's tracking is gone.

If you've ever clicked through Google Ads' Tools > Shared library > Audience manager and stopped at "Collect specific attributes or parameters to personalize ads" [10], wondering what code it wants on a Shopify store, the table is the answer: neither route needs you to paste a Google Ads tag into your theme.

Where each route breaks without an error

IDs. Google matches the event's id against the feed's id, item_group_id or display_ads_id [4]. On the free plan the app sends GA4 the variant ID; Product ID and SKU are Plus options in its "Product identifier sent in events" setting, and Google Ads has no entry there because it gets no items. Reading your feed and picking the matching option is the guide to making your product IDs match your ad catalogs.

Consent. With ad_personalization denied, Google says remarketing in Google Ads won't receive data [8]. That applies to both routes. In the app, browser events respect Shopify's Customer Privacy API signals: Google's tag doesn't load until analytics consent allows it. GA4's product events only exist for visitors whose analytics consent allows them. For events sent through the protocol without a consent field of their own, Google says GA4 "uses the consent settings from corresponding online interactions for the client" [3].

The purchase, counted once. Route 1 only, covered above.

Two senders in one GA4 property. If the channel's GA4 connection and the app both point at the same property, GA4 gets two copies of every event, and audiences built on event counts inherit the doubling. Pick one sender per property; the coexistence article linked above shows how to spot it.

How do you check that product IDs arrived?

1. In the app's Advanced Settings, turn on Enable Debug Mode. Open GA4 DebugView (the DebugView walkthrough shows where), view one product on your store, and expand view_item. Read the item_id.
2. Open the same product in Merchant Center and compare that value with its id and item_group_id. One of them should match exactly.
3. Build a GA4 audience of product viewers and read the Google Ads estimate in the audience builder, as our GA4 predictive audiences guide walks through. Google says lists can take "up to two days" to reach Google Ads [1].
4. In Google Ads, open Audience manager and read the list's size once it appears.

The Google pages we read on October 13, 2026 describe no report that shows which source supplied an audience's product IDs. For the channel route, the parameters page [6] is the reference, and step 4 shows whether the list fills.

Audiences need lead time before Black Friday on November 27, and tag and app changes belong before the freeze: "Checkout, theme, and app changes: complete by around November 13", per the Black Friday tracking freeze calendar and our BFCM readiness page.

FAQ

Can a Shopify store with server-side tracking run Google Ads dynamic remarketing?

Yes on the channel's tag route: Google lists the product IDs that tag sends [6]. On the GA4 route, the app's server-sent product events share the browser ID of the Google tag on your storefront, and Google documents both parts of that route but not whether item IDs make the trip, so switch it on and check the audience [1][2].

Does WeltPixel Conversion Tracking send product IDs to Google Ads?

No. The app uploads purchases to Google Ads with the order total, currency, order ID and click IDs among its fields, and no product list. The only product-level data it sends Google goes to GA4.

Do I need google_business_vertical for Shopify dynamic remarketing?

Google marks it Recommended, with the value "retail", and marks id Required [4]. It belongs to a Google Ads tag you install yourself [4]; Google's list for the channel's tag doesn't include it [6], and the GA4 route needs no manual mapping [1].

Is Google signals still required for remarketing?

Google's setup page still asks for Google signals or user-provided data collection [1], and its Measurement Protocol page names Signals [2], so switch Signals on. Since June 15, 2026, Consent Mode is the control for ads identifiers [9].

See which Google products get your product events

WeltPixel Conversion Tracking sends GA4 your product views, adds to cart and checkout steps from its server on the shopper's own GA4 browser ID, on every plan (the free plan covers up to 100 storefront orders a month), and uploads purchases to Google Ads on Plus at $39/month [12]. See your product views land in GA4, then switch on the remarketing route that matches.

Sources

1. Google Analytics Help, "Enable remarketing with Google Analytics data", support.google.com/analytics/answer/9313634, accessed October 13, 2026
2. Google Analytics developer documentation, "Measurement Protocol (Google Analytics 4)" overview, last updated June 8, 2026, developers.google.com/analytics/devguides/collection/protocol/ga4, accessed October 13, 2026
3. Google Analytics developer documentation, Measurement Protocol reference (consent), developers.google.com/analytics/devguides/collection/protocol/ga4/reference, accessed October 13, 2026
4. Google Ads Help, "Dynamic remarketing events and parameters", support.google.com/google-ads/answer/7305793, accessed October 13, 2026
5. Google Ads Help, "About dynamic remarketing", support.google.com/google-ads/answer/3124536, accessed October 13, 2026
6. Google Tag Platform documentation, "Shopify event parameters", last updated July 28, 2026, developers.google.com/tag-platform/gtagjs/reference/shopify-event-parameters, accessed October 13, 2026
7. Google Merchant Center Help, "Understand the conversion actions tracked in Google Ads", support.google.com/merchants/answer/15457737, accessed October 13, 2026
8. Google Tag Platform documentation, "Consent mode overview", last updated July 30, 2026, developers.google.com/tag-platform/security/concepts/consent-mode, accessed October 13, 2026
9. Google Analytics Help, "Updates to Google Analytics Data Controls", support.google.com/analytics/answer/17016975, accessed October 13, 2026
10. Google Ads Help, "Tag your website for dynamic remarketing", support.google.com/google-ads/answer/3103357, accessed October 13, 2026
11. Shopify Help Center, "Google & YouTube" sales channel overview, help.shopify.com/en/manual/online-sales-channels/google, accessed October 13, 2026
12. WeltPixel Conversion Tracking, Shopify App Store listing (free plan; Plus $39/month), apps.shopify.com/weltpixel-conversion-tracking, accessed October 13, 2026