Mobile attribution partners (Appsflyer / Adjust / Branch / Singular) use the Attribution API to send data to Amplitude. There are several potential reasons you might not be seeing your attribution events in Amplitude, including:
- The Amplitude events are not sent with an advertising ID.
- The attribution events were not successfully sent to Amplitude.
- Your project has reached the instrumentation limit.
- The event type has been blocked or deleted in the Amplitude project.
The flowchart below show how mapping is based on reconciling the Amplitude event with the attribution event via matching the advertising ID. Without the advertising ID, there is no way to connect these events. Amplitude will store unmapped attribution events for 72 hours. If there is still no corresponding Amplitude event after that, Amplitude will drop the attribution event.
How you'll troubleshoot this issue depends on how data is sent to Amplitude.
Troubleshooting for iOS SDK and Android SDK
-
-
Make sure advertising ID tracking is enabled, as described in the Track Advertising ID documentation.
-
Make sure the attribution events are being sent successfully to Amplitude. To find this out, ask your attribution provider if they are successfully sending the attribution events to Amplitude (if they are receiving 200 status codes by Amplitude, the events are being sent successfully).
-
Troubleshooting for Javascript and React Native SDK
Because these SDKs do not have the possibility to track the Advertising ID automatically, you will have to follow a slightly different procedure:
-
-
Send an Amplitude event with the advertising ID via the HTTP API (these events should be sent with the same device_id/user ID so that these user’s activities can be merged).
-
Make sure the attribution events are being sent successfully to Amplitude. To find this out, ask your attribution provider if they are successfully sending the attribution events to Amplitude (if they are receiving 200 status codes by Amplitude, the events are being sent successfully).
-