A question on r/FacebookAds recently got marketers talking: how to fix Meta SDK event attribution that has been stuck for months. The thread surfaced several practical takes on Aggregated Event Measurement (AEM) and SDK setup, but the topic deserves a deeper look.
Community Spotlight
This post was inspired by a discussion on Reddit: Need help with Meta SDK & event attribution - stuck for 3+ months (growth marketer here)
Posted by an Anonymous Community Member in r/FacebookAds
When your primary UA channel stops reporting downstream conversions, campaigns grind to a halt. Growth marketers frequently find themselves caught between Meta's opaque reporting delays and their own engineering team's SDK implementation.
Diagnosing the Event Drop-off
If installs are tracking but purchase events are not, the issue usually lies in post-iOS 14 privacy configurations. Several replies pointed out that basic SDK integration is no longer enough.
Aggregated Event Measurement (AEM): Meta requires events to be prioritised. If your high-value events aren't mapped correctly in Events Manager, iOS users who opt out of ATT will never trigger a conversion.
Event Parameter Mismatches: If the value or currency parameters passed via the SDK do not match Meta's exact schema, the event is logged but cannot be used for ROAS optimisation.
The 72-Hour Delay: SKAN conversions take up to 72 hours to report. Marketers often pause campaigns prematurely because they mistake privacy-driven delays for broken tracking.
Many teams discover too late that relying solely on the Meta SDK leaves them blind. Without raw data logs, it is impossible to know if the app failed to fire the event, or if Meta simply refused to attribute it.
Tech Explainer:
App Tracking Transparency (ATT) requires iOS apps to ask user permission before tracking them across apps and websites. When users opt out, granular event attribution is restricted, and networks must rely on aggregated, delayed reporting frameworks like SKAN.
How a Modern MMP Handles This
A modern MMP would unify deep linking and attribution, sitting between your app and the ad networks. Instead of wrestling with Meta's SDK, you integrate the MMP SDK once. The MMP then handles the complex server-to-server postbacks, automatically formats the event parameters to Meta's requirements, and provides a clear audit trail of every fired event.
Linkrunner, for instance, does exactly this. With integration typically completed in 2-4 hours, it natively manages Meta and Google integrations while providing full SKAN 4.0 support. Because Linkrunner offers unrestricted CSV and API exports, you can instantly verify if an event fired correctly on the device, isolating the problem in minutes rather than months. Check the Linkrunner SKAN setup guide to see how easy it is to manage privacy-compliant events.
Steps to Unblock Your Attribution
Verify your AEM event priority in Meta Events Manager.
Check your iOS 14+ campaign settings to ensure SKAN is enabled.
Migrate to server-to-server event tracking via an independent MMP to guarantee data delivery.
The original thread raised a valid point about the frustration of siloed network SDKs. Here's the actionable version: you need an independent source of truth.
If you're evaluating your attribution setup after reading this, Linkrunner offers 25,000 free attributed installs to test with, no commitment required. Request a demo
