What Is A Campaign In Lead Prosper?

Campaigns in Lead Prosper

A campaign is the core building block of Lead Prosper. It defines how leads enter the system, how they are validated and filtered, and how they are distributed to buyers. Every lead that flows through Lead Prosper does so through a campaign.

Whether you are generating your own leads from a landing page, buying leads from third-party suppliers, or running a real-time auction between multiple buyers, campaigns give you the structure and control to manage that entire process from a single place.

This article provides a high-level overview of how campaigns work, the types available, and the key concepts you need to understand before building your first one.


What Makes Up a Campaign

Every campaign in Lead Prosper — regardless of type — is built from the same core components:

  • Suppliers — the source of your leads. A supplier is whoever is sending lead data into the campaign, whether that is your own landing page, a third-party lead vendor, or another system.
  • Buyers — the destination for your leads. A buyer is whoever receives the lead after it has been processed. This could be a CRM, a call center, another lead platform, or any system that accepts data via API.
  • Distribution Method — the logic that determines which buyer gets the lead and in what order.
  • Campaign Fields — the data points collected on each lead (first name, last name, email, phone, zip code, etc.). Campaign fields define what information the campaign expects and what gets passed along to buyers.
  • Computed Fields - dynamically built off of campaign field values, Computed Fields allow you to run any number of transformers on the data you are collecting to ensure that the data you collect is converted to meet whatever
  • Filters — rules that determine whether a lead qualifies for distribution. Filters can check field values, validate data quality, enforce geographic restrictions, and more. You can also filter of
  • Pricing — the buy and sell prices associated with each lead. Pricing can be static, conditional (based on rules), or dynamic (determined in real time by the buyer).
  • Volume & Budget Caps — volume limits that control how many leads a buyer can receive within a given time period (daily, weekly, or monthly).
  • Third Party Integrations — third-party services that validate or enrich lead data in real time. Examples include phone validation, email verification, fraud detection, and compliance tools like TrustedForm and Jornaya LeadiD.
  • Dupe Checker - campaign level duplicate checking to ensure you are not ingesting leads that have already been sold to your buyers. Cross-Campaign Dupe Checking allows you to dupe check incoming leads against against other campaigns in your account. You can also enable a Pre-Ping Dupe Check for Direct Post campaigns that will allow Suppliers to see if the key lead details trigger the dupe checker, filters, caps, etc.
  • Campaign Triggers — conditional actions that run after a lead has processed. These can be processing an API requests, updating a Google Sheet, or sending an Email. Campaign triggers can be run in real-time, or can be scheduled as delayed triggers. Use cases for campaign triggers can be to repost leads to a separate campaign, send a postback to a separate tracking platform such as Everflow or RedTrack.

How a Lead Flows Through a Campaign

When a lead enters a campaign, it moves through a predictable sequence:

  1. Ingestion — The lead data arrives from the supplier via API.
  2. Validation & Filtering — The campaign checks the lead against all configured filters, integrations, and duplicate rules. If the lead fails any required check, it is rejected and does not reach buyers.
  3. Distribution — The lead is routed to one or more buyers based on the campaign's distribution method and each buyer's eligibility (filters, caps, schedule, etc.).
  4. Delivery — The lead data is sent to the buyer's endpoint. The buyer responds with an accept, reject, or duplicate status.
  5. Logging — Every step of the process is recorded, including the supplier source, buyer responses, pricing, and timestamps.

For a full rundown of the entire lead process check out this article - Understanding the Lead Lifecycle in Lead Prosper


Campaign Types Explained

Lead Prosper offers three campaign types. The two primary types — Direct Post and Ping Post Exchange — cover the vast majority of use cases. The third, One-to-One, serves a specialized role in consent-based lead distribution.

Direct Post Campaign

A Direct Post campaign is used when you or your supplier have a landing page or form and want all lead data ingested in a single submission. Think of it as a consumer filling out a form and hitting submit — all of that data arrives at once, and the campaign immediately begins distributing it to your buyers.

