Do You Still Need to Set Up 8 Events on Meta?
Do I still need to configure 8 events in Aggregated Event Measurement?
No. Meta says you no longer need to prioritize 8 conversion events per domain for website conversion optimization, you no longer turn on value sets for value optimization, and the Aggregated Event Measurement tab has been removed from Events Manager. Meta still processes events from iOS 14.5 and later through it, with no configuration step.
The 8-event ranking you set up after iOS 14.5 is gone for website campaigns. Meta’s own help page lists four steps you no longer take: ranking events per domain, switching on value sets, verifying a domain for event setup, and picking a conversion domain in Ads Manager. The protocol behind it still runs on iOS traffic. What changed is that you stopped configuring it, so the time goes into checks that still move results.
What did the 8-event setup do?
When Apple began requiring its App Tracking Transparency prompt, Meta introduced Aggregated Event Measurement (AEM) to measure web events from iOS 14 users. Its December 2020 developer guidance set the limit: “8 conversion events per domain”, ranked by priority, so that when a person completed two events, such as add to cart and purchase, “only the higher prioritized event will be reported” (Meta for Developers, 16 Dec 2020). Ad sets optimizing for an event outside the 8 were to be paused, value optimization needed value sets that used 4 of the 8 slots, and Meta asked advertisers to verify their domains.
Meta’s January 2021 update added an Aggregated Event Measurement tab in Events Manager for the ranking, and said the changes would start rolling out with iOS 14.5 on 27 April 2021 (Meta for Developers, 19 Jan 2021, updated 26 Apr 2021). That is the setup older guides still tell you to do.
What has Meta changed?
Meta’s current About Meta’s Aggregated Event Measurement page says: “Now, there are no steps you need to take for your events to be processed through aggregated event measurement.” It lists the changes:
| Setup step | 2021 rule (Meta for Developers) | Today (Meta Business Help Center) |
|---|---|---|
| Event ranking | Up to 8 conversion events per domain, ranked by priority | No longer needed for web conversion optimization |
| Value optimization | Turn on value sets, using 4 of the 8 slots | Value sets no longer needed for value optimization |
| Events Manager tab | Aggregated Event Measurement tab for configuration | Tab removed |
| Domain verification | Verify the domain to configure events | Not required for event configuration |
| Conversion domain | Selected when creating a campaign | No longer selected in Ads Manager |
Meta’s page describes these as “changes you’ll see when you have access”, and it does not date the switch. If an account still shows the old tab, the update has most likely not reached it yet. Meta’s page names no way to opt in early.
Is Aggregated Event Measurement gone?
No. The protocol still exists, and only the setup work went away. Meta describes it as a protocol for measuring web and app events from iOS 14+ devices, with “removing identifiers, adding differential privacy, and aggregating the data across users” before ads are personalized and measured. It also notes that events sent through the Conversions API “may also be processed in accordance with limits set by aggregated event measurement” (About AEM).
So iOS reporting still has gaps. Meta’s guide to reaching people on iOS 14.5 and later says website conversion campaigns need no setup action, but that app activity and website custom audiences may shrink as more devices update. Some results are modeled rather than counted; how far to trust that is covered in should I trust Meta modeled conversions?
App campaigns are a separate track. Meta says it is “gradually introducing” AEM updates to app campaigns, and app events sent through Apple’s SKAdNetwork still use their own event configuration in Events Manager. Nothing on this page applies to app setup.
What should I check instead of the 8 events?
The time you used to spend ranking events is better spent on the signals Meta still reads. Run these checks once, then monthly.
- Open Events Manager, select your dataset and click the Diagnostics tab. Fix any warning on Purchase first, especially missing value or currency (troubleshooting guide).
- Check that every event you optimize for fires with the standard name, such as
Purchase, because Meta treats event names as case-sensitive. - Click the Purchase event, then View details, and read the Event coverage tab. Meta recommends a 75% event coverage ratio of Conversions API to pixel events (Conversions API best practices).
- Read the Event matching tab on the same screen. Meta scores match quality from 0 to 10 on the last 48 hours of events.
- Confirm your value events carry varied values: for website value optimization Meta recommends at least 100 conversion events with at least 5 distinct values over the past 14 days (Requirements to use maximize value of conversions).
- Keep your verified domain. Meta still recommends domain verification for other reasons, such as managing who can edit links in ads pointing to your site (When to use domain verification).
- Delete the “configure 8 events” step from your onboarding checklist, agency SOP or developer handover, so nobody hunts for a tab that no longer exists.
Does this change how I pick an optimization event?
It removes one constraint. Under the old rule, an ad set optimizing for an event outside your top 8 was paused, so the ranking decided what you could optimize for. Now the choice comes down to data volume and margin. If Purchase has too few conversions a week to exit learning, the trade-off with a higher-funnel event is worked through in should I optimise for add-to-cart instead of purchase? The value-based version of that decision is in should I use value optimisation or purchase optimisation?
For the wider tracking setup, start with the Meta Pixel and CAPI hub.
FAQ
Is the 8-event limit gone for apps too?
Meta’s page treats apps separately. It says it is gradually introducing updates to app campaigns, including AEM for app promotion campaigns without configuring SKAdNetwork events, but SKAdNetwork configuration still exists for app events. The removal of 8-event prioritization described here is for website conversion optimization.
Do I still need to verify my domain?
Not for event configuration. Meta says domain verification is no longer required for event configuration, but you may still need verification for other reasons, such as managing ad link editing permissions or selling on Facebook commerce surfaces. Keep an existing verification in place.
Why do I still see the Aggregated Event Measurement tab?
Meta describes the changes as ones “you’ll see when you have access”, which means the rollout reaches accounts gradually. If the tab is still there, the update has most likely not reached that account yet, so leave its event ranking in place and check Meta’s help page again later.
Do iOS conversions now report in full?
No. Aggregated Event Measurement still processes iOS 14.5 and later events with privacy measures such as removing identifiers and aggregating data, and Meta said when it introduced the protocol that it would use statistical modeling for some metrics to account for less iOS data (Meta for Developers, 16 Dec 2020). Expect some iOS results to stay partial or modeled.
Sources
Sources: Meta Business Help Center, About Meta’s Aggregated Event Measurement, Reach people using iOS 14.5 or later with Meta ads, When to use domain verification, How to troubleshoot Meta Pixel error and warning messages, Best practices for Conversions API and Requirements to use maximize value of conversions; Meta for Developers blog, Preparing our partners for iOS 14: Mobile Web Advertising and Actions for Partners and Mobile Web Advertisers (checked 2 Oct 2026).