Meta’s Andromeda retrieval engine narrows millions of ad candidates down to roughly 1,000 before the auction even begins — and conversion signal quality is one of the documented inputs deciding which ads survive that filter. If your WooCommerce store is running only the Meta Pixel, or Pixel + CAPI with broken event_id deduplication, your ads are being demoted at a stage your Ads Manager reports do not show. The fix is not a better bid. It is a higher Event Match Quality score.
The Two-Stage Architecture: Retrieval Runs Before the Auction
Meta’s ad delivery system is no longer a single auction. It is a three-stage pipeline: retrieval, ranking, then auction. Andromeda is the retrieval stage, deployed in late 2024 and operational across Meta’s full ad surface through 2025 and 2026.
Andromeda achieves over 100x improvement in feature-extraction latency compared to Meta’s previous CPU-based retrieval components, with more than 3x end-to-end inference QPS, according to Meta’s own engineering disclosures. The engine runs on NVIDIA Grace Hopper GPUs and uses three signal categories to score every candidate ad: creative content, audience signals, and conversion signal quality from the advertiser.
Here’s how it works in plain terms. When a Meta user opens Instagram or Facebook, Andromeda scans millions of eligible ads in milliseconds and narrows the pool to about 1,000 candidates. Those 1,000 go to GEM (Generative Embedding Model) for ranking. Only the survivors enter the actual auction.
If your ad does not make it through retrieval, it never reaches the auction, regardless of budget or how aggressive your bid is. That is the structural shift. Budget and bid only matter once you are inside the auction. Andromeda decides whether you are even allowed in.
Why Pixel-Only WooCommerce Stores Are Being Filtered Out
Andromeda needs reliable conversion data to predict which user is likely to buy from your store. Reliable means matchable — Meta must be able to tie the conversion event back to a real Meta user with high confidence. That match is scored as Event Match Quality (EMQ), a 1–10 rating you can see in Events Manager.
An EMQ score below 7.0 indicates Meta is having trouble matching conversion events to real users, which degrades Andromeda’s learning — and your store’s standing at the retrieval gate.
Pixel-only WooCommerce stores cannot hit 7.0 reliably. Three reasons:
- Ad blockers strip the Pixel entirely. 31.5% of users globally run ad blockers, and the Pixel never fires for them. Every blocked event is a missing data point Andromeda uses to score your store.
- Safari ITP caps cookies at 7 days. Returning customers lose their fbc/fbp identifiers, breaking the user match.
- Browser context is thin. The Pixel can hash an email at checkout, but it cannot reliably enrich with IP, user agent, and server-side first-party context the way a CAPI call can.
The symptom most WooCommerce store owners notice is downstream: rising CPMs, falling delivery, and creative that used to last six weeks now burning out in two or three. Effective ad creative lifespan has compressed from 6–8 weeks pre-Andromeda to 2–4 weeks under the new retrieval system (Confect.io / ScaledOn practitioner data). The owner assumes audience fatigue. The actual cause is retrieval-stage filtering against a low-EMQ signal.
For the broader picture of how this scrambles attribution across platforms, see our earlier piece on why Facebook says 85 sales, Google says 60, and WooCommerce says 50 — the same upstream signal-quality problem shows up as cross-platform disagreement.
The Pixel + CAPI Trap: Deduplication Has to Actually Work
Adding CAPI is the obvious move. But the most common WooCommerce CAPI plugin defaults silently produce a worse outcome than Pixel-only — duplicate events with no way to match them.
Meta now treats Pixel + CAPI deduplication as a 2026 performance requirement. The system expects every conversion to arrive twice: once from the browser Pixel, once from your server via CAPI, both carrying the same shared event_id. Meta dedupes them against each other and uses the combined signal for matching.
An estimated 23% of WooCommerce orders are sending event_ids that don’t match between browser and server — the Pixel side uses a random JavaScript-generated identifier while CAPI sends the WooCommerce order ID. Two events arrive. Neither can be deduped. EMQ stays flat.
The fix is structural and small at the same time: generate the event_id server-side at WooCommerce order creation and pass the same value to both sides. The WooCommerce order ID is already stable, unique, and available — it is the natural shared identifier. Most plugin defaults ignore it.
What High-EMQ Capture Actually Requires on WooCommerce
For Andromeda to score your store well at the retrieval gate, four pieces have to be in place:
- Shared server-generated event_id on both Pixel and CAPI, using the WooCommerce order ID as the source of truth.
- fbc and fbp click identifiers persisted across payment-gateway redirects. When a customer bounces to PayPal or Stripe and returns, the original click attribution must survive. Browser-only persistence breaks at this exact point.
- Hashed user data sent server-side — email, phone, first name, last name, city, zip, country — using SHA-256, captured from the WooCommerce checkout fields rather than scraped from the browser DOM.
- IP address and user agent enriched on the server, not the browser. Server-side context is more reliable for matching than anything the Pixel can extract.
The validation step is non-negotiable. Set up the events. Then verify them. Our guide to validating that your server-side tracking is actually working walks through the Events Manager diagnostic — same approach applies to native CAPI without GTM.
Here’s How You Actually Do This on WordPress
Plugin-only setups struggle here because the Pixel and CAPI run in different contexts, and reconciling them requires server-side state. Transmute Engine™ is a dedicated Node.js server that runs first-party on your own subdomain — for example, data.yourstore.com. The inPIPE WordPress plugin captures WooCommerce checkout events and batches them via API to your Transmute Engine server, which generates one canonical event_id, persists fbc/fbp across payment-gateway redirects, hashes checkout data to Meta’s specification, and routes the deduplicated event to Meta CAPI alongside GA4, Google Ads, and BigQuery — simultaneously, from your own domain, bypassing the ad blockers and ITP restrictions that strip browser-side capture.
The point is not that CAPI is nice to have. CAPI is now the entry requirement to even reach the auction. Warehouse-backed signal quality is the actual edge.
Key Takeaways
- Andromeda runs before the auction. If your ads are filtered out at retrieval, no budget or bid recovers them.
- EMQ 7.0 is the working threshold. Below that, Andromeda treats your store as low-confidence signal.
- Pixel-only is no longer “less optimal” — it is pre-filtered out. 31.5% ad-blocker rate and ITP cookie limits make browser-only capture structurally insufficient.
- Deduplication has to work. Use the WooCommerce order ID as the shared event_id on both Pixel and CAPI. 23% of stores fail this silently.
- Persist fbc/fbp through payment redirects. PayPal and Stripe hand-offs are where most attribution dies.
- Validate in Events Manager. Check the Deduplication tab and the EMQ score per event type — the diagnostic is free and takes ten minutes.
Frequently Asked Questions
Both. Under Andromeda, conversion signal quality is now a documented input to the retrieval stage that runs before the auction. Pixel-only stores or stores with broken Pixel+CAPI deduplication get filtered out at retrieval, which means their ads never reach the auction regardless of budget or bid.
Practitioner consensus places the working threshold at 7.0 on Meta’s 1–10 EMQ scale. Below 7.0, Meta is having trouble matching conversion events to real users, which degrades Andromeda’s learning and reduces how often your ads survive retrieval. Aim for 8.0+ on the Purchase event.
No, but it is no longer sufficient on its own. Andromeda treats Pixel-only stores as low-signal-quality candidates and demotes them at retrieval. The Pixel still matters for browser-side capture and deduplication, but it must be paired with a Conversions API feed that sends matching server-side events using a shared event_id.
Because Andromeda probably is not letting your ads survive retrieval as often. Rising CPMs and falling delivery with unchanged creative and audience is the visible symptom of a retrieval-stage signal-quality problem. Check your Event Match Quality score in Events Manager — if it is below 7.0 on Purchase events, the auction is not your bottleneck.
The WooCommerce order ID, generated server-side at order creation and passed to both the browser Pixel and the CAPI request. Random JavaScript-generated event_ids on the Pixel side cannot be matched by CAPI, which is why an estimated 23% of WooCommerce orders fail deduplication. Use the same server-generated identifier on both sides.
Audit your Meta CAPI setup before your next creative test runs hot — the retrieval gate is upstream of everything else. Start at seresa.io.
