Audiences guide

  • Advertisers

At a glance: Audiences enables you to select app users, using rules, to generate a focused audience list. The audience is updated daily and sent to selected partners to populate your retargeting campaigns. 

audiences_example.png

Audiences main features

  • Audiences are defined using one of the following:
    • Rulesets: Filter app users using rules to select the audience from the app user population. 
    • Import: By uploading lists of user IDs generated by your other systems. Do this by file upload in the user interface or by API. 
  • Ruleset live size estimation overlap visualization widget. 
  • Audience lists are updated daily and sent to connected partners using one of the following:
    • Send the entire audience list to all connected partners.
    • Split the audience and allocate a portion to each partner.
    • Split the audience and allocate a portion to each partner and a portion to a control group.
  • Send a copy of the audience list, broken down by partners and the control group to an Amazon S3 bucket.

Setting up audiences

Setting up audiences consists of:

  • Defining the audience
  • Connecting to partners

See the procedures on how to set up Audiences.

Ruleset builder

Audiences are defined using the Audiences builder in AppsFlyer. For ease of understanding, before reading this section, familiarize and experiment with the rule builder in AppsFlyer. 

AudienceBuilder.png

  • Rulesets consist of one mandatory primary rule and optional secondary rules 
  • Rulesets can be combined using the operators: and, or, exclude
  • Using the operators, you can combine a ruleset with imported user lists
  • As you define the rules, the audience size is displayed
  • Where an audience consists of multiple rulesets, use the overlap display widget to visualize the overlap.
  • See ruleset examples

Primary rule

The primary rule has the following filter types: 

  • App
  • Engagement type
  • Engagement time frame
  • Engagement frequency

 Example: Primary rule 

PrimaryRule.png

The table below contains the list of filter options. For each filter type, a single filter can be selected. 

Filter type Filter  Filter parameter
App Users of the app App name
Engagement type Who have launched the app  
Engagement type Who have viewed an add  
Engagement type Who have clicked an add  
Engagement type Who installed the app  
Engagement type Who launched the app  
Time frame In the last n days n= number of days from 1-9999
Time frame Between start date and end date Start date, End date
Time frame At any time None
Frequency Used the app at least n times n=number of times from 1-100
Frequency Used the app exactly n times n=number of times from 1-100
Frequency Used the app at most n times n=number of times from 1-100

Secondary rule

  • Secondary rules:
    • Reduce the population selected using the primary rule.
    • Are optional, but where used, can consist of one or more rules.
  • Each rule has a unique filter type as follows:
    • Event 
    • Device
    • Attribution
  • The filter types have different filter parameters associated with them as shown in the table that follows.

 Example: Secondary rule

Secondary_rule.png

Secondary rule with in-app event

In-app events can be filtered by using the Did event or Did not event 

Where the Did event is selected, and the in-app event has attributes associated with it, you can filter by in-app-event attribute value. See the example that follows. 

Example: Secondary rule with in-app event filter

SecondRuleInApp.png

Secondary rule filter types and filters

Filter type Filter  Filter parameter Remark
Event Installed the app Time frame and Frequency   
Event Did not install the app  Time frame and Frequency   
Event Launched the app Time frame and Frequency   
Event Uninstalled the app Time frame and Frequency   
Event Launched the app Time frame and Frequency   
Events  Did event: in-app event Time frame and Frequency  Select in-app event and where relevant in-app attribute
Events  Did not do event: in-app event Time frame and Frequency  Select in-app event 
Event  Total revenue generated  Is or greater than or lower than
  • The value is in USD.
  • The value is the total value of all events reported from a device using the af_revenue parameter.
Event Location  Is or Is not 
  • The combination of Country, state, city.
  • Where multiple countries are selected you can't select the state.
  • The same is true for states and cities. 
Event Metro code Is or Is not   
Device Device brand Is or Is not   
Device Device model  Is or Is not   
Device  App version Is or Is not   
Device  OS version Is or Is not   
Device  Carrier Is or Is not   
Attribution Organic True or False  
Attribution  Retargeting True or False  

Overlap visualization

