Meta Andromeda Issues in May 2026: Pixel, Learning Phase, and CPM Bugs (Live Updates)

If you Googled "Meta Andromeda issues" because reported ROAS in your ad account dropped, your pixel events stopped deduplicating, or every minor edit is resetting Learning Phase - you're in the right place, and you're not alone. Andromeda is the single biggest source of paid media operator pain in May 2026, and most of what's broken is fixable once you know what's reporting noise vs what's real signal loss.

This post is the working log. It covers what Andromeda is (with Meta's own framing), the rollout timeline, the four primary issues operators are hitting, the order to fix them, what NOT to do during the rollout window, and how to set up monitoring so the next regression doesn't catch you blind.

What is Andromeda

What Meta says Andromeda does, in their own framing:

• Larger and deeper personalization models - the recommendation system uses more signals per user and per ad than the prior infrastructure could process
• Better matching at scale - retrieval and ranking happen in a unified architecture rather than separated stages
• Faster adaptation to new creative - the model picks up signal from new ads quicker, in theory shortening the Learning Phase exit window
• Stronger performance on Advantage+ campaign types specifically, because those campaigns lean most on Meta's personalization layer

What we observe in customer accounts during the rollout window:

• Conservative attribution that under-counts conversions vs the prior delivery system (reported ROAS down without business performance changing)
• Audience signal re-evaluation that resets Learning Phase more often than the prior threshold
• Tighter dedup logic that breaks previously-fine pixel + Conversion API setups
• CPM swings of 30-60% week-over-week without an obvious account-side cause

The first list is real long-term improvement Meta is shipping. The second list is rollout-window cost most accounts pay for 4-6 weeks before stabilization.

Why this matters more than past Meta changes

Meta has shipped major delivery changes before (the iOS 14.5 SKAN era in 2021, Advantage+ Shopping in 2022, the AEM 8-event cap in 2021, Advantage+ Audience in 2023). Andromeda is bigger than any of those for two reasons.

First, it touches the core ranking and retrieval layer, not just attribution or audience. When attribution changes, your reported numbers shift but your delivery is the same. When ranking changes, the actual ads being shown change. Both are happening with Andromeda.

Second, it's rolling out to advertiser accounts in waves over a 5-6 month window, which means peer benchmarks are unreliable - the account next to yours may be on different versions of the system than you are.

Andromeda rollout timeline

Where you are in this timeline matters more than which absolute date you read this on. An account that migrated in December 2025 has likely already stabilized; an account that migrated in late March 2026 is mid-rollout in May. Check your migration date by looking for the exact week your reported ROAS in Meta Ads Manager began diverging from your GA4 or server-side numbers - that's your Andromeda activation week.

The 4 issues we are tracking right now

Issue 1: ROAS reporting regression

Symptoms. Meta Ads Manager shows ROAS dropped 15-40% in the last 4-6 weeks. CPM looks similar. Spend is the same. Your CFO is asking what happened. Your CMO is forwarding the dashboard with an "is this real?" subject line.

What is actually happening. Andromeda's attribution model is more conservative about which conversions it credits to ads vs other channels. Conversions that previously got attributed to Meta are now getting credited to organic, direct, or other paid channels. The same is true at a smaller magnitude across attribution-window edge cases - longer-window conversions in particular are being deprioritized.

A worked example from a customer account: this DTC apparel brand had a March-April reported Meta ROAS of 2.1x, down from 3.3x in January-February. Same ad sets, same creative, same audience structure. We pulled three numbers in a triangulation:

• Meta Ads Manager: 2.1x ROAS (down 36% from January)
• GA4 with default model: 2.4x for Meta-attributed traffic (down 11%)
• Shopify total revenue / total ad spend (MER proxy): 4.0x (flat to January)

The interpretation: Meta's reported number dropped 36%, but blended business performance was flat. Cutting budgets based on Meta's number alone would have removed real revenue at the same rate it removed reporting noise.

This pattern - Meta's reported number drops more than analytics-tracked numbers, and analytics-tracked numbers drop more than total business performance - is the most common signature of the Andromeda reporting regression. We see it in roughly 7 out of 10 customer audits in May 2026.

The crucial test. Pull these three numbers for the last 30 days:

1. Meta Ads Manager reported revenue
2. GA4 (or Adobe Analytics) reported Meta-attributed revenue
3. Total business revenue (from Shopify, your CRM, server-side analytics)

If Meta's reported number dropped 30% but GA4 stayed flat AND total business revenue stayed flat - the drop is reporting accuracy, not real revenue loss. This is the most common case we see in customer audits in May 2026.

Fix order:

1. Triangulate the three revenue numbers above before changing anything.
2. Verify Attribution Setting at the campaign level - some accounts had this reset to default 7-day click + 1-day view during the rollout. The setting is at the campaign level, not the account level, so it's possible only some campaigns drifted.
3. Add server-side conversion tracking (Conversion API) if not running yet - it recovers signal Andromeda is dropping client-side.
4. Do not cut budgets based on Meta's reported ROAS alone during the rollout window. Most accounts that did this in March-April saw real revenue drop because budget cuts removed real conversions on top of reporting noise.
5. Wait 4-6 weeks per account for Andromeda to stabilize. Reporting accuracy typically recovers some - though usually not all - of the gap once Andromeda finishes its initial training phase per account.

Issue 2: Pixel and CAPI deduplication breaking

Symptoms. Started showing up in early April. Conversions inflate (pixel + CAPI both counting the same event) or deflate (neither counts). Deduplication Score in Events Manager dropped from the typical 90%+ to 40-70%.

What is actually happening. Andromeda changed dedup logic. Events that previously deduplicated within a 60-second window via event_id now sometimes get treated as separate events if other parameters differ - even when the event_id matches. The internal model is treating the two events as more independent signals than the prior system did.

The technical mechanic: Meta's deduplication on pixel + CAPI compares events on three dimensions - event_id (must match), event_name (must match), and a fuzzy match on event_time (must be within ~60 seconds). Andromeda appears to also factor in user-side signals (fbp cookie, fbc click ID, hashed user data) in a way that makes accounts missing those signals on one side fail dedup more often.

Why this matters for performance, not just reporting. Unlike Issue 1, this one is real signal loss. Meta's bid algorithms can only optimize toward conversion data they receive, and a broken dedup either inflates conversions (Meta thinks it's working better than it is) or deflates them (Meta under-bids). Both produce real ROAS damage.

