Introduction to Control Blocks
Control blocks are powerful tools within InTarget’s Marketing Automation Module that help you manage the flow of your campaigns based on specific conditions or behaviours players exhibit. These blocks include "True/False," "Wait Until," and "Wait Window," each serving a unique purpose in campaign automation.
True/False Block
Purpose:
The True/False block allows you to route players through different paths in your campaign based on whether they meet a specific condition.
How to Use:
Insert a True/False block into your campaign workflow.
Define a condition (e.g., Deposit Count > 1).
Configure actions for both outcomes:
True path: Actions to take if the condition is met.
False path: Actions to take if the condition is not met.
Example: You might want to send a bonus offer to players who have deposited more than once in the last week. Players who meet this condition (True) receive a special bonus email, while those who do not (False) receive a reminder to deposit to unlock special offers.
Wait Until Block
Purpose:
The Wait Until block pauses the campaign for a player until a specified condition is met.
How to Use:
Place a Wait Until block at the point in the workflow where you need to pause progress until the player meets a specific criterion.
Define the condition that must be met for the player to proceed.
Example: In a campaign designed to encourage second deposits, you could use a Wait Until block to pause the campaign until a player makes their second deposit. Once the deposit is made, the player progresses to the next step, which might involve a thank-you message or additional rewards.
Wait Window Block
Purpose:
The Wait Window block introduces a timeframe during which a condition must be met for the player to proceed along the desired path; otherwise, they are routed through an alternative path. By default, the block continuously monitors the condition in real-time — as soon as the condition is met, the player immediately proceeds without waiting for the time window to expire.
How to Use:
Implement a Wait Window block in your workflow where you want to give players a time-bound opportunity to meet a condition.
Set the condition and the time window (e.g., 24 hours).
Define actions for both scenarios: if the condition is met within the window, and if it is not.
Optionally enable "Wait full duration" if you want players to remain in the block for the entire time period, even after meeting the condition.
Key Behavior:
Immediate progression (default): Once the condition is satisfied, the player moves forward instantly — they don't need to wait until the end of the time window.
Wait full duration (optional): When this option is enabled, players will wait for the entire time window even if the condition is met earlier. This is useful when you want to synchronize player progression or batch-process users at a specific time.
Timeout routing: If the time window expires without the condition being met, the player is automatically routed through the false path.
Examples:
Example 1 (Default behavior): You're running a limited-time promotion where players who deposit within 24 hours after receiving a message qualify for a bonus. If a player makes a deposit after 5 minutes, they will immediately proceed to the bonus path without waiting the full 24 hours. However, if no deposit is made by the end of 24 hours, they will be routed to the false path.
Example 2 (With "Wait full duration" enabled): You want to send a follow-up message exactly 24 hours after the initial message, but only to players who made a deposit during this period. By enabling "Wait full duration," all players who deposit will wait the full 24 hours before proceeding to receive the congratulatory message at the same time, regardless of when exactly they made their deposit.
⚠️ Important: "Wait full duration" Behavior
When "Wait full duration" is enabled, the condition is re-evaluated at the end of the waiting period, not at the moment it was initially met.
What this means:
If a player initially meets the condition and enters the wait period, they will wait the full duration.
The condition is checked again when the wait period ends.
If the player no longer meets the condition at that point, they will be routed to the false/alternative path.
Understanding Period Types in Control Blocks
In addition to the basic functionalities of the True/False, Wait Until, and Wait Window blocks, InTarget allows you to specify the period during which conditions should be evaluated. This capability enhances the flexibility and precision of your campaign triggers by allowing you to define exactly when and how player behaviors are assessed.
Period Types Explained
1. After Entering This Step:
Description: The condition is evaluated based on the actions taken by the player after they reach this specific step in the campaign.
Use Case: This period type is useful for conditions that should only consider player behaviour occurring after encountering a particular campaign element.
Given that True/False blocks do not wait at the step for conditions to be fulfilled, using "After Entering This Step" as a period will result in the condition being evaluated immediately. In most cases, this leads to a False outcome because the condition (e.g., making a deposit) is unlikely to occur at the exact moment the player reaches this step.
2. Within the Last N Time:
Description: The condition checks for actions within a specified timeframe leading up to the present moment, such as the last N days, hours, or minutes.
Use Case: Ideal for temporary promotions or to gauge recent player activity, like checking if a deposit has been made in the past 7 days.
3. After Entering Campaign:
Description: Conditions are evaluated based on all actions taken by the player since they entered the campaign.
Use Case: Useful for long-term campaigns where accumulating behaviors (e.g., total deposits made) throughout the campaign duration influences the path or offers players receive.
4. During the Lifetime:
Description: This evaluates conditions based on the player's entire history with the platform, from account creation to the current point.
Use Case: Best for loyalty or VIP-focused campaigns where long-term behaviors and thresholds (e.g., total deposits or level of activity) are crucial for segmentation and personalization.
Adding Period Types to Control Blocks
When setting up any of the control blocks—True/False, Wait Until, or Wait Window—select the period type from a dropdown menu within the block's settings. This selection tailors how and when the conditions are assessed against player actions, allowing for more targeted and relevant campaign flows.
Example Implementation: Suppose you want to encourage players to make their second deposit. You could set a Wait Until block with the condition Deposit Count > 1 and select the period type "After Entering This Step." The system will then monitor deposits made after the player reaches this block, pausing the campaign flow until the condition is met.