Connect Unity Ads
Create a Unity service account with the reporting role, paste its key, and import your UA spend.
Unity Ads connects with a service-account key pair rather than OAuth. You create the key in Unity Cloud, then paste your Organization ID and the key into Revenue Sensor in a single step. The key is stored encrypted and never leaves our server.
Before you begin
- Access to the Unity organisation whose Unity Ads spend you want to track.
- Permission to create a service account under Unity Cloud → API Management → Service Accounts.
Connect the account
- 1
Create a service account
In Unity Cloud → API Management → Service Accounts, create a service account and generate a Key ID and Secret key.
- 2
Give it the reporting role
Assign the service account the Advertise Stats API Viewer role at the organisation level. A key without this role is valid but gets a 403 on every report — it is by far the most common setup failure.
- 3
Paste your details
Integrations → Unity Ads → Connect in the Revenue Sensor console. Enter your Organization ID, Key ID and Secret key.
What gets imported
| Field | Notes |
|---|---|
| Cost / spend | Daily, broken down by the promoted app and by country. |
| Impressions and clicks | Ad starts are stored as impressions, alongside clicks. |
| Installs | As reported by Unity. |
Spend only, joined to your apps
Unity is a pure spend source. Because rows carry the promoted app's store id, Unity spend joins the same per-app rows as your store connectors instead of landing in Unattributed.
Troubleshooting
- 403 on sync with a valid-looking key: the service account is missing the Advertise Stats API Viewer role. Grant it at organisation level and reconnect.
- No rows at all: check the Organization ID matches the organisation the campaigns run under.