Overview
What Is a Postback?
A Postback allows LeadExec to automatically send data to an external system when a specific event occurs, such as when a lead is delivered or sold.
Postbacks send data using query parameters. Each parameter includes a Parameter Name, Type, and Value, which together determine what information is included in the request.
Key Features
The Postback feature allows you to:
Data Transmission: Send predefined data to external endpoints
Parameter Configuration: Control exactly which data is included in each postback
Event-Based Execution: Trigger postbacks only after a lead is delivered or sold
How It Works
A lead enters LeadExec
The lead is successfully delivered or sold based on campaign rules
A postback event is triggered
LeadExec sends the configured data to the external endpoint
How to Set Up a Postback
Navigate to your Campaigns list and edit the desired campaign
Locate the Postback tab and open the configuration
Enter the Endpoint URL where the data should be sent
Select the HTTP Method (POST or GET)
Add the required Query Parameters
For each parameter, choose a Parameter Type and Value
Available Parameter Types
Static Value
A Static Value sends a fixed, hard-coded value with every postback request.
Common use cases include:
Testing and validation
Sending environment identifiers (for example,
test=1234)Passing constant values required by the receiving system
This value never changes and is not tied to lead data or campaign activity.
Lead Field
A Lead Field parameter pulls data directly from the lead record.
Available fields depend on the Lead Type linked to the campaign. Only fields that are defined and enabled for that Lead Type can be selected.
Examples include:
First Name
Last Name
Phone Number
Email Address
If a lead field is empty or not populated, the parameter may be sent with an empty value.
System Field
System Fields provide internal identifiers generated and managed by LeadExec. These are commonly used for tracking, reconciliation, and syncing data between systems.
Common System Fields include:
Lead UID
Lead Type UID
Lead Source UID
Campaign UID
These values are automatically assigned by LeadExec and do not depend on lead-submitted data.
Transactional
Transactional parameters provide outcome-based and financial data that is generated after a lead has been processed and successfully delivered or sold.
Available Transactional values include:
Postback ID
The unique LeadExec identifier for each postback event.Payout Model
Indicates how the lead revenue was calculated. Possible values include:Pay Per Lead
A fixed price is applied for each delivered lead.
Example: A lead priced at $3 returns a payout of $3, regardless of how many times it is delivered.Pay Per Sale
Used when a lead can be sold to multiple clients.
Example: If a lead is sold twice at $3 per sale, the total payout returned will be $6.Revenue Share
Returns a payout calculated as a percentage, based on the pricing rules configured in the campaign or client delivery account.
Total Sold Price
The final sale amount after all pricing calculations have been applied.Revenue Share Payout
The calculated cost of the lead when revenue share pricing is used.Number of Deliveries
Indicates how many times the lead was successfully sold or delivered.Client UID
The unique identifier for each client the lead was sold to.
Important:
All payout calculations are fully driven by the pricing settings configured in the campaign and/or delivery accounts(If applicable).
Best Practices
Parameter Selection
Use Static Values when the same value needs to be sent every time
Use Lead Fields for information submitted with the lead
Use System Fields for internal LeadExec identifiers
Use Transactional Fields when the postback depends on delivery or sale results
Event Timing
Make sure the lead has been successfully delivered or sold before expecting a postback to fire. It could take around 1 minute.
Troubleshooting
Postback Not Sending
Confirm that a delivery or sale has occurred
Postbacks do not run when a lead is first received
Missing Transactional Information
Verify that the postback is triggered after a successful delivery or sale
Transactional data is not available before that point