Automatic App Event Logging
Updated: Oct 16, 2026
Copy for LLM
You can control Automatic App Event Logging directly in the app code (using the
AutoLogAppEventsEnabled flag) or through the toggles in Events Manager. Please note that if either setting is disabled, Automatic App Event Logging will be disabled. When launching an app in Korea, please note that Automatic App Event Logging may be disabled.When you use the versions of the Facebook SDK listed below, events related to user interaction with your app are collected automatically.
This applies to the following Facebook SDKs:
- Facebook SDK for Android v4.27 (and higher)
- Facebook SDK for iOS v4.19 (and higher)
- Facebook SDK for Unity v7.11 (and higher)
For Android, call
callbackManager.onActivityResult to pass the login results to the callbackManager. iOS does not require any code to collect events.Automatically Logged Events
When using the Facebook SDK, certain events in your app are automatically logged and collected for Facebook Events Manager unless you disable automatic event logging. These events are relevant for all use cases - targeting, measurement and optimization.
There are three key events collected as part of the Automatic App Event Logging: App Install, App Launch, and Purchase. When automatic logging is enabled, advertisers are able to disable these events, as well as other Facebook internal events such as login impression events. However, if you have disabled automatic logging, but still want to log specific events, such as install or purchase events, manually implement logging for these events in your app.
| Event | Details |
|---|---|
App Install | The first time a new user activates an app or the first time an app starts on a particular device. |
App Launch | When a person launches your app, the Facebook SDK is initialized and the event is logged. However, if a second app launch event occurs within 60 seconds of the first, the second app launch event is not logged. |
In-App Purchase | When a purchase processed by the Apple App Store or Google Play has been completed. If you use other payments platforms, you will need to add purchase event code manually. Note: If you’d like to use in-app purchases to measure Dynamic Ads conversions, please set the Product ID on the Apple App Store or the Google Play store to be equivalent to the Product ID used in the associated Dynamic Ad. |
Facebook SDK Crash Report (For Facebook Use Only.) | If your app crashed due to the Facebook SDK, a crash report is generated and sent to Facebook when your app is restarted. This report contains no user data and helps Facebook ensure the quality and stability of the SDK. To opt out of logging this event, disable automatically logged events. |
Automatically include more app event details
Facebook SDK will identify and send app metadata, like app links and screen titles. These will be included with logged events by default.
You can disable additional event details by setting the
AutoLogAppMetadataEnabled flag in your app code or by turning it off in Events Manager. If either of these toggles is disabled, this feature will be off.Disabling Automatic App Event Logging
If you do not want the Facebook SDK to collect app events automatically, you can disable automatic logging. If you have disabled automatic logging but still want to log specific events for Facebook Analytics, you must manually implement logging for these events in your app.
Send additional app information for Meta product development
FB SDK will automatically send sampled information about your app, such as the layout of elements on app screens. This information helps Meta improve ads systems and build new features. It is not used for ads delivery. You can disable sending product development data by setting the
LogProductImprovementEnabled flag in your app code or by turning it off in Events Manager. If either of these toggles is disabled, this feature will be off.