What You Will Learn
- The Events Manager interface — what each section contains
- How to verify pixel and CAPI events are firing with correct parameters
- Configuring Aggregated Event Measurement — domain verification and 8-event priority list
- How to diagnose and fix common event tracking errors
- Creating Custom Conversions from standard and custom events
- Managing multiple data sources (pixels, offline event sets, app events)
Events Manager Overview
Events Manager (accessed from Meta Business Manager or directly at business.facebook.com/events_manager) is the dashboard for all Meta tracking configuration. Key sections:
- Overview. Event volume chart, active data sources, and quick health indicators for your pixel and CAPI. Shows total events received in the last 7 days by event type.
- Events. Detailed breakdown of each event type — volume over time, top parameters, match quality, and any issues detected.
- Test Events. Real-time event testing tool — enter your website URL and Meta shows events firing live as you browse.
- Diagnostics. Active issues requiring attention — missing required parameters, AEM configuration warnings, signal quality problems.
- Settings. Pixel ID, access tokens, AEM configuration, advanced matching settings, and partner integration connections.
Access path
business.facebook.com → Events Manager
Event retention
Events Manager stores up to 180 days of event data
AEM events limit
Maximum prioritised events per domain
Verifying Events
Test Events tool
The Test Events tool is the most reliable method to verify pixel and CAPI events. In Events Manager → your pixel → Test Events tab:
- Enter your website URL in the "Test browser events" field
- Click "Open website" — your site opens in a new window
- Complete the actions you want to verify (visit a product page, add to cart, complete a purchase)
- Events appear in real time in the Test Events panel
Each event entry shows: event name, timestamp, source (pixel/browser vs CAPI/server), parameters received, and any validation warnings. Verify that Purchase events include value, currency, and content_ids; that AddToCart events include content_ids and value.
What to check for each event
| Event | Must Have | Should Have |
|---|---|---|
| PageView | Fires on every page | No parameters required |
| ViewContent | content_ids, content_type | value, currency |
| AddToCart | content_ids, value, currency | content_type, num_items |
| InitiateCheckout | value, currency | num_items, content_ids |
| Purchase | value, currency (required) | content_ids, order_id, content_type |
| Lead | Event fires on form submission | value, currency if applicable |
Aggregated Event Measurement Configuration
AEM must be configured before Meta can attribute iOS 14+ conversions to your ads. Two steps required:
Step 1: Verify your domain
In Meta Business Manager → Brand Safety → Domains → Add a Domain. Enter your root domain (e.g. yourdomain.com — not www or a subdomain). Verification options:
- HTML file: upload a Meta-provided file to your root domain directory
- Meta tag: add a meta verification tag to your homepage
<head> - DNS TXT record: add a TXT record to your domain's DNS settings
Once verified, click "Verify Domain" and check the status turns green. Only verified domains can have AEM events configured.
Step 2: Prioritise your 8 events
In Events Manager → your pixel → Aggregated Event Measurement → Configure Web Events:
- Click "Add Events" and select up to 8 events from your active pixel events
- Drag to reorder — Priority 1 is the most important event (typically Purchase)
- Click Publish
Recommended priority order (e-commerce)
| Priority | Event | Why |
|---|---|---|
| 1 | Purchase | The primary conversion — always highest priority |
| 2 | InitiateCheckout | High-intent funnel step; proxy for Purchase when volume is low |
| 3 | AddToCart | Product interest signal for Smart Bidding |
| 4 | ViewContent | Product page view for dynamic remarketing |
| 5 | Lead | If applicable to the business |
| 6–8 | Business-specific events | Custom conversions relevant to your funnel |
Diagnosing Common Issues
| Issue | Likely Cause | Fix |
|---|---|---|
| No events appearing in Events Manager | Pixel not installed; JavaScript error preventing pixel from loading | Use Pixel Helper to check if base code is present; check browser console for JavaScript errors |
| Purchase event not firing | Pixel event code not on confirmation page; GTM trigger not firing | Verify GTM trigger conditions; check the confirmation page URL pattern matches the trigger |
| Purchase firing on wrong page | Pixel event code placed globally or on the wrong template | Restrict the Purchase event tag trigger to confirmation page URL only |
| Double conversion counting | CAPI and pixel both firing without event_id deduplication | Add matching event_id to both pixel and CAPI calls |
| Low Event Match Quality (<6) | Missing email/phone in CAPI user_data | Pass hashed email and phone with every CAPI event; enable Advanced Matching on pixel |
| AEM warning in Diagnostics | Domain not verified or events not prioritised | Complete domain verification and configure 8-event priority list |
Custom Conversions
Custom Conversions allow you to define specific conversion conditions from standard or custom pixel events — for example, a Purchase event where value is above £100, or a PageView on a specific URL pattern.
Create in Events Manager → Custom Conversions → Create Custom Conversion:
- Select the event type to base the conversion on (standard event or custom event name)
- Add rules to narrow the trigger (URL contains, event parameter equals a specific value)
- Set a conversion name and assign a category (Purchase, Lead, etc.)
- Optionally set a default conversion value
Custom Conversions are useful for: tracking specific product category purchases separately from all purchases; distinguishing high-value orders from low-value orders; tracking conversions from specific landing pages when you cannot easily modify the pixel event code.
Managing Data Sources
Events Manager manages all Meta data sources from one location — not just web pixels:
- Web (Meta Pixel). Browser-based tracking for website events — the primary source for most advertisers.
- App (Mobile SDK). In-app event tracking via Facebook SDK or Mobile Measurement Partner (MMP) for mobile apps.
- Offline Event Sets. Upload CSV files of offline conversions (in-store purchases, phone orders) to attribute them to Meta campaigns. Match by email, phone, or other identifiers.
- CRM / Conversions API. Server-side event sources — CAPI-connected data sources appear alongside pixel sources with their own EMQ score.
- Partner Integrations. Connected platform integrations (Shopify, WooCommerce) appear as data sources with their own event stream.
Authentic Sources
AEM setup, domain verification, and event prioritisation.
Using the Test Events tool to verify pixel and CAPI events.