Campaign audience organization recommendations

Overview

This document provides recommendations for setting up and organizing process blocks within an audience in Redpoint Interaction (RPI). The organization of an audience will depend on what you’re trying to achieve for a specific outcome, so the following will be general recommendations.

Background

Within RPI there are many ways to configure or organize an audience. For each different possibility, there are questions about what the “best” way is to set them up. Since each person who works within RPI may have their own way of doing this work, this document provides some guidelines to help you follow a flow within your audiences.

Common organizational questions

Question 1: Where to put filters and suppressions in the workflow

Should we organize all filters up front at the beginning of workflow and organize all suppressions at the end (or vice versa)?

Recommendation: Put filters and splits closer to the beginning of the workflow and put suppressions closer to the end. This allows you to see the record counts of qualified records and then those that are falling out due to these suppressions.  

Question 2: Whether to pair filters and suppressions in the workflow

Instead of organizing filters at beginning and suppressions at end, should we stagger filters and suppressions in pairs throughout the workflow to reduce joins within a Create Table and take advantage of additional temp tables?

Recommendation: Put all of the filters up front in the workflow, and then follow those with suppressions, and then finally any needed splits. This will get the population smaller faster by going through the filters first and then allowing the workflow to process through any suppressions.

Question 3: Ordering filters by size

Should I start the workflow with the smallest filter first (or alternatively, by largest filter first)?

Recommendation: Place the largest filters at the front of the workflow; this will cut down on the population sooner and speed up the downstream process blocks. For example, use the filter that will get the campaign to a more granular level, such as “purchased a specific item in the last 30 days” vs. “purchased in the last 30 days”.

Question 4: Using multiple filter blocks vs. a single split block

Should I use multiple filter blocks or a single split block?

Key differences between filter vs. split

When to use filter vs. split

• Use filter block when you need to:

  • Refine the audience to a specific subset.

  • Apply a binary condition (e.g., “Include only customers who subscribed to SMS notifications”).

• Use split block when you need to:

  • Segment an audience into multiple groups for different messaging or experiences.

  • Prioritize paths based on conditions (e.g., targeting VIPs first, then Regulars, then Inactive users).

Consideration: Can records that do not meet selection criteria be sent an offer to promote engagement?

Recommendation: If records that do not meet any of the selection criteria will be sent an offer, then you need to use a split block. Using a split block allows for an “All Remaining” group for records that do not qualify for any of the selection rules. By having this group, you can then select them in an interaction and send them an offer.

Question 5: How many selection rules in a suppression block

Should suppression blocks only have one selection rule per block to reduce joins per suppression block?

Recommendation: Try to limit suppression blocks to no more than 5 suppressions in a single block, due to processing time and the joins that are being processed behind the scenes when those blocks are running. Once you reach 5 suppressions in a block, then add another suppression group using the remaining records from the previous suppression block.