Documentation

Support

Unity Ads User Acquisition

Campaigns

Attribution

Open User Acquisition dashboard

Unity Ads User Acquisition

AppsFlyer required integration fixes

Review the MMP integration rules and how to resolve integration setup warnings in the User Acquisition Dashboard.
Read time 7 minutesLast updated 2 days ago
When you integrate your user acquisition campaign with AppsFlyer, the Unity dashboard validates your integration setup to ensure it's configured correctly. If you don't resolve these integration errors, you can't launch new or paused campaigns, and your live campaigns can suffer serious performance and attribution issues. You must adhere to the following rules to set your campaigns live: Refer to the following sections for instructions on how to resolve these issues.

The Game ID must match

To meet this validation rule, ensure that the Game ID you enter in the AppsFlyer dashboard matches the Game ID in the Unity Ads User Acquisition dashboard exactly. To retrieve your Game ID from the Apps page of the Unity dashboard, follow these steps:
  1. Go to Apps from the left navigation menu of the dashboard. The provided table lists each of your organization's apps. Following each app name, the dashboard displays the app platform and Game ID.
  2. Select the Copy symbol next to the ID to copy it to your clipboard.
You can also retrieve your Game ID from the Campaigns, Campaign details, and Creative packs pages of the dashboard. Refer to the Game ID documentation for details.

Postback windows must be at least 180 days

To meet this validation rule with AppsFlyer, set your In-app event postback window to 
lifetime
. To set this window, follow these steps:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. Set the In-app event postback window to lifetime.
    The in-app event postback window setting in the AppsFlyer integration setup

    Lifetime postback window

Click-through lookback windows must be at least 2 days

To meet this validation rule, set your click-through lookback window to 
2
days. To set this window, follow these steps:
  1. Go to the Install attribution section of the Integration tab.
  2. In the Install engaged click-through lookback window section, select Days.
  3. Using the slider, set the window to 2 Days.
    The install engaged click-through lookback window setting in the AppsFlyer integration setup

    2-day click-through lookback window

View-through lookback windows must be at least 7 days

To meet this validation rule, set your view-through lookback window to 
7
days. To set this window, follow these steps:
  1. Go to the Install attribution section of the Integration tab.
  2. In the Install engaged view-through lookback window section, select Days.
  3. Using the slider, set the window to 7 Days.
  4. Activate the Install view-through attribution toggle.
    The install engaged view-through lookback window setting in the AppsFlyer integration setup

    7-day view-through lookback window

View-through attribution must be enabled

To meet this validation rule, ensure that you enable view-through attribution in your AppsFlyer integration setup. To enable view-through attribution, follow these steps:
  1. Go to the Install attribution section of the Integration tab.
  2. Following the Install engaged view-through lookback window section, activate the Install view-through attribution toggle.
    The install view-through attribution toggle in the AppsFlyer integration setup

    View-through attribution enabled

Level Complete event postbacks must contain values

To meet this validation rule, ensure that you choose Values & revenue when you map Level Complete events in your AppsFlyer integration setup. To configure this data-sharing setting, follow these steps:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. In the including column of the mapping table, select Values & revenue:
Refer to the following example of correct mapping:

AppsFlyer event

mapped to partner event

for users from

including

af_level_achieved
level_complete
All media sources, including organicValues & revenue
The Values & revenue selection in the AppsFlyer event mapping table

Share Level Complete event values and revenue

Purchase event postbacks must contain values

To meet this validation rule, ensure that you choose Values & revenue when you map Purchase events in your AppsFlyer integration setup. To configure this data-sharing setting, follow these steps:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. In the including column of the mapping table, select Values & revenue:
Refer to the following example of correct mapping:

AppsFlyer event

mapped to partner event

for users from

including

af_purchase
purchase
All media sources, including organicValues & revenue
The Values & revenue selection in the AppsFlyer event mapping table

Share Purchase event values and revenue

Revenue event postbacks must contain values

To meet this validation rule, ensure that you choose Values & revenue when you map Ad revenue events in your AppsFlyer integration setup. To configure this data-sharing setting, follow these steps in the Integration tab of the AppsFlyer integration setup:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. In the including column of the mapping table, select Values & revenue:
Refer to the following example of correct mapping:

AppsFlyer event

mapped to partner event

for users from

including

af_ad_revenue
ad_revenue
All media sources, including organicValues & revenue
The Values & revenue selection in the AppsFlyer event mapping table

