|
What's new |
Changes to integration and attribution rules for Apple Search Ads, starting with iOS 14.3.
Action required!Some changes require action on your part:
|
||||||||||||||||||||
| Bulletin date |
January 6, 2021 updated on April 7, 2021 |
||||||||||||||||||||
| Effective date |
|
||||||||||||||||||||
| Where | Apple Search Ads (ASA) is implementing a number of changes that impact install attribution, population of campaign fields, and required settings for attribution of agencies and ASA marketing partners. | ||||||||||||||||||||
|
What's changing |
ATT based attribution rules apply to all users brought by ASA irrespective of ATT statusUntil now, installs brought by ASA without IDFA were recorded as organic installs. Starting with iOS 14, ATTrackingManager (ATT) governs the availability of IDFA and ASA attributes all installs based on the ATT status detailed in the table as follows:
Identification of agencies and marketing partnersThe ASA Campaign Group Name field, used to identify agencies and marketing partners, is replaced by Campaign Group ID. Note! This is available in the ASA dashboard. In most cases on the Effective Date, AppsFlyer made the change for you. However, we weren't able to do so in all cases. What you need to do: For each Apple Search Ads marketing partner, verify that in the AppsFlyer dashboard that the Apple Search Ads Campaign Group ID is correctly populated. To verify and set the Campaign Group ID:
Network account IDThe network_account_id population is changing for installs that take place starting with the Effective Date: network_account_id (available via raw data) and the associated in-app events are populated with org-id provided by ASA. Until now, this field was populated with org-name. Note! This change doesn't impact the in-app events of installs that took place before the Effective Date. Meaning, network_account_id continues to be populated by org-name. Analytics reports (campaign name)ASA is deprecating the campaign name field. We'll try to populate it from other sources. In cases where this is not possible, campaign name is populated with campaign ID. |
||||||||||||||||||||
|
What's going away |
Availability of campaign names and other identifiersGoing forward, some fields are no longer available.
Data Locker customers: Starting February 4, 2021, Keyword ID is available via Data Locker. |
||||||||||||||||||||
|
What's staying the same |
Availability of raw data (user level) continues to be available via the data delivery tools like Pull API, Export data, and Data Locker. However, some data points, listed in the previous table, are deprecated. |
||||||||||||||||||||
|
FAQ |
Impact of attribution before ATT is mandatory Q: Will attribution be impacted in the period starting on the Effective Date until Apple enforces ATT? A:
Apple Search Ads and SKAdNetwork Q: Does ASA support SKAdNetwork. A: No. ASA doesn't report installs in the framework of SKAdNetwork.
Cohort dashboard Q: If I currently get analytics reports using keywords via Cohort what will happen? A: Keywords is available if Cost integration is enabled for ASA. Otherwise, AppsFlyer populates the keywords field with the data reported by Keywords ID. Note that Keyword IDs are not mapped to the current keywords.
Campaign names Q: In analytics dashboards will I still see campaign names? A: Yes. We will continue to populate, where possible, the campaign name from other sources. If we can't resolve the campaign name, we will populate campaign name with the campaign ID value.
[Updated July 21, 2021] Reinstall over-counting of users without IDFA (non-consenting) Q: If a user, without IDFA, installs the app, deletes it, and reinstalls it does AppsFlyer record an additional install to Apple Search Ads. A: Yes. If the install occurs during the ASA lookback window, ASA claims it as their install. Because the user doesn't have IDFA ASA doesn't report the click time and we don't detect that it is a reinstalling user. |
List of what's new in AppsFl
Comments
January 18, 2020, update regarding the population of raw data field: network_account_id
January 27, 2021, the Effective Date has been changed to February 15, 2021.
February 4, 2021: An FAQ has been added to clarify the impact on attribution if you don't adopt the most recent SDK.
February 4, 2021: Apple Search Ads and Data Locker
If you are a Data Locker customer, you probably need to enable the Keyword ID field in Data Locker. This field was not available in Data Locker until today.
February 17, 2021: We've completed the change to the ASA integration. The bulletin contains clarifications relating to the populating of campaign names. There are instances where we populate campaign name with campaign ID.
April 7, 2021: Campaign name and ad name are available if you enable the ASA cost API. This API is available to all advertisers irrespective of their subscription plan.
Please sign in to leave a comment.