AppsFlyer integration validation

Review the AppsFlyer integration rules and how to resolve integration setup warnings in the User Acquisition Dashboard.

Read time 27 minutes

Last updated a month 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.

Integration validation rules

Refer to the following tabs for lists of the required and recommended integration rules and their associated campaign goals:

Required integration rules

You must adhere to the following rules to set your campaigns live:

Rule	Description	Associated campaign goals
Game ID	The Game ID in the AppsFlyer integration setup must match the Game ID in the Unity dashboard.	All campaign goals
View-through attribution	View-through attribution must be enabled.	All campaign goals
View-through lookback window	View-through lookback windows must be at least seven days.	All campaign goals
Click-through lookback window	Click-through lookback windows must be at least two days.	All campaign goals
AppsFlyer event mapping	AppsFlyer post-install events must be mapped to the correct Unity Ads event name.	All optimized campaign goals, including the following: Return on Ad Spend (ROAS) Event optimization (CPE)
In-app purchase event mapping	In-app purchase events must be mapped correctly.	In-app purchase ROAS Hybrid ROAS Payer CPE
In-app purchase event values and revenue	In-app purchase event postbacks must contain both values and revenue.	In-app purchase ROAS Hybrid ROAS Payer CPE
In-app purchase postbacks	Within seven days of launch, campaigns must have one or more in-app purchase event postbacks.	In-app purchase ROAS Hybrid ROAS Payer CPE
Ad revenue event values and revenue	Ad revenue event postbacks must contain both values and revenue.	Ad revenue ROAS Hybrid ROAS
Ad revenue postbacks	Within seven days of launch, campaigns must have one or more Ad Revenue event postbacks.	Ad revenue ROAS Hybrid ROAS
Level Complete events	Level Complete event postbacks must not include values or revenue.	Level Complete CPE
Session events	Session event postbacks must not include values or revenue.	Retention CPE
Install postbacks	Within two days of launch, the app must have at least one install postback in the past 90 days.	All campaign goals

Recommended integration rules

The following integration rules aren't required to set your campaign live. However, failure to meet these recommended rules can negatively impact campaign performance and attribution:

Rule	Description	Associated campaign goals
Unattributed and organic installs	Send Install event postbacks for users from all sources, including organic.	All campaign goals
Unattributed and organic in-app purchase events	Send In-app Purchase event postbacks for users from all sources, including organic.	In-app purchase ROAS Hybrid ROAS Payer CPE
Unattributed and organic ad revenue events	Send Ad Revenue event postbacks for users from all sources, including organic.	Ad revenue ROAS Hybrid ROAS
Unattributed and organic session events	Send Session event postbacks for users from all sources, including organic.	Retention CPE
Unattributed and organic level complete events	Send Level Complete event postbacks for users from all sources, including organic.	Level Complete CPE
Lifetime postback windows	Set in-app event postback windows to lifetime.	All optimized campaign goals, including the following: Return on Ad Spend (ROAS) Event optimization (CPE)

Required rule resolutions

To meet the required integration rules, refer to the following resolution information.

Game ID

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 enter your Unity Game ID in the AppsFlyer integration setup, follow these steps:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the General settings section.
Enter your Game ID in the Unity Ads Game ID field. To copy your Game ID from the Unity Dashboard, refer to the following steps:

To retrieve your Game ID from the Apps page of the Unity Dashboard, follow these steps:

Go to Apps from the left navigation menu. The provided table lists each of your organization's apps. Following each app name, the dashboard displays the app platform and Game ID.
Select Copy () next to the ID to copy it to your clipboard.

View-through attribution

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 the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the Install attribution section.
Activate the Install view-through attribution toggle.

The install view-through attribution toggle in the AppsFlyer integration setup. — View-through attribution enabled

View-through lookback window

To meet this validation rule, set your view-through lookback window to 7 Days.

To set the view-through lookback window to 7 days, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the Install attribution section.
Set the Install engaged view-through lookback window to Days.
Using the slider, set the window to 7 Days.
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

Click-through lookback window

To meet this validation rule, set your click-through lookback window to 2 Days.

To set the click-through lookback window to 2 Days, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the Install attribution section.
Set the Install engaged click-through lookback window to Days.
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

AppsFlyer event mapping

To meet this validation rule, ensure that you map all AppsFlyer events to the correct Unity Ads event name.

To map your AppsFlyer events to Unity Ads events, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
Map your post-install events to Unity Ads 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 table for suggested AppsFlyer event names and required Unity Ads event names:

Event type	Suggested AppsFlyer event	Required Unity Ads partner event	Mapping notes
Session	`af_app_opened`	`session`	-
Ad revenue	`af_ad_revenue`	`ad_revenue`	If your AppsFlyer account supports ad revenue data-sharing, enable ad revenue sharing with the Get ad revenue data toggle in the Ad revenue tab. Otherwise, don't send ad revenue events. Mapping ad revenue events as other event types can cause campaign optimization to stop working. Refer to the AppsFlyer Ad revenue attribution documentation for details and instructions.
In-app purchase	`af_purchase`	`purchase`	Don't map revenue events to purchase events.
Milestone completion	`af_level_achieved` `{custom_milestone_event_name}`	`level_complete`	You must enter `level_complete` in the mapped to partner event field. You can enter custom SDK event names in the AppsFlyer event field.

