AppsFlyer

This integration combines Amplitude's analytics with AppsFlyer's attribution tools into one unified system. With it, you can share all user data in real-time and help non-technical team members pinpoint your targeting, optimize your ad spend, and boost your Return on Investment (ROI).

About AppsFlyer

AppsFlyer provides mobile advertising attribution and analytics, helping marketers to pinpoint their targeting optimize their ad spend and boost their ROI. Send your AppsFlyer data to Amplitude to view how your different acquisition sources are performing.

Considerations

AppsFlyer has two integrations with Amplitude:

• Amplitude Attribution API to send install data to Amplitude. Make sure you understand the limitations of the Attribution API before setting up this integration.
• Amplitude HTTP V2 API to send install and in-app data to Amplitude.

Attribution API limitations:

• Attribution events are held for up to 72 hours for potential user matching. If a user didn't trigger an Amplitude event within 72 hours of the attribution event, the attribution data is dropped.
• Attribution is matched to Amplitude users or events with the Advertising ID (IDFA/IDFV or ADID). Make sure you send this ID with your Amplitude events. Configure the Android SDK and iOS SDK to send this data. If you use Browser SDK, send the Advertising ID with HTTP API.

These limitations can cause discrepancies between AppsFlyer and Amplitude data. When a user doesn't trigger any events measured by Amplitude within 72 hours, the links between the same user across both platforms may be temporarily affected.

This can result in a lower event count in Amplitude when comparing to events in AppsFlyer.

Amplitude removes the advertising ID information due to privacy concerns, so you may see ADID = null when you send it.

The attribution information is processed, but is stripped of the ADID before the event is saved.

When choosing the HTTP V2 API integration, make sure to setup the following:

• Amplitude device ID
• Customer user ID
• Amplitude session ID

Choose either the Amplitude Attribution API (V1) or HTTP V2 API (V2) integration.

Don't use both simultaneously. Using both versions at the same time may result in duplicate events being sent to Amplitude.

Some media sources have data restrictions that cause app installs to be categorized as organic or to not be shared with third parties like Amplitude. When required, installs and in-app events are sent without media source name and campaign details.

Find more information about sources with data restrictions in Appflyer's documentation.

For more information about AppsFlyer's integration, view their help center

Set up and use the integration

You can find detailed instructions on implementing this integration in the AppsFlyer documentation.