1. Home
  2. Meta Hub
  3. Tracking & Operations
  4. Aggregated Event Measurement (AEM) on Meta in 2026: What Changed and What Still Applies to iOS Traffic
Tracking & Operations · 8 min read

Aggregated Event Measurement (AEM) on Meta in 2026: What Changed and What Still Applies to iOS Traffic

By the Power Ads teamUpdated 2026-11-20Checked against 13 sources1,455 words

Older setup checklists, and even some of Meta's own developer pages, still describe ranking eight conversion events per domain in Events Manager. That step no longer exists. Meta's Help Center says there are no steps you need to take for website events to be processed through Aggregated Event Measurement (AEM), and the Events Manager tab that held the ranking is gone. AEM itself is still running. This guide covers what AEM is, how it worked at launch, exactly what Meta says changed, what domain verification still does, what still applies to iOS 14.5+ traffic and how it shows up in reporting. Each rule comes from Meta's Help Center or developer documentation, and our own advice is labelled as such.

What Aggregated Event Measurement is, and how it started

Meta describes Aggregated Event Measurement as a protocol that allows for the measurement of web and app events from people using iOS 14 and later devices. Its processing includes removing identifiers, adding differential privacy and aggregating the data across users before Meta personalizes ads and measures how they perform. For websites, Meta's Help Center says AEM helps it recover limited measurement of conversions from people using iOS 14.5 and later devices. Meta's developer documentation for apps describes AEM as measuring app events from iOS 14.5+ users who have opted out of app tracking.

Meta's key concepts article gives the reason: Apple's policy prohibits certain data collection and sharing unless people have given App Tracking Transparency (ATT) permission, so ads personalization and performance reporting may be limited for both app and web conversion events. Our post-iOS measurement guide covers ATT, Safari and the Conversions API in depth; this guide stays on AEM.

The original web rules came from Meta's developer blog in 2021, with reporting changes from January 19, 2021, and an update saying Facebook would begin rolling out the new measurement protocols on April 27, 2021. Advertisers were limited to 8 conversion events per domain, ranked by priority, and only the higher prioritized event would be reported. One Business Manager had to verify the domain, at the eTLD+1 level, to edit that configuration. The same post said Meta would no longer support 28-day click, 28-day view and 7-day view attribution windows, and that offsite conversions would be reported by the time they occurred, not the time of the ad impression. Most stale AEM advice dates from this period.

What changed for website events, and when

Meta's current AEM article says it has introduced updates to website conversion campaigns and that there are now no steps you need to take for your events to be processed through AEM. On timing, it gives no date for these web changes. It says Meta is gradually introducing updates to AEM for website and app events and lists the changes as ones you'll see when you have access, so the rollout was staged rather than one switch-over. The one dated change on the page is on the app side: as of October 9, 2024, Meta sends AEM reporting to mobile measurement partners (MMPs), with the same privacy processing. Meta's older articles on how AEM affects the Meta Pixel and on best practices for web event configuration now redirect to that main AEM article.

The changes Meta lists for website campaigns:

  • You no longer need to prioritize 8 conversion events per domain for web conversion optimization.
  • You don't need to turn on value sets to use value optimization.
  • The Aggregated Event Measurement tab in Events Manager has been removed, because web events no longer need configuring.
  • You aren't required to verify website domains for purposes related to event configuration.
  • You don't need to select a conversion domain when you create a campaign in Ads Manager.
Power AdsUnlimited Meta agency ad accounts on our corporate cards, with 24/7 support on Telegram and WhatsApp, for teams spending roughly $100,000+/mo. 4% per top-up, no setup fee. Apply for access →

Domain verification's role now

Meta says you aren't required to verify website domains for event configuration, but adds that you may still need to verify for other reasons. Its article on when to use domain verification lists them: managing which advertisers can edit link previews in ads pointing to your domain, editing organic link previews, registering for the news Page index, selling through Facebook commerce surfaces, maintaining lists of Pages without Open Graph tags, controlling which domains can use your pages as a canonical URL, and completing business verification without a business phone number or with an email domain that doesn't match your website. Conversion tracking is not on that list. Our domain verification guide walks through the methods and common errors.

What still applies to iOS 14.5+ traffic

Removing the configuration did not remove the privacy processing. Meta's AEM article still describes identifiers being removed, differential privacy added and data aggregated for events from iOS 14 and later devices, and it notes that events sent through the Conversions API may also be processed in accordance with limits set by AEM. A server connection does not take iOS events outside AEM.

Meta's guide to reaching people on iOS 14.5 or later says there are no actions you need to take to use AEM for website campaigns, but it still flags targeting: as more devices update, app activity custom audiences, website custom audiences and app connections audiences may shrink, and it suggests a broad audience or targeting expansion as alternatives.

App campaigns still have setup work. For app re-engagement and app promotion campaigns, Meta says to check whether your app is eligible for AEM, and its developer documentation requires iOS Universal Links support. iOS 14+ app promotion campaigns use either AEM or Apple's SKAdNetwork as the campaign attribution method; our SKAdNetwork guide covers the second option.

How AEM affects reporting and attribution settings

Expect some results to be modeled. Meta says that where conversion data may be missing or partial, it may use statistical modeling to give a more complete view of results, and it annotates those results in Ads Manager and Ads Reporting. Modeling draws on several data sources, and Meta notes that where it isn't used, results may not include all conversions. Combined with differential privacy, that means small iOS-heavy ad sets report less precisely than large ones.

