Audiences Partners Integrations

Below you can find instructions for integrating your audiences with the various ad networks that support receiving this data.

Amazon S3

Creating an S3 integration allows AppsFlyer to send you the audience Device IDs directly to your S3 bucket.

  1. Create a new Amazon S3 integration. The following screen is displayed:
    amazon.png
  2. Before going through the integration process, you must first create a Policy dedicated to AppsFlyer’s Audience feature.
  3. In your AWS console, go to IAM >> Policies tab.
  4. Click Create Policy and then Create your own policy.
  5. Enter the following policy document (this is a suggestion):
    {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Effect": "Allow",
         "Action":[
               "s3:PutObject", "s3:DeleteObject", "s3:ListBucket"  
          ],
         "Resource": "arn:aws:s3:::YOUR-BUCKET-NAME/*",
         "Condition": {"StringEquals": {"sts:ExternalId": "PROVIDED EXTERNAL ID"}}
       }
     ]
    }
  6. Replace YOUR-BUCKET-NAME with the name of the bucket you want AppsFlyer to upload your audience to and PROVIDED EXTERNAL ID with the value presented previously on the audiences integration screen, under External ID.

amazon_2.png
NOTEThis is a sample policy. Your policy must restrict the access only for the provided external ID. The actions PutObject, DeleteObject and ListBucket are MANDATORY for AppsFlyer to perform minimal actions on your bucket.

  1. After creating your policy, proceed to the next steps:
  2. In your AWS Dashboard, go to IAM and click Create a new role.
    amazon_3.png

     

  3. Under Role for cross-account access, select the option to Provide access between your AWS account and a 3rd party AWS account.

    amazon_4.png

  4. Copy the AccountID and ExternalID provided AppsFlyer's S3 integration screen, and paste them into the appropriate input boxes in the role's creation screen.
    amazon_5.png

     

  5. You are prompted to select a policy from the existing policies in your AWS account. Choose the policy previously created.

  6. Once the new role is created, click the name of the role to enter its properties window.

  7. Copy the ARN.

    amazon_6.png
  8. Paste the ARN, with your bucket name, into the appropriate box in the AppsFlyer integration window. 

    If you want to transfer the files into a specific folder within a bucket, provide the bucket name with the subsequent folders inside it, separated by "/" for example (bucketname/foldername/foldername).

    If you provided a folder name that does not already exist, AppsFlyer creates it during the upload process.

amazon_7.png

