Skip to main content

mParticle Integration

Bluedot is a location platform that provides an accurate and simple geofencing platform for apps. After integrating the Bluedot SDK and setting geofences, customer’s can create personalised location-based experiences for their users.

mParticle is a customer data platform that unifies customer data in one place and connects it to 175+ leading marketing, analytics, and data warehousing solutions.

Through this integration, Bluedot’s first-party, accurate, and privacy compliant location data can be connected and utilised across all of the platform and apps supported by mParticle.  

Associated Documentation

Integration Overview

Before you begin the integration, ensure you have an active customer account with Bluedot & mParticle. Decide on the custom data you'll be passing from Bluedot Events to mParticle:

Events type

The mParticle integration will also support the following events:

  • Geo-trigger: Entry and/or exit into a Zone/Geofence
  • Tempo: ETA calculations as a user moves towards a Zone
  • Wave: API events when a user notifies of their arrival
  • Hello Orders: Events when the state of an order has been updated in Hello Screens

To use the Geo-trigger and Tempo events, you'll need to integrate the Bluedot SDK within your mobile app:

For Wave and Hello Orders, please refer to the following:

Add a Bluedot integration to your mParticle account, as mentioned in mParticle's documentation.

Add your mParticle iOS, Android and/or Web publishable API keys and secrets to the Project via the Integrations section in Canvas.


You have the option to send data to mParticle as either development or production data. When set to development, all data is treated as such and remains separate from your production data. If set to production, the data is forwarded to all configured integrations for your application. We recommend using the development setting for testing purposes. This allows you to view Bluedot events in the Live Stream view.

Custom Attributes / Sending events to mParticle

Custom attributes can be passed along to mParticle as key/ value pairs in Bluedot’s Custom Event Metadata.
An example will be:

mparticle_customer_id : "<your mparticle customer id>",
another_custom_field : "another value",

At least one of user_dentities listed in mParticle’s documentation with the mparticle_ fields must be included in the Custom Event Metadata in order to push events to mParticle.


The custom event metadata is not persisted across SDK sessions. If the SDK is logged out the custom event metadata is cleared by the SDK. We suggest setting the custom data every time the SDK is authenticated in the app.

More information on best practices of setting and using custom event metadata can be found here.

If you have any technical issues or questions you please use to reach out to our Support team.