Integration

Zembula + mParticle

mParticle keeps the audience memberships of each person on a user profile. Zembula can read that profile by mParticle ID when the email opens.

It's our business to grow yours

Book a demo

What Zembula can read from mParticle

mParticle is a customer data platform. It collects events, resolves user profiles and forwards data and audiences to other tools. Its Profile API returns one person’s profile on request. The profile holds user identities, device identities, user attributes, audience memberships, attribution and partner identities.

Zembula can read these fields and use them in an image. You look a person up by mParticle ID. You can also use an immutable identity such as a Customer ID, which the resolve endpoint turns into the mParticle ID. The Profile API needs API credentials that you create in the mParticle interface, with the Profile API enabled for each workspace.

The default rate is 15 requests per second, which mParticle sets for testing, and a higher rate is a premium feature. A profile that nobody accessed or updated for 90 days expires by default, and the API no longer returns it. mParticle also forwards events and audiences to data warehouse, analytics and marketing automation tools.

DataDetailLooked up by
User attributesAttributes of one person on the mParticle user profile.mParticle ID, or an immutable identity such as Customer ID
Audience membershipsWhich audiences one person belongs to.mParticle ID
User identitiesThe identities that mParticle holds for one person.mParticle ID, or an immutable identity such as Customer ID
Device identitiesThe device identities that mParticle holds for one person.mParticle ID, or an immutable identity such as Customer ID
AttributionAttribution data on the profile of one person.mParticle ID, or an immutable identity such as Customer ID

How the data arrives

  • API: Zembula calls the Profile API with your API credentials and reads one person’s profile by mParticle ID.
  • ESP merge tags: mParticle forwards audiences to marketing automation tools. Your email service provider sends the lookup value in the image URL as a merge tag.

What you need

  • API credentials from the mParticle interface, with the Profile API enabled for each workspace.
  • An API key or a data export from mParticle. Zembula sets up the connection for you.
  • The person’s mParticle ID or Customer ID, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
Profile API: 15 requests per second by default. Higher rates are a premium feature.A burst of opens above 15 a second may fail.
Profiles that nobody accessed or updated for 90 days expire and are not returned, by default.Long-idle people return no profile data.

Ideas for email

  • Pick the email offer image from a person’s audience memberships.
  • Fill an image with a user attribute such as the last category viewed.
  • Hide a promotion image from people whose attributes show a recent purchase.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.