Global 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 Global Event Postback API fires a conversion or tracking event across all campaigns within an organization using a single endpoint. It is designed for buyers and third-party systems that receive leads from multiple campaigns but want to post conversion data back using one consistent URL — without needing a different endpoint per campaign. Pingtree resolves the campaign and lead from thetransaction_id automatically. No cid is required in the request body.
Endpoint
{org-id} with your organization’s unique ID (available in your Pingtree dashboard under account settings).
Authentication
No token-based authentication header is required. Theorg-id path parameter scopes the request to your organization.
Request Parameters
Path Parameters
Body Parameters (JSON)
Example Request
Non-Conversion Event
Example Responses
Success — Conversion Event Fired
Success — Tracking Event Fired
Error — Missing Event ID
Error — Missing Transaction ID
Error — Lead Not Found
Error — Invalid Event ID
Error — Duplicate Event
Status Codes
Comparison with Campaign-Specific Event Postback
Tips
- Preferred endpoint for buyers. If you are a buyer receiving leads from multiple campaigns within the same organization, use this global endpoint to avoid managing per-campaign event URLs.
- Event ID must exist in the matched campaign. Even though you do not pass a
cid, Pingtree resolves the campaign from thetransaction_id. Theevent_idmust be configured in that campaign’s event settings. - Revenue is required for conversion events. If the matched event is a conversion type, omitting
revenuereturns a 400 error. - Deduplication. If the campaign event has duplicate conversion disabled, sending the same
event_id+transaction_ida second time returns a 400 duplicate error. - Postback URL format. When configuring this as a server-to-server postback URL in a third-party platform, use a template like:
https://api.pingtree.com/api/event/global/org_5f1a2b3c?event_id=sale_completed&transaction_id={transaction_id}&revenue={payout}
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)