Share Ad Revenue event values and revenue

Session event postbacks must contain values

To meet this validation rule, ensure that you choose Values & no revenue when you map Session events in your AppsFlyer integration setup. To configure this data-sharing setting, follow these steps:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. In the including column of the mapping table, select Values & no revenue:
Refer to the following example of correct mapping:

AppsFlyer event

mapped to partner event

for users from

including

af_app_opened
session
All media sources, including organicValues & no revenue
The Values & no revenue selection in the AppsFlyer event mapping table

Share Session event values only

Purchase event postbacks must be mapped correctly

To meet this validation rule, ensure that you map Purchase events correctly in your AppsFlyer integration setup. To map your Purchase event postbacks, follow these steps:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. Map your Purchase event row as follows:

AppsFlyer event

mapped to partner event

for users from

including

af_purchase
purchase
All media sources, including organicValues & revenue
The event mapping table in the AppsFlyer integration setup

Purchase event mapping for In-app Purchase campaigns

AppsFlyer events must be mapped to the correct Unity event name

To meet this validation rule, ensure that you map all AppsFlyer event postbacks correctly. To map your events, follow these steps:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. Map your post-install events to Unity events in the mapped to partner event column as follows:
    • Session events to 
      session
    • Level Complete events to 
      level_complete
    • Ad Revenue events to 
      ad_revenue
    • In-app Purchase events to 
      purchase
Refer to the following example of correct event mapping:

AppsFlyer event

mapped to partner event

for users from

including

af_purchase
purchase
All media sources, including organicValues & revenue
{custom_sdk_event_name}
level_complete
All media sources, including organicValues & revenue
af_app_opened
session
All media sources, including organicValues & no revenue
af_ad_revenue
ad_revenue
All media sources, including organicValues & revenue

App must receive at least one install postback

To meet this validation rule, ensure that you configure your Default postbacks settings correctly so your campaigns can receive install postbacks. Configure these AppsFlyer integration settings as follows:
  1. Go to the Default postbacks section of the Integration tab.
  2. In the 
    Install
    row, use the for users from dropdown to select All media sources, including organic.
    The Default postbacks section of the AppsFlyer integration setup

    Share all sources, including organic

Campaigns must receive one or more Ad Revenue postbacks

To meet this validation rule, ensure that you enable ad revenue data in your AppsFlyer integration setup. To share ad revenue event data with your campaign, follow these steps:
  1. Go to the Ad revenue tab of your AppsFlyer integration setup.
  2. Activate the Get ad revenue data toggle.
    The Ad revenue tab and Get ad revenue toggle in the AppsFlyer integration setup

    Get ad revenue toggle

  3. From the AppsFlyer dashboard side menu, go to Settings > Revenue Settings.
  4. In the Ad revenue tab of the Revenue settings page, select New ad revenue integration.
  5. Select Unity Ads from the list of revenue partners.
  6. In the partner configuration, select Impression-level (via SDK) with Device-level (via S2S API) as the report type.
    The Impression-level with Device-level option in the AppsFlyer Ad revenue partner configuration

    AppsFlyer Revenue settings configuration

  7. Enter your API credentials. Enter your Game ID in the App Key field. To retrieve your Secret key from the Unity dashboard, refer to the following steps:

To retrieve your Secret key from the Unity Dashboard, follow these steps:
  1. From the left navigation menu, go to API Management.
  2. Select Advertising Management API > Service account.
    The API Management page of the User Acquisition dashboard

    Advertising Management Service account

  3. If you don't have a service account, select + New. If you have a service account already, select it from the table.
  4. In the service account page, go to the Keys section.
  5. Select + Add key to generate a new key.
  6. Select the copy buttons following the Secret key to copy the ID.

Campaigns must receive one or more In-app Purchase postbacks

To meet this validation rule, ensure that you map Purchase events correctly in your AppsFlyer integration setup. To map your Purchase event postbacks, follow these steps:
  1. Go to the In-app event postbacks section of the Integration tab.
  2. Activate the In-app event postbacks toggle.
  3. Map your Purchase event row as follows:

AppsFlyer event

mapped to partner event

for users from

including

af_purchase
purchase
All media sources, including organicValues & revenue
The event mapping table in the AppsFlyer integration setup

Purchase event mapping for In-app Purchase campaigns