# Events Manager, AEM and event quality

> Use Events Manager diagnostics, Event Match Quality, Aggregated Event Measurement changes and dataset hygiene.

Source: https://mentionx.ai/learn/meta-ads/meta-ads-events-manager-aem  
Author: Dipuck Jones, founder of MentionX  
Updated: 5 November 2026  
Level: Practitioner

**Events Manager is the control room for your Meta dataset (Pixel). After you connect Pixel and Conversions API, you use it to verify event volume, read Event Match Quality, fix broken parameters, and understand how Aggregated Event Measurement (AEM) now works for iOS-era privacy. The old "pick eight website events" choreography is largely gone for web — Meta documents automatic AEM processing for eligible website events and removal of the AEM configuration tab — but you still need clean events, value parameters and identifiers. This lesson is the weekly hygiene pass performance teams skip until CPA explodes.**

> **Key takeaways**
>
> - **Dataset hygiene beats new campaigns.** Broken events poison Advantage+.
> - **EMQ** shows how well events match people; raise it with lawful advanced matching.
> - **AEM for website events** is largely automatic now; do not hunt for a deprecated eight-event priority UI unless your account still shows it.
> - Send **value and currency** on purchase-like events for value optimisation.
> - Review **browser vs server** volume weekly after any site release.

*Checked 5 November 2026 (CET) against Meta Business Help Center, Meta for Developers docs, Meta for Business news posts and the Ads Manager UI labels cited in Sources. Meta renames and rolls out features by account, so confirm labels and availability in your own Ads Manager. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.*

## What you look at every week in Events Manager

| View | Question it answers | Red flag |
|---|---|---|
| Overview / activity | Are key events firing today? | Sudden zeroes after a deploy |
| Per-event diagnostics | Are required parameters present? | Purchase without value/currency |
| Event Match Quality | Can Meta match events to accounts? | Poor/Low for the optimisation event |
| Integration quality | Is CAPI connected and verified? | Server volume near zero |
| Test events | Does a real conversion appear end-to-end? | Test works, production does not |

Bookmark the dataset URL. Do not rely on Ads Manager alone; it hides parameter failures.

## Event Match Quality in practice

EMQ scores how effectively Meta can match your event to a person using identifiers you send. Meta's Event Match Quality help explains that scores update from recent event traffic (commonly described around a recent window such as the last 48 hours in Meta developer materials).

| Identifier | Why it helps | Marketer tip |
|---|---|---|
| Email (hashed) | Strong match key | Capture on lead/demo forms |
| Phone (hashed) | Strong on mobile-heavy markets | Normalise country codes before hash |
| fbp | Browser Pixel cookie | Needs Pixel loading |
| fbc | Click ID from fbclid | Preserve in landing URLs / first-party storage |
| external_id | Your CRM/user id | Stable per person |
| Client IP / user agent (server) | Helps server events | Sent by proper CAPI payloads |

*Our view:* EMQ work is usually form-field and CRM work, not Ads Manager tinkering. Marketing ops owns it with engineering.

## Aggregated Event Measurement status (web vs app)

Historically, iOS 14+ forced advertisers to prioritise a small set of website events for AEM. Meta's Aggregated Event Measurement help and product updates have since moved website AEM toward **automatic processing**, including removal of the AEM configuration tab that held the eight-event priority list and related domain steps for that web workflow. App measurement and MMP reporting paths can still use AEM protocols with privacy protections.

What you should do in November 2026:

1. Open Events Manager and confirm whether any AEM configuration UI still appears on your dataset (rollouts vary).
2. Stop teaching your team a rigid "eight events only" process for web if the UI no longer supports it.
3. Still keep event taxonomies tight — automatic processing is not a licence for 40 noisy custom events.
4. For apps, read the current app + MMP AEM notes before changing the event schema.

## Custom conversions vs custom events

| Tool | What it is | Use when |
|---|---|---|
| Custom event | Fired from Pixel/CAPI with your name | You control the code/GTM |
| Custom conversion | Rules on URL or event parameters inside Events Manager | You need a quick rule without a release |
| Standard event | Meta's named events (Purchase, Lead…) | Default choice for optimisation |

Prefer standard events for optimisation. Use custom events for SaaS milestones (`qualified_demo`) sent via CAPI, then optimise to them when volume allows.

## Value optimisation prerequisites

If you want ROAS goals or value optimisation:

1. Purchase (or equivalent) events include `value` and `currency`.
2. Values match the order revenue finance trusts (tax/shipping policy documented).
3. Refunds and cancellations have a reconciliation plan (even if imperfect).
4. CAPI carries the same value as the Pixel for deduplicated purchases.

## Domain and brand safety connections

Verify the domain in Business settings when Meta asks for features that require it (branded content, some claiming flows, historical AEM steps). Keep the Page, Instagram account and dataset linked so diagnostics do not show ownership warnings that block tools.

## Worked example: Ledgerline

*Ledgerline is a fictional accounts-payable software company. Details are illustrative.*

