Meta · Published 2025-11-25 · 2 min read
A Meta error. AEM campaigns: no installs and no purchase events
On a first AEM campaign launch you often see Ads Manager showing neither installs nor purchases. As a rule the problem is the integration: events from the MMP are not reaching AEM.
Diagnostics
- Open Event Manager.
- Select the app.
- Go to the event in question.
- Under Settings → Check App Eligibility, look at the status.
The most common messages
- “Advertiser Tracking Enabled parameter volume out-of-range”
- “Action required from mobile measurement partner”
The cause. Meta is telling you it receives too few events from users who allowed tracking via ATT. In practice the problem is more often a conflict between AppsFlyer and the Facebook SDK. When both sources send events, AEM stops accepting them correctly.
Fixes
- Quick (temporary):
In Event Manager → Choose Event → Manage → Choose one integration to send this event to META, pick either AppsFlyer or the Facebook SDK. After that Meta will only receive events from the chosen source.
- Proper:
Decide on one primary source
- using the Facebook SDK → disable the AppsFlyer partner;
- using AppsFlyer → remove the Facebook SDK from the code.
Why the temporary fix is a bad idea. AppsFlyer warns officially that the quick method can duplicate events, purchase events in particular. That doubles revenue and corrupts campaign optimisation. Source: AppsFlyer — Meta ads discrepancies.
A different message. If you see “We haven't received enough signals from the app event over the last 30 days”, make sure the integration is set up correctly (see above) and wait 24–48 hours. The error clears itself.
🎓 UA Manager 2026 — starts 15 January 2026. Everyone on the UA Manager 2026 course gets access to a Notion with checklists and videos walking through the standard integrations (AppsFlyer, Adjust, Apphud and others). If you want to get UA straight and avoid mistakes like this one, sign up for the cohort starting 15 January 2026.