When you define more than one audience ruleset, it is likely that users will belong to more than one ruleset. The Overlap widget displays the size and relationship of the different audience rulesets. 

Overlap widget

Ruleset examples

Examples: 

Users who installed the app during the last 7 days, and spent at least $1audiences_new_21.png Example: Users from New York who uninstalled the app in the last month

audiences_new_22.png

 Remarketing Example

Using clicks and views for effective remarketing with audiences Remarketing is a method of advertising to audiences who have viewed or clicked on your ads but who did not convert. It may be that to convert these users, all that is needed, is a little extra convincing or a gentle reminder. These users, have a high chance of converting, so remarketing to them can produce significantly better results than advertising to new audiences.

You can create precise audiences for remarketing based on the clicks and impressions data collected by AppsFlyer.

Build an audience of potential users that clicked on an ad, but did not install in the last 2 days.

These are users who in the recent past were sufficiently interested in your mobile app to click on your ad, but for some reason did not install the app, or installed the app but did not launch it. Some users just need a reminder (push) to install it. Others may need to see more screens or features of your app to finally convert. Therefore, if you have a primary creative you use on new audiences, it is might be better to use a different creative for audiences that clicked but did not install.

Procedures

The sections that follow contain the procedures to use Audiences.

To create a new audience, complete the defining an audience ruleset procedure followed by the connecting to partners procedure.

Defining audience rulesets

Audiences can be defined using one of the following:

  • Create a new ruleset
  • Use an existing audience ruleset 
  • Import an audience from your other systems by file upload or API 

Define the audience using one of the methods that follow.

New ruleset

Rulesets consist of one primary rule that defines the global population with optional secondary rules that further filter the population. 

To create a primary rule:

  1. Go to Integration > Audiences.
    The Audiences window opens. 

  2. Click Add Audience.
    The Audience window opens. The Build tab displays.

  3. Enter a unique Audience Name.

  4. Select the audience platform: Android or iOS.

  5. Users of the app: Select the app.

  6. Who have select one of the following: engaged, installed, launched the app

  7.  Set the time frame filter using one of the following:

    • In the last n days: n is the number of days going backward, starting from today.

    • Between: Enter a specific data range

    • At any time: include all available dates, starting from the first date of available audience data.

  8. Do one of the following:
    • Click Save Audiences and proceed. Continue to Connect to partners procedure.
      --OR --
      Click Add Filter, to add a secondary filter and continue with the procedure that follows.

To add a secondary filter:

  1. Click Add Filer

  2. Complete the rule fields that display. The fields that display vary according to the filter type selected.
    Note: In-app events can be filtered by using the did use/did not use event types. See secondary rules for more details. See the example that follows this procedure.

  3. Do one of the following:
    • Add Filter to add another secondary filter and repeat this procedure.
    • Cancel
    • Save Audience and Proceed: Continue to Connect to partners procedure
    • Combine this ruleset with another ruleset using an operator: AND, OREXCLUDE
      An additional ruleset panel displays. Use one of the following procedures:

 Example: Ruleset with in-app event

 

The ruleset above defines an audience of users that have made at least 1 purchase of 1 item, that cost over $10, in the last 120 days.

Select from my audiences

You can create new audiences by selecting an existing audience, or by combining an existing audience with new rulesets. Note: It is not possible to select an audience that already includes another audience.

  1. Go to Integration > Audiences.
    The Audiences window opens.

  2. Click Add Audience
    The Audience window opens. The Build tab displays.

  3. Enter a unique Audience Name.

  4. Select the audience platform: Android or iOS.

  5. Click Select from my Audience.

  6. Users of the audience: Select an audience. 
  7. Do one of the following:
    • Cancel
    • Save Audience and Proceed: Continue to Connect to partners procedure
    • Combine this ruleset with another ruleset using an operator: AND, OREXCLUDE
      An additional ruleset panel displays. Use one of the following procedures:

Import audience

Use the data in your own systems, for example, BI, CRM, to prepare lists of device IDs. Import the list to AppsFlyer to create an audience. The list can be imported by file upload in the interface or by API.

Examples

Promotional retargeting 

To target users who have a birthday with promotional offers.

