Before you start this activity, you should have already created an audience.
In mParticle, an audience is a set of users who match a given set of criteria. When mParticle prepares to forward an audience, it is broken down into a series of messages about audience membership. Each message contains:
mParticle then translates these messages into a format that can be read by each audience output partner, and forwards them via HTTP API. Each output deals with audience information a little differently, depending on their data structure, but there are two main patterns.
Some audience output partners allow mParticle to either to directly create an audience (some call them ‘lists’, or ‘segments’) via their API, or at least to manage the membership of an existing audience. The end result will be an ‘audience’ in the partner system, containing as many identities from the original mParticle audience as the output can accept. mParticle will continue to update the membership of the audience in the partner system as users are added and removed. Email marketing and social media platforms are usually in this category.
Not all audience output services have a concept of ‘audiences’ that mParticle can map to. Others don’t allow their audiences to be directly managed via API. In these cases, mParticle usually forwards audiences as some kind of user attribute or tag. Push messaging and other mobile-oriented services often fall into this category.
As an example, Braze, has it’s own audience feature, called ‘Segments’, but it does not allow mParticle to create segments via API. Instead, for each Braze-supported identity in the audience, mParticle sets a tag on the user, named after the audience. You can then easily find matching users in Braze by searching for that tag.
The catch here is that it is often necessary for the output service to already have a record of the users you want to target. For this reason, this type of audience integration usually works best when paired with a matching event integration.
Just like event outputs, each audience output will follow a similar setup process, with the exact prerequisites and settings being different for each. This tutorial forwards an audience to Mailchimp as an example. You can follow the same steps with a different output, or create a free Mailchimp account to follow along exactly.
mParticle sends audiences to Mailchimp via its List API. For this to work, You need to have already created a list in my Mailchimp account, and you need to know the List ID. You can give your Mailchimp list the same name as the mParticle audience you want to forward.
You’ll also need to create a Mailchimp API Key, which you can do from the Extras tab of your Mailchimp Account Settings.
The simplest way to check that your Connection is working is to see if your Mailchimp list is showing subscribers. For most audience outputs, mParticle begins forwarding data immediately and continues to update audiences in near real time. For some outputs, however, the design of the output partner’s API requires that we queue audiences messages and upload at a regular interval. In these cases, we make a note of the upload criteria in the docs for that output.
mParticle forwards to Mailchimp in realtime, and you should be start to see results in the mailchimp dashboard within ten minutes.
Open the Lists tab in your Mailchimp dashboard. Find the list you used to set up the connection. If you see a positive subscriber count, your connection is working.
Many audience outputs are services which allow you to send mass communications or target advertising to wide audiences, so access to the features that mParticle forwards audiences to is often tightly controlled. To be able to view and manage audiences in the output service, you may need to do one or more of the following:
A common question around forwarding audiences is why the size of the audience (or list, or segment) you see in the partner’s dashboard doesn’t match the size of the audience shown in mParticle. This is common, and usually does not mean anything is wrong. When you create an audience in mParticle, we will include as many identities as we have for each user in the audience. However, most outputs only support a small subset of identity types. Here’s a simple example:
If you’ve followed all of our Getting Started tutorials, you have now:
The final section covers some of the more advanced mParticle features you can use to transform and refine your data.
Was this page helpful?