Mobile attribution troubleshooting
이 페이지는 아직 귀하의 언어로 번역되지 않았습니다. 현재 작업 중이므로 곧 다시 확인해 주십시오.
Mobile attribution events from partners such as AppsFlyer, Adjust, or Branch can fail to match a user in Amplitude. This page covers Apple's IDFA changes, which are the most common root cause, and the two failure modes that follow from them.
iOS 14 changes
At WWDC 2020, Apple announced that iOS 14 requires users to opt in to tracking. The IDFA is only present for users who explicitly opt in, and the percentage of users who do so is likely to be low.
This article covers frequently asked questions about Apple's iOS 14 IDFA changes.
Does Amplitude accept IDFA (Identifier for Advertisers) as the device identifier on iOS?
By default, Amplitude's iOS SDK uses IDFV (Identifier for Vendor) for the device ID. You can change this and use any value as the device identifier. The SDK includes an option to use IDFA as the device ID, but this option only works if the user has permitted the application to use IDFA.
What are the implications of Apple's IDFA changes on user tracking?
For logged-in users, there's no impact. Even if the device ID changes, events continue to merge from devices when Amplitude receives a common user ID. Anonymous users have some potential for impact.
For anonymous users, there are no changes in most cases, because most Amplitude customers don't set IDFA as the device ID. For customers who do set IDFA as the device ID, Amplitude stores the device ID when the SDK initializes, and the SDK continues to send Amplitude the same ID as long as the application remains installed on the device.
If a user deletes and reinstalls an application that uses IDFA for device ID, the SDK doesn't retain the former device ID. Instead, the SDK generates a new random device ID, unless the user grants the application permission to use IDFA.
For all new application installs, the SDK accepts IDFA if the user has opted in and the application chooses to use IDFA.
Does Amplitude require IDFA on attribution events?
No. Amplitude's attribution API accepts both IDFA and IDFV, and tries to match those IDs to user events Amplitude receives later. In some cases, IDFV is enough to make a match, but some Amplitude customers' attribution providers only send IDFA. For these customers, Amplitude can no longer match attribution events unless the user has explicitly opted in to both the referring and installed application.
Some attribution vendors are likely to stop sending individual attribution events. Vendors are unlikely to send aggregated data to Amplitude (because of the nature of the platform), unless customers or attribution vendors can segment that data and use it to set user properties.
How does this affect outbound integrations?
If you send data to outbound integrations, you see a lower match rate when using IDFA to match devices between Amplitude and the integration. Amplitude recommends switching to IDFV or another common identifier instead.
Missing mobile attribution events
Mobile attribution partners identify events using advertising IDs like IDFA, IDFV, or ADID. Amplitude identifies users based on a combination of user_id, device_id, and amplitude_id.
Amplitude's Attribution API reconciles these differences and maps attribution events to existing users in Amplitude. Some mobile attribution partners (Appsflyer, Adjust, Branch, and Singular) use this API to send their non-custom, standard data with the advertising IDs as the identifier.
Amplitude stores unmapped attribution events for 72 hours. During that time, Amplitude looks for a matching IDFA, IDFV, or ADID on an existing user in an Amplitude project. If a match exists, Amplitude routes the attribution event to that user. If no match exists, Amplitude drops the attribution event after 72 hours.
To support this process, instrument Amplitude with advertising IDs enabled.
Why mobile attribution events may be missing
You can resolve some causes quickly:
- The attribution events didn't successfully send to Amplitude. Confirm that the attribution partner receives a success response (for example, a 200) when sending events.
- Your project has reached the instrumentation limit. Delete event types or properties to allow Amplitude Analytics to ingest new event types and properties.
- You blocked or deleted the event type in the Amplitude project. Restore the event type or property through Amplitude Data to fix the issue.
Other causes require more investigation:
- No existing user in Amplitude with the matching IDFA, IDFV, or ADID.
- Amplitude didn't complete mapping within 72 hours.
Troubleshoot: No existing user in Amplitude with the matching IDFA, IDFV, or ADID
This is the top reason why Amplitude Analytics doesn't ingest mobile attribution events. You must instrument Amplitude before you can send mobile attribution events.
Determine if you're tracking advertising IDs
Advertising IDs are IDFA, IDFV, or ADID. If you track advertising IDs in your Amplitude events, Amplitude Analytics captures their value in the respective property field. For security and PII reasons, advertising IDs don't appear as a usable property, and Amplitude removes advertising IDs from your raw data after capture (unless you instrument advertising IDs as a custom property).
Amplitude stores a hashed version of the advertising IDs in a field called amplitude_attribution_ids. Use this field to determine whether you're instrumenting advertising IDs. If the value is null, Amplitude captured no advertising IDs for this user.
A null value generally means either that you haven't instrumented Amplitude Analytics to capture advertising IDs, or that the end user has opted out of advertising ID tracking.
You must honor user opt-outs. If you track advertising IDs properly and want to confirm that amplitude_attribution_ids = null results from a user opt-out, contact Amplitude Support.
Solution: Tracking advertising IDs
If you use JavaScript, which can't track advertising IDs automatically, send an Amplitude event with the advertising ID through the HTTP API.
Troubleshoot: Mapping didn't happen within 72 hours
Amplitude holds an attribution event for 72 hours. If Amplitude doesn't make a match during that time, Amplitude drops the event.
For example, User A downloads a game app on December 1 but doesn't open the app until December 7:
- Mobile attribution partners list an Install event for User A on December 1 and send that event to Amplitude on December 1.
- User A doesn't record their first event in Amplitude until they open the app on December 7. Amplitude considers User A a new user on December 7.
Amplitude drops User A's Install event because User A didn't exist in Amplitude within 72 hours of the attribution event. User A only existed in Amplitude seven days after the Install event, which is longer than the 72-hour holding period.
Determine if the attribution event came too early
Amplitude's iOS SDKs capture IDFV as device_id by default. If you use the default setting for iOS SDKs, use this process to troubleshoot:
- Identify an iOS SDK user in Amplitude who doesn't have an
Installevent, even though there is a value foramplitude_attribution_ids. - Copy the
device_id(IDFV) of that user. - With your mobile attribution provider, look for the
Installevent of the IDFV. - Check the date on the
Installevent. - Compare that date to the New User date in Amplitude.
The mobile attribution provider likely sent the Install event more than 72 hours before the user existed in Amplitude.
You can also check whether a user already exists in Amplitude by following a similar process:
- Identify an iOS Install event from the mobile attribution provider that doesn't appear in Amplitude yet.
- Get the IDFV on that payload.
- Enter the IDFV in the user look-up feature as the device ID.
The IDFV likely doesn't associate with a profile in Amplitude Analytics, which means Amplitude hasn't seen the user yet.
Solution: Create users before real user activity
An end user exists in Amplitude when Amplitude receives the user's first event. If you don't want to wait on the end user's actions to trigger profile creation, create a profile yourself by either:
- Sending a placeholder event with advertising ID and
device_idoruser_idthrough the HTTP API. - Creating a profile with advertising ID and
device_idoruser_idthrough the Identity API.
Creating a profile is only possible if you can capture the advertising ID on your own. Maintain the correct device_id or user_id so you connect real-world user activity to the right profile.
이 내용이 도움이 되었나요?
For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.