You must enter the required Unity Ads event name in the mapped to partner event field. You can enter custom SDK event names in the AppsFlyer event field. However, the recommended best practice is to use the Suggested AppsFlyer event names provided here.

In-app purchase event mapping

To meet this validation rule, ensure that you configure in-app purchase events correctly in your AppsFlyer integration setup.

To map your in-app purchase event postbacks, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
Map your Purchase event row as follows:

AppsFlyer event	mapped to partner event	for users from	including
`af_purchase`	`purchase`	All media sources, including organic	Values & revenue

The event mapping table in the AppsFlyer integration setup. — Purchase event mapping for In-app Purchase campaigns

In-app purchase event values and revenue

To meet this validation rule, ensure that you include Values & revenue when you map in-app purchase events in your AppsFlyer integration setup.

To configure the included data in your in-app purchase event postbacks, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
In the including column of the mapping table, select Values & revenue:

The Values & revenue selection in the AppsFlyer event mapping table. — Share Purchase event values and revenue

If you don't include both values and revenue in your in-app purchase event postbacks in the AppsFlyer integration setup, you receive the following error message in the Unity Dashboard:

Required MMP integration fixes

Integration blocking issues detected. These issues can severely impact your existing and new campaign performance:

In-app purchase event postbacks for In-app Purchase and Hybrid ROAS campaigns must contain values.

In-app purchase postbacks

To meet this rule within seven days of launching your campaign, your app must have received one in-app purchase postback in the last 90 days.

Ensure that you map your purchase postbacks correctly and include both values and revenue.

To map your in-app purchase event postbacks, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
Map your Purchase event row as follows:

AppsFlyer event	mapped to partner event	for users from	including
`af_purchase`	`purchase`	All media sources, including organic	Values & revenue

If, a week after launching your campaign, your app hasn't received any in-app purchase postbacks in the last 90 days, you receive the following error message in the Unity Dashboard:

Required MMP integration fixes

Integration blocking issues detected. These issues can severely impact your existing and new campaign performance:

Within 7 days of launch, campaigns must receive at least one in-app purchase postback.

Ad revenue event values and revenue

To meet this validation rule, ensure that you include Values & revenue when you map ad revenue events in your AppsFlyer integration setup.

Important

To map Ad revenue events with AppsFlyer, you must first enable ad revenue sharing. Refer to the AppsFlyer Ad revenue attribution documentation for details and instructions.

To configure this data-sharing setting, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
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 organic	Values & revenue

If you don't include both values and revenue in your ad revenue event postbacks in the AppsFlyer integration setup, you receive the following error message in the Unity Dashboard:

Required MMP integration fixes

Integration blocking issues detected. These issues can severely impact your existing and new campaign performance:

Revenue event postbacks for Ad Revenue and Hybrid campaigns must contain values.

Ad revenue postbacks

To meet this rule within seven days of launching your campaign, your app must have received one ad revenue postback in the last 90 days.

Ensure that you enable ad revenue data in your AppsFlyer integration setup.

To share ad revenue event data with your campaign, follow these steps in the AppsFlyer dashboard:

Activate ad revenue sharing

To activate ad revenue data-sharing, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Ad revenue tab, 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

Configure ad revenue data-sharing

To configure your ad revenue data-sharing settings, follow these steps in the AppsFlyer dashboard:

From the AppsFlyer dashboard side menu, go to Settings > Revenue Settings.

Important

To access the Revenue Settings menu, you need an AppsFlyer ROI360 subscription. Refer to the AppsFlyer Ad revenue attribution documentation for details and instructions.

In the Revenue settings > Ad revenue tab, select New ad revenue integration.
Select Unity Ads from the list of revenue partners.
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

Enter your API credentials

To finish your ad revenue data-sharing setup, follow these steps in the AppsFlyer dashboard Revenue Settings:

Enter your Unity Game ID in the App key field. To retrieve your Game ID from the Unity Dashboard, refer to the following steps:

To retrieve your Game ID from the Apps page of the Unity Dashboard, follow these steps:

Go to Apps from the left navigation menu. The provided table lists each of your organization's apps. Following each app name, the dashboard displays the app platform and Game ID.
Select Copy () next to the ID to copy it to your clipboard.

Enter your Unity API Service account secret key in the Secret key field. To retrieve your secret key from the Unity Dashboard, refer to the following steps:

To retrieve your API service account secret key from the Unity Dashboard, follow these steps:

From the left navigation menu, go to API Management.
Select Advertising Public API > Service account.

The API Management page of the User Acquisition dashboard. — Advertising Public API Service account

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

If, a week after launching your campaign, your app hasn't received any ad revenue postbacks in the last 90 days, you receive the following error message in the Unity Dashboard:

Required MMP integration fixes

Integration blocking issues detected. These issues can severely impact your existing and new campaign performance:

Within 7 days of launch, campaigns must receive at least one ad revenue postback.

Level Complete events