Fix order:

1. Open Events Manager > pixel > Deduplication. Note the score.
2. Open Test Events. Send a test conversion through both pixel and CAPI with the same event_id. Watch dedup status in real time.
3. If pixel uses one event_id format (e.g., timestamp-based) and CAPI uses another (e.g., UUID), align them. Pixel and CAPI must use IDENTICAL event_id strings, not just consistent generation logic.
4. Verify CAPI is passing fbp and fbc cookies on every event. Without these, Andromeda cannot reliably match against pixel.
5. Verify CAPI is sending hashed user data (em, ph, fn, ln) when available. Andromeda uses these as additional dedup signals.
6. If all of the above is correct and dedup score is still below 70%, file a Meta support ticket referencing the Andromeda dedup regression. Support has been escalating these faster since mid-April.

For the full pixel troubleshooting guide: /blog/meta-pixel-not-tracking-conversions. For CAPI setup: /blog/what-is-conversion-api.

Issue 3: Learning Phase resetting on minor edits

Symptoms. Every budget tweak (5-10% adjustments) is resetting Learning. Creative swaps that previously did not reset are now triggering it. Several ad sets stuck in Learning Limited that were healthy 6 weeks ago.

What is actually happening. Andromeda tightened the "significant edit" threshold during the rollout. The internal model treats more edits as significant because the personalization graph is still evaluating audience signals - any edit that changes a signal it's mid-evaluation on triggers a reset.

The Learning Phase fundamentals are unchanged: an ad set needs 50 conversions on the optimization event in any 7-day window to exit Learning. What changed is which edits force the 7-day window to restart from zero.

What's resetting Learning under Andromeda that didn't before:

• Budget changes of 5-10% (was ~20%+ pre-Andromeda)
• Single creative swap in a 4-creative ad set (was usually only 2+ swaps)
• Audience size adjustments (any direction)
• Schedule changes (start/end date or dayparting)
• Optimization goal changes (was always a reset; now slightly more sensitive)

What's NOT resetting Learning:

• Bid cap adjustments
• Ad-level edits below the ad set threshold (placement changes within the same ad set)
• Renaming the ad set or campaign
• Changing campaign-level settings that don't filter to the ad set

Fix order:

1. Bundle all edits into a single window once per week. Multiple edits across a week can each trigger Learning resets and compound the damage.
2. Use 'Duplicate to test' for major creative changes - the original keeps learning while the duplicate explores.
3. If an ad set has reset Learning 2+ times in 30 days, freeze edits on it for 14 days. The reset cycle is dragging more performance than the edits are adding.
4. Check ad set conversion volume against the 50-conversions-in-7-days floor. If under that volume, the issue is structural (volume), not Andromeda specifically.
5. Consider switching to an upstream optimization event (Initiate Checkout vs Purchase) on ad sets where Purchase volume is below the 50/7d floor.

Full Learning Phase guide: /blog/meta-ads-learning-phase-stuck.

Issue 4: CPM volatility

Symptoms. CPM swings of 30-60% week-over-week with no obvious cause. CPMs that were 18 USD in February jumped to 32 USD in mid-April and dropped back to 22 USD by late April-early May.

