Inclusive & Exclusive Audiences adds support for both inclusive and exclusive audience membership. In the current version of Audiences, all audiences are exclusive by default, meaning users can belong to only one audience within a group. The Early Access release adds the option to make audiences inclusive within a single logic block, allowing users to belong to multiple audiences at the same time if they meet the criteria for each.
\nThis update also introduces logic blocks, which give you the ability to control when audiences should be inclusive and when they should remain exclusive. The addition of logic blocks makes audiences more flexible and allows you to mirror real marketing and lifecycle strategies more closely within mParticle.
\nInclusive audiences let users be added to more than one audience within the same logic block. This approach is useful when you want to target overlapping behaviors or attributes, such as reaching users who have both viewed a product and made a purchase. By using inclusivity, you can combine multiple behavioral or contextual audiences without worrying about them canceling each other out.
\nInclusive audiences help you deliver more personalized messaging and run cross-channel or cross-offer campaigns efficiently. For example, if a user qualifies for both “High Intent” and “Email Engaged” audiences within the same logic block, they will appear in both. This ensures that they can receive communications tied to both engagement patterns.
\nLogic blocks are containers that control how audiences relate to one another inside an audience group. They do not change who qualifies for an audience. Instead, they control which audiences a user is added to when they qualify for more than one.
\nWithin a single logic block, audiences are inclusive. If a user qualifies for several audiences in the same block, the user is added to all of them. This is useful when you want overlapping audiences, such as multiple behavior-based segments that can all apply at once.
\nLogic blocks are exclusive relative to other logic blocks that share the same parent audience. If a user qualifies for audiences in more than one of these sibling blocks, they are only added to audiences from the highest priority block. Logic blocks under different parent audiences do not compete with each other, so a user can still belong to audiences in logic blocks under multiple parents.
\nYou can also nest logic blocks to apply this pattern at more than one level. For example, you might use top-level blocks to keep lifecycle stages exclusive, then use nested blocks inside each stage to manage overlapping offer or behavior audiences.
\nExclusivity applies across logic blocks that are children of the same parent audience.
\nA group of sibling logic blocks under one parent represents a mutually exclusive set of audiences. When a user qualifies for audiences in more than one of these blocks, they are added only to audiences in the highest priority block according to the block order you define.
\nThis setup helps you maintain clean audience boundaries. It is particularly useful for lifecycle, funnel, or testing workflows where users should only belong to one stage or group at a time. For example, if you have blocks for “New Users,” “Active Users,” and “Lapsed Users,” exclusivity ensures that no user appears in more than one at once.
\nLogic blocks provide more flexibility and better reflect how teams manage audiences in real-world scenarios. Many use cases require some audiences to overlap, such as when running multi-offer or cross-sell campaigns, while others require strict exclusivity, such as A/B testing or funnel progression.
\nBy introducing logic blocks and supporting both inclusive and exclusive audiences, mParticle allows you to control both types of behavior within the same framework. This approach simplifies configuration, reduces errors, and improves your ability to manage complex audiences at scale.
\nYes. The generally available version of Audiences continues to function as it always has. Only a limited set of customers have access to Inclusive & Exclusive Audiences. If an mParticle workspace does not include logic blocks, audiences remain exclusive by default.
\nIf you’re part of the Early Access program, your feedback helps shape the final release of Inclusive & Exclusive Audiences. To share comments, suggestions, or issues, contact your mParticle account representative or customer success manager. You can also submit feedback directly through your mParticle workspace if that option has been enabled for your account.
\nLogic blocks are created automatically when you add a second sibling audience using the Add path button. To create additional logic blocks and separate audiences, use the Move action on an audience and select Create New Logic Block.
\nFor detailed instructions, see Creating and Managing Logic Blocks.
\nYes. Logic block priority determines which block users are added to when they qualify for audiences in multiple sibling blocks. To change block priority, click the action menu on a logic block and select Edit Logic & Priority. You can then drag blocks to reorder them or use the arrow icon to increase a block’s priority.
\nFor detailed instructions, see Change a Logic Block’s Name and Priority.
\nIf a user qualifies for audiences in multiple sibling logic blocks under the same parent, they are added only to audiences in the highest priority block. Logic blocks are evaluated in priority order (highest to lowest, displayed left to right in the Audience Group Editor), and the user is added to the first block where they meet the criteria.
\nYes. Logic blocks are only exclusive relative to other sibling logic blocks under the same immediate parent. If logic blocks are under different parent audiences, they can share users.
\nFor example, if you have “Comedy: Basic Subscribers” under “Comedy Viewers” and “Drama: Basic Subscribers” under “Drama Viewers,” the same user can appear in both audiences because the logic blocks have different parents.
\nA remaining users logic block is a special block that automatically collects all users who do not meet the criteria for any other block. This ensures that all users in your dataset are accounted for, even if they do not currently qualify for any explicitly defined audiences.
\nTo create a remaining users logic block, click the path icon and select Add Remaining Users Split. The remaining users block always has the lowest priority and cannot be reprioritized.
\nYou cannot directly delete a logic block. However, if you move or delete all audiences within a logic block, the block is automatically deleted. Logic blocks only exist as containers for audiences—when they’re empty, they are removed.
\nNo. Connecting audiences to outputs works the same way regardless of logic blocks. You still:
\nLogic blocks only control which users are added to which audiences. Once an audience is populated, forwarding to outputs is unchanged.
\nFor more information, see Connect an Audience.
","frontmatter":{"title":"Inclusive & Exclusive Audiences FAQ","order":4,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/audiences/early-access/faq/"}},"staticQueryHashes":["2950460867"]}