| Metric | Before (illustrative) | After (illustrative) |
|---|---|---|
| Schedule EMQ | Poor | Good |
| Identifiers on Schedule | fbp only | fbp + email hash + external_id |
| Server share of Schedule | 12% | 78% |
| Ads Manager vs CRM gap (28d) | 34% undercount | 9% undercount |
| Custom junk events | 22 | 7 |

### Walkthrough

1. Ledgerline's GTM preview showed Lead firing on every form start, not submit. Events Manager volume looked healthy while sales starved.
2. They fixed the trigger, added Schedule from the CRM via CAPI, and hashed business email.
3. EMQ on Schedule moved to Good within a few days of traffic. Learning stabilised on the Advantage+ Leads ad set.
4. Competitor C still optimised to the broken Lead event because "volume looked fine" in Ads Manager. Their CRM acceptance rate told the real story.

> **Pro move:** after every major website release, run Test Events with one real conversion (or staging) and paste a screenshot into the release ticket. No screenshot, no ship — same discipline as [GTM debugging](https://mentionx.ai/learn/gtm/gtm-debugging-preview-tag-assistant).

## Common mistakes

- **Celebrating event volume** without checking parameters and EMQ.
- **Teaching the deprecated eight-event web priority ritual** after Meta removed that tab for website AEM.
- **Forty custom events** named by different agencies over three years.
- **Value in the wrong currency** or net vs gross mismatch with finance.
- **Never comparing** Events Manager to CRM or GA4 key events ([GA4](https://mentionx.ai/learn/ga4/ga4-for-marketers)).

## Try it yourself

In Events Manager, open your main optimisation event. Record EMQ rating, whether server events appear, and whether value/currency is present if relevant. File one ticket for the biggest gap.

## Quick quiz

**1. What does Event Match Quality measure?**

*Answer:* How effectively Meta can match your events to people using the identifiers you send.

**2. What changed about website AEM configuration?**

*Answer:* Meta moved eligible website AEM processing toward automatic handling and removed the old AEM configuration tab used to prioritise up to eight events — confirm your UI.

**3. Why send value and currency on Purchase?**

*Answer:* So value optimisation and ROAS goals have accurate revenue signals.

## What should you check before the next lesson?

- EMQ and server share for your optimisation event are written down.
- You know whether any AEM UI still appears on your dataset.
- Creative stakeholders are lined up for lessons 8 and 9.

Previous: [Meta Pixel and Conversions API setup](https://mentionx.ai/learn/meta-ads/meta-ads-pixel-conversions-api). Next: [Creative diversification and Meta Andromeda](https://mentionx.ai/learn/meta-ads/meta-ads-creative-diversification-andromeda). Or return to the [Meta Ads for Marketers track](https://mentionx.ai/learn/meta-ads/meta-ads-for-marketers). Related: [GTM Meta Pixel and CAPI](https://mentionx.ai/learn/gtm/gtm-meta-pixel-capi), [GA4 events and enhanced measurement](https://mentionx.ai/learn/ga4/ga4-events-enhanced-measurement), [GTM debugging with Preview](https://mentionx.ai/learn/gtm/gtm-debugging-preview-tag-assistant).

## Common questions

**Do I still prioritise eight Aggregated Event Measurement events?** For website events, Meta moved AEM to automatic processing and removed the old AEM configuration tab that made advertisers prioritise up to eight events. Confirm the current Events Manager UI in your account; app campaigns may still differ.

**What Event Match Quality should I aim for?** Meta's guidance centres on Good or Great. Practically, many teams treat about 6.0+ as the floor while they add email, phone, fbp, fbc and external_id where lawful.

**Where do I see server vs browser event volume?** In Events Manager, open the dataset and review diagnostics / overview charts that break out browser and server activity for each event.
## Sources

- Meta Business Help Center, [About Meta's Aggregated Event Measurement](https://www.facebook.com/business/help/721422165168355)
- Meta Business Help Center, [About Event Match Quality](https://www.facebook.com/business/help/765081237991954)
- Meta for Developers, [Verifying your Conversions API setup](https://developers.facebook.com/docs/marketing-api/conversions-api/verifying-setup/)
- Meta for Developers, [Dataset Quality API](https://developers.facebook.com/docs/marketing-api/conversions-api/dataset-quality-api)
- Meta Business Help Center, [Get started with Events Manager](https://www.facebook.com/business/help/890079207922484)
- All accessed 5 Nov 2026.

## Frequently asked questions

### Do I still prioritise eight Aggregated Event Measurement events?

For website events, Meta moved AEM to automatic processing and removed the old AEM configuration tab that made advertisers prioritise up to eight events. Confirm the current Events Manager UI in your account; app campaigns may still differ.

### What Event Match Quality should I aim for?

Meta's guidance centres on Good or Great. Practically, many teams treat about 6.0+ as the floor while they add email, phone, fbp, fbc and external_id where lawful.

### Where do I see server vs browser event volume?

In Events Manager, open the dataset and review diagnostics / overview charts that break out browser and server activity for each event.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/meta-ads/meta-ads-events-manager-aem