What is actually happening. Andromeda is re-pricing audiences as the personalization model evaluates new signals. Audiences that were "well-known" to the previous delivery system are getting re-explored. This shows up as CPM volatility for advertisers competing in those auctions.

A second factor: Andromeda's exploration phase per audience is hungrier than the prior system - it spends more impressions on testing newer audience-creative combinations, which can pull average CPM up in the short run before settling.

Fix order:

1. Hold steady. CPM volatility during the rollout is largely outside your control.
2. Do not aggressively cut budgets in high-CPM weeks - the auction stabilizes within 1-2 weeks for most accounts.
3. Monitor CPM trend on a 28-day rolling window, not week-over-week. The 28-day trend smooths the volatility and shows the real direction.
4. If CPM is structurally up over 60+ days post-Andromeda, that may be a real auction shift in your niche - different problem requiring different fix (audience expansion, creative refresh, channel diversification).
5. Track frequency along with CPM - rising CPM with rising frequency is creative fatigue layered on top of Andromeda volatility, and the fix is creative refresh.

How Andromeda affects Advantage+ campaigns

Advantage+ campaign types - both Advantage+ Shopping and Advantage+ Audience - are most disrupted during the Andromeda rollout because they rely most heavily on Meta's personalization layer, which is exactly what Andromeda is re-architecting.

If you run Advantage+ Shopping as a primary campaign type, expect the largest reported regressions and the most volatility. The Meta-side guidance on this category is to give Advantage+ campaigns more time during transitions - Andromeda is no exception. Cutting Advantage+ budgets during the rollout window has been the most expensive mistake we've seen operators make in March-April 2026.

What operators are reporting

Beyond customer accounts, the operator forums are the fastest signal on which issues are widespread vs account-specific. As of May 6, 2026, the most-discussed Andromeda topics across r/FacebookAds, r/PPC, AdLeaks, and the Modern Retail forums:

The pattern recognition is the value, not any single thread. If your account is hitting one of these symptoms in a way that matches the operator-reported timing - mid-March through May 2026 - assume Andromeda is the cause until your triangulation proves otherwise.

What NOT to do during the rollout

How to set up monitoring

The Andromeda rollout is a stress test on your monitoring stack. Accounts with strong cross-channel attribution had an easier time triangulating real loss vs reporting noise; accounts with single-source attribution panicked.

The minimum monitoring setup for the rollout window:

• Conversion API running with verified event_id consistency vs pixel
• GA4 with proper Meta source/medium attribution and conversions imported into Google Ads (yes, even if you don't run Google - GA4 is your independent source)
• Server-side analytics (Shopify reports, your CRM, or a data warehouse) reporting total revenue and total ad spend in the same view
• Weekly triangulation review that compares Meta reported ROAS, GA4 attributed revenue, and total business MER

Optional but high-leverage:

• Server-side GTM with Stape or your own server pushing events to CAPI directly (bypasses browser entirely - recovers more iOS opt-out signal)
• A dashboard that shows Meta reported ROAS, GA4 ROAS, and MER side-by-side - the gap between them is the regression signal
• Automated alerts when Meta reported ROAS diverges from MER by more than 25% in any 7-day window

This setup matters more during Andromeda than at any other point in the last several years because the gap between reported and real is wider than usual. Operators flying on Meta's reported number alone are flying half-blind.

Glossary of Andromeda-related terms

How Hyper helps with Andromeda specifically

The hardest part of the Andromeda rollout is not figuring out what is broken - it's figuring out what is real loss vs reporting noise so you don't panic-cut budgets. Hyper agents monitor reported ROAS against GA4, CRM, and server-side conversion data continuously and surface the gap. When Meta's reported number drops 25% but server-side data is flat, the agent flags this as 'reporting regression, hold budget' rather than letting it look like real loss.

The same agent monitors Deduplication Score, Learning Phase status, AEM priority lists, and Attribution Setting daily - catching the silent regressions before they cost a quarter. We have a Hyper Effects YouTube walkthrough showing this monitoring layer specifically against the Andromeda rollout. The case study at /blog/ai-marketing-case-study covers the full operating model, with real numbers from an apparel customer's account through the rollout window.

The biggest mistake we see in May 2026 is operators cutting Meta budgets during the rollout based on reported ROAS, then watching real revenue drop 4 weeks later because they removed real conversions in addition to reporting noise. Hyper exists in part to prevent that mistake - across 1,000+ customer accounts and 10M+ USD/month in managed ad spend, the agents have caught the reporting-vs-real divergence reliably enough that customer ROAS through the Andromeda window has held within normal seasonal variance.

If you're hitting any of the four issues above in your account this week and you don't have an independent monitoring layer set up yet - this is the week to add one. The next 4-6 weeks per account are the hardest stretch of the rollout; getting through them with intact budgets is mostly about not panicking on reported numbers that don't match real business performance.

Frequently asked questions