Release Noteslink
November 2023link
The AppsFlyer connector now supports custom configuration of the Connection Name through the setup form for syncing Data Locker events. The default value for the Connection Name will continue to be data-locker-hourly/
, if not configured differently in the setup form.
August 2023link
We can now sync Cohort analytics aggregate reports from Data Locker into the COHORT_EVENT
table.
May 2023link
We can now sync the raw data and aggregate data reports from the Pull API V2. For more information, see our AppsFlyer documentation and the REST API configuration parameters.
March 2023link
We can now sync the SKAdNetwork (SKAN) attribution events from Data Locker and Webhooks. We are gradually rolling out this feature to all existing customers. For more information, see our AppsFlyer documentation.
January 2022link
AppsFlyer has changed the retention period for Data Locker events (stored in the AppsFlyer S3 bucket) from 30 days to 14 days. We now retrieve events from the last 14 days. Previously, we retrieved events from the last 30 days.
November 2021link
We now use the is_primary_attribution
column of the EVENT
table for primary key hashing. To generate the hash of the primary key, we use the following logic :
- For an event on or before
2021-11-10T00:00:00Z
, we use the existing column list. - For an event after
2021-11-10T00:00:00Z
, we use the existing column list and theis_primary_attribution
column.
January 2021link
The AppsFlyer connector now supports syncing Data Locker events from your custom AWS S3 buckets. Previously, we only supported Data Locker events from AppsFlyer-managed buckets. See our setup instructions for more information.
April 2020link
You can now configure your AppsFlyer connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
February 2020link
Data collection using Push API V1.0 and Data Locker V1.0 has been deprecated. We will continue to support all deprecation changes for the next three months, so be sure to make the required schema changes by May 31, 2020.
Use Push API V2.0 and Data Locker V2.0 to continue using the service. Connectors must register the Push API V2.0 specific URL generated by Fivetran, with AppsFlyer. For more details see AppsFlyer Push API V2.O documentation.
We now sync data from Push API V2.0 and Data Locker V2.0 into a common table EVENT
.
We have deprecated the following tables:
DATA_LOCKER_V1_EVENTS
DATA_LOCKER_V2_EVENTS
WEBHOOK_EVENTS
August 2019link
We have deprecated service version 0 of our AppsFlyer connector. This connector will stop functioning after October 1, 2019.
June 2019link
We have released a new version of the AppsFlyer connector.
We have split the
EVENT
table from the old version into two new tables:DATA_LOCKER_EVENTS
WEBHOOK_EVENTS
The
DATA_LOCKER_EVENTS
table captures events from AppsFlyer Data Locker. TheWEBHOOK_EVENTS
table captures webhook events.We have removed the following tables:
WEBHOOK_EVENT_ATTRIBUTE
S3_EVENT_ATTRIBUTE
The new version supports AppsFlyer Data Locker 2.0
The new version resolves a data integrity issue with events and webhooks. Fivetran now better captures events from AppsFlyer Data Locker and webhooks.
December 2018link
AppsFlyer is a mobile app tracking & attribution analytics platform.