Connect Unity Ads Data to Revenue Sensor for Ad Reporting
Create a Unity service account with the reporting role, paste its key, and import your UA spend.
Unity Ads connects with a service account rather than a sign-in popup. You create the service account in Unity Cloud, then paste your Organization ID and its key into Revenue Sensor in a single step. The key is stored encrypted and never shown again.
Before you begin
- Owner or Manager access to the Unity organisation whose Unity Ads spend you want to track. You need it to create a service account and change its roles.
- If you belong to several organisations, connect them one at a time. Each one is its own connection with its own service account.
Connect the account
- 1
Find your Organization ID
Sign in at cloud.unity.com and switch to the organisation. The Organization ID is the long number in the dashboard URL, right after /organizations/. It is digits only, not the organisation's name.
- 2
Create a service account
Open Administration → Service Accounts and click New. Name it “Revenue Sensor” so you can recognise it later.
- 3
Give it the reporting role
On the service account's Roles tab, grant Advertise Stats API Viewer at the organisation level. Project-level roles are not enough. Without this role Unity answers every report with a permission error, which is by far the most common setup failure.
- 4
Create a key
On the service account, open Keys and click Add key. Copy the Key ID and the Secret key now: the secret is shown once.
- 5
Paste your details
Integrations → Unity Ads → Connect in the Revenue Sensor console. Enter your Organization ID, Key ID and Secret key, then click Continue. We run a small test report before loading the apps you advertise.
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 its report names the app each campaign promotes, Unity spend lands on the same per-app rows as your store connectors instead of in Unattributed. You can connect before any campaign has spent: switch on Track all apps on the account's Config tab and apps that start advertising later are added on their own.
Troubleshooting
- “Unity rejected these credentials”: the service account is missing Advertise Stats API Viewer at organisation level, or the Key ID and Secret key do not belong to it. Grant the role and connect again.
- “We couldn't find that Unity organization”: copy the Organization ID from the dashboard URL again.
- You rotated the key in Unity: the old key stops working here. Open the connection and click Reconnect to paste the new Key ID and Secret key.