Direct Post campaigns support one supplier (or multiple suppliers) sending full lead data in a single API call. The campaign then applies your filters, validations, and distribution logic to route the lead to the appropriate buyer(s).

This is the most common campaign type for lead generators who own their traffic source and control the data collection process.

Key characteristics:

  • Full lead data is received in one step
  • You control the lead source (your own forms, landing pages, or known suppliers)
  • Six distribution methods are available to control how leads reach buyers
  • Pricing can be static, conditional, or real-time (via ping post buyers on the backend)

Ping Post Exchange

A Ping Post Exchange is used when you are brokering leads between third-party suppliers and buyers in a real-time auction environment. This campaign type is built for situations where suppliers are sending you leads and you want to sell those leads to the highest-paying buyer available at that moment.

Unlike a Direct Post campaign where all data arrives at once, the Ping Post Exchange operates in two distinct steps:

  1. PING — The supplier sends a lightweight request containing non-personally-identifiable information (such as zip code, state, or lead vertical). The campaign evaluates the ping, checks which buyers are available, and returns a bid price to the supplier.
  2. POST — If the supplier accepts the bid, they send the full lead data. The campaign delivers the lead to the winning buyer.

The Ping Post Exchange supports two selling modes:

  • Exclusive Leads — The highest bid wins, and the lead is sold to a single buyer. The supplier sees only the top bid price.
  • Shared Leads — Multiple buyer bids are returned to the supplier. The supplier can choose which buyer(s) to sell the lead to.

It is important to understand that even if a supplier receives an accepted bid on the PING, they are not required to send the POST. Suppliers may choose not to post if the bid is no longer competitive compared to other exchanges or if the lead was already sold elsewhere. This is normal behavior in a ping post environment.

Key characteristics:

  • Two-step process (PING then POST)
  • Auction-based — buyers compete on price in real time
  • Supports exclusive and shared lead selling
  • Margin controls let you define your profit on each transaction
  • Distribution is always based on highest bidder logic

One-to-One Campaign

The One-to-One campaign type is designed for consent-based lead distribution, where consumers must explicitly choose which businesses they agree to be contacted by. This campaign type uses a "Ping, Pick, Post" approach — the consumer sees available buyers and their details, selects who they consent to engage with, and only those selected buyers receive the lead.

This campaign type is purpose-built for TCPA compliance and dynamic consent workflows. For a full breakdown of how One-to-One campaigns work, see the [dedicated One-to-One Campaign article].


When to Choose Direct Post vs. Ping Post Exchange

The decision comes down to where your leads are coming from and how pricing works.

Choose Direct Post when:

  • You are the lead generator — you own the landing page, form, or traffic source
  • Your supplier sends full lead data in a single submission
  • Pricing is pre-negotiated or based on rules you control
  • You want flexibility in how leads are distributed (waterfall, round robin, buyer groups, etc.)

Choose Ping Post Exchange when:

  • You are buying leads from third-party suppliers or lead vendors
  • You want real-time, auction-based pricing where buyers compete on bid
  • Suppliers need to know the bid price before deciding to sell the lead
  • You want to maximize revenue per lead through competitive bidding

In simple terms: Direct Post is for when you control the lead source and want to distribute. Ping Post Exchange is for when you are brokering between suppliers and buyers and want to auction.


Lead Distribution Methods

Distribution methods control how leads are routed to buyers once they pass validation. Direct Post campaigns offer six distribution methods. Ping Post Exchange campaigns use auction-based (highest bidder) distribution exclusively.

Waterfall

Buyers are arranged in a fixed priority order. The system attempts to sell the lead starting from the top and moves down the list until a buyer accepts or all buyers are exhausted.

Best for: strict control over buyer priority and predictable routing order.

Highest Bidder

