Mobile Considerations

The Engine API allows you to update, test, and personalize any part of your iPhone or Android app without waiting for app store approvals. Use the same targeting data available for web and mobile Web to conduct in-app testing and to send push notifications to re-engage your customers.

Regardless of the channel, the Monetate platform UI is the same. You can easily create new experiences across channels and include specific targeting, scheduling, and context.

Integration Options

Depending on how your mobile app is built, you can rely solely on Monetate for event-reporting, or you can report events through an integrated partner, such as mParticle.

Monetate offers two options for integrating with your mobile app:

  • mParticle
  • Direct Engine API integration


The mParticle tool collects end-user interactions, such as product views, purchases, add-to-cart actions, and more. You can integrate Monetate and the mParticle SDK in the programming language of your choice.

Monetate clients that have also integrated mParticle into their mobile apps can connect and send that data to Monetate in near real time. This data is then available for targeting in experiences just as it would be if it came in from the Web.

You must request an API key for mParticle to complete this integration. Submit a support ticket using the Kibo Technical Support portal ( to obtain one.

Monetate can connect to mParticle and subscribe to the event stream from your app to receive all events triggered by your customers who use your application. In this situation you don't need to add events to your Engine API calls. As long as you can send the same customer ID or device ID to both systems, Monetate can join the data together.

Illustration of the two main functions of the Engine API

See mParticle's documentation site at for more information about the mParticle/Monetate integration.

Direct Engine API Integration

You can leverage the Engine API as a direct entry point into Monetate's decision engine. It looks up customer data, including historical behavior, across channels in real time. The Engine returns decisions and actions when you send a request from the API that includes events and all experiences configured for a particular channel.

See Server-Side Integrations for more information on integrating directly with the Engine API.