To meet this validation rule, ensure that you choose No values & no revenue when you map level complete events in your AppsFlyer integration setup.

To configure the included data in your level complete postbacks, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
In the including column of the mapping table, select No values & no revenue:

Refer to the following example of correct mapping:

Note

You can enter custom SDK event names in the AppsFlyer event field. You must enter

level_complete

in the mapped to partner event field.

AppsFlyer event	mapped to partner event	for users from	including
`af_level_achieved`	`level_complete`	All media sources, including organic	No values & no revenue

The No values & no revenue selection in the AppsFlyer event mapping table. — No values or revenue in level complete event postbacks

If you include values or revenue in level complete event postbacks in your AppsFlyer integration setup, you receive the following error message in the Unity Dashboard:

Required MMP integration fixes

Integration blocking issues detected. These issues can severely impact your existing and new campaign performance:

Level Complete event postbacks for Level Complete campaigns must not contain values or revenue.

Session events

To meet this validation rule, ensure that you choose No values & no revenue when you map session events in your AppsFlyer integration setup.

To configure the included data in your session event postbacks, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
In the
```
session
```
event row, use the including dropdown to select No 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 organic	No values & no revenue

Install postbacks

To meet this rule within two days of launching your campaign, your app must have received one install postback in the last 90 days.

Ensure that you configure your Install attribution and Default postbacks settings correctly so your campaigns can receive install postbacks:

Activate the Share organic/non-organic indication toggle.
Set the click-through lookback window to 2 days.
Set the view-through lookback window to 7 days.
Activate the Install view-through attribution toggle.
Select for users from > All Media sources in the install event Default postbacks setup.

To activate the Share organic/non-organic indication toggle, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the General settings section.
Activate the Share organic/non-organic indication toggle.

Recommended rule resolutions

To meet the recommended integration rules, refer to the following resolution information.

Unattributed and organic installs

To meet this recommended integration rule, ensure you configure the following sections correctly in your AppsFlyer integration:

General settings: Activate the Share organic/non-organic indication toggle.
Default postbacks: Use the for users from dropdown to select All media sources, including organic.

To configure your install postbacks to include all sources, including organic, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the Default postbacks section.
In the Install event row, use the for users from dropdown to select All media sources, including organic.

Unattributed and organic in-app purchase events

To meet this recommended integration rule, ensure that you send in-app purchase event postbacks for users from All media sources, including organic.

To send in-app purchase event postbacks for users from all sources, including organic, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
In the row for
```
purchase
```
events, use the for users from dropdown to select All media sources, including organic

Unattributed and organic ad revenue events

To meet this recommended integration rule, ensure that you send ad revenue event postbacks for users from All media sources, including organic.

To send ad revenue event postbacks for users from all sources, including organic, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
In the row for
```
ad_revenue
```
events, use the for users from dropdown to select All media sources, including organic

Unattributed and organic session events

To meet this recommended integration rule, ensure that you send session event postbacks for users from All media sources, including organic.

To send session event postbacks for users from all sources, including organic, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
In the row for
```
session
```
events, use the for users from dropdown to select All media sources, including organic

Unattributed and organic level complete events

To meet this recommended integration rule, ensure that you send level complete event postbacks for users from All media sources, including organic.

To send level complete event postbacks for users from all sources, including organic, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
In the row for
```
level_complete
```
events, use the for users from dropdown to select All media sources, including organic

Lifetime postback windows

To meet this validation rule with AppsFlyer, set your In-app event postback window to Lifetime.

To set the postback window length to lifetime, follow these steps in the AppsFlyer dashboard:

Go to Collaborate > Partner Marketplace and search for
```
Unity Ads
```
to open your Unity Ads integration.
In the Integration tab, go to the In-app event postbacks section.
Activate the In-app event postbacks toggle.
Set the In-app event postback window to lifetime.

The in-app event postback window setting in the AppsFlyer integration setup. — Lifetime postback window

AppsFlyer integration validation

Integration validation rules

Required integration rules

Rule

Description

Associated campaign goals

Required rule resolutions

Game ID

Copy your Game ID from the Unity Dashboard

View-through attribution

View-through lookback window

Click-through lookback window

AppsFlyer event mapping

Event type

Suggested AppsFlyer event

Required Unity Ads partner event

Mapping notes

In-app purchase event mapping

AppsFlyer event

mapped to partner event

for users from

including

In-app purchase event values and revenue

In-app purchase postbacks

AppsFlyer event

mapped to partner event

for users from

including

Ad revenue event values and revenue

AppsFlyer event

mapped to partner event

for users from

including

Ad revenue postbacks

Activate ad revenue sharing

Configure ad revenue data-sharing

Enter your API credentials

Copy your Game ID from the Unity Dashboard

Copy your secret key from the Unity Dashboard

Level Complete events

AppsFlyer event

mapped to partner event

for users from

including

Session events

AppsFlyer event

mapped to partner event

for users from

including

Install postbacks

Recommended rule resolutions

Unattributed and organic installs

Unattributed and organic in-app purchase events

Unattributed and organic ad revenue events

Unattributed and organic session events

Unattributed and organic level complete events

Lifetime postback windows