Integrating Moloco Ads on Clarisights
Moloco is a programmatic user-acquisition and re-engagement DSP. Connecting Moloco to Clarisights lets you blend Moloco performance with the rest of your paid stack and analyze spend, installs, and creative-level performance side-by-side with your other channels.
At a glance
| Authentication | Moloco DSP API token (API key) or workplace email + password |
| Permissions needed | Read access on the Moloco Cloud DSP API (ad-accounts and reports endpoints) |
| Account discovery | Automatic — every ad account linked to the API key is offered on connect |
| Data freshness | Daily (data for the previous day is available the next day; ingestion time is configurable) |
| Lookback window | 30 days on the standard refresh DAG; older history available on request |
| Backfill on connect | Last 30 days; longer backfills can be requested via Moloco support |
| Timezone | Per-account, taken from Moloco (e.g. America/Los_Angeles) |
| Currency | Per-account, taken from Moloco; converted to your reporting currency by Clarisights |
| Levels supported | Account · Campaign · Ad (no native Ad Group) |
| Limited rollout | No |
Prerequisites
An active Moloco DSP advertiser account.
An API key (preferred) issued from the Moloco Cloud DSP, or workplace credentials (workplace ID, email, password) with API access.
Read access on the
/cm/v1/ad-accountsand/cm/v1/reportsendpoints. Ask your Moloco account manager if you're not sure whether your token has these scopes.
Steps to Connect
Step 1 — Generate an API key in Moloco
In your Moloco Cloud DSP workspace, go to Settings → API access and create an API key. Copy the full key value — you'll paste it into Clarisights in Step 3.
If your workspace doesn't expose self-service API keys, ask your Moloco Account Manager to issue one for the workspace you want to connect.
[TODO: Screenshot of Moloco Settings → API access page]
Treat your API key like a password. It grants read access to every ad account in the workspace it was issued for.
Step 2 — Add Moloco in Clarisights
In Clarisights, go to Integrations → Moloco → Add Account.
[TODO: Screenshot of Integrations page Moloco row]
Step 3 — Enter credentials
Provide a friendly Username (your email or any label) and paste your API Key. Click Connect Source.
Clarisights authenticates with Moloco's /auth/tokens endpoint and retrieves every ad account linked to the key.
⚠ "Failed to authenticate with Moloco" / 401 error → The API key is invalid, revoked, or rotated. Re-issue a key from Moloco and retry. If you're using email + password, double-check the workplace ID is set correctly.
Step 4 — Select accounts
Pick the ad accounts you want to connect, optionally rename them, and click Create Accounts. Each account's native timezone and currency are pre-filled from Moloco and shown in the table.
Verify the connection
Go to Integrations → Moloco. Each connected ad account should show a "Connected" status.
First data appears within ~24 hours. The Moloco Reports API returns next-day numbers, and Clarisights pulls them on the daily refresh schedule.
Quick start: create a new report, add Moloco as the data source, and add Account · Campaign · Impressions · Clicks · Spend.
Data available
Hierarchy
How Moloco's native levels map to the standard Clarisights levels:
Native level (Moloco) | Clarisights level |
Ad Account (+ App) | Account (Clarisights uses |
Campaign | Campaign |
Ad Group | Not modelled in Clarisights. Moloco ad groups typically represent placements and the volume per campaign is too high to import; ad-group fields are ignored on ingest. |
Creative | Ad |
Dimensions
Dimension | Level | Description |
Account / Account ID | Account | Moloco ad-account name and ID (combined with App ID for uniqueness) |
Ad Account ID | Account | Raw Moloco ad-account ID |
App ID / App Title | Account | The promoted app's Moloco ID and display name |
App OS | Account | Operating system of the promoted app (iOS / Android) |
App Store ID | Account | App Store / Play Store identifier |
Currency | Account | Account reporting currency from Moloco |
Campaign / Campaign ID | Campaign | Campaign name and ID |
Campaign Country | Campaign | Campaign target country |
Ad / Ad ID | Ad | Creative name and Moloco creative ID |
Asset | Ad | Alias of the Ad name, kept for cross-channel asset reporting |
Asset Type | Ad | Creative type (image, video, native, etc.) |
Asset Preview | Ad | URL to the creative preview rendered as an image in Clarisights |
Metrics
Metric | Description |
Impressions | Total impressions |
Clicks | Total clicks |
Spend | Total spend in account currency |
Installs | App installs attributed by Moloco |
Revenue | Attributed revenue in account currency |
Limitations & known constraints
No Ad Group level: Moloco's ad-group concept is typically a placement and per-campaign volume is very high. Clarisights ingests data at Account, Campaign, and Creative (Ad) levels only.
App-scoped accounts: a single Moloco ad account that promotes multiple apps appears as one Clarisights account per app (
AdAccount_ID:App_ID). Roll-ups across apps are done via Clarisights groupings.Date-range rate limits: Moloco's reports endpoint enforces stricter quotas for longer date ranges (30/day for 0-1d, 10/day for 2-7d, 5/day for 8-31d). Clarisights handles this automatically by splitting failed ranges into smaller chunks, but very large historical backfills will be paced over multiple runs.
Async report generation: Moloco generates each report asynchronously. A single split is polled with exponential backoff for up to ~45 minutes before failing.
No segment breakdowns: Moloco does not expose breakdowns by geography, demographic, device, or audience via the Reports API used here.
Operating notes
Refresh schedule: daily, with a configurable run time. Tell us when you'd like the daily pull to fire.
Lookback: 30 days on each refresh, with rate-limit-aware date splitting (30d → 7d → 1d) when Moloco returns 429.
Multi-account: a single API key can connect every ad account in a Moloco workspace. Use separate keys to onboard workspaces managed by different Moloco AMs.
Currency conversion: each ad account's local currency is preserved on ingest and converted to your reporting currency by Clarisights.
Historical backfill: if you need data older than 30 days, ask your Moloco AM to make it available on the same report endpoint, then let your CSM know — we'll re-run the pull for the requested range.
Credential rotation: update the API key any time from Integrations → Moloco → Edit API Key.
Need help?
When contacting support from the in-app messenger, please include:
The integration name and account ID (Integrations → Moloco)
The exact error message or screenshot
The step where the issue occurred
When the issue started