How to identify zombie SKUs across Google Ads Shopping and PMax campaigns?

Pull the product-level performance report from each Shopping and PMax campaign, filter for products with 20+ clicks and zero purchases over the last 60–90 days, and cross-reference those product IDs against your active feed. Every SKU matching those criteria is a zombie — 'alive' because Google keeps showing it and users keep clicking, 'dead' because zero revenue results. The 60–90 day window provides statistical confidence that the SKU has had a fair chance to convert. The Zombie Products Audit automates this across all your Shopping and PMax campaigns simultaneously and classifies each zombie with an action tag: EXCLUDE, FIX FEED, or MONITOR.

What are zombie products and how do they work?

Zombie products are Shopping SKUs that receive consistent clicks and spend but have never recorded a sale. They persist because the bidding algorithm only has a negative signal (clicks without conversions is inconclusive, not conclusively bad) — it keeps funding them waiting for the conversion that never comes. The term comes from the pattern: the campaign cannot tell the product is worthless because clicks exist, so spend continues indefinitely. The Zombie Products Audit surfaces every SKU meeting the zombie threshold, calculates daily burn rate per product, and produces a campaign-ready exclusion list.

Why do products get clicks but no sales in Google Shopping?

Four common causes: feed mismatch (the title or image attracts curiosity clicks from the wrong audience), price uncompetitiveness (users click, see the price, bounce), landing page issues (out-of-stock or 404 pages), and wrong audience matching (research-mode users rather than buyers). Each has a different fix — feed issues are fixable, audience mismatches usually are not. The distinction matters because excluding a product with a fixable feed issue forfeits real revenue, while fixing the feed on a product nobody wants is wasted effort. The Zombie Products Audit cross-references your GA4 add-to-cart and product view data to distinguish genuine zombies from fixable problems.

How to separate winners from losers in a Shopping campaign

Break your inventory into three performance tiers via custom labels in the Merchant Center feed: Tier 1 (SKUs converting at or above target ROAS), Tier 2 (SKUs with clicks and no sales over 60 days — zombies), and Tier 3 (SKUs with insufficient data to judge). Run Tier 1 in a high-budget, high-priority campaign; isolate Tier 2 in a low-budget exclusion-test campaign or pause them entirely; give Tier 3 a dedicated test budget in a separate low-priority campaign. This prevents the algorithm from concentrating budget on already-popular items and starving new ones of impressions. The Zombie Products Audit produces the exact tier assignment for every SKU in your feed.

How to push low-coverage items to a new campaign

Create a new Standard Shopping campaign set to Low priority, add custom_label_0 = 'low_coverage' to the low-visibility SKUs in your feed, and filter the new campaign's inventory to include only that label. Then set the original high-coverage campaign to exclude those SKUs. This forces the algorithm to allocate impressions to previously-starved inventory by removing them from competition with the winners. The Zombie Products Audit identifies SKUs with fewer than 50 impressions over 30 days and produces the custom label list to upload alongside the campaign-split recommendation.

Zombie products getting zero visibility in PMax — what's the fix?

PMax concentrates spend on high-converting products and systematically starves the rest regardless of whether they are good or bad SKUs — low-impression products are often not true zombies, they are suppressed by the algorithm. The fix is to migrate suppressed products into a Standard Shopping campaign with manual CPC bidding, which forces impression allocation that PMax refuses. After 30 days of Standard Shopping exposure, you can reliably classify them as genuine zombies (no sales with adequate impressions) or suppressed performers (sales once given visibility). The Zombie Products Audit identifies PMax-suppressed SKUs separately from genuine zombies and recommends which ones to migrate for diagnostic testing.

Shopping campaign has 0 impressions for all products — why?

Four diagnostic causes, in order of frequency: (1) Merchant Center feed has product disapprovals at scale, (2) the campaign is targeting geos where you have no pricing or shipping coverage, (3) bids are below the minimum threshold for your category auction, (4) the campaign is paused or limited by budget. Check the Merchant Center Diagnostics page first — bulk feed disapprovals are the most common cause and often stem from a single policy flag applied across the feed. The Zombie Products Audit includes a feed-health check that surfaces disapproval rate, eligibility status, and bid competitiveness per product category.

How do I set up ads for a large catalog of 100k+ products?

Never run a single 'catch-all' campaign — the algorithm will concentrate budget on the top 1–2% of SKUs and starve the rest. Segment the catalog into at least three tiered campaigns by historical performance, margin, or search volume. For 100k+ SKUs specifically: run a Top-Sellers campaign (the converting 5–10%), a Mid-Tier campaign (products with clicks but insufficient conversion data), and a Long-Tail campaign (low-search-volume products at lower bids). Use custom labels or product type splits to enforce the segmentation. The Zombie Products Audit produces the exact segmentation for your catalog based on 90-day performance data, including the recommended budget split across tiers.