You can do the following:

  1. User your other system to generate a list of users with birthdays. Export this list as a list of device IDs
  2. Upload the list to AppsFlyer and send it to the audience partner of choice
  3. Setup up a campaign in the audience partner to target the audience accordingly

Acquiring additional users

Your app development studio acquires another studio. This studio has a list of users that installed their apps and you want to target these users to install your existing apps.

You can do the following:

  • Take the list of device advertising IDs that belong to the users of the studio that you acquired
  • Import this list to AppsFlyer and upload it to your audience partner of choice
  • Target these users to install your apps

 

Import audience by uploading a CSV file

Prerequisites:

Prepare a CSV file with the following format and schema:

  • The file contains one column.
  • There is no heading row.
  • Each row contains a single device ID.
  • The maximum number of rows is 10 million. 

Example CSV file:

d5e97b54-5ded-4570-ad87-fe9b42f18820
c2595c12-9110-4c09-a80e-34cf6c0caf61
ae2fbdf8-82f1-46a8-8a84-13d6da7e2c7c
7a1e87b9-b4c2-4869-a55e-5bf1d1278476

To upload the audience CSV file

  1. Go to Integration > Audiences.
    The Audiences window opens.

  2. Click Add Audience.
    The Audience window opens. The Build tab is displayed.

  3. Enter a unique Audience Name.

  4. Select the audience platform: Android or iOS.

  5. Select Import Audience.
  6. If it's a new audience:
    • Enter an Audience Name.
    • Click Save.
  7. Click CSV Upload.
  8. Choose what to do with the imported audience:
    • Add new devices: adds the list of device ids to the existing list.
    • Overwrite all existing devices: replace the entire list of device IDs with the uploaded list
    • Exclude from existing device list: remove devices in the upload list from the audience.
  9. Chose the CSV file to upload, click Upload
  10. Wait for a confirmation message. 
  11. Follow the instructions connect to partners

Upload confirmation messages 

Message Cause What to Do
Uploaded successfully    
Seems like your device list is empty. Add some device IDs to it and try again The CSV file is empty

Make sure that the CSV contains at least one device ID

We couldn’t understand one or more of your device IDs
  • The CSV format is incorrect
  • The file you uploaded is not a CSV file
  • The CSV file was edited and saved by a program other than a valid CSV editor (i.e. Microsoft Excel)
  • One or more device IDs is in the wrong format
  • Make sure that the CSV is in the required format
  • The CSV should contain one column and one device ID per row. The CSV should contain no headers.
  • Make sure that all device IDs are in the correct GUID format

See table above for the correct formats

We just had a temporary connection problem and couldn’t upload your file. You can try again now Possible network error Try to upload the CSV file again

Import an audience using the API

To import an audience using the API:

  1. Go to Integration > Audiences.
    The Audiences window opens.

  2. Click Add Audience.
    The Audience window opens. The Build tab is displayed.

  3. Enter a unique Audience Name.

  4. Select the audience platform: Android or iOS.

  5. Select Import Audience.
  6. Click API.
  7. Select API Action
    • Add: Add additional device advertising IDs to an existing audience. 
    • Remove: Remove a list of device advertising IDs from an existing audience.
      Note: Choosing an API Action changes the endpoint path referenced. It doesn't persist after you save the audience. When you want to add or remove devices from an audience, you can specify the action using the necessary path. 
  8. Copy the API Request URLthe API token is already included in the URL.
  9. Copy the API Request Body.
  10. Click Save Audience and Proceed.
  11. (optional) Connect your audience to partners.
    You can now import the list of device IDs to the newly created audience.

 Notes

  • The API doesn't create audiences. You must create and save the audience before you can use the API
  • The API is for updating the audience, meaning adding or removing devices

Importing device IDs into the audience

The next step is to send a POST request to the API endpoint with a body that contains the device IDs.

 Important!

  • Each imported audience that you create has its own import key. The import key identifies a specific audience for adding or removing device IDs from the audience.
  • When you make the request, make sure that the import key belongs to the audience that you want to add devices to or remove devices from.
  • When you make the request, make sure that the platform (Android or iOS) is the same as the platform that you choose when you create the audience.

