Get Started

OverviewCreate a sourceCreate a modelCreate a destinationCreate a sync


Table of Contents
MParticle is a customer data platform for brands to accelerate growth. With MParticle, brands can unify data and simplify partner integrations with enterprise-class security and reliability. It improves marketing, advertising, and analytics by connecting data seamlessly across channels.


This integration allows you to sync data between your sources and mParticle.

Initial Setup

To find the setup keys, navigate to Inputs, then Add Feed Input and select Custom Feed.Copy the Server to Server Key into the API Key field, and Server to Server Secret into the API Secret field.

Syncing mParticle Objects

Sync Modes

This integration only supports the Upsert mode.In this mode, new users will be inserted into mParticle and all user attributes will be kept up-to-date within mParticle.

Record Matching

Records can be matched from your source to your mParticle workspace by the mParticle customer ID or email.

Field Mapping

You can sync columns from your source to mParticle's default and custom fields.

Delete Mode

Delete mode allows you to decide what to do when a record is no longer in the query results. For mParticle, Hightouch allows you to either do nothing or clear the mapped attribute fields.

Syncing mParticle Events

Track Event Configuration

Depending on the event type, Hightouch will allow you to map your columns to different fields in mParticle. For the most common event type custom_event , Hightouch requires setting a static event name and custom event type.If you would like to set these dynamically based on column, you can statically set a random event name and custom event type and map columns to those fields in the next section.Hightouch also expects a timestamp of standard ISO 8601 format. Hightouch will automatically convert this to the unix time that mParticle expects.

Field Mappings

Hightouch allows you to pass data to the default properties and the custom event properties of an mParticle event. The properties you can map to are based on the event type that you selected. Keep in mind that for some fields, such as product_action of the commerce_event, a JSON object is expected.