When designing your workflows, you may wonder about how to apply filter conditions throughout the flow. Filter conditions apply to segments, decision nodes, timer nodes, and some action nodes.
Where to apply filter conditions
Here is a helpful way to think about where to apply filter conditions:
Segments: Define which account enter a workflow.
Decision nodes: Provide paths that are evaluated immediately through the flow.
Timer nodes: Indicate when progression happens.
Use segment filter conditions:
To define which accounts are eligible to enter the workflow.
For stable, reusable audience logic, such as your ideal customer profile (ICP) definition, firmographics data, or baseline intent/engagement.
Use decision node filter conditions:
To determine which path the audience should take immediately.
To apply branching logic based on attributes or behavior at that point in time.
When no waiting is required before routing.
Use timer node filter conditions (OR logic):
To wait up to X time, but progress or branch sooner if specific actions occur.
When timing and early exit are both required (such as, “wait 30 days or move on once engaged”).
When the condition exists to shorten the wait, not to perform immediate routing.
Timer conditions can branch, but they do not replace decision nodes; they just add early-exit logic to a wait period.
In the Audience Workflow example shown above, starting from a segment, a decision node checks whether someone from an account visited a webpage (URLs visited filter). Those accounts get pushed to a 6sense Advertising campaign. A timer node runs the campaign for 30 days, and it checks whether anyone from the account registered for a webinar, and if so, adds the account to an AI Email campaign.
Account- and people-level filters
Filters function on account- and people-level attributes. However, whether a filter returns account or people records depends on the type of node.
Returned records for segments and decision nodes
When you create a segment or decision node, you can filter on account-level records or on people-level records. Either type of filter returns account-level records. If the filter is at the people level, the node will determine the account to which the person belongs and return the account.
Returned records for action nodes
Action nodes are categorized as account-level or people-level. Account-level push-action nodes send accounts to campaigns. People-level push-action nodes send contacts or leads to 6sense AI Email or a CRM, MAP, or SEP. Refer to Audience Workflows Action Nodes.