DestinationCDPs & data

mParticle

mParticle's Events API takes batches PER PERSON — identities (email, customer id) live at the top of the batch, not on the event. The platform groups automatically: events from different people never share a request.

Connect now Read the docs

Data delivered

Custom events with full attributes
user_identities (email and customer id) per batch
Configurable pod (us1, us2, eu1…)

What it is for

What you can do with it

Feed audiences and connections that already exist in your mParticle

Why integrate

The business reason, not just the tech

One batch per person — as the API demands

mParticle's Events API binds identity to the BATCH, not the event. Mixing people would attribute everything to the first one. Automatic identity grouping eliminates that class of error.

Feed what already exists

Audiences, connections and rules you already built in mParticle start receiving resolved events — no new SDK.

How to connect

Step by step

Step 1
Copy the api key and api secret from your input feed.
Step 2
Create the destination (pod optional).
Step 3
Create a Delivery with the events.

Frequently asked questions

Why does "grouped per person" matter?

Because in mParticle's API identity applies to the whole batch. Mixing people would attribute every event to the first one — the platform splits requests so that never happens.