Your Google Ads dynamic remarketing campaign is live. The budget is running. But the ads are serving blank product images — or worse, showing products the user never looked at. The culprit in WooCommerce is almost always a product ID mismatch: your tag sends the WordPress post ID, Google Merchant Center uses the SKU, and Google can’t connect the two.
This is called an ecomm_prodid mismatch, and it kills dynamic product ads silently. No error. No alert. Just blank ads and wasted spend.
The Dynamic Remarketing Tag for WooCommerce — What It Actually Does
Google Ads dynamic remarketing works by tagging every page visit with two variables: ecomm_prodid (the product ID) and ecomm_pagetype (the type of page). When someone views a product, Google logs that product ID against their visitor profile. When they later browse the web, Google looks up the product ID in your Merchant Center feed and pulls the correct image, title, and price for the dynamic ad.
The whole chain depends on one thing: the product ID in your tag must exactly match the product ID in your Merchant Center feed.
WooCommerce breaks this by default. Most implementations — whether through GTM, a plugin, or Google’s own Site Kit — use the WordPress post ID as ecomm_prodid. But Merchant Center feeds typically use the product SKU, or a prefixed custom ID like WC-123, or whatever your product feed plugin outputs. The IDs never match, and Google silently fails to look up the product.
The Two Root Causes
Root Cause 1: Product ID Format Mismatch
WooCommerce products have multiple IDs. A product might have WordPress post ID 4821, SKU SHIRT-BLU-L, and a Merchant Center feed ID WC-4821. Your remarketing tag likely sends 4821. Your feed has WC-4821. That leading prefix is enough to break the match completely.
The fix requires knowing exactly what ID format your Merchant Center feed uses — and then configuring your tag to send that same format. If your feed uses SKUs, your tag must send SKUs. If your feed uses custom IDs, your tag must send custom IDs.
There’s no universal right answer. The right answer is whatever your feed uses.
Root Cause 2: Wrong ecomm_pagetype Values
The ecomm_pagetype variable tells Google where in the funnel a visit occurred. Correct values are: home, category, product, cart, purchase, and other. Most WooCommerce implementations either set a hardcoded other everywhere, or fire the wrong type on WooCommerce’s non-standard page structure.
A wrong ecomm_pagetype corrupts your audience segmentation. Your cart-abandonment list ends up mixed with general browsing. Your purchase-intent list includes people who just visited the homepage. The dynamic ads serve to the wrong audiences at the wrong stages.
According to Google Ads Documentation (2025), Performance Max campaigns depend on high-quality audience signals — poor remarketing tag data directly degrades Smart Bidding performance. This isn’t a cosmetic problem. It costs you in every auction.
You may be interested in: Performance Max Can Now Show You Where Your Budget Went — That Doesn’t Mean the Problem Is Solved
How to Diagnose the Problem
The fastest diagnostic tool is Google Tag Assistant Legacy (Chrome extension). Visit three page types on your WooCommerce store: a single product page, the cart, and the order confirmation page. For each, look at what value is being sent as ecomm_prodid.
Then open your Google Merchant Center and check the ID format in your product feed. They must match exactly — same format, same prefix rules, case-sensitive.
While you’re in Tag Assistant, also verify these ecomm_pagetype values:
- Product page →
product - Cart page →
cart - Order confirmation (/order-received/) →
purchase - Shop/category pages →
category
If any of these are wrong, your remarketing audiences are polluted — even if the product IDs match perfectly.
The Ad Blocker Problem on Top of Everything Else
Even after you fix the ID mismatch, you’re still running a browser-based tag. 31.5% of global users run ad blockers (Statista, 2024) that block Google’s gtag.js from executing entirely. Let that sink in. A third of your visitors — including the high-intent product viewers you most want to remarket to — are invisible to your remarketing lists.
This isn’t a minor data gap. It’s a systematic exclusion of a significant portion of your potential audience. 43.5% of all websites run on WordPress (W3Techs, 2024), which means this problem affects a substantial share of global ecommerce. And 68% of multi-touch attribution models over-credited digital channels in 2025 precisely because of this kind of data gap (MarTech Series, 2025). Your remarketing lists look smaller and less engaged than they actually are.
Server-side tracking recovers up to 30% more conversion signals compared to browser-only tracking (SweetCode, 2025). That’s 30% more accurate audience data feeding back into your dynamic remarketing campaigns.
You may be interested in: The Google Ads Conversion Lag Problem: Why WooCommerce Store Owners Keep Pausing Campaigns Too Early
The Server-Side Fix
Here’s the thing: both problems — the ID mismatch risk and the ad blocker invisibility — are solved by the same architectural change. When your tracking runs server-side on your own subdomain, the tag fires reliably regardless of browser-side blocking, and you control exactly which product ID format gets sent.
Transmute Engine™ is a first-party Node.js server that runs on your subdomain (e.g., data.yourstore.com). The inPIPE WordPress plugin captures WooCommerce events — including product page views, cart updates, and purchases — and sends them via API to your Transmute Engine server, which then formats and routes each event to Google Ads with the correct product ID format and pagetype values. No browser required. No ad blocker interference.
Key Takeaways
- Product ID mismatch is the leading cause of blank or wrong dynamic remarketing ads — check your tag’s
ecomm_prodidagainst your Merchant Center feed ID format exactly - Wrong ecomm_pagetype values corrupt audience segmentation even when product IDs are correct — verify all six page types
- 31.5% of users block Google’s tag (Statista, 2024) — your remarketing lists are systematically incomplete if you rely on browser-side firing only
- Performance Max Smart Bidding degrades directly when audience signals are poor (Google Ads Docs, 2025) — this is a campaign performance problem, not just a reporting problem
- Server-side tracking solves both the data loss and the format control problem simultaneously
The most common cause is a product ID mismatch. WooCommerce sends the WordPress post ID to the remarketing tag, but Google Merchant Center uses a different identifier — typically the product SKU or a custom ID like a ‘WC-‘ prefix. When these IDs don’t match, Google can’t map the tag signal to the correct product feed entry, resulting in blank or wrong ads.
ecomm_prodid mismatch occurs when the product ID passed in the Google Ads remarketing tag doesn’t match the ID format used in your Google Merchant Center product feed. Google uses this ID to look up which product to display in a dynamic ad. If the lookup fails, the ad either shows nothing or falls back to a random product.
Install Google Tag Assistant Legacy (Chrome extension) and visit a product page, cart page, and order confirmation page. For each, check the ecomm_prodid value being sent and compare it to the IDs in your Merchant Center feed. Also verify that ecomm_pagetype is set correctly — ‘product’ on product pages, ‘cart’ on cart pages, and ‘purchase’ on the thank-you page.
Yes. 31.5% of users globally run ad blockers (Statista, 2024), and most block Google’s gtag.js entirely. This means your remarketing lists are systematically missing a third of your visitors — including high-intent shoppers who viewed products but didn’t convert. Server-side tag deployment is the only reliable fix.
Use ‘home’ on the homepage, ‘category’ on shop/category pages, ‘product’ on single product pages, ‘cart’ on the cart page, ‘purchase’ on the order-received (thank-you) page, and ‘other’ everywhere else. Missing or wrong pagetype values corrupt your audience segmentation in Google Ads, especially for cart abandonment and purchase-intent lists.
Your dynamic remarketing campaigns can only be as good as the data feeding them. See how Seresa’s server-side tracking fixes the feed at source.