Event Postback API
The Event Postback API is designed to trigger events that track and update lead data. It also supports converting leads into successful conversions, ensuring real-time data synchronization and improved campaign insights.
Overview
The Event Postback API fires a named tracking event against an existing lead. Use it to signal downstream actions — such as phone call completions, form steps, quote views, or conversions — that occur after the initial lead submission. When an event is a conversion event, arevenue value can be passed to trigger payout processing and buyer postbacks.
The endpoint is typically called from your webflow or landing page JavaScript using the Pingtree SDK, but it can also be called server-side.
Endpoint
Authentication
No token-based authentication header is required for this endpoint. Campaign identity is established through thecid field in the request body.
Request Parameters
Body Parameters (JSON)
Example Request
Conversion Event with Revenue
Example Responses
Success — Event Fired
Success — Conversion Event Fired
Error — Missing Event ID
Error — Missing Transaction ID
Error — Invalid Event ID
Error — Duplicate Event (deduplication enabled)
Error — Source Inactive
Status Codes
Tips
- Event IDs must be pre-configured. The
event_idvalue must match an event defined in the campaign’s event settings. Contact your campaign manager to confirm available event IDs. - Conversion events require
revenue. If the event is marked as a conversion type in the campaign settings, omittingrevenuereturns a 400 error. - Deduplication: If the campaign event has duplicate conversion disabled, firing the same
event_id+transaction_idcombination a second time returns a 400 duplicate error. EnableisDuplicatein event settings to allow repeated firing. - Concurrent lock: The API applies a 2-second lock per
transaction_id+event_idpair to prevent race conditions from duplicate HTTP requests. Retries within this window return a 403. - SDK usage: When using the Pingtree JS SDK on a webflow, events are typically fired automatically based on user interactions. Direct API calls are for server-side or non-webflow implementations.
Body
Lead details to add to the campaign
conversion_timezone should be as following, 'PST'(For Pacific Stand Time (UTC-8)), 'EST'(For Eastern Standard Time (UTC-5)), 'CST'(For Central Standard Time (UTC-6)), 'MST'(For Mountain Standard Time (UTC-7)), 'AKST'(For laska Standard Time (UTC-9)), 'SST'(For Samoa Standard Time (UTC-11)), 'HST'(For Hawaii-Aleutian Time (UTC-10)), 'AST'(For Atlantic Standard Time (UTC−4)