Global Event Postback API

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 the transaction_id automatically. No cid is required in the request body.

Endpoint#

POST /api/event/global/{org-id}

Replace {org-id} with your organization's unique ID (available in your Pingtree dashboard under account settings).

Authentication#

No token-based authentication header is required. The org-id path parameter scopes the request to your organization.

Request Parameters#

Path Parameters#

Body Parameters (JSON)#

Example Request#

curl -X POST "https://api.pingtree.com/api/event/global/org_5f1a2b3c" \
  -H "Content-Type: application/json" \
  -d '{
    "event_id": "sale_completed",
    "transaction_id": "txn_7f3a2b1c-4d56-78ef-9012-abcdef123456",
    "revenue": 85.00
  }'

Non-Conversion Event#

curl -X POST "https://api.pingtree.com/api/event/global/org_5f1a2b3c" \
  -H "Content-Type: application/json" \
  -d '{
    "event_id": "application_submitted",
    "transaction_id": "txn_7f3a2b1c-4d56-78ef-9012-abcdef123456"
  }'

Example Responses#

Success — Conversion Event Fired#

{
  "status": 200,
  "message": "Event triggered successfully",
  "data": {
    "cid": "cmp_9z8y7x6w",
    "pid": "src_abc123",
    "transaction_id": "txn_7f3a2b1c-4d56-78ef-9012-abcdef123456",
    "conversion_id": "conv_a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "conversion": true
  }
}

Success — Tracking Event Fired#

{
  "status": 200,
  "message": "Event triggered successfully",
  "data": {
    "cid": "cmp_9z8y7x6w",
    "pid": "src_abc123",
    "transaction_id": "txn_7f3a2b1c-4d56-78ef-9012-abcdef123456",
    "conversion_id": "",
    "conversion": false
  }
}

Error — Missing Event ID#

{
  "status": 400,
  "message": "event_id is required"
}

Error — Missing Transaction ID#

{
  "status": 400,
  "message": "transaction_id is required"
}

Error — Lead Not Found#

{
  "status": 400,
  "message": "No lead found for the provided transaction_id in this organization"
}

Error — Invalid Event ID#

{
  "status": 400,
  "message": "Invalid event_id — event not configured for the associated campaign"
}

Error — Duplicate Event#

{
  "status": 400,
  "message": "Duplicate event for this transaction_id"
}

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 the transaction_id. The event_id must be configured in that campaign's event settings.
• Revenue is required for conversion events. If the matched event is a conversion type, omitting revenue returns a 400 error.
• Deduplication. If the campaign event has duplicate conversion disabled, sending the same event_id + transaction_id a 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}