February 5, 2020 — OWOX BI Pipeline. Use the AppsFlyer Push API V2.0 for your AppsFlyer → Google BigQuery pipeline

Now the AppsFlyer → Google BigQuery supports the new AppsFlyer Push API V2.0 that lets you collect more data to BigQuery.

AppsFlyer will no longer update the old Push API V1.0 will shut it down on August 31, 2020.

We recommend you to enable the Push API V2.0 now to start collecting more data with your AppsFlyer → Google BigQuery pipeline and avoid the data collection shutdown when AppsFlyer will discontinue the old version of their API.

What's new in the Push API V2.0?

The new API collects 40 additional fields and introduces the new schema for the collected data: some fields were renamed, some were replaced with new ones.

Read more about the changes in the AppsFlyer Help Center.

The new data structure is also already documented in the OWOX BI Help Center.

What happens with my AppsFlyer → Google BigQuery if I don't enable the Push API V2.0?

Your pipeline will continue collecting data as before — up until the moment when AppsFlyer shuts down the Push API V1.0. After that, the pipeline will stop collecting data and you'll need to enable the API anyway.

How to enable the Push API V2.0 for my AppsFlyer → Google BigQuery pipeline?

Method 1. Create a new AppsFlyer → Google BigQuery pipeline and enable the Push API V2.0 in the AppsFlyer settings.

If you take this way, OWOX BI will collect your AppsFlyer data into the new data table with the new schema. This means you'll need to update your SQL request you were using for the old table so they could work with the new schema.

  1. Create the new pipeline in OWOX BI. Note that the new pipeline can't collect data in the same BigQuery data set as the old one. You'll have to select another data set.
  2. On the stage when you need to paste the postback URl in AppsFlyer, select Push API version as 2.0:AppsFlayer_postback_configuration_API__highlight.png

Done. The new pipeline will now collect data from AppsFlyer into a Google BigQuery table with the Push API V2.0 schema.

Method 2. Enable the Push API V2.0 in the AppsFlyer settings for an existing AppsFlyer → Google BigQuery pipeline.

If you don't want to walk away from the old field names yet and are not ready to update your requests for the new schema, just select Push API version as 2.0 in the Postback Configuration settings in AppsFlyer, as shown on a screenshot above.

In this case, the pipeline will start collecting all the data available with the Push API V2.0 and store it in the same table as before, with a joined schema.

This table includes both the old and new fields. The values from the renamed and replaced fields will be duplicated to the old fields making sure your SQL requests will work correctly with the new table.

The joined table structure:

 Field name  Comment
 event_name  New field, replaces event_type
 event_type  Contains the same value as event_name
 media_source  New field, replaces attribution_type
 attribution_type  Contains the same value as media_source
 attributed_touch_time  New field, replaces click_time
 click_time  Contains the same value as attributed_touch_time
 device_download_time  New field, replaces download_time
 download_time  Contains the same value as device_download_time
 af_prt  New field, replaces agency
 agency  Contains the same value as af_prt
 campaign  New field, replaces fb_campaign_name
 fb_campaign_name  Contains the same value as campaign
 af_c_id  New field, replaces fb_campaign_id
 fb_campaign_id  Contains the same value as af_c_id
 af_adset  New field, replaces fb_adset_name
 fb_adset_name  Contains the same value as af_adset
 af_adset_id  New field, replaces fb_adset_id
 fb_adset_id  Contains the same value as af_adset_id
 af_ad  New field, replaces fb_adgroup_name
 fb_adgroup_name  Contains the same value as af_ad
 af_ad_id  New field, replaces fb_adgroup_id
 fb_adgroup_id  Contains the same value as af_ad_id
 original_url  New field, replaces click_url
 click_url  Contains the same value as original_url
 af_cost_value  New field, replaces cost_per_install
 cost_per_install  Contains the same value as af_cost_value
 retargeting_conversion_type  New field, replaces re_targeting_conversion_type 
 re_targeting_conversion_type   Contains the same value as retargeting_conversion_type
 appsflyer_id  New field, replaces appsflyer_device_id
 appsflyer_device_id  Contains the same value as appsflyer_id
 device_type  New field, replaces both the device_brand and device_model fields. Contains info on both the device brand and model
 device_brand  Contains the same value as device_type
 device_model  Contains the same value as device_type
 af_cost_currency  New field, replaces currency
 currency  Contains the same value as af_cost_currency
 amazon_aid  New field
 contributor_1_campaign  New field
 contributor_1_match_type  New field
 contributor_1_media_source  New field
 contributor_1_af_prt  New field
 contributor_1_touch_time  New field
 contributor_1_touch_type  New field
 contributor_2_campaign  New field
 contributor_2_match_type  New field
 contributor_2_media_source  New field
 contributor_2_af_prt   New field
 contributor_2_touch_time  New field
 contributor_2_touch_type  New field
 contributor_3_campaign  New field
 contributor_3_match_type  New field
 contributor_3_media_source  New field
 contributor_3_af_prt  New field
 contributor_3_touch_time  New field
 contributor_3_touch_type  New field
 custom_data  New field
 device_category  New field
 gp_click_time   New field
 gp_install_begin  New field
 gp_referrer  New field
 gp_broadcast_ referrer  New field
 keyword_match_type  New field
 match_type  New field
 deeplink_url  New field
 oaid  New field
 keyword_id  New field
 store_reinstall   New field



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.