InMobi Integration
Beta
The InMobi integration is still being verified with live advertiser accounts. If the numbers in adstage differ from the InMobi console, please let the adstage support team know.
In adstage, you can automatically collect spend, impressions, clicks, and installs per InMobi campaign and review them in reports. This is a key-based integration rather than a sign-in flow: you paste the key issued by InMobi. The integration consists of a single Cost Integration tab under Integrations > Ad Channel Integration > InMobi, and the collected cost is reported under the inmobi.ads channel.
1. Integration Overview
| Feature | Supported | Description |
|---|---|---|
| Cost collection | Yes | Spend, impressions, clicks, and installs per campaign, collected automatically every 4 hours |
| Click attribution | After partnership | InMobi has its representatives set up tracking links from its list of designated measurement partners (MMPs). Click macros that an advertiser could add to a landing URL are not published |
| Conversion sending | After partnership | Sending conversions measured by adstage back to InMobi. InMobi does not publish a postback specification for measurement tools, so this is not offered |
Click attribution and conversion sending open up once adstage partners with InMobi. We have asked InMobi whether a custom tracker is allowed and are waiting for a reply; this page will be updated as soon as we hear back. See the Tracking Links and Conversion Sending section below for details.
2. Choosing the API Type
InMobi uses different APIs for self-serve advertisers and for campaigns run by its own team. When you add an account, pick one under API Type and only the matching fields are shown.
| API type | Choose this when | Values needed | Where it comes from |
|---|---|---|---|
InMobi Portal (Self-serve) | You sign in to the InMobi advertiser portal and run campaigns yourself | Login Email, API Key | Issued by you in the advertiser portal |
InMobi DSP (Managed by InMobi) | An InMobi account manager runs the campaigns for you | Client ID, Client Key (Secret) | Issued by your InMobi account manager |
If you are not sure which one applies, you are on InMobi Portal (Self-serve) whenever you create campaigns by signing in to the InMobi advertiser portal yourself.
3. Getting Your Key
InMobi Portal (Self-serve)
-
Sign in to the InMobi advertiser portal. You can also open it with the
Open InMobi key pagebutton in adstage. -
Generate and copy the API key in the Account Settings section.
-
The email address you use to sign in to the portal is your Login Email.
The same steps are shown in the How to get your InMobi key panel in the adstage dashboard.
InMobi DSP (Managed by InMobi)
Ask your InMobi account manager to issue a Cost API Client ID and Client Key (Secret). An advertiser cannot issue these keys directly. They are different from the self-serve portal key, so mixing the two will be rejected during integration.
4. Connecting Your Account
-
In Integrations > Ad Channel Integration, select InMobi and open the
Cost Integrationtab. -
Turn on the InMobi Cost Integration switch. While it is off, the
Add Integration Accountbutton cannot be clicked. -
Click
Add Integration Accountto open the InMobi Cost Integration dialog. -
Enter an Account Label to identify this account in adstage, choose the API Type, and fill in the fields shown below it. Secret values (API Key, Client Key) are masked as you type, and leading and trailing spaces are removed automatically.
-
Click
Integrate. Before saving, adstage requests a session (or a token) from InMobi once to confirm the key is valid — the button showsVerifying.... Once confirmed, the key is stored encrypted and the first collection of the last 30 days starts immediately.
Right after connecting, the account status shows Preparing and changes to Success when the first collection finishes. InMobi reports are generated asynchronously, so the first sync may take a few minutes.
| Error message during integration | Cause | What to do |
|---|---|---|
| This account is already registered | The same key is already registered in this organization | Keep using the existing account |
| The key was rejected by InMobi. Please check the key and its permissions. | The key or email is wrong, or the key type does not match the API type | Re-check the API type and paste a freshly copied key |
| Could not reach InMobi to verify the key. Please try again later. | A temporary InMobi API outage or rate limiting | Try again shortly |
Connected accounts appear in the account list with Account Name, Status, Last Data Update, and Management (delete) columns. To change a key, delete the account with the trash icon in the Management column and add it again with the new key. There is no way to edit a stored key in the UI.
5. Collected Data
| Item | Description |
|---|---|
| Collection interval | Every 4 hours (01, 05, 09, 13, 17, 21 KST) |
| Update range | Last 30 days (D-30 to D-1, excluding the day of the update). Each run re-fetches this window and refreshes the values |
| Data level | Campaign level (day x campaign) |
| Metrics | Spend, impressions, clicks, installs |
| Currency | USD. The InMobi Advertiser Reporting API documentation states that spend is in US dollars. Values are converted to the organization base currency before being stored |
| Timezone | UTC |
| Channel name | inmobi.ads (shown as InMobi in the report channel filter) |
In reports, metric names carry (Channel) to indicate values reported by the ad network.
| Report metric | InMobi value |
|---|---|
| Ad Spend (Channel) | spend for Portal, media_cost (indicative billable amount) for DSP |
| Impressions (Channel) | impressions |
| Clicks (Channel) | clicks |
| Conversions (Channel) | downloads (app installs) for Portal, installs plus skan_installs for DSP |
| Conversion Value (Channel) | Not collected. Use purchase revenue measured by the adstage SDK |
Please note
- The previous day is finalized after 06:00 UTC (15:00 KST). A run before that collects only up to two days ago, and the previous day is filled in on the next run.
- InMobi only serves the last 90 days, so anything older than that cannot be retrieved.
InMobi DSP (Managed by InMobi)queries the Network, Programmatic, and SKAN reports and combines them. When the same day, campaign, and OS appears in more than one report, it is counted once, so there is no double counting.- The InMobi DSP Cost API documentation does not state its currency or timezone. adstage assumes USD and UTC, the same as Portal, so if your ad account is not billed in USD, confirm with your InMobi account manager and let the adstage support team know.
6. Tracking Links and Conversion Sending
InMobi has its own representatives configure campaign tracking links, and only from its list of designated measurement partners (MMPs). Neither the click macros an advertiser could add to a landing URL nor the postback specification a measurement tool would use to send conversions back is published.
As a result, adstage does not offer an InMobi tracking link template, and InMobi does not appear in the ad channel list under Deep Links > Create. There is also no InMobi preset in Network Postback, which is configured per link. Both features open up once adstage partners with InMobi and receives the specification.
Cost collection works without tracking links or conversion sending. We recommend leaving your existing MMP setup in place for InMobi install and conversion measurement, and using adstage alongside it for cost.
Clicks and conversions arriving through a custom link whose channel name is inmobi are reported under the same inmobi.ads channel as the cost. You can use this approach if your InMobi representative allows an adstage link.
7. Cautions
Please note the following.
- Numbers may differ between InMobi and adstage. InMobi reports are in UTC, and aggregation timing and currency conversion differ as well.
- If you regenerate the API key in the portal, or your representative rotates the Client Key, collection stops with the old key and the status changes to Failed. Delete the account and register it again with the new key.
- Turning off the InMobi Cost Integration switch stops collection for every InMobi account in this organization. Account details are kept, so collection resumes when you turn it back on.
- adstage only reads InMobi reports and never changes campaign settings.
8. Troubleshooting
The account cannot be added
- Check the API type: make sure a self-serve portal key was not entered under
InMobi DSP, or a manager-issued key underInMobi Portal - Check the email: in Portal mode, enter exactly the email address you use to sign in to the portal
- Check for a truncated paste: make sure the key was copied in full (leading and trailing spaces are removed automatically)
- Check the switch: the InMobi Cost Integration switch must be on for the
Add Integration Accountbutton to be enabled
The status is Failed
- Read the error: hover over the status badge to see the error
- Check whether the key was revoked: if the error says the key was rejected, the key was revoked or reissued, so delete the account and register the new key
- Rate limiting or temporary errors: these are retried automatically, so wait for the next update
No data is being collected
- Check that the integration is enabled: confirm the InMobi Cost Integration switch is on
- Check that ads are running: days where spend, impressions, clicks, and installs are all zero are not stored, so confirm that ads actually ran on InMobi
- Check the update cycle: the current day is never collected, so today's numbers appear tomorrow. The previous day arrives with the first run after 15:00 KST
- Check for a warning: if no cost data is stored for more than three days, a warning appears next to the status, and hovering over it shows how many days have passed without data
The numbers differ from the InMobi console
- Timezone: set the InMobi console to UTC and compare the same dates
- Currency: adstage values are converted to the organization base currency
- Aggregation timing: InMobi values can change retroactively and are picked up when the last 30 days are re-fetched
- Granularity: adstage stores campaign totals only, so do not compare them directly with InMobi views split by country or OS
Contact the adstage support team if you need further help.
9. FAQ
Is there an InMobi sign-in (OAuth) integration?
No. The InMobi reporting APIs are called with the issued key alone, so there is no sign-in or permission approval step.
Can I register both Portal and DSP?
Yes. Add one account per API type and both are collected. However, if the same campaign exists in both products, its cost may be added twice, so we recommend asking your representative which one is the actual billing basis and registering only that one.
Why does Conversions (Channel) differ from installs in adstage?
Conversions (Channel) are installs counted by InMobi, while adstage installs are measured by the adstage SDK and tracking links. While an adstage tracking link cannot be used with InMobi, installs from InMobi are not attributed to the inmobi.ads channel in adstage, so the two numbers will differ.
10. Reference Documents
- InMobi Advertiser Reporting API Guide — API key location in Account Settings, 24-hour session validity, 90-day window, UTC and USD basis, column definitions (the URL contains
/ja/but the page itself is in English) - Cost API Integration for InMobi DSP — how to request the Client ID and Key, 8-hour token validity, 90-day window, metric definitions for the Network, Programmatic, and SKAN reports

