What Are Campaign Triggers & How To Use Them

In a Lead Prosper campaign, leads enter through your Suppliers and are distributed to your Buyers. But lead routing often requires more than just that primary distribution layer. You may need to fire a conversion postback to an affiliate tracking platform after a lead sells, send failed leads to a secondary campaign for additional monetization, push accepted lead data to a CRM or dialer, log every processed lead to a Google Sheet, or notify a buyer via email the moment a new lead arrives. Campaign Triggers handle all of this. They allow you to define conditional, event-driven actions that run automatically after a lead has been processed and distributed to your Buyers. Each trigger follows an IF this — THEN that structure: you set the conditions a lead must meet, and you define the actions that fire when those conditions are satisfied.

How Campaign Triggers Work

Campaign Triggers are built around two core components: Conditions and Actions.

Conditions define the rules a lead must satisfy for the trigger to fire. You can add multiple conditions to a single trigger, and all conditions must be true for the actions to execute (conditions are joined with AND logic).

Actions define what happens when the conditions are met. You can attach multiple actions to a single trigger, and each one runs independently.

By default, all Campaign Triggers run in real time — the actions fire as soon as the lead has been ingested into the campaign and processed. You also have the option to run actions on a Scheduled Delay, which queues the action and fires it based on timing rules you configure. For a full breakdown of delayed triggers, including delay types, delivery strategies, blocked dates, and queue management, see Schedule, Repost, and Delay Leads via Campaign Triggers.

Trigger Conditions

Conditions control when a Campaign Trigger fires. This is the IF part of the Campaign Trigger.

You can combine any number of the following condition types within a single trigger.

Lead Status

The Lead Status condition fires the trigger based on the outcome of the lead after processing. You first select a comparison mode, then choose the status value(s).

Comparison modes:

Equal — the lead status must match the selected status exactly.
Any one of — the lead status must be one of the selected statuses.
Except — the lead status can be any status except the selected status(es).

Status values (when set to Equal):

Any Status — the trigger fires whenever a lead has been processed, regardless of the outcome.
Accepted — the lead was accepted and sold to a buyer.
Duplicated — the lead was flagged as a duplicate at the campaign level. This does not account for leads flagged as a duplicate by a specific buyer.
Error — the lead resulted in an error. When you select Error, you can narrow down to one or more of the following error groups:
1. Not Sold - Any Error — the lead status is Error. Error groups are ignored.
2. Invalid supplier data — the lead status is Error because the data the Supplier sent was incorrectly formatted or contained an invalid campaign field value.
3. External Validations — the lead failed to sell because a third-party integration flagged the lead and caused it to be rejected.
4. Supplier cap reached — the lead was never distributed to buyers because the Supplier cap had been exhausted.
5. Available buyer - cap reached — the lead was never distributed because all buyers in the campaign had hit their caps.
6. Invalid day / time — the lead was never distributed or sold because of a Day / Time Parting filter that was in place. This only accounts for Global or Supplier filters, not Buyer-level filters.
7. Rejected by filter(s) — the lead contained data that was rejected by a filter. This only accounts for Global or Supplier filters, not Buyer-level filters.
8. Not sold - buyer related errors only — the lead was eligible to be sold to one or more buyers in the campaign but failed to sell to any of them for any number of reasons (no buyers available, duplicated by buyer, etc.).

Field

The Field condition evaluates a specific campaign field value on the lead. After selecting a campaign field, you choose from the following comparison operators:

Is blank — the field came in empty with no value.
Is not blank — the field came in with any value.
Equal — the field value matches this exact value.
Not Equal — the field value is anything except this value.
Greater than — the field value is greater than this value.
Greater than or equal to — the field value is greater than or equal to this value.
Less than — the field value is less than this value.
Less than or equal to — the field value is less than or equal to this value.
Between — the field value falls between a start value and an end value.
Any one of — the field value is any one of the specified values. If the selected field uses a List of Allowed Values, you can pick from the list directly.
Not any one of — the field value is anything except the specified values. If the selected field uses a List of Allowed Values, you can pick from the list directly.
Contains — the field value contains this value.
Does not contain — the field value does not contain this value.
Starts with — the field value starts with this value.
Ends with — the field value ends with this value.

Day / Time

The Day / Time condition restricts the trigger to fire only during specific days and times. It uses the same selection tool found in Day / Time Parting filters.

You configure a timezone, then select the day(s) and time window(s) during which the trigger is allowed to fire. Any lead processed during those selected times will satisfy this condition.

Sell Price

The Sell Price condition fires the trigger based on the lp_lead_sell_price — the price the lead sold to a buyer (or multiple buyers). Available comparison operators:

Greater than — the sell price is greater than this value.
Greater than or equal to — the sell price is greater than or equal to this value.
Less than — the sell price is less than this value.
Less than or equal to — the sell price is less than or equal to this value.
Between — the sell price falls between a start price and an end price.

Supplier

The Supplier condition fires the trigger based on which Supplier sent the lead.

