AppsFlyer Integration with Adobe Analytics

Introduction

Adobe Analytics (formerly Omniture) is a set of tools for predictive and real-time analytics that can be integrated into third-party sources. It includes the Marketing Reports and Analytics (SiteCatalyst), Ad hoc analysis (Adobe Discover) and Insight applications to help create a holistic view of business activities by transforming customer interactions into insights. With simple and interactive dashboards and reports, a user can manage and share real-time information which helps identify issues, discover opportunities and measure key performance indicators.

If you are using Adobe Analytics Report suite for overall campaign performance analysis and segments creation, AppsFlyer’s integration with Adobe Analytics enables automatic transfer of attribution data from AppsFlyer to Adobe to help you achieve your goals.

This information consists of:

  • Campaign Name
  • Ad Network Name
  • Ad Provider which is set to AppsFlyer

This article describes the steps required to integrate AppsFlyer’s data with Adobe Analytics.  

NOTE: This integration consists of two way data flow between Adobe and AppsFlyer.  For the integration to be successful, this integration requires code implementation in your your app.  Both AppsFlyer and Adobe requirements must be met for the integration to be fully successful.  

Adobe Requirements

This integration requires code implementation in your mobile app. Below are a number of requirements that must be fulfilled to enable the integration:

  1. Must be using Adobe Analytic SDK 4.3 or later in your mobile apps
  2. Must already be using Marketing Cloud Visitor ID service 
  3. Must have admin access to Adobe Analytics to enable Data Connectors and reserve eVars
  4. Have three eVars in each report suite which can be used for the sole purpose of this integration.

Integration

Pass the Adobe Visitor ID to AppsFlyer.

  1. Follow the documentation here to update the application and extract the Marketing Cloud Visitor ID using Adobe SDK method right after the Adobe SDK is initialized.

  2. Set the Adobe Marketing Cloud Visitor ID as AppsFlyer Customer User ID using the AppsFlyer SDK method right after the AppsFlyer SDK is initialized and before trackAppLaunch.
AppsflyerLib.setCustomerUserId(“ADOBE_VISITOR_ID”);
[AppsFlyerTracker sharedTracker].customerUserID =@"ADOBE_VISITOR_ID";

For more details on the Customer User ID, click here.

Configuring Adobe Analytics in the AppsFlyer Dashboard

IMPORTANT NOTE: AppsFlyer Customer User ID MUST be set to collect Adobe ID.

Follow the instructions below to set up the integration:

  1. Go to Integrated Partners and search for Adobe Analytics

    Adobe_Omniture_1.png
  2. On the Adobe App Analytics configuration page, enable the integration parameters and insert the Report_Suite_ID (highlighted in green) & Adobe_Analytic_server_URL (highlighted in blue).

    The parameters can be found in the Adobe Analytics SDK under ADBMobileConfig.XML file.

    Example XML File:

    AAInteg1.png

  3. Click Save & Close

Once this configuration is saved, AppsFlyer begins sending the following data to Adobe Analytics for every organic and non-organic install:

  • Report Suite ID & Server URL
  • Customer Device ID
  • Media Source
  • Campaign Name

According to Facebook's T&Cs, we cannot share user level data with any 3rd party. As a result, all Facebook and Twitter installs are sent to Campaign as organic.

Configuring the Integration in the Adobe Analytics Interface

Use these instructions to configure the integration in the Adobe Analytics interface.

  1. In the Data Connectors UI, click Add New

    AA1.png

  2. Using the alphabetical view, search for and select AppsFlyer.

    AA2.png

  3.  Click Activate.

     This opens the AppsFlyer integration wizard.

  4.  Accept the terms and conditions.

    AA3.png

  5. Choose the report suite where the AppsFlyer data flows to.

    This report suite must be the same as what was used in the AppsFlyer URL configuration. You can provide any name for this integration.

  6. Map the available eVars from the dropdown list where the AppsFlyer data flows to, as appropriate. You may rename the variable, if needed.

  7. The final step is to review the variable mappings and other parameters.

  8. Click Activate Now to activate the integration.

    Once activated, the data connector automatically creates the required processing rules.

    AA_4.png

  9. Repeat these steps for each report suite where the integration is required 

Domain and Security Details

Set out below are the details of the domain and security issues.

  1. ANALYTIC_SERVER_DOMAIN can be found as the server variable in your App’s Config file.  You can select any domain for tracking analytics.  In general, standard domains for the Adobe Analytics collections service such as sc.omtrdc.net are used.  This can be found under the analytics (server) settings in their ADBMobile.config file.

  2. The protocol (HTTP/HTTPS) of the URL depends on whether the ANALYTIC Server Domain is secure or not.  It is important that you use the correct protocol.  To find out if the setting is secure, check whether the analytics (SSL) setting is set to true in the ADBMobile.config file.  If your connection is secure use HTTPS, if it is not secure use HTTP.

  3. REPORT SUITE ID can be found as the rsids variable in your Apps’ Config file.  You can give any name to your report suite.

  4. The ts={timestamp} is only used if your offlineEnabled configuration is true in your Config file. Remove this parameter from the URL if the offlineEnabled is set to False or if your report suite is not Time Stamp enabled.
Was this article helpful?
0 out of 0 found this helpful