PostBack Config

Overview

PostBack Config lets MyAdOptimizer fire a server-to-server postback to your endpoint whenever a tracked event happens on your traffic. It is managed from Exchange Manager > PostBack Config, under your Publisher profile.

Caution

Only a MAO sysadmin can create, edit, or delete a PostBack Configuration. If you need a postback set up or changed, please request it through your PE Manager.

This guide documents the configuration your PE Manager will set up on your behalf, so you know what to provide and what to expect on your endpoint.

Supported Trigger Event

A PostBack Configuration is created per Trigger Event. Today the only supported event is:

• Click — fired when a valid, tracked click happens on one of your Landing Pages.

Note

A Publisher can have at most one PostBack Configuration per Trigger Event. Since Click is currently the only event available, this means one Click postback per Publisher.

Configuration Fields

Field	Description
Endpoint URL	Your absolute http/https URL that will receive the postback.
HTTP Method	GET or POST.
Content-Type	Applies to the request body (e.g. application/json), used when HTTP Method is POST.
Active	Toggles whether the postback fires. Inactive configurations are kept but never dispatched.

Caution

Body parameters are not allowed when HTTP Method is GET. If your endpoint needs to receive data in the body, it must be configured as POST.

Request Parameters

Each parameter sent to your endpoint is mapped to a MAO field (placeholder) and a location: Query string, Body, or Header. The parameter name (key) is up to you — only the mapped value is fixed by MAO.

Supported Placeholders — Click

Placeholder	Description
{ClickID}	Unique click identifier
{Revenue}	Payout/revenue amount
{SourceID}	Traffic source ID
{Timestamp}	Event timestamp
{ExtClickID}	External click identifier (from the media exchange)
{CampaignID}	Internal ad campaign ID
{LandingPageID}	Internal landing page ID
{CustomVar1} … {CustomVar5}	Generic custom tracking variables

Headers

Headers are sent as-is with the request. A header value can be static text or include a placeholder from the table above (e.g. Authorization: Bearer {CustomVar1}).

Note

A header can be marked Sensitive. Once saved, its value is stored encrypted and is never shown back in plain text — it always displays as ********. This is intended for values like API keys or auth tokens.

Example Resolved Payload

HTTP Method: GET

Since GET requests cannot carry a body, all parameters must be configured with Location Query or Header.

Given a Click PostBack Configuration with HTTP Method: GET, two Query parameters, and one Header:

Endpoint (Query parameters appended):

https://your-endpoint.example.com/postback?cid=CL-1234567890&revenue=12.50

Headers:

Authorization: Bearer ********

HTTP Method: POST

With POST, parameters can also use Location Body, serialized per the configured Content-Type.

Given a Click PostBack Configuration with HTTP Method: POST, Content-Type: application/json, one Query parameter, one Header, and two Body parameters:

Endpoint (Query parameter appended):

https://your-endpoint.example.com/postback?cid=CL-1234567890

Headers:

Authorization: Bearer ********

Body (JSON):

{
  "revenue": "12.50",
  "source_id": "SRC-001"
}

Note

Placeholders are resolved with the real values from the click that triggered the postback at dispatch time. The values above are examples only.