InMobi

Sync audience segments to InMobi DSP for mobile advertising, retargeting, and prospecting campaigns. Upload your warehouse segments to InMobi’s audience platform using device identifiers (IDFA, GAID).

Prerequisites

An InMobi advertiser account with API access enabled
An API key (Secret Key) generated from your InMobi account settings
Your InMobi Account ID
Your Property ID (Advertiser ID)

Permissions

Your InMobi account must have:

API access enabled (contact your InMobi account manager if not available)
Permission to create and manage audience segments
Access to the advertiser property you want to sync segments to

Authentication

InMobi uses API key-based authentication with session tokens.

In InMobi, go to My Account > Account Settings
Navigate to the API Key tab
Click Generate API Key to create your secret key
Copy the API Key and your Account ID
Enter both values in Zeotap

Zeotap automatically generates and refreshes session tokens using your API key. Sessions are valid for 24 hours and are refreshed proactively.

Configuration

Field	Type	Required	Description
Property ID (Advertiser ID)	Text	Yes	Your InMobi advertiser property ID. Found in My Account > Account Settings. Example: `1234567890`

Target Settings

Field	Type	Required	Description
Segment Name	Text	Yes	Name of the InMobi audience segment. Must be uppercase with no spaces or special characters. Example: `MY_CDP_AUDIENCE`
Segment ID	Text	No	Existing segment ID to update. Leave blank to create a new segment automatically.
Membership TTL (Days)	Text	No	Number of days a user remains in the segment. Default: `30`

Supported Operations

Sync Modes

This destination is audience-only and does not support standard data sync modes.

Audience Sync Modes

Mode	Supported
Add	Yes
Remove	Yes
Mirror	Yes
Upsert	—

Features

Field Mapping: No
Schema Introspection: No

Required Mapping Fields

InMobi requires mobile device identifiers for audience matching. Your data must include at least one of:

Field	Description
`idfa`	Apple Identifier for Advertisers (iOS devices)
`gaid`	Google Advertising ID (Android devices)
`device_id`	Generic mobile advertising identifier

How It Works

Session Generation: Zeotap authenticates with InMobi using your API key and account ID to generate a session token (valid 24 hours)
Segment Creation: If no segment ID is provided, Zeotap creates a new audience segment using the InMobi segment API
Batch Upload: Device identifiers are compiled into a gzip-compressed CSV file and uploaded via the InMobi batch ingestion endpoint
Processing: InMobi processes uploaded data asynchronously. It may take up to 24 hours for audience data to reflect in the DSP

Batch Details

Upload format: Gzip-compressed CSV (.csv.gz)
Max file size: 10 MB per upload
Chunk size: Up to 100,000 device IDs per request
Identifier types: IDFA (iOS), GAID (Android)

Rate Limits

InMobi enforces the following limits:

Session tokens expire after 24 hours from generation
Batch upload files must not exceed 10 MB (compressed)
Contact your InMobi account manager for specific API rate limit details for your account tier

Best Practices

Use uppercase segment names without spaces or special characters (e.g., HIGH_VALUE_USERS instead of High Value Users)
Set appropriate TTL values based on your campaign lifecycle. Shorter TTLs ensure fresher audiences
Map both IDFA and GAID fields when available to maximize audience match rates across iOS and Android
Monitor processing status in the InMobi DSP console. Uploads may take up to 24 hours to process
Use Mirror mode for ongoing syncs to keep your InMobi audience in sync with warehouse segments, automatically adding new members and removing departed ones
Reuse the Segment ID after the first run — the InMobi segment API has no name-based lookup, so leaving Segment ID blank on subsequent runs creates a new segment each time. After the first successful sync, copy the returned segment ID into the target settings to keep reusing the same segment

Troubleshooting

Authentication failed: invalid API key or account ID

Verify your API key and account ID in the InMobi portal under My Account > Account Settings > API Key. Regenerate the API key if needed. Ensure your account has API access enabled.

Segment creation failed

Segment names must be uppercase with no spaces or special characters. Check that your Property ID is correct and that your account has permission to create segments.

Upload returned HTTP 400 or 413

The upload file may exceed the 10 MB size limit. Reduce the batch size or ensure device IDs are not duplicated. Verify that the segment ID and property ID are valid.

No device IDs found in batch

InMobi requires mobile device identifiers (IDFA or GAID). Ensure your source data includes columns named idfa, gaid, or device_id with valid advertising identifiers.

Audience data not appearing in DSP

InMobi processes audience uploads asynchronously. Allow up to 24 hours for data to appear. Check the upload job status in the InMobi DSP console.

Duplicate segments created on each sync

If you leave Segment ID blank, Zeotap creates a new InMobi segment on every sync run because InMobi does not expose a lookup-by-name endpoint. After the first successful run, check the InMobi DSP console for the created segment ID and paste it into the Segment ID target setting so subsequent runs update the same segment.

Session expired errors

Sessions are valid for 24 hours. Zeotap automatically refreshes sessions, but if you see session errors, verify that your API key has not been rotated in the InMobi portal.