All eligible buyers are evaluated and assigned a bid price — whether static, conditional, or returned in real time via a ping. Buyers are sorted from highest to lowest bid, and the system attempts to sell in that order.

Best for: maximizing revenue by always attempting the highest-paying buyer first.

Send to All

The system attempts to sell the lead to every eligible buyer in the campaign. An optional sell limit can cap how many buyers receive the lead.

Best for: shared leads where multiple buyers can purchase the same lead.

Round Robin

Leads are distributed evenly across all eligible buyers in a rotating sequence. Each time a buyer accepts a lead, they move to the back of the line. The next lead goes to the next buyer in rotation.

Note: distribution may not be perfectly even if filters, caps, or other constraints affect buyer eligibility.

Best for: fair and balanced distribution across buyers.

Weighted Round Robin

A variation of Round Robin that assigns buyers a percentage-based share of the rotation. Instead of equal distribution, buyers receive leads proportional to their assigned weight.

Note: like standard Round Robin, actual distribution may not be perfectly proportional due to filters, caps, or eligibility constraints.

Best for: mostly balanced distribution with preference given to specific buyers.

Buyer Groups

Buyer Groups let you organize buyers into tiers, each with its own distribution method (Waterfall, Highest Bidder, Send to All, or Round Robin). Leads flow through groups sequentially, and you control whether distribution stops after a group sells the lead or continues to the next group.

Best for: advanced multi-tier strategies — such as trying premium buyers first and falling back to secondary buyers, or mixing exclusive and shared selling within a single campaign.

Buyer Groups are only available in Direct Post campaigns.

Choosing the Right Distribution Method

Goal Recommended Method
Maximize revenue per lead Highest Bidder
Strict buyer priority Waterfall
Sell to multiple buyers Send to All
Even distribution Round Robin
Weighted prioritization Weighted Round Robin
Complex multi-tier logic Buyer Groups

Pricing and Revenue

Lead Prosper tracks revenue at the campaign level by recording buy prices (what you pay the supplier) and sell prices (what the buyer pays you). The difference is your margin.

Pricing can be configured in several ways:

  • Static — a fixed price per lead, defined in the buyer setup.
  • Conditional — pricing that adjusts based on rules (e.g., leads from Florida sell for more than leads from other states).
  • Real-time / Dynamic — the price is determined by the buyer's API response at the time of the ping. This is used in Ping Post Exchange campaigns and in Direct Post campaigns with Highest Bidder distribution where some buyers return bids via ping post.

In Ping Post Exchange campaigns, margins are applied to buyer bids before the price is returned to the supplier. This ensures you earn a spread on every transaction. Margins can be set globally, overridden per buyer, or overridden per supplier.


Filters, Dupe Checking, Validations, and Third Party Integrations

Campaigns support multiple layers of lead quality control:

Campaign Field Filters let you accept or reject leads based on the values of any field — state, zip code, age, income range, or any custom field. Filters support conditions like equals, contains, greater than, between, starts with, and regular expressions.

Computed Field Filters let you run the same level of filters as campaign fields, but off of the values that are generated by Computed Fields.

API Filters allow you to run an API request during the ingestion process and Allow or Block a lead based off of the API response.

Dupe Checking rejects leads that match previous submissions that have sold based on a combination of fields within a configurable time window.

Cross Campaign Dupe Checking allows the leads to also be checked against other internal campaigns within your account.

Pre-Ping Dupe Checker allows Suppliers to send partial lead data to a dedicated endpoint before submitting the full lead. Lead Prosper evaluates the request against duplicate rules, filters, and caps, and returns whether the lead is likely to be accepted—helping suppliers avoid sending duplicates or invalid leads.

*Please note that data sent through pre-ping are not stored in any way, it is dropped immediately. For this reason there are no logs and therefore no records or reports for pre-pings. The only metrics are total pre-pings, accepted pre-pings, and rejected pre-pings.

