AEM Is Dead(ish) — and Your Pixels Are Now 'Datasets'
In June 2025 Meta removed the 8-event limit and the entire AEM configuration screen — while the aggregation quietly kept running for opted-out iOS users. Around the same time, 'pixels' became 'datasets.' Here's what actually changed, what survived, and the four-line checklist that replaces the old ceremony.
In June 2025 Meta quietly retired AEM’s 8-event limit and its whole configuration UI. Nothing needs migrating — prioritization is automatic now, and aggregated measurement still runs invisibly for opted-out iOS users. Separately, your “pixel” is now a “dataset” in Events Manager. Same plumbing, new name, one less checklist to maintain.
JUNE 2025 CHANGE 8-EVENT LIMIT GONE NOTHING TO MIGRATE PIXELS → DATASETS
A 60-second history (why AEM existed at all)
Aggregated Event Measurement was Meta's 2021 answer to Apple's App Tracking Transparency: for iOS users who opted out of tracking, Meta could only receive limited, delayed, privacy-thresholded conversion data — so it made advertisers rank up to 8 conversion events per domain, and only the highest-priority event a user completed got reported. For four years, "configure your AEM event priority" sat in every launch checklist, every audit template, every agency SOP. Whole blog posts existed about whether Purchase should outrank Subscribe. That's the world the stale guides still describe.
What Meta actually changed in June 2025
The mid-2025 Events Manager reshuffle in one card — nothing to reinstall, several things to stop doing.
The pattern across all six rows: work you used to do manually became invisible automation. The stale guides still ranking in 2026 describe a control panel that no longer exists.
Two separate cleanups landed close together and got blurred into one rumor. First, AEM's visible machinery went away: the 8-event limit was lifted, the configuration screen disappeared, and event prioritization became automatic — Meta's systems now decide internally how to handle opted-out iOS conversions, with no advertiser input. Critically, the underlying aggregation didn't die: iOS traffic from opted-out users is still measured through delayed, modeled, privacy-thresholded reporting — you just can't (and don't need to) configure it. Meta's remaining public documentation on aggregated event measurement reflects the slimmed-down reality. Second, the terminology shift: what Events Manager called a "pixel" is now a dataset — the same ID and base code, reframed as a container that can hold web, app, offline and CRM events together. Nothing broke; thousands of "where did my pixels go?!" panics were people meeting a rename.
What still matters in 2026 (the non-nostalgic list)
Domain verification survived every cleanup and still gates real functionality — verify every domain you advertise for, in the Business Manager that owns the relationship (multi-BM setups: one BM verifies, others request access; unverified domains still produce mystery friction). Signal quality replaced event ranking as the thing worth your hours: a pixel plus Conversions API with proper deduplication feeds the automated systems that took over AEM's job — the better your signal, the better the invisible machinery models your opted-out iOS traffic. And iOS reporting expectations: opted-out conversions still arrive delayed and partially modeled; that's not a bug to fix but a property to plan reporting around — the same "measurement vs reality" discipline from our 2026 attribution overhaul guide applies here.
The 2026 replacement checklist
Strike "configure AEM event priority" from your SOPs and replace the whole section with four lines: (1) every advertised domain verified in the owning BM; (2) dataset (né pixel) firing browser-side AND server-side with dedup confirmed in Events Manager; (3) conversions you optimize toward receiving real weekly volume (~50/week per ad set remains the learning rule of thumb); (4) iOS-heavy accounts annotate reporting for delay/modeling instead of "fixing" it. That's the entire modern replacement for what used to be an afternoon of AEM ceremony — and if a guide, auditor or agency hands you an AEM priority worksheet in 2026, you've learned something useful about how current their playbook is.
The control panel is gone; the system is automatic — spend the reclaimed hours on signal quality, not rituals.
Frequently asked questions
Is Aggregated Event Measurement gone completely?+
Do I need to do anything to migrate off AEM?+
Where did my pixels go in Events Manager?+
Is a dataset different from a pixel technically?+
Does the 8-event limit removal mean I can optimize on any event now?+
Is domain verification still required?+
Why are iOS conversions still delayed in my reports?+
My agency's audit asked for our AEM event priority list — red flag?+
Did the AEM changes affect Android or web traffic?+
Do the 2026 attribution changes relate to this?+
What should replace AEM steps in my launch checklist?+
Does account trust affect how well the invisible modeling works?+
Automation took the ceremony — keep the signal
Whitelisted infrastructure with history and headroom — dense, trusted signal for the systems that now run themselves.