Integrations and Activation
This domain tests how data and audiences leave mParticle: connection design, filtering, transformation, and activation to partners.
Connection anatomy
A connection maps an input (an SDK platform, feed, API source, or audience) to an output (an integration). Settings include which events are eligible, data filters, custom mapping or transformation, and forwarding rules. Integrations include analytics and marketing destinations, warehouses, cloud storage, and audience destinations.
Rules
- An event must pass the data plan and the connection filter before it is forwarded.
- Transformations map mParticle event names and attributes to the partner schema; use them instead of renaming events at the source.
- Audience connections send membership changes (add and remove) rather than a full list each time; confirm whether the partner needs a backfill.
- PII controls belong on the connection, not only in application code.
- Verify behavior in the live event stream before enabling the connection.
Worked example
A team wants purchase value in an ad platform. They create a connection from the iOS input to the ad integration, filter to Purchase only, transform the value attribute into the partner's required field, and map the event name. Enabling first and filtering later would have exposed the full event stream.
Traps
- Enabling a connection before filters, exposing unwanted data.
- Duplicate connections forwarding the same event twice.
- Assuming audience sync is instantaneous to every partner.
- Transforming attributes the data plan does not define, which produces empty fields.