Note: This tab is available in Custom Source (CS), Marketing Partner (MP), and Media Channel (MC) source types.

The Postbacks tab allows you to configure postback URLs for a specific source. Postbacks are a way to notify the source about user actions or campaign events, enabling deeper performance tracking and optimization.

​
What is a Postback?

A postback is a server-to-server communication triggered by user actions or lead events. It enables the exchange of information — such as lead status or conversion — between Pingtree and the traffic source’s own tracking system.

​
How is a Source Postback Used in a Pingtree Campaign?

When a traffic source sends you leads, they may want feedback on those leads for two main reasons:

  1. To track which leads generated revenue.
  2. To analyze lead performance quality for optimization.

Although Pingtree offers a partner/affiliate portal, sources — especially Marketing Partners and Custom Sources — often prefer to receive data on their own platforms via postbacks.

A source postback is triggered based on events configured in your campaign or manually fired as needed.

​
What’s Required?

To configure a source postback, the source must provide the following:

  1. Postback URL

    • The endpoint on their server where Pingtree will send the data.

  2. Data and Field Mapping

    • Only data captured with the lead can be dynamically sent.
    • You must map Pingtree’s fields to the source’s expected field structure.
    • You can also include static fields with predefined values.

  3. Request Method

    • Pingtree supports both GET and POST requests.

  4. Payload Format

    • Default: POST request in JSON format.
    • Optional formats:
      • xml-8 & xml-16
      • x-www-form-urlencoded
      • form-data

​
Postback Types

You must choose what type of postback to configure:

​
Form Data Postback

  • Trigger: Fired immediately upon lead distribution completes.
  • Use Case: General data feedback, real-time tracking.

​
Event Data Postback

  • Trigger: Fired when a specific Pingtree event occurs (e.g., lead sold, converted, rejected).
  • Use Case: More controlled and conditional tracking (e.g., payout confirmation, conversion approval).

By setting postbacks properly, you ensure your traffic sources receive accurate feedback, which can be used to improve lead quality, ROI, and campaign efficiency.