SuppressionList Add-Ons

Feature Snapshot

Summary:
SuppressionList Add‑Ons are pre‑built integration steps in LeadConduit that enable you to query one or more suppression lists directly within your flow—without writing custom API code.

Key Benefits:

• Simplified integration that removes the need to manage raw API calls
• Centralized data quality control for duplicate or unwanted entries
• Flexible duplicate and profanity filtering using a user‑friendly, low‑code interface

Typical Use Cases:

• Preventing duplicate leads across multiple offers by querying several suppression lists simultaneously
• Filtering leads based on specific criteria (such as profanity or known duplicates) without manual API integration
• Enhancing lead validation workflows by abstracting complex API calls into simple flow steps

How the SuppressionList Add‑Ons work?

SuppressionList Add‑Ons integrate with your LeadConduit flow by providing dedicated steps that internally manage the process of querying one or more suppression lists. Instead of writing custom API calls to the SuppressionList service, you simply add an add‑on step to your flow. When the step executes, it standardizes your query data, sends a request to one or multiple suppression lists, and appends two key pieces of data to your lead: a Boolean flag indicating if a match was found and an array listing the specific lists where the match occurred. This output enables you to configure subsequent filters or decision rules to block duplicate or otherwise unwanted leads.

Step‑by‑Step Instructions

1. Add the SuppressionList Add‑On Step:
   In the LeadConduit flow editor, click “Add to Flow > Add-Ons” and select one of the SuppressionList Add‑Ons from the catalog.
2. Configure the List Mapping:
   In the add‑on configuration, enter the names of the suppression lists you want to query. To query multiple lists at once (for example, offer_1_dupes, offer_2_dupes), separate the list names with a comma.
3. Map the Query Field:
   Select the lead field (such as email or phone) that will be used to check against the suppression lists.
4. Set Up Filtering or Decision Rules:
   Immediately after the add‑on step, add a filter step. You can either check the “SuppressionList Query Item Found” Boolean flag for simple duplicate blocking or inspect the “SuppressionList Query Item Found In” array to determine which specific lists contained the value.
5. Review and Save the Flow:
   Confirm that the list names, field mappings, and filters are configured correctly, then save your flow.

Expected Result:
The add‑on step returns a Boolean flag indicating if the queried value exists in any of the listed suppression lists and an array with the names of the lists where the value was found. Appropriate filters then block or process leads based on these outcomes.

Validation & Monitoring (optional)

• Test the Setup: Submit test leads with known values that exist in one or more of your configured suppression lists and verify that the “Query Item Found” flag and “Query Item Found In” array return correct results.
• Where to Monitor?: View the lead event details in the LeadConduit Events tab to ensure that filtered leads are stopped based on the appended suppression list query data.

Best Practices

• Always verify that the suppression list names are entered exactly as stored in your SuppressionList account (watch for extra spaces or typos).
• Place the filter step immediately after the SuppressionList Add‑On to prevent later steps from overwriting the appended data.
• Use the “Query Item Found In” array for granular control when you need to take different actions based on which specific list triggered the flag.
• Test the configuration under multiple scenarios (duplicate found in one list only, in multiple lists, or not at all) to ensure reliable operation.

Troubleshooting

Frequently Asked Questions (FAQ)

What exactly are SuppressionList Add‑Ons?

They are pre‑built integration steps in LeadConduit that allow you to query one or more suppression lists directly from your flow, eliminating the need for custom API integrations.

Why are SuppressionList Add‑Ons important?

They simplify lead filtering by abstracting complex API calls into an easy‑to‑configure step, reducing errors and streamlining duplicate and profanity checking across multiple lists.

How do I use SuppressionList Add‑Ons in my flow?

Simply add the SuppressionList Add‑On step, configure it by entering comma‑separated list names and mapping the query field, then follow it with a filter step that uses the appended Boolean flag or list array to conditionally stop unwanted leads.

How is using SuppressionList Add‑Ons different from using the SuppressionList API directly?

The Add‑Ons provide a graphical, low‑code interface that automatically handles field standardization, API authentication, data querying, and response parsing, whereas using the API directly requires manual coding, handling authentication, and parsing complex responses.

Glossary