Exempting LeadConduit Flow Steps from Test Leads

When you or your lead vendors are posting test leads to a flow, you might not always want to run every step in that flow. For example, you probably want to skip the de-duplication step so you can submit the same lead data as many times as needed. Here’s one way to set that up.

Step 1) Add the Test Lead (is_test) field to your flow. We’ll use this standard field to indicate whether the lead data is real or only meant for testing purposes. The Flow must still be configured to use it as LeadConduit will not take any actions based on this field otherwise.

Step 2) Determine what steps can be bypassed in testing. Here’s an example flow with a couple of steps you’d probably want to skip when testing:

• SuppressionList
• Filter (Catch Bad Emails)

Step 3) Let’s add or update Step Criteria to those Flow Steps.

1. Expand the step
2. Click Step Criteria
3. Click Add Rule
4. Set the flow field to Test Lead and the operator to is not true

Here the is not true operator means Test Lead is either blank or false.

This means if the Test Lead Field (is_test) is omitted or if Test Lead is set to false, the flow proceeds normally.

However, if the Test Lead field is included and the value is true, the step is skipped. Test Lead is a boolean field value and the following values will all be evaluated to true (yes, true, 1).

Step 4) Skipping Filters are a little different than other steps because they do not have Step Criteria. Instead, you have to include the Test Lead Step Criteria as one of the conditions to stop the flow.

Here’s a fairly generic filter setting:

Here’s what you’d need to add to exempt Test Leads from the Filter.

If you have other Test Lead scenarios, especially if they’re complex, we’d be happy to help you solve those puzzles.

• is_test_field.png100 KB
• all_steps.png200 KB
• BV_default_filter.png100 KB
• SL_step_rule.png50 KB
• BV_filter_rule.png70 KB