Sprinklr + AppsFlyer API integration

Updated 

Fetch and leverage Cohorts API data to monitor how effectively your ads are working, and optimize them accordingly.

Sprinklr Marketing (Ads) has integrated the AppsFlyer Cohorts API to provide advertisers with a programmatic way to fetch cohort data. The cohort data helps advertisers track users and analyze how their behavior changes over time.

Appsflyer’s data will be associated with a social ad id enabling you to determine the effectiveness of your ads and social campaigns and optimize accordingly. You will also be able to create audience segments from app user data to target via your social campaigns.

What is a Cohort?

A cohort is a collection of unique users that installed your app within your selected timeframe and fit the criteria you have defined with filters. They must also have had your app installed for at least the amount of time in whatever period you are looking at:

  • Period refers to the day post-attribution, where period 0 is the attribution day. For example, a user installs the app on January 1st. This is the attribution day.

  • A purchase made on period 0 means it was made on January 1st.

  • A purchase made on period 3 means it was made on January 4th.

  • Similarly, if you install the app on the 11th of January, this will be period 0. However, a purchase made on 14th January would be period 3.

AppsFlyer mobile measurement use cases

AppsFlyer mobile measurement

  • Verification of measurement data in regards to conversion.

  • Mobile app tracking of in-app events.

  • Business intelligence regarding demographic and psychographic make-up of app-users. For example, who is installing, who is buying, leaving, etc.

  • Consolidated destination to optimize campaigns against SDK data in one workflow. For example, you can view AppsFlyer data in Ads Manager and make required management/optimization decisions.

  • Holistic reporting and insights due to SDK and native channel campaign datasets in one dashboard.

AppsFlyer + Sprinklr integration

Term
Description
Data Fetching

The data will be processed every 4 hours.

Data Mapping

Data is mapped to an individual Ad Variant Id and aggregated up to the Campaign level.

Timezone

AppsFlyer uses UTC as the default timezone and can be changed by setting an app-specific timezone.

As UTC time is constant and doesn't have summer/winter times, setting an app-specific timezone will pull grouped data into days using local time rather than UTC.

Example:

Beijing: If the app-specific timezone is set to Beijing (UTC +8 ), then the day starts at 16:01 UTC and ends at 16:00 UTC the following day.

Los Angeles: If the app-specific timezone is set to Los Angeles (UTC -8), then the day starts at 08:01 UTC and ends at 08:00 UTC the following day.

For more information on Date and Timezone principles, see AppsFlyer Timezones.

Supported Channels

Sprinklr will map to the specific ad id for the following channels:

  • Facebook

  • Pinterest

  • Twitter

    • Needs a 3rd party agreement to be signed by Sprinklr, Appsflyer, and Customer

  • Snapchat

  • TikTok

Historical Data
Sprinklr will only be able to fetch historical data back to 1st January 2019.

AppsFlyer enablement in Sprinklr

Pre-enablement requirements:

  • Do you have access to Cohort reporting API?

    • Only accounts that have Growth and Enterprise subscriptions are eligible for Cohort Reporting API.

  • What metrics are you currently analyzing within AppsFlyer?

    • Due to the number of API calls we can make, we should ask clients which events would they require for Optimization and Reporting.

    • Events include Custom Events, Standard Events, and Cohort Period the clients require.

  • AppsFlyer allows 20 API calls per minute and 50K API calls per day for one access token. If clients utilize Sprinklr’s partner token, then the number of updates Sprinklr can make will be affected due to this limit. Alternatively, clients can provide us with their access token which will allow us to make more calls for them and update data more frequently.

Enablement note:

To learn more about getting this capability enabled in your environment, please work with your Success Manager.

In order to enable AppsFlyer, you will need to grant the Cohort API access along with the other relevant data. Follow the steps given below to execute this task:

  1. Open the AppsFlyer Dashboard.

  2. From the left pane of the AppsFlyer Dashboard, click Integrated Partners under the Configuration section.

  3. Search and click Sprinklr - API Permissions Integration.

  4. Slide the Toggle icon Hyperspace_Toggle_Disabled.png alongside Grant partner access to 'Cohort API' to enable access to the Cohort API.

  5. Once you have granted access to the Cohort API, you will then need to send the following:

    • Timezone - It needs to be set as True for app-specific timezone or else UTC (Coordinated Universal Time) will be set as default.

    • Currency - It needs to be set as True for app-specific currency or else USD ($) will be set as default.

    • Event Names - All the event names that you want to report/optimize in Sprinklr.

    • Attribution - All the cohort periods required for reporting.

    • App Id - App Id should be for both Android and iOS.

    • Channel Ad Account Id - It should be in the format: Channel name: Ad account Id

Optimization

  • Strategy Group - Optimize your AppsFlyer data using Strategy Groups to easily create and apply various optimizations to your ad campaigns. This capability provides a platform where you can add parameters that are common to multiple features from a single place.

  • Rule Engine - Optimize your AppsFlyer data using the Paid Rule Engine which is a powerful tool that can be used to automate workflows, assignments, properties, and more. By configuring Rules, you can increase efficiency by transforming manual processes into automatic actions that execute according to the conditions that you set.

AppsFlyer reporting

AppsFlyer Cohort metrics in Sprinklr

The AppsFlyer reporting metrics within Sprinklr will obey the following syntax:

AppsFlyer Cohort <metric name> <cohort period> (cohort type) <conversion type> <post attribution touch type>

where:

  • Cohort Period = 0 Day, 1 Day, and so on. For cumulative data, it will be within 7 days and so on.

  • Cohort Type = User Acquisition, Unified or Retargeting.

  • Conversion Type = Reattribution, Install, or Retargeting.

  • Post Attribution Touch Type = Post Click, or Post Impression.