Sample request

HTTP POST 
https://hq1.appsflyer.com/audience-import-api?api_token=
Accept: application/json
Content-Type: application/json
body: {
     "import_key": "EKFH2UMC5PPCU8J7M5QQCBPKIH89E6NCOB7XQFWMC",
     "platform": "android", 
     "devices": [
      "a23416b8-a21a-4051-a62f-5d3cb85e16ed",
      "09a14a6b-cce8-44f3-8f77-62eff8b5aa4f",
      "289da41f-0473-4977-89ae-8fc92234a921"
     ]
}

Responses

Code Message Description

200

The request was successful Audience successfully imported
400 Seems like your device list is empty. Add some device IDs to it and try again

The request body contains an empty list of devices.

You must provide at least 1 device ID per request.

400 Cannot process more than 10,000 devices per request (x devices counted in this request) The request body contains a list of more than 10,000 device IDs
400 We couldn’t understand one or more of your device IDs Some device IDs are not valid IDFA / GAID
400 Invalid audience platform, this audience is already configured for Android/IOS. To use a different platform, please create a new audience in the UI The platform specified in the request body doesn't match the platform specified when creating the audience
403 Forbidden Incorrect or missing import key
500 Could not parse request

Invalid request body format.

See the request sample above.

API limitations

  • You can only add devices to one audience per request
  • You can only remove devices from one audience per request
  • Batch requests (multiple audiences) are not supported
  • You can send up to 10,000 device IDs per request

Connecting to partners

  • The audience is sent by upload to one or more selected partners.
  • The audience is updated daily and replicated to the partner. AppsFlyer either sends a new list to the partner or notifies the partner which devices to add/delete. The methodology differs from partner to partner but the end result is the same. 
  • The following sending options are available:
    • Send the entire audience list to all connected partners.
    • Split the audience and allocate a portion to each partner.
    • Split the audience and allocate a portion to each partner and a portion to a control group.
  • (Optional) Send a copy of split audience groups, to an Amazon S3 bucket. This includes the control group where applicable. Note: This is not the same as defining Amazon S3 as a connected partner.
  • Download audience lists: The audience list can be downloaded to a CSV file. You can use the CSV file, for example, to send to partners who are not integrated with AppsFlyer. To download the file: In the Audiences window, hover-over Actions, select Download CSV

To connect an audience to a partner:

  1. In the Audience builder window, select the Connect tab.
    The list of partners displays. 

  2. Select a partner.
    The connect to partner window displays.
    Connect2Window.png

  3. Do one of the following:
    • Select Existing Connection.
      --OR --
    • Select Add a new connection and follow the partner-specific instructions for the selected partner. 
  4. Select one or more connections for the partner. Selecting multiple connections means that the audience is sent to the partner multiple times. 

  5. Click Save Connections.
    The partner is added to the list of partners. 

  6. Do one of the following:

    • To select an additional partner, repeat this procedure.

    • Split Audience: To split the audience with optional control groups follow the instructions in the section that follows.
    • CloseThe connection is complete. The audience is sent to the partners daily. Note: In this configuration, the entire audience is sent to all connected partners daily. 

Splitting an audience and control groups

Split audience

Split Audience enables advertisers to split the audience from two to ten partners. Each partner is allocated a unique part, by percent, of the audience. When Split Audience is enabled, it means that a user is uploaded to only one partner.

Advertisers split audiences for a variety of reasons like A/B testing, target a user from a single channel, etc.

You can modify split audience configurations after creation, meaning that you can change the allocation between partners, remove, and add partners. Take into consideration that allocation modifications can impact the validity of A/B or other test measurements. For this reason, we display an alert message, before you can make a modification.

Control groups

A portion of the audience can be sent to a control group. The control group is not sent to any partner. Use the control group to compare the behavior of targeted users relative to the control group. 

Send copies of split audience lists to S3 

CSV files containing the split audience lists and control group can be sent to an Amazon S3 bucket. The directory and file name structure is as follows:

  • Directory structure
     \YYYY-MM-DD\audienceID_audienceName_timestamp\
  • Filename: The name of the partner or control group. Note: If the connection to the partner fails, and the file is not uploaded then the parnter_name will have the suffix failed. Example: partner_name_failed.csv 

