Integrations / Customer Data Platform
mParticle
Server-to-server event delivery to the mParticle Customer Data Platform via the Events API (POST /v2/events). Sends page views, custom events, and commerce events with user_identities (customer_id, email, anonymous_id) so mParticle IDSync can resolve profiles and forward to downstream outputs.
Datafly Signal delivers first-party events to mParticle server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload mParticle expects.
Why route mParticle through Datafly Signal
Profiles update from the server, not the browser
Events reach mParticle even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what mParticle needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the mParticle rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
mParticle is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartadd_to_wishlistbegin_checkoutloginpagepurchaserefundremove_from_cartsearchsign_upview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the mParticle documentation.
Frequently asked questions
Does Datafly Signal integrate with mParticle?
Yes. Datafly Signal delivers first-party events to mParticle server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload mParticle expects. The integration is included in every deployment at no additional cost.
How is server-side mParticle tracking different from the mParticle tag?
The mParticle tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to mParticle from your server, so delivery does not depend on browser conditions.
Which events can Signal send to mParticle?
The blueprint ships with mappings for add_to_cart, add_to_wishlist, begin_checkout, login, page, purchase, refund, remove_from_cart, and more. Any event in your schema can be mapped to mParticle through pipeline configuration without a code change.
Do I need to keep the mParticle tag on my site?
No. Signal delivers to mParticle from the server, so no client-side mParticle script is required on your site.
Other customer data platform integrations
Ready to move mParticle server-side?
See how Datafly Signal delivers first-party events to mParticle from infrastructure you control, with hashed identity and consent enforcement built in.