What is a zombie product's daily burn rate?

Daily burn rate is the average spend per day on a zombie product, calculated as total zombie-period spend divided by the number of days the SKU has been a zombie. A product spending £8/day with zero sales over 30 days has burned £240. This matters for prioritisation — a £50/day zombie needs action today, a £2/day zombie can wait. The Zombie Products Audit surfaces burn rate per product so you can prioritise which zombies to address first, rather than working through them alphabetically or by click count.

Does excluding zombie products hurt Shopping campaign performance?

No — removing SKUs with zero conversion history removes dead weight from the campaign. Smart Bidding learns from conversion signals; a product with 200 clicks and zero purchases actively teaches the algorithm that this traffic type does not convert, which degrades targeting for your entire Shopping account. Excluding it improves signal quality for your remaining products. In most accounts, removing zombies improves overall Shopping ROAS within 7–14 days as budget reallocates to products with conversion history.

Is there any point in running PPC for a low ticket item?

Only if the unit economics justify it — run the math on break-even ROAS first. A £15 product with a 50% margin yields £7.50 of gross profit per sale, meaning your CPA ceiling is £7.50 and the break-even ROAS is 2x. In competitive Shopping verticals, CPCs of £0.80–£2 are common, so you need a conversion rate of 4–10% just to break even. Low-ticket items only work in PPC when the conversion rate is unusually high, the LTV is high (subscription or repeat purchase), or the volume lets you amortise overhead. The Zombie Products Audit flags low-margin SKUs that cannot plausibly recover their ad spend based on current CPA and suggests them for exclusion regardless of click volume.

ClickCatalyst

Zombie Products · Methodology

Back to Zombie Products Audit

Authority Layer · 6 metrics · 3 data sources

Inside the Zombie Products Engine

Every metric in your Zombie Products audit uses documented detection logic. This page explains the currency-adaptive threshold, margin eater identification, GA4 cross-reference validation, and the EXCLUDE/FIX/MONITOR classification system.

Jump to metric

Zombie Detection Threshold01 Daily Burn Rate02 Margin Eater Detection03 GA4 Cross-Reference Validation04 Zombie Action Split (EXCLUDE / FIX / MONITOR)05 Recovery Summary & Conversion Simulation06

Data Sources

read-only OAuth · no campaign changes ever

All data is read via Google Ads API and GA4. Derived intelligence tables are pre-computed in our pipeline before your audit runs.

Google Ads API — Shopping Performance

google_ads_shopping_performance

Product-level cost, clicks, units_sold, gross_profit, product attributes for zombie detection and margin analysis

Google Ads API — Shopping Benchmarks

google_ads_shopping_benchmarks

Google's benchmark CPC and CTR for industry comparison

GA4 — Ecommerce Products

ga4_ecommerce_products

GA4 product views, cart adds, purchases for cross-platform zombie validation

Zombie Detection Threshold

Currency-adaptive logic that catches every zombie without false positives

A product is flagged as a zombie when three conditions are simultaneously true: zero units_sold, at least 20 clicks (ensuring meaningful traffic), and cost above a dynamic floor. The floor adapts to account economics — it takes the account's average CPC multiplied by 20, which adjusts automatically for high-CPC markets (USD) and low-CPC markets (INR).

⚠️

Why this matters: A static $50 threshold catches zombies in USD accounts but misses them in INR accounts (where ₹50 is negligible) and over-flags in low-CPC accounts. The dynamic threshold ensures every account gets accurate detection regardless of currency or industry CPC.

💡

In plain English: We find products that got at least 20 clicks (enough traffic to judge) and zero sales, AND spent more than a meaningful amount. The 'meaningful amount' adjusts to your account — if your average click costs $2, the threshold is $40. If it costs ₹5, the threshold is ₹100. This prevents flagging products that barely spent anything.

All 3 metConfirmed zombie — exclude from campaigns

Clicks < 20Insufficient data — not flagged yet

Daily Burn Rate

How fast each zombie consumes budget per day

Total zombie waste divided by the reporting period for account-level burn. Per product: total cost divided by COUNT(DISTINCT date) with spend. Products with high daily burn are the most urgent exclusion candidates — they waste disproportionately per day of inaction.

⚠️

