Update March 30: this release is now live. That means both SKAN installs and SKAN purchases (for AppsFlyer only) metric data are now available.
Over the next several days, we plan to release new SKAdNetwork (SKAN) metrics. We will update this post once the new metrics are available.
We will no longer change the existing Install metric. Based on feedback received, and in order to minimize any impact to existing workflows, the existing Install metric will remain as is.
- That means there is no action required at launch. In other words, you will no longer need to refetch “Install” metric specific data at launch.
Once the new SKAN metrics release, we recommend refetching relevant data to display in these fields.
This update is a follow up to our post here.
What will be releasing?
New SKAN installs and SKAN app purchases (starting with AppsFlyer) metric data will be available at launch.
These are optional, additional metrics to give advertisers increased visibility into their app campaign results. We recommend displaying these metrics to relevant advertisers.
We are providing historical data for these two new metrics, available from Feb 3rd 00:00 UTC, on the release date.
You can leverage the Active Entities endpoint to help identify changed metrics. If you decide to surface these metrics and would like to use this approach, make sure that your application or platform supports this endpoint.
Reminder: one of the new SKAN metrics, SKAN app purchases (AppsFlyer), will only surface data for advertisers who use AppsFlyer as a Mobile Measurement Partner (MMP). Support for other MMPs is planned for the near future.
Moving forward
Build out support for these metrics to capture them when they launch. Once they are available, prefetch relevant data to populate these metrics.
Again, there is no required action at the time of this launch as we are no longer changing the existing “Install” metric. We will follow up on this post once these new metrics have become available.
Please let us know if you have any questions.
Twitter Ads API team