Documentation

User Acquisition

What's new

Review updates to the Unity User Acquisition documentation.
Read time 6 minutesLast updated 2 days ago

Discover new features and improvements in the latest updates to Unity User Acquisition. This page lists changes by month with the most recent changes first.

September 2026

Updated app setup procedure

The procedure to add an app reflects the Add app dialog in the current dashboard and includes the Set your target audience step, where you indicate whether your app targets children.
For instructions, refer to Add an app to the dashboard.

Service account roles for API credentials

The procedure to create a Secret key and Key ID reflects the Settings > API management page in the current dashboard. After you generate a key, you must assign an organization role to your service account. Requests from a service account with no role fail with a
403
error and an Invalid Credentials message.
  • MMP integrations require the Advertise Stats API MMP Viewer role.
  • Reporting requires the Advertise Stats API Viewer role.
  • Campaign management requires an Advertise API role for each resource you manage, such as apps, bids, or campaigns.
The dashboard displays the Secret key only once, so store it somewhere secure after you generate it.
For instructions, refer to Locate advertiser credentials.

Advertiser Public API

The User Acquisition documentation now links to the Advertiser Public API reference, which replaces the Advertising Management API (
/advertise/v1
). If you have an existing integration that calls the Advertising Management API, migrate to the Advertiser Public API.

AppsFlyer integration validation rules

The User Acquisition dashboard validates your AppsFlyer integration and reports setup issues that affect your campaigns. The new Integration validation reference lists each required and recommended rule, the campaign goals it affects, the steps to resolve it, and the dashboard error message it produces.
You must resolve the required rules before you can launch new or paused campaigns. Recommended rules don't block a launch, but unresolved issues can affect campaign performance and attribution.

Updated AppsFlyer integration guide

The AppsFlyer integration guide now covers attribution and post-install event settings in full, including the click-through and view-through lookback windows, install postbacks for all media sources, and the Lifetime in-app event postback window. A new section explains how to enable ad revenue data-sharing for Return on Ad Spend (ROAS) Ad revenue and Hybrid campaigns.
For instructions, refer to Integrate AppsFlyer with Unity.

Singular event mapping by revenue type

Map Singular events based on whether they include revenue. Map ad revenue and in-app purchase events in the Revenue Events Postbacks section, and map milestone completion and session events in the Events Postbacks section.
Map ad revenue events to __ADMON_USER_LEVEL_REVENUE__. Don't map revenue events to __REVENUE__.
For instructions, refer to Integrate Singular with Unity.

Adjust data-sharing and event mapping requirements

To enable ROAS and Event optimization campaigns with Adjust, you must share all data types.
Milestone completion events also require a specific partner event name format,
level_complete_{NameOfEvent}
, where
NameOfEvent
contains no spaces.
For instructions, refer to Integrate Adjust with Unity.

Event mapping reference tables

Each MMP integration guide now includes an event mapping table that lists the Unity event name, the partner event name, and mapping notes for in-app purchase, ad revenue, milestone completion, and session events. The same tables appear in the Integration troubleshooting guide so that you can compare your setup against the correct mapping.

Updated Game ID retrieval

The procedure to copy your advertiser Game ID reflects the current dashboard, where you copy the Game ID from the MMP settings section of the app details page.
For instructions, refer to Locate advertiser credentials.

August 2026

Supported MMPs for Event optimization campaigns

Event optimization campaigns, also known as Cost per Event (CPE) campaigns, require a supported Mobile Measurement Partner (MMP). To run a Retention, Payer, or Level Complete campaign, you must use Adjust, AppsFlyer, or Singular. This requirement now appears on each Event optimization page so that you can confirm your MMP before you create a campaign.
For more information, refer to Introduction to Event optimization campaigns.

June 2026

Shared daily budgets across country groups

You can now share a single daily budget across a group of countries in the same campaign. Unity distributes spend across the countries in a group in real time and prioritizes where bids win and conversions happen.
For instructions, refer to Set Campaign and Daily budgets. For guidance about when to group countries, refer to Budget best practices.

Payer and Retention campaigns as Event optimization goals

Payer and Retention campaigns are now optimization options for Event campaigns. Both goals use your target cost per event (tCPE) and Unity's machine learning models predict conversion likelihood and adjust bids to meet your target.
  • Payer campaigns optimize for users predicted to make an in-app purchase within seven days of installation.
  • Retention campaigns optimize for users predicted to remain active in your app at least seven days after installation.

Integration troubleshooting guide

Optimized campaign goals such as Return on Ad Spend (ROAS) and Event optimization depend on the post-install events that your MMP sends to Unity. The new Integration troubleshooting guide helps you diagnose events that don't reach the User Acquisition dashboard.

Historical Retention campaigns replaced by the Event optimization goal

The previous standalone Retention campaign goal stopped delivering on July 9, 2026. Create all new Retention campaigns with the Event optimization campaign goal and Retention optimization type. For more information, refer to Introduction to Event optimization campaigns.

May 2026

Updated end card dimensions and video overlay templates

Square end cards at 800 × 800 pixels (1:1) are now the default end card type and the recommended best practice. The end card specifications list the resolution and ratio for each end card type so that you can confirm your files before you upload them.
The video creative templates now show where Unity overlay items display on portrait and landscape videos, so you can keep important content clear of the overlays.
For more information, refer to Creative specifications.

Requirements for the D28 Ad Revenue and D28 Hybrid ROAS goals

The Return on Ad Spend (ROAS) goal reference now lists the required data-sharing inputs and the minimum data thresholds for the D28 Ad Revenue and D28 Hybrid goals. Use this reference to confirm that your app meets the requirements for a goal before you create a campaign.
For more information, refer to Introduction to ROAS campaigns.

New User Acquisition documentation

The User Acquisition documentation is now available at docs.unity.com/user-acquisition to support the redesigned User Acquisition dashboard. The documentation covers the following areas:
  • Campaign goals, including Cost per Install (CPI), ROAS, Event optimization, and Creative Testing campaigns
  • Creatives, creative packs, custom app listings, and creative moderation
  • Bidding, bid limits, and budgets
  • Campaign targeting and source bidding
  • Attribution, post-install event data sharing, and custom server integrations
  • MMP partner integrations for Adjust, AppsFlyer, Airbridge, ByteBrew, Singular, and Tenjin
  • Campaign management, bulk management templates, and performance reporting
To start with an overview of the workflow, refer to Getting started with User Acquisition.