These in-app events help you to log how loyal users discover your app, and attribute them to specific
campaigns/media-sources. Please take the time define the event/s you want to measure to allow you
to send ROI (Return on Investment) and LTV (Lifetime Value). [...]
Opt-out of collection of Android ID.
If the app does NOT contain Google Play Services, Android ID is collected by the SDK.
However, apps with Google play services should avoid Android ID collection as this is in violation of the Google Play policy.
Opt-out of collection of IMEI.
If the app does NOT contain Google Play Services, device IMEI is collected by the SDK.
However, apps with Google play services should avoid IMEI collection as this is in violation of the Google Play policy.
Setting user local currency code for in-app purchases.
The currency code should be a 3 character ISO 4217 code. (default is USD).
You can set the currency code for all events by calling the following method.
Setting your own customer ID enables you to cross-reference your own unique ID with AppsFlyer’s unique ID and the other devices’ IDs.
This ID is available in AppsFlyer CSV reports along with Postback APIs for cross-referencing with your internal IDs.
The sharing filter blocks the sharing of S2S events via postbacks/API with integrated partners and other third-party integrations.
Use the filter to fulfill regulatory requirements like GDPR and CCPA, to comply with user opt-out mechanisms, and for other business logic reasons.
Once this API is invoked, our SDK no longer communicates with our servers and stops functioning.
In some extreme cases you might want to shut down all SDK activity due to legal and privacy compliance.
This can be achieved with the stop API.