Rokt mParticle’s Inclusive/Exclusive Audiences allows you to create both overlapping and mutually exclusive audiences within the same audience group.
\nCurrently, Audiences are exclusive by default. This means that within an audience group, users are only added to one audience at a time, even if they qualify for more than one audience in the group.
\nHowever, with Inclusive/Exclusive Audiences, you can use logic blocks to combine overlapping audiences into inclusive groups. By separating audiences into different logic blocks, you can enforce exclusivity. This allows you to build more complex audience groups that more accurately reflect your users and their behaviors.
\nFor example, you might want users to belong to a single lifecycle audience such as New Customers, Active Customers, or Lapsed Customers, so your lifecycle messaging is based on one stage at a time. However, within each lifecycle stage, users might be added to multiple behavior based audiences such as High Value Purchasers or Sports Fans.
\nInclusive/Exclusive Audiences would allow you to keep your lifecycle audiences mutually exclusive while still allowing users in each stage to join multiple behavior based audiences.
\nLogic blocks are the foundation of Inclusive/Exclusive Audiences. They act as containers that determine how audiences relate to one another within an audience group. Logic blocks are tools you use when building audiences. They are not unique entities, like a user profile or an audience, that can be managed outside the audience group.
\nAll audiences within the same logic block are treated as inclusive. If a user qualifies for multiple audiences in the block, they are added to all of them.
\nFor example, if you place two audiences called High Intent Users and Recent Purchasers in the same logic block, a user who meets both sets of criteria will appear in both audiences.
\nIt’s important to note that logic blocks are only exclusive relative to other logic blocks that are children of the same immediate parent.
\nFor example, if two logic blocks sit under the same parent audience, a user can only be added to audiences in one of those blocks at a time, but logic blocks under different parent audiences can share users.
\nWhen more than one logic block shares the same parent audience, you use block priority to control which block “wins.”
\nIn the Audience Group Editor, blocks are ordered from highest to lowest priority. If a user qualifies for audiences in more than one of these sibling logic blocks, the blocks are evaluated in priority order and the user is added only to audiences in the first block that matches.
\nLogic blocks can only be created, renamed, reprioritized, and deleted within the Audience Group Editor.
\nIf you place two audiences inside the same logic block and a user qualifies for both audiences, the user is added to both audiences. This reflects scenarios in which a single user matches several defined behaviors, interests, or attributes that you want to recognize and act on.
\nKeeping our example from above, a user may qualify for the New Customers audience as well as the Sports Fans and High Value Purchasers audiences. By placing the Sports Fans and High Value Purchasers audiences within the same logic block under the New Customers parent audience, you can ensure that the user receives relevant messaging for both sports and higher value products.
\nInclusive audiences are useful when:
\nInclusive audiences help you reach the full set of users who meet your criteria, without forcing a choice about which behavior should win.
\nIf you place two audiences inside separate logic blocks and a user qualifies for both audiences, the user is only added to the audience in the block with the highest priority. This reflects scenarios in which you need to enforce non-overlapping audiences for things like A/B tests or lifecycle stages where it doesn’t make sense for a user to belong to more than one audience.
\nFor example, the New Customers, Active Customers, and Lapsed Customers audiences should never overlap. By separating these into three logic blocks, you can ensure that each user is added to only one of the three audiences at a time. Even if a user qualifies for more than one lifecycle audience, they are only assigned to the audience in the highest priority block.
\nExclusive audiences are useful when:
\nExclusive audiences help you assign users based on your strategic priorities and avoid conflicting messaging, double counting, or ambiguity.
\nWhile Inclusive/Exclusive Audiences adds new options for structuring your audiences, it does not change the core Audiences workflows you already use. You still:
\nTo learn more about these unchanged audience workflows, see:
\n\n