Aggregated Event Measurement (AEM) on Facebook
Master Facebook's Aggregated Event Measurement system to maintain conversion tracking and campaign optimization in the post-iOS 14 privacy landscape.
Key Takeaways
- What Is Aggregated Event Measurement?
- How AEM Works Under the Hood
- Configuring AEM for Your Domain
- Event Prioritization Strategy
73%
More Accurate Data
3x
Better ROAS
40%
Lower CPA
24/7
AI Optimization
What Is Aggregated Event Measurement?
When Apple launched iOS 14.5 in April 2021 with App Tracking Transparency (ATT), the digital advertising world fundamentally changed. Suddenly, users could opt out of cross-app and cross-website tracking—and the majority did. For Facebook advertisers, this meant losing visibility into a huge portion of conversions from iOS users.
Aggregated Event Measurement (AEM) is Facebook's solution to this challenge. It's a privacy-focused measurement protocol that allows you to track web conversions from iOS 14.5+ users who opt out of tracking—but with significant limitations:- You can only measure up to 8 conversion events per domain
- Event data is aggregated and anonymized, not user-level
- Attribution windows are limited to 7-day click and 1-day view (no 28-day)
- There's a 72-hour waiting period for configuration changes
Think of AEM as Facebook's compromise between respecting user privacy and giving advertisers enough data to measure and optimize campaigns. You don't get the granular, user-level data you had before iOS 14, but you get enough aggregated signal to understand if your ads are working.
Key Insight: AEM isn't optional—it's a requirement for measuring iOS 14.5+ conversions. If you haven't configured AEM, you're missing conversion data from opted-out iOS users, which could be 50-70% of your iPhone traffic depending on your audience.
Without proper AEM setup, Facebook's algorithm can't optimize your campaigns effectively because it's missing conversion signals. This leads to:
- Higher cost per conversion (the algorithm doesn't know what's working)
- Inaccurate ROAS reporting (you're missing conversions)
- Difficulty scaling campaigns (optimization is based on incomplete data)
Let's break down exactly how AEM works and how to configure it correctly for your business.
iOS 14+ Impact on Conversion Tracking
Percentage of trackable vs. limited iOS conversions before and after AEM implementation
How AEM Works Under the Hood
The iOS 14 Privacy Framework
When an iOS 14.5+ user opens an app for the first time, they see Apple's ATT prompt asking if they want to allow tracking. If they tap "Ask App Not to Track" or "Don't Allow," that app (including Facebook and Instagram) cannot:
- Track their activity across other apps and websites
- Use their IDFA (Identifier for Advertisers) for ad targeting
- Collect granular, user-level conversion data
How Facebook Measures Opted-Out Users
For iOS users who opt out, Facebook uses Aggregated Event Measurement to capture conversion data in a privacy-compliant way:
| Data Point | Available with AEM? | Notes |
|---|---|---|
| Conversion count | Yes | Aggregated across users |
| Conversion value | Yes | Total, not per-user |
| Event priority (top 8) | Yes | You configure this |
| User-level journey | No | Privacy-protected |
| Detailed demographics | Limited | Modeled/aggregated |
| Real-time data | No | Up to 3-day delay |
AEM vs. Non-AEM Tracking
To understand AEM's impact, let's compare what you get with opted-in users (non-AEM) vs. opted-out users (AEM):
Opted-In User (Non-AEM):- Facebook sees: user viewed ad → clicked → visited product page → added to cart → purchased $127.50
- You get: full funnel visibility, real-time data, user-level optimization
- Attribution: normal windows apply (7-day click, 1-day view)
- Facebook sees: aggregated data showing conversions happened, but not complete user journey
- You get: event counts and total value, delayed by up to 3 days, limited to your top 8 events
- Attribution: limited to 7-day click and 1-day view only
The Role of Conversions API
AEM determines which events Facebook can measure, while Conversions API (CAPI) determines how well Facebook can measure them. These two systems work together:
- Facebook Pixel: Browser-based tracking, heavily limited by iOS 14 and ad blockers
- Conversions API: Server-to-server tracking, bypasses browser restrictions
- AEM: Defines which events get measured for opted-out iOS users
Important: Even with perfect Conversions API implementation, you're still limited to 8 events per domain for opted-out iOS users. That's an Apple privacy requirement, not a Facebook limitation.
For a complete guide on CAPI setup, see our tutorial on Facebook Conversions API implementation.
Pro Tip
This section contains advanced strategies that can significantly improve your results. Make sure to implement them step by step.
Configuring AEM for Your Domain
Setting up AEM correctly is a one-time process that has lasting impact on your conversion tracking. Here's the step-by-step:
Step 1: Verify Your Domain
Before you can configure AEM, you need to verify that you own your website domain:
- DNS verification (recommended): Add a TXT record to your domain's DNS
- HTML file upload: Upload a file to your website root
- Meta tag verification: Add a meta tag to your site's header
Once verified, your domain will show a green checkmark. This step is required before you can configure AEM events.
Step 2: Access Events Manager
Now that your domain is verified, head to Events Manager to configure your conversion events:
You'll see an interface showing your domain and a list of up to 8 event slots.
Step 3: Prioritize Your Top 8 Events
This is the most important decision: which 8 events matter most to your business?
AEM will only measure your top 8 events for opted-out iOS users. If you have more than 8 events configured on your pixel, events ranked 9+ won't be measured for privacy-protected traffic.
Common event prioritization by business type: E-commerce:Step 4: Configure Event Values (Optional but Recommended)
For events like Purchase, you should include event values so Facebook can optimize for value, not just conversion count:
- Purchase: Pass the actual transaction value
- Lead: Pass the estimated value of a lead (e.g., $50 based on historical close rate)
- AddToCart: Pass the cart value
- Subscribe: Pass the subscription value (e.g., $29/month = $348 annual value)
This lets you optimize for ROAS instead of just cost per conversion, which is far more valuable for scaling.
Step 5: Wait 72 Hours for Changes to Take Effect
Here's the frustrating part: AEM configuration changes have a mandatory 72-hour waiting period before they take effect. This is a privacy requirement from Apple.
During those 72 hours:
- Don't make additional changes (they'll reset the clock)
- Don't panic if you don't see events immediately
- Continue running campaigns normally—existing configuration still applies
After 72 hours, your new event prioritization will be active for all future conversions.
Planning tip: If you're launching a major campaign or sale, configure your AEM events at least 3-4 days in advance so the waiting period doesn't impact your launch.
AEM Configuration Workflow
Complete process for setting up and optimizing Aggregated Event Measurement
Verify Domain
Confirm domain ownership in Facebook Business Manager
Prioritize Events
Rank your top 8 conversion events by business value
Configure AEM
Set event priority in Events Manager and wait 72 hours
Implement CAPI
Deploy Conversions API for maximum data capture
Monitor & Optimize
Track event performance and adjust priority as needed
Event Prioritization Strategy
Choosing the right 8 events is part art, part science. Here's how to think strategically about prioritization:
Prioritize Business Outcomes Over Vanity Metrics
It's tempting to track everything, but you only get 8 slots. Focus on events that directly tie to revenue or qualified leads:
Good priority order:- PageView (too generic, little signal)
- Button clicks that don't indicate intent
- Events that have low frequency (not enough data to optimize)
Use Custom Parameters Within Events
Since you're limited to 8 events, use custom parameters to add granularity without consuming additional event slots:
Example: Instead of creating separate events for "Purchase_Electronics" and "Purchase_Clothing," use a single "Purchase" event with a custom parameter:fbq('track', 'Purchase', {
value: 79.99,
currency: 'USD',
content_category: 'Electronics', // Custom parameter
content_type: 'product'
});
You can then segment and optimize based on these parameters in Ads Manager without consuming extra event slots.
Consider Multi-Stage Funnels
If you have a long sales funnel, balance between top-of-funnel signals and bottom-of-funnel conversions:
For a B2B SaaS company:This gives Facebook signals across the entire funnel, helping the algorithm optimize even when ultimate conversions (Subscribe) are rare.
Align with Campaign Objectives
Make sure your top-ranked AEM events match your campaign optimization goals:
| Campaign Objective | Top AEM Event Should Be |
|---|---|
| Conversions (Purchase) | Purchase |
| Lead Generation | Lead or CompleteRegistration |
| Catalog Sales | Purchase or AddToCart |
| App Installs | App Install event |
| Engagement | ViewContent or custom engagement event |
Review and Adjust Quarterly
Your business changes, your campaigns evolve, and your priorities shift. Review your AEM event prioritization every 3 months to ensure it still aligns with your strategy:
- Are you launching new products that need new events?
- Has your sales funnel changed?
- Are lower-ranked events generating more value than higher ones?
Remember: any changes require a 72-hour waiting period, so plan adjustments during low-traffic periods if possible.
The businesses that succeed are those that embrace data-driven decision making and continuous optimization.
Optimizing Campaigns with AEM
AEM isn't just about tracking—it directly affects how Facebook's algorithm optimizes your campaigns. Here's how to work with AEM constraints:
Choose Optimization Events Wisely
When setting up campaigns, the event you optimize for should be ranked high in your AEM priority list. Otherwise, Facebook won't have enough iOS conversion data to optimize effectively.
Best practice: Optimize for events ranked #1-3 in your AEM configuration. Lower-ranked events might not have sufficient signal for Facebook's algorithm to learn.Use Value-Based Bidding
If you've configured event values in AEM, use value optimization instead of conversion optimization:
- Bid strategy: Choose "Maximize Value" or "ROAS"
- Optimization event: Purchase or Lead with value
- Why it works: Facebook optimizes for higher-value conversions, not just volume
This is especially powerful for e-commerce where purchase values vary significantly.
Leverage Broad Targeting
With limited conversion data from iOS users, Facebook's algorithm benefits from broader targeting to find patterns:
- Use Advantage+ audiences or broad interest targeting
- Avoid overly narrow audiences (less than 1 million)
- Let the algorithm find high-value users within broad parameters
Implement Conversions API (If You Haven't)
We've mentioned this before, but it bears repeating: Conversions API is essential for maximizing AEM effectiveness:
Check out our complete CAPI setup guide for implementation details.
Monitor Modeled Conversions
Facebook uses statistical modeling to estimate total conversions when data is limited by privacy restrictions. In Ads Manager, you'll see two columns:
- Conversions: Actual tracked conversions
- Modeled conversions: Estimated total including untracked events
Troubleshooting Common AEM Issues
Even with proper setup, AEM can be tricky. Here are the most common issues and how to fix them:
Issue #1: Events Not Appearing in AEM Configuration
Symptom: You fire events from your pixel, but they don't show up when configuring AEM. Causes:- Events haven't been sent to Facebook yet (need at least one fire)
- Domain isn't verified
- Using custom event names that aren't recognized
Issue #2: Can't Configure AEM (Greyed Out)
Symptom: The "Configure Web Events" button is disabled or greyed out. Causes:- Domain not verified
- You don't have admin access to the Business Manager
- Someone else is already editing AEM configuration
Issue #3: Too Many Events (More Than 8)
Symptom: You have 15+ events on your pixel but can only prioritize 8 in AEM. Fix: This isn't really fixable—it's a hard limit. You need to:- Instead of: Purchase_Electronic, Purchase_Clothing, Purchase_Home
- Use: Purchase (with content_category parameter)
Issue #4: Conversions Dropped After iOS 14
Symptom: Your reported conversions dropped 30-50% after iOS 14.5 launched. Reality check: This is expected. You're not actually losing conversions—you're losing visibility into iOS users who opt out. Fix:Issue #5: 72-Hour Wait Is Too Long
Symptom: You need to change AEM configuration but can't wait 3 days. Reality: There's no workaround. The 72-hour waiting period is mandated by Apple for privacy reasons. Mitigation:- Plan AEM changes well in advance of major campaigns
- Make changes during slow periods (weekends, off-season)
- Avoid frequent changes—get your prioritization right the first time
The Future of Privacy-First Advertising
AEM is just the beginning. Apple, Google (with Privacy Sandbox), and regulators worldwide are pushing toward more privacy-focused advertising:
- Third-party cookie deprecation (Google Chrome is phasing these out)
- Stricter GDPR and CCPA enforcement
- More user control over data sharing
The advertisers who succeed will be those who:
AEM is annoying, yes—but it's also your training ground for the privacy-first future. Get good at working within constraints now, and you'll be ahead when more restrictions inevitably come.
Ready to audit your AEM setup and ensure you're capturing every possible conversion? Sign up for AdsMAA and get an AI-powered analysis of your tracking configuration, AEM prioritization, and optimization opportunities across your entire Facebook ad account.For more advanced tracking strategies, explore our guides on Facebook attribution windows and fixing conversion tracking issues.
Frequently Asked Questions
What is Aggregated Event Measurement?
Aggregated Event Measurement (AEM) is Facebook's privacy-focused measurement protocol for web conversions from iOS 14.5+ users who opt out of tracking. It allows you to measure up to 8 conversion events per domain in a privacy-compliant way using aggregated, anonymized data.
Do I need to configure AEM if I have the Conversions API?
Yes, absolutely. Even with Conversions API, AEM configuration is required for iOS 14.5+ users who opt out of tracking. The Conversions API and AEM work together—CAPI sends the data, while AEM determines which events get prioritized and measured for opted-out users.
Can I measure more than 8 events with AEM?
No, AEM has a hard limit of 8 conversion events per domain. This is a privacy requirement from Apple. You need to carefully prioritize which events matter most for your business and use custom parameters to add granularity within those 8 events.
How long does it take for AEM changes to go into effect?
AEM configuration changes have a 72-hour waiting period before they take effect. Plan ahead when making changes to your event prioritization, as you won't see the impact immediately and can't optimize based on new events during that window.
Ready to Transform Your Advertising?
Join thousands of marketers using AdsMAA to optimize their advertising with AI-powered tools.
No credit card required · Free plan available
Related Articles
Server-Side vs Client-Side Tracking: Which is Better for Your Business?
A comprehensive comparison of server-side and client-side tracking methods. Learn why 73% of marketers are switching to server-side tracking in 2025.
The Cookieless Future: How to Adapt Your Advertising Strategy in 2025
Third-party cookies are disappearing. Learn how to prepare your advertising strategy for a cookieless world with first-party data, server-side tracking, and AI.
10 Digital Advertising Trends That Will Define 2025
Stay ahead of the curve with these key digital advertising trends for 2025. From AI automation to privacy-first strategies, learn what's shaping the future.