Comparison modes:

Equal — the Supplier must match the selected Supplier exactly.
Any one of — the Supplier must be any one of the Suppliers in the list.
Except — the Supplier can be any Supplier except the Supplier(s) in the list.

Buyer

The Buyer condition fires the trigger based on which Buyer processed the lead and what their status was for that lead. This condition has two parts: the Buyer selection and the Buyer status.

Buyer comparison modes:

Equal — the Buyer must match the selected Buyer exactly.
Any one of — the Buyer must be any one of the Buyers in the list.
Except — the Buyer can be any Buyer except the Buyer(s) in the list.

Buyer status values:

Any Status — the trigger fires whenever a lead has been processed by the selected buyer(s), regardless of the outcome.
Accepted — the lead was accepted and sold to the selected buyer(s).
Duplicated — the lead was flagged as a duplicate by the selected buyer(s).
Error — the lead failed to sell to the selected buyer(s). When you select Error, you can narrow down to one or more of the following error groups:
1. Any error — the lead failed to sell to the specific buyer(s) for any reason.
2. Real-time errors — the lead was sent to the buyer but the buyer rejected it on the POST.
3. Buyer not eligible — the buyer was not eligible to accept the lead. This could be due to buyer filters, buyer caps, the buyer being outbid (in a Ping Post Exchange), etc.

Trigger Actions

Actions execute once all conditions on the trigger are met. You can add as many actions as needed to a single Campaign Trigger, and each action runs independently.

There are three action types: HTTP / API, Email, and Google Sheets.

HTTP / API

The HTTP / API action sends an API request to an external endpoint. It uses the same payload builder available on Buyer pages. You can configure the following:

Type — GET, POST, or PUT.
Posting URL — the API endpoint to send the request to.
Headers — custom headers, if needed.
Format — JSON, FORM, or XML.
Body — the request body. This can be built using Campaign Fields, Computed Fields, System Fields, hardcoded values, and payload transformers, just like a standard buyer payload.

Common use cases for the HTTP / API action include conversion or affiliate tracking postbacks to platforms like Everflow or RedTrack, posting data to third-party analytics platforms, Meta Conversion API events, sending lead data to a CRM or dialer, and routing leads to a secondary Lead Prosper campaign.

Email

The Email action sends a plain text email to up to 5 email addresses. You can configure the following:

From name — the display name on the outgoing email.
Reply to email — the email address recipients can reply to.
Email subject — the subject line.
Body — the email body, structured like a regular text email. You can use any Campaign Field, Computed Field, or System Field in the body.

Emails are sent from no-reply@leadprosper.io using Lead Prosper's email servers. HTML is not supported — only plain text.

Google Sheets

The Google Sheets action uses Lead Prosper's native Google Sheets integration to update a Google Sheet in real time as leads are processed. For detailed setup instructions, see:

Reviewing Campaign Trigger Logs

How you review trigger activity depends on whether the trigger runs in real time or on a scheduled delay.

Real-Time Triggers

To check whether a real-time Campaign Trigger fired for a specific lead, go to Leads and open the individual lead. If one or more Campaign Triggers fired for that lead, you will see a Triggers Log tab. If the tab is not present, no trigger was associated with or fired for that lead.

Inside the Triggers Log tab, you can see which trigger(s) and action(s) fired, the data that was sent, and the response returned from the receiving platform.

Delayed Triggers

Delayed trigger logs are available in two places:

Individual lead view — Open a lead from the Leads page. If a delayed trigger has been fired for that lead, you will see a Delayed Triggers tab. Click into it to view the details of the delayed action, the data that was sent, and the response.
Analytics log — Go to Analytics > Logs > Delayed Triggers in the left menu. Select the Campaign, Trigger, and Date Range to filter. If any delayed triggers were processed during that time frame for the selected Campaign and Trigger, they will appear in a list for you to review.

Common Use Cases

Campaign Triggers support a wide range of post-processing workflows. Some of the most common include:

Affiliate and conversion tracking — Send postbacks to platforms like Everflow or RedTrack when a lead sells, including conversion data and sell prices.
CRM delivery — Post accepted leads to a secondary CRM (such as GoHighLevel) in addition to the primary buyer endpoint.
Warm transfers — Send lead data to a call center or dialer for immediate follow-up.
Secondary monetization — Route failed or duplicate leads to a different Lead Prosper campaign to sell to secondary buyers with less stringent requirements.
Buyer notifications — Send email or SMS notifications to buyers when a new lead has been delivered to them.
Real-time reporting — Log every processed lead (or specific subsets) to a Google Sheet for tracking and analysis.
Analytics and attribution — Fire events to third-party analytics platforms or the Meta Conversion API for downstream reporting.

Campaign Triggers are one of the most flexible tools in Lead Prosper. Any workflow that requires an action to happen after a lead has been processed — whether that is an API call, an email notification, or a spreadsheet update — can be handled through a trigger. If you need help configuring a trigger for a specific use case, reach out to the Lead Prosper support team.