SuppressionList in Real-Time Bidding

Feature Snapshot

Summary:
SuppressionList in Real‑Time Bidding is a LeadConduit feature that leverages pre‑populated lists of unique identifiers to check incoming lead data (such as phone numbers or email addresses) during the bidding process, ensuring that only unique, high‑quality leads trigger bid submissions.

Key Benefits:

• Prevents wasted bid spend by filtering duplicate and undesirable leads in real time.
• Enhances lead quality by integrating established suppression data into the bidding decision.
• Enables rapid, dynamic decision making that protects campaign budgets and improves overall ROI.
• Can be extended to filter other unwanted content (for example, profanity) through dedicated list configurations.

Typical Use Cases:

• Filtering duplicate leads during real‑time bidding to avoid redundant purchases.
• Enforcing campaign standards by excluding leads flagged in suppression lists for disallowed attributes.
• Dynamically adjusting bid decisions based on pre‑defined quality criteria using one or more suppression lists.
• Supporting multi‑list queries for comprehensive lead validation across various offers.

How the SuppressionList in Real‑Time Bidding works?

When a lead is submitted via a real‑time bid (ping), a designated SuppressionList Query step is executed. This step checks key lead fields—typically a standardized phone number or email address—against one or more pre‑populated suppression lists. If the value is found, the system appends data such as suppressionlist_query_item_found (and optionally suppressionlist_query_item_found_in) to the lead’s package. A subsequent Filter Step immediately evaluates these results; if a match is detected, the lead is halted from further processing and the bid is blocked. If no match is found, the bidding process continues and an Add to List step updates the suppression list with the new lead’s key, ensuring future duplicates are caught. Additionally, this mechanism can be adapted for other quality controls (for example, filtering profanity) by creating separate lists and configuring dedicated query and filter steps.

Step‑by‑Step Instructions

1. Create or Pre‑Populate Your SuppressionList:
   • Log into your SuppressionList account.
   • Create a new list (or update an existing one) with the unique values you plan to check (e.g., standardized phone numbers or email addresses).
   • For broader applications, consider creating dedicated lists for different purposes like duplicate checking and content filtering.

2. Integrate the SuppressionList Query Step in Your RTB Flow:
   • In your real‑time bidding flow, enable “SuppressionList” using the option on the top navbar.
   • Map the appropriate lead field(s) (for instance, “Phone 1” or “Email”) to the query ensuring values are standardized (digits only for phones, lowercased for emails).

3. Add the Lead to the SuppressionList:
   • After the lead passes all further validations and is accepted, use a “SuppressionList Add to List” step near the end of the flow.
   • This step updates the list with the new lead’s key to prevent future duplicate submissions.

4. Optional – Configure Additional Query Steps for Specific Use Cases:
   • For example, to filter profanity, create a separate suppression list loaded with banned words and add dedicated query and filter steps for fields such as first name and last name.

Expected Result:
When a lead is submitted via RTB, the system queries the suppression list(s). Unique leads return suppressionlist_query_item_found=false and continue through the bidding process, while duplicate or flagged leads return suppressionlist_query_item_found=true and are immediately halted. Accepted leads update the suppression list to prevent future duplicates.

Validation & Monitoring (optional)

• Test the Setup: Submit test leads with known unique identifiers, then submit duplicate leads to verify that the query appends a “found” flag and that the filter halts processing accordingly.
• Where to Monitor?: Review the LeadConduit events log and RTB dashboard to inspect the appended suppression query data and monitor bid outcomes.

Best Practices

• Always standardize key field values (e.g., remove punctuation, use a consistent format) before submitting them to the suppression query.
• Pre‑populate your suppression lists with historical data to improve duplicate detection from the outset.
• For extended use cases—such as filtering for profanity—set up separate Query and Filter Steps for each field rather than attempting to combine multiple fields.
• Document your flow configuration details so team members understand which suppression criteria are active and how they interact with pricing and bid logic.

Troubleshooting

Frequently Asked Questions (FAQ)

What is SuppressionList in Real‑Time Bidding?

It is a feature within LeadConduit that uses pre‑populated lists to check key lead identifiers in real time, ensuring that duplicate or otherwise undesired leads do not trigger bid submissions.

Why is it important to use SuppressionList in RTB?

It prevents wasted bid spend by filtering out duplicate or non‑compliant leads, thereby enhancing lead quality and preserving campaign budgets.

How do I use SuppressionList in RTB?

First, create or update your suppression list with standardized key values. Then, enable SuppressionList in your RTB flow to check incoming leads, set an Acceptance Criteria rule to block leads flagged as duplicates, and finally add validated leads to the list using an Add to List step.

What happens if the SuppressionList Query returns “found”?

If a query returns “found,” the corresponding Filter Step will halt further processing of that lead, thereby preventing the bid from being placed.

Glossary