For website conversions, Meta's attribution article currently lists 1-day or 7-day click-through, 1-day view-through and 1-day engage-through, which counts non-link clicks and, for video, 5-second plays. Some accounts may still use prior versions while this rolls out. The article lists narrower settings for iOS 14+ app campaigns using AEM: re-engagement reports using 1-day attribution, and installs using 1-day or 7-day click. Meta also says results can't be compared in the Campaign Overview table across ad sets with different attribution models. See our attribution settings guide.

App campaigns get extra reporting detail. Meta says AEM reporting for app promotion campaigns is close to real time, that SKAdNetwork reporting can be viewed beside it through Compare attribution settings, and that 8 breakdowns are available: age, gender, age and gender, country, impression device, platform, platform and device, and placement.

Practitioner advice: running web campaigns under today's AEM

This section is our own practice, not Meta's documentation.

  • Optimize for the event that matches your goal. With no eight-slot ranking, there is no reason to pick a proxy event because it once ranked higher.
  • Keep the Pixel and the Conversions API sending the same events with deduplication. AEM changed configuration, not the need for clean, complete events.
  • Judge iOS-heavy ad sets over longer date ranges and at higher levels of aggregation, since aggregated, noise-added and partly modeled results swing more on small numbers.
  • Keep domains verified if you care who edits link previews to your site, but don't hold a launch back waiting for verification to unlock events.
  • Record the attribution setting with every comparison you report, and reconcile against your backend orders rather than one platform's count.
  • Power Ads supplies Meta agency ad accounts and does not configure tracking, so dataset and event setup stay with your team.

Common mistakes and stale guidance

Most AEM mistakes now come from following instructions written for the 2021 setup.

  • Trying to rank 8 events per domain. Meta's Help Center says that is no longer needed and the AEM tab is gone. If a checklist sends you looking for it, the checklist is out of date.
  • Trusting every Meta page equally. Meta's developer pages on the Pixel for the Marketing API and on AEM and SKAdNetwork limitations still say AEM limits domains and apps to 8 configured, prioritized events. The Help Center describes the current web flow.
  • Assuming AEM is gone. The web configuration went away; Meta still processes iOS 14 and later events through it.
  • Treating the Conversions API as a way around AEM. Meta says those events may be processed within AEM's limits too.
  • Setting up value sets for web value optimization. Meta says they aren't needed; value sets still belong in SKAdNetwork configuration for apps.
  • Expecting 28-day or 7-day view windows. Meta dropped them in 2021, and its current list for website conversions stops at 7-day click and 1-day view.
  • Assuming app campaigns need no setup. AEM for apps still depends on app eligibility and Universal Links.

Key takeaways

  • Meta's Help Center says no steps are needed for website events to be processed through Aggregated Event Measurement.
  • Ranking 8 events per domain, the Events Manager AEM tab, value sets for web value optimization and choosing a conversion domain are gone.
  • Meta gives no date for the web changes and describes a gradual rollout.
  • AEM still processes iOS 14+ events with identifiers removed, differential privacy and aggregation, including events sent through the Conversions API.
  • Domain verification is no longer needed for event configuration but still controls link editing and can support business verification.

FAQ

Is Aggregated Event Measurement still used on Meta?

Yes. Meta's Help Center still describes AEM as the protocol for measuring web and app events from people on iOS 14 and later devices. What went away for websites is the configuration: no event ranking, no AEM tab and no conversion domain to pick.

Do I still need to prioritize 8 events in Events Manager?

No. Meta says you no longer need to prioritize 8 conversion events per domain for web conversion optimization, and the Aggregated Event Measurement tab has been removed from Events Manager. Some Meta developer pages still mention the 8-event limit; the Help Center is the current account for web campaigns.

When did Meta remove the 8-event limit?

Meta's Help Center does not give a date. It says Meta is gradually introducing updates to AEM and lists the web changes as ones you'll see when you have access, so they reached accounts in stages.

Do I need domain verification for AEM?

Not for event configuration. Meta says you may still need it for other reasons, such as controlling who can edit link previews pointing to your domain, maintaining Pages linked to it or completing business verification without a matching business email or phone number.

Does the Conversions API avoid AEM limits on iOS traffic?

No. Meta notes that events sent through the Conversions API may also be processed in accordance with limits set by Aggregated Event Measurement. Send server events for completeness and match quality, not to get around iOS privacy.

Why are some of my conversions marked as modeled?

Meta says that where conversion data is missing or partial, it may use statistical modeling to give a more complete view of results, and it annotates those results in Ads Manager and Ads Reporting. Without modeling, results may not include all conversions.

Need agency ad accounts?Unlimited Meta agency accounts on our corporate cards, shared to your Business Manager through partner access. 4% per top-up, no setup fee, unused balance refunded within 24 hours (business days), free replacements, 24/7 on Telegram and WhatsApp.
@power_ads_hqGet the next one in Telegram.Meta policy shifts, spend-limit fixes and scaling notes from the Power Ads team. Join 3,000+ subscribers. Free, read-only, one tap to leave.Join channel

Sources

Power Ads background
By application only

We don't talk. We solve.

Unlimited Meta agency ad accounts on our corporate cards for teams spending roughly $100,000+ a month. 4% per top-up, no setup fee, 24/7 on Telegram and WhatsApp.

Telegram support · 24/7
TelegramWhatsAppApply