Creating a split audience configuration and control group

Before you can split the audience:

To create a split audience configuration:

  1. Click Split Audience.
    The Set Audience Percentages window displays.
  2. Enable Split audience
  3. (option) To enable a control group: Select Enable Control Group 
  4. Fill in the audience allocation, in percentage, for each partner and if needed for the control group. 
  5. Click Apply.
    The percentage allocated to each partner is displayed. 

    ControIcon.png

  6. (Optional) Send split groups to S3: Sends the audience list in CSV files to an Amazon S3 bucket. (See above for details.) 
  7.  Click Close.
    AppsFlyer sends the split audience to the designated partners once a day.

Modifying split audience configurations

You can modify the split audience allocation as follows:

  • Modify the current allocation 
  • Remove a partner
  • Add a partner

When you modify the allocation between partners, the entire audience is redistributed between the partners. Note that this could impact the validity of A/B or other test measurements. In addition, modification resets the existing audience allocation.

To modify a split audience configuration:

  1. Go to Integration > Audiences.
  2. Select the audience to be modified.
  3. Go to the Connect tab.
    The split audience allocation displays.
  4. Select one of the following:

Modify the Current Allocation 

  1. Click Split Audience.
    An alert displays.
  2. Click Continue to proceed.
  3. Fill in the audience allocation, in percentage, for each partner.
  4. Click Apply.
    The percentage allocation to each partner displays. The modification is complete.
  5. Click Close.

Remove a partner

  1. Select the partner you want to remove.
    An alert displays.
  2. Click Got it to proceed.
    The partner's connection list displays.
  3. Clear the checkbox on one or more of the existing connections.
  4. Click Save Connections.
    The partner is removed.
  5. Click Split Audience.
    The Set Audience Percentages window displays.
  6. Switch Enable Split Audience on.
  7. Fill in the audience allocation, in percentage, for each partner.
  8. Click Apply.
    The split audience is enabled. The percentage allocation to each partner displays.
  9. Click Close.

Add a partner

  1. Select a partner to add.
    An alert displays.
  2. Click Cancel or continue to configure using the partner configuration instructions.

Viewing and managing audiences

Go to IntegrationAudiences to view and manage your Audiences.

In the Audiences window, you can view information about audiences, add an audience, use the actions and bulk actions controls. These features are described here. 

In the Audiences window you can view the following information: 

  • Audience name
  • Size: number of users in the audience
  • App name 
  • Upload to: names of partners to whom the audience is sent. 
    • If split audiences are enabled the icon mceclip1.png displays next to the list
    • If a control group is enabled this is indicated by the control group icon. mceclip2.png
  • Upload Status has the following indicators:
    • Success and the last upload time 
    • Failure, click View Details to see the reason the upload failed

Actions control 

Select an audience Action control to perform one of the following: 

  • View history displays the upload history of that audience. Because the audience updates daily, you can view the size differences of the user list throughout its lifecycle:
  • Upload now sends the audience to the connected partners
  • Download as CSV to download the audience device ID list in a CSV file. There is a separate file for each partner. 
  • Duplicate allows you to make a copy of the selected audience definition. (Option) remove one or more of the existing partners. Note: Audience names do not have to be unique. When you duplicate an audience you should give it a unique name. 

  • Delete

Bulk actions

The Bulk actions control enables you to carry out the same action on multiple audiences. To use Bulk actions, select two or more audiences and a Bulk action: 

  • Upload now sends the audience to the connected partners.
  • Show audience overlap: displays the audience overlap between the selected audiences,
  • Delete the selected audiences 

 Note

The Audience user base is updated daily. It contains user information up to and including the previous day. That means yesterday and all the days before it.

Partner configuration instructions

Aarki

  1. Obtain your app's API Key from your Aarki account manager.
  2. Create a new Aarki integration. The following window opens:

    Aarki_1.png

  3. Paste your API Key in the input bar.
  4. Click Add Connection.

