Connecting ironSource on Clarisights
ironSource (now part of Unity, also known as LevelPlay and Aura) is a leading mobile advertising and user-acquisition platform. Connecting ironSource to Clarisights brings your campaign, creative, and title-level performance into your reports so you can analyse impressions, clicks, completions, installs, and spend alongside your other paid channels, and answer questions like "which creative is driving installs in my top markets?" or "how is ironSource performing on iOS vs Android per title?".
Note: ironSource is set up by Clarisights. It is not shown on the Integrations page; onboarding happens through Clarisights support.
At a glance
| Authentication | ironSource secret key + refresh token |
| Permissions needed | An ironSource user with access to the Advertisers Reporting API on the title(s) you want to connect |
| Account discovery | Manual: each credential pair is connected as one account that covers every Title the user has access to |
| Data freshness | Daily (managed by Clarisights) |
| Lookback window | 30 days |
| Backfill on connect | Last 30 days |
| Timezone | UTC (set by ironSource Advertisers Reporting API) |
| Currency | USD (ironSource reports spend in USD) |
| Levels supported | Account · Campaign · Ad (Creative) |
| Limited rollout | Yes. Not shown on the Integrations page; contact Clarisights support to enable it. |
Prerequisites
An active ironSource (Unity / LevelPlay / Aura) advertiser account with at least one Title
Access to the Advertisers Reporting API credentials in the ironSource platform, available from the API tab under your account settings
The two API credential values:
Secret key
Refresh token
The Title(s) and campaigns you want to report on already running in ironSource
Steps to Connect
Because ironSource is set up by Clarisights, the steps below describe what you need to provide to Clarisights support and what happens next. There is no self-serve flow on the Integrations page.
Step 1: Generate API credentials in ironSource
In the ironSource platform, open your account profile and navigate to the API section. Generate (or copy) the secret key and refresh token for the Advertisers Reporting API.
For where to find your secret key and refresh token, see ironSource's documentation: API authentication.
Treat the secret key and refresh token like passwords. Anyone with both values can pull reports for every Title that the user has access to.
Step 2: Share the credentials securely with Clarisights
Open a request from the in-app messenger or with your Customer Success contact and ask to enable the ironSource integration. Clarisights will share a secure channel for transmitting the secret key and refresh token.
Step 3: Clarisights configures the channel
The Clarisights team will:
Create the ironSource channel for your company
Store the secret key and refresh token encrypted
Validate the connection by signing in to ironSource with the credentials and pulling a sample report
⚠ Authentication failure during validation → The secret key or refresh token is invalid, expired, or has been rotated in ironSource. Re-generate the credentials in the ironSource API tab and resend them via the secure channel.
⚠ Empty report on validation → The user owning the credentials does not have access to the expected Title(s), or the Title has not yet served impressions in the last 30 days. Verify Title access in ironSource and confirm the campaigns are live.
Step 4: Wait for the first data import
Once the channel is configured, Clarisights schedules the first import. Backfill covers the last 30 days. You will be notified when data is available in your workspace.
Verify the connection
Confirm with Clarisights support that the ironSource channel has been created and the first import has completed.
Open any report or dashboard, add ironSource as a data source, and pull Campaign, Impressions, Clicks, Installs, and Spend for the last 7 days. Non-zero rows confirm the connection is healthy.
First data appears within about 24 hours of the credentials being configured (ironSource data is imported daily).
Data available
Hierarchy
How ironSource's native levels map to the standard Clarisights levels:
Native level (ironSource) | Clarisights level |
API credential pair (all Titles it can access) | Account |
Campaign | Campaign (ironSource has no Ad Group level) |
Creative | Ad |
Dimensions
Dimension | Level | Description |
Campaign / Campaign ID | Campaign | Campaign name and ID |
Ad / Ad ID | Ad | Creative name and ID |
Metrics
Metric | Description |
Impressions | Ad impressions served |
Clicks | Ad clicks |
Completions | Video / rewarded creative completions |
Installs | App installs attributed to the campaign |
Spend | Total spend in USD |
Limitations & known constraints
Set up by Clarisights: there is no self-serve onboarding from the Integrations page. All onboarding and credential changes go through Clarisights support.
No Ad Group level: ironSource does not expose Ad Groups, so data is available at Campaign and Creative level.
Fixed dimensions and metrics: data is broken down by day, campaign, creative, and title, with Impressions, Clicks, Installs, Completions, and Spend. Other breakdowns (for example country, device OS, ad unit, or placement) are not available.
30-day lookback: backfill and ongoing imports cover the last 30 days.
USD-only spend: spend is imported in USD. Conversion to your reporting currency happens inside Clarisights.
UTC timestamps: ironSource reports day-level data in UTC and Clarisights stores it as such. Compare against other channels with UTC in mind.
One account per credential pair: every Title accessible to the credential pair is imported into the same Clarisights account.
Operating notes
Refresh schedule: daily, managed by Clarisights.
Lookback: 30 days.
Multi-account: a single ironSource credential pair pulls data for every Title it has access to, into one Clarisights account.
Currency handling: spend is imported in USD and converted into your reporting currency by Clarisights.
Credential rotation: when the secret key or refresh token changes, send the new values to Clarisights support via the in-app messenger. Self-serve credential edits are not available for this integration.
Token handling: Clarisights signs in to ironSource with a fresh token for every import; tokens are not stored long-term.
Need help?
When contacting support from the in-app messenger, please include:
That you are asking about ironSource
The ironSource Title ID(s) and name(s) involved
Whether the issue is with onboarding, credential rotation, missing data, or unexpected metrics
The exact error message or screenshot, if any
The date range you expected data for, and what you are seeing instead
When the issue started