Skip to main content

InMobi DSP

Extract pulls daily advertiser cost reports from the InMobi DSP Cost API.

Setup

Request a Client ID and Client Secret for the Cost API from your InMobi account manager and enter them when connecting the source. Login validates the credentials by requesting an access token, matching Singular’s InMobi integration. It does not create or wait for reports. Reporting permissions are checked when the selected reports run.

Streams follow the configured connection concurrency. Run logs show report requests, polling, downloads, and processed row counts. Expired or rejected tokens are refreshed once on HTTP 401; concurrent streams share that refresh.

Backfill (Days) defaults to 7 and accepts 1–89. Extract refreshes recent date partitions through yesterday; requests older than the supported 89-day history are clipped and logged. Reports that are not yet available fail for retry without advancing the cursor.

Reports and permissions

  • campaign_report requests account, advertiser app, campaign, country, OS, exchange, channel, and event dimensions, without creative or publisher fields.
  • creative_report adds ad ID, ad name, publisher app bundle, and publisher app name. Select this only when your credentials have creative and publisher reporting access.

Both reports include impressions, clicks, installs, events, and media cost. They describe the same activity at different granularities; do not sum their totals together. Vendor OS values and event names are preserved. Rows without creative IDs are retained, including SKAN rows for which the vendor does not provide creative attribution.

Use SKAN Endpoint

This connection option defaults to off and applies to both report levels:

  • Off: fetch all operating systems from programmatic.
  • On: fetch Android from programmatic and iOS from skan, writing both into each selected report. The programmatic OS filter prevents overlapping iOS cost.

report_endpoint identifies each row's origin. SKAN rows include skan_installs, skan_events, and probabilistic_events; installs is the vendor's probabilistic install metric. The non-SKAN events and channel columns are empty for SKAN rows. These metrics are kept separate rather than combined or renamed.

When changing this option, re-run the historical date range you want to replace (within retention). Dates outside the refreshed range retain their previous reporting mode. Each successfully refreshed date partition replaces the previous rows from both endpoints.

API reference

InMobi Cost API documentation

campaign_report

Loading ....

creative_report

Loading ....

Report requests cover at most seven days each. Up to four batches per stream are created and polled concurrently. Each stream extraction has a four-hour total limit, including waiting, downloads, and processing. Its cursor advances only after every batch succeeds.