AdColony

  1. Obtain your app's API Key from your AdColony Account Manager
  2. Create a new AdColony integration. 
  3. Enter the API Key.
  4. Click Add Connection.

Adikteev

 To connect to Adikteev:

  1. Obtain the API Username, API Password, and Company ID from your Adikteev account manager.
  2. Click Add a new connection.
  3. Complete the fields API username, API Password, and Company ID. 
  4. Click Add Connection.
    The connection is created. 

Adobe Audience Manager (AAM)

AppsFlyer creates and syncs Traits with your selected DataSource.

  1. Log into your Adobe Maketing Cloud dashboard
  2. Go to Manage Data > Data Sources

    On the Data Sources page, create a new Data Source.
  3. Set as follows:

    • ID Type to Device Advertising ID,

    • Inbound settings to Customer ID.

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

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

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

  12. Paste the values you copied in their corresponding locations
  13. 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.

Affle

  1. Obtain your app’s API Key from your Affle account manager.
  2. Create a new Affle integration. The following window opens:

  3. Paste your API Key in the input bar.
  4. Click Add connection.

Amazon S3

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

  1. Create a new Amazon S3 integration. The following window opens:

  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:*",
    										"Resource": "arn:aws:s3:::BUCKET-NAME/*"
    										}
    										]
    										}
    									
  6. Replace BUCKET-NAME with the name of the bucket to which you want AppsFlyer to upload your audience.

     Note

    The policy must contain only the root bucket and not additional directories in the path. For example, the resource arn:aws:s3:::BUCKET-NAME/Directory/* is not supported. If you need the files to be transferred to a specific directory, see step 14.

    The actions PutObject, DeleteObject and ListBucket are MANDATORY for AppsFlyer to perform minimal actions on your bucket.

  7. After creating your policy, proceed to the next steps:
  8. In your AWS Dashboard, go to IAM and click Create a new role:

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

  10. Select Require external ID.

    Copy the AccountID and ExternalID provided in AppsFlyer's S3 integration screen. Paste them into the appropriate input boxes in the role's creation screen.

  11. You are prompted to select a policy from the existing policies in your AWS account. Choose the policy previously created.
  12. Once the new role is created, click the name of the role to open its properties window.
  13. Copy the Role ERN.

  14. 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.

    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.

Applift

  1. Obtain your API Key from your Applift account manager.
  2. Create a new Applift integration. The following window opens:

  3. Enter your DataLift 360 Advertiser email (your login email to DataLift 360’s dashboard) the API Key you've just copied.
  4. Click Add Connection 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

  1. Obtain your Custom Audience Key from your Applovin advertiser’s account page.

  2. Create a new Applovin integration. The following window opens:

  3. Paste your Custom Audience Key in the input bar.
  4. Click Add Connection.

Appreciate

  1. Obtain your app’s API Key from your Appreciate account manager.
  2. Obtain your buyerId from your Appreciate account manager.
  3. Create a new Appreciate integration, you will see the following screen:

    appreciate_audience_connect.png

  4. Paste your buyerId and API Key in the input bar, click Add Connection.

Beeswax

  1. Obtain your Buzzkey from Beeswax
  2. Obtain your Account ID from Beeswax
  3. Create a new Beeswax integration. The following window opens:

    beeswax-audiences.png

  4. Complete all the necessary fields - email, password, Buzzkey and Account ID.
  5. Click Add Connection

Beintoo

  1. Obtain your app’s API Key from your Beintoo account manager.
  2. Create a new Beintoo integration. The following window opens:

  3. Paste your API Key in the input bar.
  4. Click Add connection.

Chartboost

  1. Obtain your Chartboost User ID and User Signature from your Chartboost account dashboard.
  2. Create a new Chartboost integration. The following window opens:

  3. Paste your User ID and User Signature in the input bar.
  4. Click Add connection.

Criteo

  1. Obtain your Criteo Advertiser ID.
  2. Create an API User in your Criteo dashboard -

    Criteo Marketing API

  3. Copy the API User’s Client ID and Secret, provided to you after its creation.
  4. Create a new Criteo integration. The following window opens:

  5. Paste your API User’s Client ID and Client Secret, along with your Advertiser ID in the input bar.
  6. Click Add Connection.

Downstream

  1. Obtain your API Key from your Downstream.ai account manager.
  2. Create a new Downstream.ai integration. The following window opens:

  3. Paste your API Key in the input bar.
  4. Click Add connection.

Facebook

  1. Create an Ad Account on Facebook
  2. Select Facebook in AppsFlyer’s Audiences integrations page. The following window opens:

  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.

Httpool

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

    httpool_loginpng.png

  2. Login to your Httpool account. You then see a new timestamp:

    httpool_connect.png

  3. Click Add Connection.

GetLoyal

  1. Obtain your app's API Key from your GetLoyal account manager.
  2. Create a new GetLoyal integration. The following window opens:

  3. Enter your API Key in the input bar.
  4. Click Add Connection.

InMobi

  1. Obtain your app's Property ID from InMobi's dashboard.
  2. Under the Monetize tab, select your app and copy the Property ID displayed at the top of the screen:

  3. Create a new InMobi integration. The following window opens:

  4. Paste your Property ID in the input bar.
  5. Select the DST LIST Type you want 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:

  5. Create a new ironSource integration. The following window opens:

  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 Add to complete the connection.

Jampp

  1. Obtain the following from your Jampp account manager:
    • Client ID
    • Client secret
    • App ID
  2. Create a new Jampp integration. The following window opens:

    connect_to_jampp.png

  3. Paste the client ID, client secret and app ID in the relevant fields.
  4. Click Add Connection.

Lemmonet

  1. Obtain your app’s API Key from your Lemmonet Account Manager.
  2. Create a new Lemmonet integration. The following window opens:

    Lemmonet_audiences.png

  3. Paste your API Key in the input bar.
  4. Click Add connection.

Liftoff

  1. Obtain your app’s API Key from your Liftoff Account Manager.
  2. Create a new Liftoff integration. The following window opens:

  3. Paste your API Key in the input bar.
  4. Click Add connection.

Manage

  1. Obtain your app's API Key from your Manage Account Manager.
  2. Create a new Manage integration. The following screen opens:

  3. Paste your API Key in the input bar.
  4. Click Add Connection.

MediaSmart

  1. Request your MediaSmart account manager to provide you with an Organization ID.
  2. Create a new MediatSmart integration.
    The window opens.
  3. In the organizationid field, paste the Organization ID you received from MediaSmart.
  4. Click Add Connection.

Mobusi

  1. Obtain your app’s API Key from your Mobusi account manager.
  2. Create a new Mobusi integration. The following window opens:

  3. Paste your API Key in the input bar.
  4. Click Add connection.

Mobvista

  1. Obtain your app’s API Key and Advertiser ID from your Mobvista account manager.
  2. Create a new Mobvista integration. The following window opens:

  3. Paste your API Key and Advertiser ID in the input bar.
  4. Click Add connection.

MyTarget

  1. Select MyTarget in AppsFlyer’s Audiences integrations page. The following window opens:
  2. Login to your MyTarget account, and select your ad account.
  3. Click Add Connection.

After uploading an Audience to MyTarget, it appears in your MyTarget’s Users Lists dashboard.

Oracle Data Cloud

  1. Create a new Oracle Data Cloud connection, as in the screenshot below:

  2. Copy AppsFlyer’s Seat ID, and request your Oracle Data Cloud account manager to whitelist it for you. This enables AppsFlyer to create categories on your behalf.
  3. Insert your Seat ID and Site ID (you can receive them from your Oracle Data Cloud account manager).
  4. After verifying your Seat ID, a dropdown list displays all of your Parent Categories:

  5. Select the Parent Category under which your sub-categories should be created.
  6. Click Add Connection.

Persona.ly

  1. Obtain your app’s API Key from your Persona.ly account manager.
  2. Select Persona.ly in AppsFlyer’s Audiences integrations page. The following window opens:

    personaly_connect.png

  3. Paste the API key.
  4. Click Add Connection.

PushSpring

  1. Select PushSpring in AppsFlyer’s Audiences integrations page. The following window opens:

  2. Click Login with PushSpring and complete the login process. Once you've logged in, a new timestamp is displayed.

  3. Click Add Connection.

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

Remerge

  1. Obtain your Access Key Id from your Remerge account manager.
  2. Obtain your Secret Access Key from your Remerge account manager.
  3. Obtain the Path from your Remerge account manager.
  4. Select Remerge in AppsFlyer Audiences integrations page
    remerge_audience_integration.png
  5. Paste your Access Key Id, Secret Access Key and the Path in the relevant fields.

  6. Click Add Connection.

RTBHouse

  1. Obtain your app API Key from your RTBHouse account manager.
  2. Select RTBhouse in AppsFlyer Audiences integrations page. The following window opens:
    RTBHouse.png
  3. Paste your API Key in the Your API Key field.

  4. Click Add Connection.

SFTP

  1. Create SFTP access credentials which include Server IP, Username, and Password.
  2. Create a new SFTP connection. The following window opens:

  3. Enter the SFTP credentials.
  4. If you want the files to be transferred to a specific folder path in the server, enter the path with “/” delimiters (for example, “appsflyer/audiences”).

     Note

    Each file will be added to a folder named after the Audience name itself. The file name will contain the audience name and relevant date (eg. “appsflyer/audiences/MyAudience/MyAudience_2017-10-02”).

    If you leave this blank, the files will be added to the root folder of your SFTP server.

  5. If you want the files to be compressed with GZIP, enable the GZIP files option.
  6. Click Add Connection.

Slack

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

  1. Create a new Slack integration. The following window opens:

  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 downloaded to the selected channel.

Smadex

  1. Create a new Smadex integration. The following window opens:

  2. Login to your Smadex account and authorize AppsFlyer to access your account.
  3. Click Add Connection.

Snapchat

  1. Select Snapchatin AppsFlyer’s Audiences integrations page. The following window opens:

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

  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 smaller audience size.

Startapp

  1. Obtain your app's API Token from your StartApp account manager.
  2. Create a new StartApp integration. The following window opens:

  3. Paste your API Token in the input bar.
  4. Click Add Connection.

Tapjoy

  1. Obtain your Partner ID from your Tapjoy Account Manager.
  2. Obtain your Publisher Reporting API Key from your Tapjoy App Settings page.

  3. Create a new Tapjoy integration. The following window opens:
  4. Paste your Tapjoy Partner ID and Publisher Reporting API Key in the input bar.
  5. Click Add.

Taptica

  1. Obtain your app’s API Key from your Taptica Account Manager.
  2. Create a new Taptica integration. The following window opens:

    Taptica_Audiences.png

  3. Paste your API Key in the input bar.
  4. Click Add connection.

Verizon Media (aka Oath: Ad Platforms / Yahoo Gemini)

  1. Create an Ad Account on Yahoo Gemini
  2. Select Verizon Media in AppsFlyer’s Audiences Integrations page. The following window opens:

  3. Login to your Yahoo account, and select your desired Ad Account.

After uploading an Audience to Verizon Media, you can view it in your Verizon Media dashboard.

Limitations

  • At least one positive condition is required to create the base audience, which can be reduced by further negative conditions (Example installed the app AND did not do af_purchase event).
  • Windows Phone is not supported.
  • Audience names cannot be changed on the connected partners’ side.
  • Nested event values are not supported.
  • When creating an audience, at times, not all the events appear. Only the top 100 are displayed, however, when you begin entering an event name, all the events are shown.
  • The clicks and impressions data only contains devices which have advertising_id / idfa on their original click URL. Therefore devices of users from SRNs, which don't use external attribution links, are not included in the clicks data for audiences.
  • When using the Total Revenue filter within the query builder, the Estimated Audience Size is not available. This does not affect the Audience creation and the Audience list.
  • You cannot combine audiences created by import with other audiences or rulesets.
  • As a security measure, where the account of the team member, who created an audience is deleted, AppsFlyer stops uploading audience data to the advertising partner. To check the upload status of your audiences, go to Integration > Audiences. To reactivate the audience, in the Audiences window, duplicate the audience, and configure the split audience settings.
Was this article helpful?
2 out of 2 found this helpful