Third-party integrations validate lead data in real time before distribution. Supported integrations include phone validation (Trestle), email verification (XVerify), fraud detection (Anura, MaxMind), and compliance tools (TrustedForm). These run inline — if a lead fails validation, it is rejected before reaching any buyer.


Caps and Budget Controls

Caps let you limit the number of leads a buyer receives within a defined period. You can set caps at the daily, weekly, monthly or total level. Once a buyer hits their cap, they become ineligible for distribution until the cap is reset.

You can set caps across all campaigns, suppliers, and buyers by lead volume or total budget.

In some cases you can also set Ping Volume Caps on buyers and suppliers to cap the amount of PINGs ingested or sent to your buyers.

Caps work alongside filters and distribution logic — a Buyer or Supplier who has hit their cap is skipped in the rotation just like a lead whose filters reject that lead.


Campaign Triggers

Campaign Triggers are rules that run after a lead has been processed through the standard buyer flow. They follow an IF/THEN structure: if certain conditions are met, then one or more actions are executed.

Triggers operate independently from your primary buyer setup and are used for secondary logic — things that happen after the lead has already been accepted, rejected, or duplicated by your buyers.

How Triggers Work

Each trigger has two parts:

  • IF rules — conditions that must all be true for the trigger to fire. You can build rules based on field values, lead status (accepted, error, duplicated), specific suppliers, specific buyers, sell price, or day/time.
  • THEN actions — what happens when the conditions are met. Actions can send an HTTP post (with full payload builder), send an email, or post the lead to another campaign.

Common Use Cases

Affiliate Tracking Postbacks — Send conversion data (lead sold, sell price, transaction ID) back to platforms like Everflow after a lead is accepted.

CRM Delivery — Post accepted leads to a secondary CRM (like GoHighLevel) in addition to the primary buyer endpoint.

Routing Failed Leads to DQ Campaigns — If a lead is rejected by all primary buyers, trigger a post to a different campaign with less strict requirements or different buyer verticals.

Email or SMS Notifications — Notify buyers or internal teams in real time when a lead is accepted, using services like Twilio for SMS or SendGrid for email.

Cross-Campaign Reposting — Send leads that fail in one vertical to campaigns in adjacent verticals (e.g., a rejected home improvement lead might qualify for a home insurance campaign).

Delayed Triggers

In addition to real-time triggers, Lead Prosper supports delayed triggers that let you schedule lead delivery for a later time. Delayed triggers are useful for matching buyer business hours, spreading delivery throughout the day to simulate organic traffic, or retrying failed leads the next business day.

Delayed triggers support configurable delay types, delivery windows, pacing strategies, and blocked dates. For full details on delayed trigger configuration, see the [Delayed Campaign Triggers article].


Best Practices

Start with your buyer's API specs. Before building anything, have your buyer's posting instructions in hand. Knowing what fields they require, what format they expect, and how they respond will save time and prevent errors.

Always test before going live. Use Lead Prosper's built-in test mode to send test leads to your buyers and confirm successful delivery before turning on real traffic.

Set caps early. Configure daily or monthly caps before activating suppliers. This prevents budget overruns if lead volume spikes unexpectedly.

Use filters to protect lead quality. Define your ideal lead criteria upfront with filters rather than relying on buyers to reject bad leads after delivery.

Match your distribution method to your goals. If revenue matters most, use Highest Bidder. If buyer fairness matters, use Round Robin. If you need complex tiered logic, use Buyer Groups.

Monitor your analytics. Lead Prosper logs every lead event. Review acceptance rates, buyer performance, and revenue regularly to identify issues early and optimize over time.

Use Campaign Triggers. Keep your primary buyer setup clean and use triggers for affiliate tracking, CRM delivery, notifications, and fallback routing.

Name campaigns clearly. The campaign name appears on API specs sent to suppliers. Use descriptive names that make it easy to identify the vertical, traffic type, or purpose at a glance.


Next Steps

Once you understand the concepts above, you are ready to build your first campaign. Here are the most common starting points:

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.