Pulsar
field guide · domain & ios events
Present: ← → Space · Esc back to Doc

Pulsar · Field guide · No. 18 · What iOS 14.5 broke, what Aggregated Event Measurement is, and the domain-verification setup that keeps your money events counting.

Don’t Let iOS Eat Your Conversions

Since iOS 14.5, opted-out users go dark. Domain verification + Aggregated Event Measurement are how you keep your Purchase events counting on Apple devices.

01

What iOS 14.5 actually broke

iOS 14.5 introduced App Tracking Transparency — the “Ask App Not to Track” prompt. Most people tap it. For every opted-out user, the browser signal collapses and Meta’s attribution windows shrink.

A big slice of your Apple traffic now buys invisibly — the sale happens, the event just can’t be tied back the old way.

You can’t opt those users back in. But you can configure the workaround Meta built — and it starts with proving you own your domain.

02

Aggregated Event Measurement (AEM)

AEM is Meta’s privacy-safe workaround for opted-out iOS users. The catch: a maximum of 8 events per domain, ranked in priority order — and for an opted-out user, only the highest-priority event they trigger is counted.

i
8 slots, ranked. If Purchase isn’t near the top, an opted-out buyer who also viewed and added-to-cart may get counted on the lesser event — and your Purchase number understates reality.
03

Verify your domain first

Before you can rank events, Meta needs to know the domain is yours. You verify it in Business Settings → Brand Safety → Domains by one of three proofs.

MethodHow
DNS TXT recordadd a TXT record at your registrar (most durable)
Meta-tagpaste a <meta> tag into your homepage <head>
HTML fileupload a verification file to your web root

Only the verifying business can configure that domain’s events and control who edits link content. Verify the root domain so subdomains are covered.

04

Rank your 8 events — Purchase on top

In Events Manager, pick and order up to 8 events for the domain. Rank by money impact, highest first.

1 · Purchase (or your true money event) — always the top slot.
2 · InitiateCheckout — the strongest pre-purchase intent.
3 · AddToCart, then ViewContent, Lead, etc. down to 8.

Optimizing a campaign for an event that isn’t configured (or is ranked low) quietly caps what it can learn from iOS users.

05

The attribution window shrank too

Post-iOS, the default attribution setting narrowed to 7-day click / 1-day view (the longer 28-day windows largely went away). Your reported conversions look lower not because sales dropped — but because the counting window shrank.

Plan reporting around it: compare like-for-like windows month to month, and don’t read a drop the day a window changes as a real decline.

06

Setup steps, gotchas — and pairing with CAPI

Verify the domain (DNS / meta-tag / file) in Business Settings.
Configure the 8 events in Events Manager and rank Purchase #1.
Allow ~72 hours for changes to propagate; re-ranking has a cooldown.
  • ×
    Unverified domain. You simply can’t configure AEM — iOS conversions stay broken.
  • ×
    Purchase ranked low. Opted-out buyers get miscounted on a lesser event.
⚙
Pair this with the Conversions API (No. 17): server-side sending recovers signal the browser lost to ATT, while AEM keeps the opted-out slice counting. Do both.
1 / 8