Connecting InMobi on Clarisights

InMobi DSP is a global mobile programmatic advertising platform. Connecting InMobi to Clarisights lets you blend mobile DSP spend, impressions, clicks, and creative performance with your other paid channels and analyze it side-by-side with attribution and conversion data.

At a glance

Prerequisites

• An active InMobi DSP advertiser account

• A Client ID and Client Secret issued by InMobi — request these from your InMobi account manager

• Credentials must have read access to the /api/v3/reports/programmatic endpoint

Steps to Connect

Step 1 — Obtain your API credentials

Contact your InMobi account manager and request an API Client ID and Client Secret for your advertiser. You can also find these under Account Settings in the InMobi DSP portal once enabled. Copy both values — you will paste them into Clarisights in Step 3.

Treat your Client Secret like a password. It grants read access to all advertiser/app combinations linked to it.

Step 2 — Add InMobi in Clarisights

In Clarisights, go to Integrations → InMobi → Add Account.

[TODO: Screenshot needed — Integrations page InMobi row with Add Account button]

Step 3 — Enter credentials

Paste your Client ID and Client Secret into the form and click Validate. Clarisights authenticates with InMobi (POST /api/v3/auth/token), retrieves an access token, and discovers every advertiser/app combination linked to the credentials by scanning the last 90 days of reporting activity.

⚠ "Failed to retrieve token" on validate → Confirm the Client ID and Client Secret have not been rotated or revoked in the InMobi DSP portal. Re-issue credentials from your InMobi account manager and retry.

⚠ No accounts discovered → InMobi discovers accounts from the last 90 days of reporting data. If your advertiser had no activity in that window, no accounts will be returned. Run a small test campaign or contact support so we can extend the discovery window manually.

Step 4 — Select accounts

Pick the advertiser/app combinations you want to connect, optionally rename them, and click Create Accounts. Each row represents a unique InMobi Account ID / App Bundle pair — one account per advertiser per app.

Verify the connection

• Go to Integrations → InMobi. Each connected advertiser/app should show a "Connected" status.

• First data appears within ~24 hours.

• Quick start: create a new report, add InMobi as the data source, and add Advertiser · App · Campaign · Impressions · Clicks · Spend.

Data available

Hierarchy

How InMobi DSP's native levels map to the standard Clarisights levels:

Dimensions

Metrics

Limitations & known constraints

• No Ad Group level: InMobi DSP's API does not expose Ad Groups. Ad Group fields in Clarisights map to Campaign.

• No segment breakdowns: InMobi's /reports/programmatic endpoint, as configured here, does not return geography, device, OS, or audience-level breakdowns.

• Limited conversion metrics: The default schema fetches Impressions, Clicks, and Media Cost. Installs, Events, CTR, CR, IPM and other native InMobi measures are available from the API but are not exposed by default — contact support to add them.

• 7-day API request cap: InMobi's reporting API does not allow date ranges greater than 7 days per request. Clarisights splits longer ranges automatically, but very long backfills can take significantly longer to complete.

• Account discovery via reporting: Accounts are discovered by scanning the last 90 days of reporting data. An advertiser/app pair with no activity in that window will not appear in the account selector.

• UTC only: All accounts are stored in UTC. There is no per-account timezone override.

Operating notes

• Refresh schedule: daily.

• Lookback: 30 days (today_30d) on every run, so late-arriving conversions and corrections within the last 30 days are picked up automatically.

• Tokens: InMobi access tokens are short-lived. Clarisights auto-refreshes them before each pull using your stored Client ID and Client Secret — no manual rotation needed unless those credentials change.

• Multi-account: a single Client ID/Secret pair can connect every advertiser/app combination linked to it. Use separate credentials to onboard advertisers managed by different InMobi account managers.

• Currency conversion: account currency (USD by default) is preserved on ingest and converted to your reporting currency by Clarisights.

• Credential rotation: update the Client ID and Client Secret any time from Integrations → InMobi → Edit Credentials.

• Rate limits: requests are throttled to ~10 requests per 6 seconds per channel; reports are split into 1-day chunks by default to stay within InMobi's per-request limits.

Need help?

When contacting support from the in-app messenger, please include:

• The integration name and account ID (Integrations → InMobi)

• The exact error message or screenshot

• The step where the issue occurred

• When the issue started