Skip to main content

Supported syncing

For more information about sync modes, refer to the sync modes docs.

Connect to InMobi

This integration requires prior approval from the InMobi team and the Hightouch team before proceeding. To gain approval, please and connect us directly with your InMobi rep who will verify approval. Once we have confirmed, we will unlock the integration for you to connect. To connect, input the following provided by your InMobi rep:
  • Access key
  • Secret key
  • Bucket name

Syncing custom audiences

Hightouch will upload a file to the specified bucket with a naming pattern agreed upon by Hightouch and InMobi for your use case.

User identifiers

To identify which users to add or update in an audience, select model columns and the corresponding InMobi fields. You can match on any of the following user fields:
  • MAID (preferred)
  • Email
  • IP Address
  • Ramp ID
  • ID5
Increase match rates in InMobi by enabling Match Booster.

Handling PII and hashing

InMobi expects email values to be hashed. For audience syncs, by default, Hightouch automatically hashes first-party user data fields before sending requests to Reddit. If the data in your model is already hashed, you can disable PII hashing to successfully send data to Reddit.

Delete behavior

The only supported sync mode is all mode, meaning that each sync run will refresh the entire audience. Users removed from your audience will automatically be dropped with each refresh - only present users will be in InMobi’s audience.

Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .

Live debugger

Live debugger view is not support for this integration. Please if you see any issues.
Last modified on September 23, 2026