Why this matters: Total waste is an abstract number. Daily burn makes it visceral: 'This product wastes $12 per day' is immediately actionable. Multiply by 30 for monthly exposure. The burn rate creates urgency that total-waste figures don't.

💡

In plain English: We divide each zombie product's total wasted cost by the number of days it was active with spend. A product wasting $5/day sounds small — but that's $150/month on a product that never sells. The daily number makes the cost of waiting tangible.

High burnExclude immediately — disproportionate daily cost

Low burnLower urgency — batch exclude

Margin Eater Detection

Products that sell but destroy profit after ad costs

From google_ads_shopping_performance: products with conversions > 0 (they sell) but gross_profit minus ad spend < 0. Uses the gross_profit field which requires cost_of_goods_sold in your Merchant Center feed. These are more dangerous than zombies because the algorithm sees conversions and scales them.

⚠️

Why this matters: The algorithm optimizes for conversion volume, not profitability. A product with a 5% margin that converts well will receive aggressive budget — making you poorer with every 'successful' sale. The algorithm literally cannot see COGS.

💡

In plain English: We find products that actually sell (unlike zombies) but where advertising costs more than the profit the product generates. You lose money on every sale — and the algorithm keeps pushing more budget to these products because it only sees the sale, not the loss.

Small lossAdjust ROAS target upward

Large lossExclude from paid — sell via organic

GA4 Cross-Reference Validation

Confirming zombies across both platforms

Zombie product titles joined with ga4_ecommerce_products on LOWER(item_name) = LOWER(product_title). Checks GA4 cart_adds, purchases, and view-to-purchase rate. If GA4 also shows zero purchases, the zombie is confirmed across both platforms — no attribution gap is creating false positives.

⚠️

Why this matters: A product might show zero sales in Ads due to attribution differences but actually sell through organic or direct channels that GA4 captures. The cross-reference prevents excluding products that DO sell — just not through the tracked ad path.

💡

In plain English: We check each zombie product against your GA4 analytics data. If GA4 also shows zero purchases, the product is genuinely dead across both platforms — safe to exclude with confidence. If GA4 shows cart adds but no purchases, the product has demand but fails at checkout — a different problem.

Confirmed deadBoth platforms agree — exclude with confidence

Cart adds existHas demand — investigate checkout UX

Zombie Action Split (EXCLUDE / FIX / MONITOR)

Not every zombie gets the same treatment

Each zombie is classified by combining cost level with feed data completeness. Products with complete attributes (brand + category present) and high cost = EXCLUDE (low demand, not discoverability). Products missing brand or category = FIX FEED FIRST (never had a fair chance). Products with moderate cost = MONITOR. Priority uses average zombie cost as the benchmark.

⚠️

Why this matters: Blindly excluding all zombies wastes the learning on fixable products. A product missing its brand attribute can't be matched to relevant audiences — fixing the feed may resurrect it. The split prevents you from killing products that just need better data.

💡

In plain English: We classify each zombie into three buckets: EXCLUDE (the product has complete data and still doesn't sell — it's a demand problem), FIX FEED (the product is missing brand or category info — Google can't match it properly), or MONITOR (not enough data to decide yet). Priority tells you which to act on first.

EXCLUDEComplete data, no sales — remove from ads

FIX FEEDMissing attributes — update Merchant Center

MONITORInsufficient data — reassess in 2 weeks

Recovery Summary & Conversion Simulation

What you get back by excluding zombies

Total recoverable budget (zombie waste), expressed as percentage of total Shopping spend, with a conversion simulation: recovered budget divided by account average CPA = projected additional conversions. This is a conservative estimate — it assumes current CPA holds at higher productive spend.

⚠️

Why this matters: This is the business case for acting on the exclusion list. Stakeholders need a concrete number: 'Excluding N products recovers $X/month and generates Y additional conversions at no extra cost.' The simulation provides exactly that.

💡

In plain English: We add up all zombie waste, calculate what percentage of your Shopping budget it represents, and then project how many additional conversions you'd gain if that money went to products that actually sell (at your current average cost-per-conversion).

< 10% of spendManageable — targeted exclusions

10–30%Significant — prioritize exclusions this week

> 30%Structural — catalog strategy review needed

Proprietary notice: The methodology, scoring models, waste classification logic, and recovery projections are proprietary to ClickCatalyst Digital and provided for informational purposes only. Results are subject to standard market volatility. Recovery projections are estimates, not guarantees. Contact us within 14 days if any metric appears inaccurate.

Also worth reading

How to Read Your Zombie Products Report →

Every section explained with exact action steps

See these metrics applied to your account

Run My Free Zombie Products Audit