Adjust

This integration combines Amplitude's analytics with Adjust's attribution tools into one unified system. Use this integration to share user data in real time and help non-technical team members see where users come from and identify your highest-performing sources.

About Adjust

Considerations

• Adjust uses the Attribution API, which means:
  • Amplitude holds attribution events for up to 72 hours for potential user matching. If a user doesn't trigger an Amplitude event within 72 hours of the attribution event, Amplitude drops the attribution data.
  • Amplitude matches attribution to users or events with a device identifier shared between your Amplitude events and the attribution postback. This identifier can be the Advertising ID (IDFA on iOS, or ADID/GAID on Android) or a non-advertising identifier (IDFV on iOS, or App Set ID on Android). Send the same identifier with your Amplitude events. You must configure the Android SDK and iOS SDK to send this data. If you use the Browser SDK, send the identifier with the HTTP API.
  • Note that while the Advertising ID can be set as Device ID (the SDKs set this automatically), the Advertising ID must also be set as a top-level field in your request payload to Amplitude. You can find this in the HTTP API V2 example upload request body.
  • When you can't collect advertising IDs, for example in child-directed apps, match on a non-advertising identifier. On Android, use App Set ID: the Amplitude Android SDK collects it by default and enableCoppaControl doesn't disable it. Make sure your app includes the Google Play Services App Set dependency (com.google.android.gms:play-services-appset) so the SDK can read the ID, and that you don't call disableAppSetId(), then configure Adjust to send the matching App Set ID in its postback. On iOS, IDFV serves the same purpose, and the SDK collects it by default without ATT consent. Note that enableCoppaControl disables IDFV along with IDFA, so if you enable COPPA control on iOS, no vendor or advertising ID is available for matching.
• Adjust and Amplitude data can sometimes show a discrepancy. When a user doesn't trigger any events that Amplitude tracks within 72 hours, the linkage between the same user across both platforms may be temporarily affected. This may result in a lower event count in Amplitude when compared to events in Adjust.
• Amplitude removes the ADID information for privacy reasons, so you see ADID = null when you send ADID. Amplitude processes the attribution information, but strips the ADID before saving the event.

Set up the integration