When using the Meta SDK for app event tracking, you may encounter issues such as missing metrics or discrepancies in event attribution. This guide provides an overview of common issues, their causes, and actionable steps to resolve them.

The Meta SDK enables tracking of various app events, such as fb_mobile_activate_app, Purchase, and View Content. These events help measure user interactions and campaign performance. However, proper configuration is essential to ensure accurate tracking and attribution.

The fb_mobile_aem_auto_setup_opt_out status indicates that AEM Auto Setup is disabled in the app (FBSDKAemAutoSetupEnabled = false). This setting:

The Mobile App Install metric in Events Manager or Ads Manager represents Meta’s attributed install (the first app open after an ad click). It is not a separate event fired by the app. If fb_mobile_activate_app events are logging correctly but Install counts are missing, the issue is likely related to:

Ensure that the Meta SDK is properly initialized in your app. The presence of fb_mobile_activate_app events confirms that the SDK is logging events correctly.

Review your attribution setup in Events Manager to ensure that:

If Install counts are low or missing, recreate your app install ads or campaigns using the latest settings. This ensures that install attribution is correctly applied.

Does the fb_mobile_aem_auto_setup_opt_out status affect app event tracking?

No, it only disables automatic deep-link capture for AEM on iOS 14.5+ users who opted out via ATT. Other app events are not affected.

Why are Mobile App Install metrics missing while other events are logging?

This usually points to an issue with attribution setup or campaign configuration, not the SDK itself. By following these steps and understanding the underlying causes, you can effectively troubleshoot app event tracking and attribution issues in the Meta SDK.

We're happy to help. Reach out through LiveChat on your Tapcart Dashboard or email us at [email protected].