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: The ironSource integration is currently admin-managed by Clarisights. There is no self-serve flow on the Integrations page — onboarding happens through Clarisights support.
At a glance
| Authentication | ironSource secret key + refresh token, exchanged for a bearer token |
| Permissions needed | An ironSource user with access to the Advertisers Reporting API on the title(s) you want to connect |
| Account discovery | Manual — titles are returned by the report; one ironSource user can connect every title it has access to |
| Data freshness | Daily (non-periodic ingestion 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 (Title) · Campaign · Ad (Creative) |
| Limited rollout | Yes — admin-managed integration. Contact Clarisights support to onboard. |
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 an admin-managed integration, the steps below describe what you need to provide to Clarisights support and what happens behind the scenes. There is no self-serve UI 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.
[TODO: Screenshot needed — ironSource API credentials screen]
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 by exchanging the credentials for a bearer token at
platform.ironsrc.com/partners/publisher/authand pulling a sample report
⚠ "Failed to authenticate IronSource (401 / 403)" → 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 ingestion run
Once the channel is configured, Clarisights schedules the first ingestion. 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 run has completed.
Open any report or dashboard, add ironSource as a data source, and pull Title, Campaign, Impressions, Clicks, Installs, and Spend for the last 7 days. Non-zero rows confirm the connection is healthy.
First data appears within ~24 hours of credentials being configured (ironSource ingestion runs daily).
Data available
Hierarchy
How ironSource's native levels map to the standard Clarisights levels:
Native level (ironSource) | Clarisights level |
Title (app) | Account |
Campaign | Campaign and Ad Group (ironSource has no native Ad Group; Ad Group fields alias to Campaign) |
Creative | Ad |
Dimensions
Dimension | Level | Description |
Title ID / Title | Account | The ironSource Title (app) ID and name |
Campaign / Campaign ID | Campaign | Campaign name and ID |
Ad / Ad ID | Ad | Creative name and ID |
Country | Ad | ISO country of the user |
Device OS | Ad | iOS or Android |
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
Admin-managed: 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. Ad Group fields in Clarisights alias to Campaign.
Fixed dimensions and metrics: the integration uses a single Advertisers Reporting API call broken down by day, campaign, creative, and title with metrics impressions, clicks, installs, completions, and spend. Custom breakdowns (e.g. ad unit, ad placement) are not exposed.
30-day lookback: backfill and ongoing ingestion are limited to the last 30 days.
USD-only spend: spend is ingested 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 credential pair per company: every Title accessible to the credential pair is ingested under the same channel. To split by Title, request multiple credential pairs from ironSource.
Operating notes
Refresh schedule: daily, managed centrally by Clarisights.
Lookback: 30 days.
Multi-account: a single ironSource credential pair pulls data for every Title it has access to. Each Title appears as a separate Account in Clarisights.
Currency handling: spend is ingested in USD and converted into your reporting currency by Clarisights' standard FX pipeline.
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 mints a fresh bearer token for every ingestion run from the secret key + refresh token; tokens are not stored long-term.
Need help?
When contacting support from the in-app messenger, please include:
That you are asking about ironSource (admin-managed integration)
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