Applift

  1. Obtain your API Key from your Applift account manager.
  2. Create a new Applift integration, you will see the following screen:
    applift.png
  3. Enter your DataLift 360 Advertiser email  (your login email to DataLift 360’s dashboard) the API Key you've just copied.
  4. Click on Add to complete the connection.
  5. After uploading an Audience to AppLift, you will see it in your DataLift 360’s Audiences dashboard (https://applift.datalift360.com/audiences).

Applovin

Once the integration process is complete and an audience is uploaded, you can see a CSV file with the Device IDs in the bucket specified. 

  1. Obtain your Custom Audience Key from your Applovin advertiser’s account page
    Applovin_1.png
  2. Create a new Applovin integration. the following screen is displayed:
    Applovin_2.png
  3. Paste your Custom Audience Key in the input bar, and click on Add Connection.

Facebook

  1. Create an Ad Account on Facebook
  2. Select Facebook in AppsFlyer’s Audiences integrations page. The following screen is displayed:
    FB1.png
  3. Login to your Facebook account and select the required Ad Account.

After uploading an Audience to Facebook, it appears in your Facebook’s Custom Audiences dashboard.

InMobi

  1. Obtain your app's Property ID from InMobi's dashboard. 
  2. Under the Monetize tab, select your app and copy the the Property ID displayed at the top of the screen:
    inmobi.png
  3. Create a new InMobi integration. The following screen is displayed:
    inmobi_2.png
  4. Paste your Property ID in the input bar, and click Add.

IronSource

  1. Obtain your API Key from IronSource's dashboard. 
  2. On the top right-hand side, click your account email.
  3. From the dropdown menu select My Account
  4. In the Account window, under Reporting API tab, copy the Secret Key:
    ironsource.png
  5.  Create a new ironSource integration, the following screen is displayed:

    ironsource_2.png
  6. Enter your IronSource User ID (your email address, specified on the top right-hand side of the IronSource dashboard), and the API Key you just copied.
  7. Click on Add to complete the connection.

Slack

AppsFlyer uploads a CSV file of Device IDs to your public Slack channel.

  1. Create a new Slack integration.  The following screen is displayed: 
    slack.png
  2. Click Add to Slack button. You are redirected to an authentication screen, where you pick your relevant Slack Team.
  3. Once the Slack Team is selected, select your public Channel.
  4. Click Add.

Once the integration process is complete, and an audience has been uploaded, you can see a CSV file with the Device IDs sent to the selected channel.

Tapjoy

  1. Obtain your Partner ID from your Tapjoy Account Manager.
  2. Obtain your Publisher Reporting API Key from your Tapjoy App Settings page.
    tapjoy.png
  3. Create a new Tapjoy integration. The following screen is displayed:
    tapjoy_2.png
  4. Paste your Tapjoy Partner ID and Publisher Reporting API Key in the input bar
  5. Click Add.

Yahoo Gemini

  1. Create an Ad Account on Yahoo Gemini
  2. Select Yahoo Gemini in AppsFlyer’s Audiences Integrations page. The following screen is displayed:
    yahoo_1.png
  3. Login to your Yahoo account, and select your desired Ad Account.

After uploading an Audience to Yahoo Gemini, you can view it in your Yahoo Gemini Advertiser dashboard.

Adobe Marketing Cloud

AppsFlyer creates and syncs Traits with your selected DataSource.

  1. Log into your Adobe Maketing Cloud dashboard
  2. On the left-hand menu, select Manage Data >> Data Sources

    AMC_1.png
  3. In your Data Sources page, create a new Data Source.
  4. Set the ID Type to Device Advertising ID, and the Inbound settings to Customer ID.

    AMC_2.png
  5. Once saved, you are redirected to the Data Sources selection menu. Find your newly created Data Source, and save its ID for later.
  6. In the left-hand menu, select Administration >> Groups.
  7. Create a new group, and in the permissions settings tab, select the Data Source you previously created:

    AMC_3.png
  8. Save the group and go to Administration >> Users.
  9. Create a new user for AppsFlyer’s Audiences:

    AMC_4.png
  10. In the Assigned Groups selection menu and select the group you previously created.
  11. Copy the Data Source ID, and the Email and Password of the user you previously created.
  12. Go to AppsFlyer’s Audiences page, and select Adobe Marketing Cloud.  The following screen opens:

    AMC_5.png
  13. Paste the values you copied in their corresponding locations
  14. Save the connection.

About 24 hours after uploading your audience to Adobe, you can see the data in your Adobe Marketing Cloud dashboard, under Analytics >> Onboarding Status.

PushSpring

  1. Select PushSpring in AppsFlyer’s Audiences integrations page. You will see the following screen:

 Pushspring_1.png

  1. Login to your PushSpring account. You will see a new timestamp -

 Pushspring_2.png

  1. click on Add Connection.

After uploading an Audience to PushSpring, it appears in your PushSpring’s Imported Audiences dashboard.

Snapchat

  1. Select Snapchat in AppsFlyer’s Audiences integrations page. The following window is displayed:

    Snapchat_Int_1.png

  2. Login to your SnapChat account.
  3. Select your Organization and Ad Account

    Snapchat_Int_2.png
  4. Click Add Connection.

24 hours After uploading an Audience to Snapchat, it can be seen in the dashboard.

NOTE: Snapchat deducts unfamiliar Device IDs, which potentially results in a smaller audience size.

 

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