How to Configure Aggregated Event Measurement Priorities for D2C Catalog Brands

iOS 14.5 launched in 2021 and brought Aggregated Event Measurement (AEM). Most Indian D2C founders accepted Meta's defaults and moved on. Five years later, the default AEM setup is silently costing catalog-heavy brands 20-40% of attributed conversions.

AEM is the system Meta uses to track iOS conversions despite Apple's ATT restrictions. You get 8 prioritized events per verified domain, and the prioritization order changes how Meta reports your sales. Catalog brands need a different priority structure than non-catalog brands.

First: Confirm What AEM Actually Does

When an iOS 14.5+ user converts and they've denied ATT tracking, Meta can only report ONE conversion event per user per ad — the highest-priority event in your AEM configuration that fired.

• You define 8 events in priority order per verified domain

• The top event is the most valuable — it's the one Meta reports if the user fires it

• Lower-priority events are reported only if the higher-priority events don't fire for that user

• Non-iOS users and ATT-opted-in users see normal multi-event tracking

Priority is critical. If you have AddToCart at priority 1 and Purchase at priority 4, every ATT-restricted iOS user who added to cart will report as AddToCart, not Purchase — even if they bought. Your reported Purchase volume cratters.

The Standard D2C Priority Order

For most Indian D2C brands without catalog complexity:

1. Purchase

2. AddPaymentInfo (or InitiateCheckout)

3. AddToCart

4. ViewContent

5. Search

6. Lead (newsletter signup)

7. CompleteRegistration

8. Contact

Highest commercial value at the top. Lower-funnel events come last. This ensures iOS users who completed a Purchase report as Purchase, not lower events.

Why Catalog Brands Need a Different Order

Catalog brands (jewelry, apparel, electronics, beauty with SKU-level variation) often use product-specific events like 'PurchaseGold', 'PurchaseSilver', 'PurchaseBridal' or sub-category Purchase events. If you have multiple value tiers within Purchase, you need them at the top of AEM priority.

Recommended Catalog Brand Priority Order

1. Purchase (High Value) — e.g., orders over ₹5,000 or premium category

2. Purchase (Medium Value) — e.g., orders ₹2,000-5,000

3. Purchase (Standard) — e.g., orders below ₹2,000

4. AddPaymentInfo

5. AddToCart

6. ViewContent

7. Search

8. Lead

Why this works: Meta's Conversion Value Optimization in iOS uses AEM priorities. Splitting Purchase into value tiers lets Meta's optimization see high-value vs low-value conversions distinctly, even on ATT-restricted users. ROAS lifts 15-30% for catalog brands after this restructure.

How to Set Up Value-Tiered Purchase Events

Option A: Custom Events with Conditional Firing

Create custom events ('PurchaseHigh', 'PurchaseMid', 'PurchaseLow') in Events Manager. In your Pixel/CAPI implementation, fire the appropriate custom event based on order value:

• Order ≥ ₹5,000 → PurchaseHigh + standard Purchase

• Order ₹2,000-4,999 → PurchaseMid + standard Purchase

• Order < ₹2,000 → PurchaseLow + standard Purchase

Then set AEM priorities: PurchaseHigh top, PurchaseMid next, PurchaseLow third, standard Purchase fourth. This captures value tiers in priority without losing the standard Purchase reporting.

Option B: Meta's Built-in Value Optimization

Newer Meta accounts can enable Value Optimization on Purchase events, which automatically splits AEM into value buckets. Available in Events Manager → AEM → Configure Value Sets. Less customization but simpler setup.

Common Mistakes Indian D2C Catalog Brands Make

1. Leaving AEM at default with Purchase at priority 1 and no value differentiation. Loses Conversion Value Optimization signal.

2. Adding too many low-funnel events to AEM. Slot 5-8 should be high-funnel: Search, Lead, Registration. Don't waste them on AddPaymentInfo variants.

3. Changing AEM priorities mid-quarter. Each change triggers a 72-hour re-stabilization window. Plan changes around campaign launch dates.

4. Forgetting to verify domain before configuring AEM. AEM only works on verified domains. Unverified domains get a default fallback config that's worse than custom.

5. Not aligning AEM with optimization event. If you optimize campaigns for AddToCart but AEM prioritizes Purchase, iOS users firing both events report as Purchase — your optimization signal weakens.

How Wittelsbach AI Optimizes AEM for Catalog Brands

Bach AI analyzes your order value distribution and recommends the optimal AEM priority order — including custom event splits for value tiers. It also flags AEM-optimization-event misalignment that's silently hurting iOS performance. Most catalog brands see 15-30% iOS ROAS lift within 30 days. Connect your Meta account at [app.wittelsbach.ai](https://app.wittelsbach.ai) for a free audit.

Frequently Asked Questions

How long does AEM reconfiguration take to show results?

72 hours for stabilization, then 7-14 days for measurable performance shift. Don't expect immediate ROAS lift. The change accumulates as more iOS users convert under the new priority order. Don't make a second AEM change inside 14 days — you'll obscure which change moved the needle.

Do I need separate AEM configs for each catalog category?

Not usually. AEM is per-domain, not per-category. If all your catalog products live on the same domain, one AEM config covers them. The differentiation happens at the event level (PurchaseHigh vs PurchaseLow), not at the domain level. Multi-domain catalog brands (separate domains per category) configure AEM per domain.

How does Advantage+ Shopping interact with AEM?

Advantage+ Shopping respects AEM priorities for iOS users but its broader optimization algorithm aggregates signal differently. Value-tiered AEM helps Advantage+ Shopping distinguish high-value vs low-value buyers, which improves the auction model. Don't run Advantage+ Shopping with default AEM if you have meaningful AOV variation.

Can I have more than 8 events in AEM?

No. 8 events per verified domain is the hard limit. If you have more events you care about, prioritize ruthlessly — the top 4 should be your commercially critical events, the bottom 4 are upper-funnel signals. Don't waste slots on rarely-fired events or test events.

Does AEM affect non-iOS users?

No. Android users, desktop users, and iOS users who opted-in to ATT see normal multi-event tracking — all events you fire are reported. AEM only constrains the ATT-restricted iOS subset, which is roughly 35-55% of users in Tier 1 Indian metros and 15-25% in Tier 2/3 cities.