Skip to content

What is S2S postback tracking? How it works

Novaxnetwork explains S2S postback tracking as a way for one server to notify another that a tracked conversion event has occurred. S2S means server-to-server. In a common affiliate setup, the advertiser returns a click identifier to the tracking platform, allowing the platform to connect the event with its original referral.

A postback can report a lead, sale, registration, or another agreed event. Recording that event and approving a commission are separate decisions, so a successful callback does not automatically establish that a lead is payable.

How does S2S postback tracking work?

The click-ID-based process has two parts: identifying the referral and reporting the subsequent event.

  1. The tracking platform records a click. It creates or associates an identifier with the referral and its offer information.
  2. The advertiser receives that identifier. The tracking link passes it through a parameter the advertiser’s system recognizes.
  3. The advertiser preserves the identifier. It must remain connected to the relevant session, lead, order, or customer record.
  4. A defined event occurs. The advertiser sends a server request containing the identifier and the required conversion information.
  5. The receiving platform processes the request. It checks the supplied data, records the result, and applies the configured attribution and commission rules.

The person completing the form does not need to be redirected back to the network for the server callback itself. However, the preceding referral still needs to be captured correctly.

The guide to click IDs in affiliate tracking explains the identifier’s role in connecting clicks with later activity.

What is S2S postback tracking
How does S2S postback tracking work?

Why can different systems have different click IDs?

A traffic partner, a network, and an advertiser may each maintain their own records. Their identifiers do not have to be identical, but the integration must preserve the relationship between them.

Consider this hypothetical mapping:

Record Example value Purpose
Partner’s original click ID pub_731 Lets the partner recognize its own referral
Network’s click ID net_482 Connects the advertiser’s callback with the network’s click record
Advertiser’s conversion reference lead_901 Identifies the reported lead event in the advertiser’s records

The advertiser returns net_482 to the network. When notifying the partner, the network returns the stored partner reference pub_731 through the agreed field. Sending the network’s identifier in a field expecting the partner’s original identifier can prevent the partner from matching the conversion.

Use the receiving system’s supported fields for this mapping. The explanation of sub-ID tracking in affiliate marketing covers how additional referral values can travel alongside a campaign’s main identifier.

What does a postback URL look like?

The reserved example domains and parameter names below illustrate the flow. Use the real endpoint and supported fields supplied by the receiving platform when configuring an integration.

First, a landing-page URL passes the network’s click reference to the advertiser:

https://advertiser.example/quote?ref=net_482

After the defined lead event, the advertiser’s server sends a callback containing that same reference:

https://tracker.example/postback?click_id=net_482&event=lead&conversion_id=lead_901

The parameter receiving the identifier on the landing page is called ref in this example. The callback uses click_id. The names can differ because the systems agree how the stored value is mapped.

Macros are placeholders replaced by actual values when a system builds a URL. Their syntax and meaning are platform-specific. If a request expected to contain a stored identifier still contains an unresolved placeholder, inspect the macro and where substitution should occur.

What is S2S postback tracking
What does a postback URL look like?

Choose the event trigger before configuring the URL

Define the business milestone the callback represents. A form button click, a successfully stored inquiry, an email confirmation, and an approved lead can occur at different times. The sender should report the event agreed for that integration.

For example, an offer may require a confirmed registration. A notification sent when the person first opens the form would describe an earlier action. Conversely, waiting for a later manual review when the receiver expects an immediate pending event can make the initial report appear incomplete.

Document how the advertiser’s event names map to the receiver’s goals. Names such as lead and sale in this guide are illustrative; the real platform may require specific event identifiers. Where several milestones are supported, keep their meanings and duplicate-handling rules separate.

Which information should a postback contain?

The receiving platform determines the required fields. A useful integration specification distinguishes these roles:

Information What it establishes
Referral identifier Which tracked click or other supported referral record receives credit
Event or goal Whether the callback represents a signup, lead, purchase, or another milestone
Conversion reference Which event is being reported, subject to the platform’s duplicate-handling rules
Amount and currency What monetary value is supplied and how the receiver should interpret it
Status and authentication data How the event should be processed and whether the request meets access requirements

Do not infer a field’s meaning from its name alone. A platform’s transaction ID may identify a click, while another system uses similar wording for a conversion or order. Match the documented purpose at both ends.

Keep revenue and payout values separate

A purchase value, the network’s revenue, and the partner’s commission are different amounts. A callback carrying a $100 sale value does not establish a $100 affiliate payout.

Confirm whether the receiver calculates commission from offer settings or expects an explicit amount. The distinction between RevShare and CPA affiliate marketing matters when commissions depend on revenue rather than a fixed amount.

For variable payments, agree on the revenue base, currency, adjustments, and which final value is forwarded downstream. This avoids applying a revenue-share percentage twice or reporting revenue as commission.

The callback reports monetary information; it does not transfer funds. An approved commission can still await settlement under the applicable payment schedule.

What is the difference between incoming and outgoing postbacks?

An incoming advertiser postback sends conversion information to the network. An outgoing partner postback sends the relevant information from the network to the partner’s tracking system.

These are separate integrations. An advertiser callback can record correctly while the outgoing partner callback fails because its URL, identifier mapping, trigger, or authentication is incorrect.

Review each direction independently. Establish which event or status triggers the outgoing notification and whether subsequent updates are sent. Do not assume an amount revision automatically generates another callback.

What is S2S postback tracking
What is the difference between incoming and outgoing postbacks?

How does S2S differ from browser-based pixel tracking?

A browser-based conversion pixel depends on a browser executing or loading the conversion request. An S2S callback is sent by a server after the configured event is recognized.

The comparison of pixel tracking vs S2S postback examines those implementation differences. For S2S, the practical benefit is moving the conversion notification to a server integration; the initial referral still needs a working capture and storage method.

If that storage depends on browser state that is lost, the server may lack the identifier it needs. S2S alone therefore does not establish complete cross-device attribution or eliminate every browser-related dependency.

How should you test a postback integration?

Use an agreed test environment or authorized test flow. Follow the complete referral journey so the callback is checked against a genuine test click.

  1. Record the test click. Retain the relevant identifiers and campaign context.
  2. Inspect the landing-page handoff. Confirm that the expected value reaches the advertiser through the correct parameter.
  3. Verify storage. Establish that the identifier remains associated with the lead or order.
  4. Trigger the specified event. Confirm that the sender uses the intended endpoint, HTTP method, and event mapping.
  5. Check the receiver’s result. Inspect the response body, processing logs, and recorded conversion.
  6. Verify the downstream notification. If a partner callback is configured, check its identifier, amount, status, and receipt separately.

Test status behavior as well as delivery. If an incoming event is pending and the outgoing callback is configured to fire only after approval, no immediate partner notification may be the expected result. Verify that rule before diagnosing a delivery failure. The test should confirm the intended business flow, not merely make a callback fire.

Check the required HTTP method explicitly. Some affiliate postback endpoints require GET requests despite the word “postback.”

TUNE’s server postback implementation guide notes that its endpoint can return HTTP 200 even when conversion processing is unsuccessful. Read the application-level result and verify the recorded event instead of relying on the HTTP status alone.

Why might a postback fail to record correctly?

Observed problem What to check
Unknown click identifier Capture, storage, truncation, unresolved macros, and identifier validity
Request received but event rejected Response details, required fields, offer settings, and authentication
Wrong event recorded Goal mapping and the event selected by the sender
Wrong monetary amount Revenue-versus-payout mapping, currency, and calculation settings
Network records a conversion but partner does not Outgoing callback trigger, delivery logs, and original partner ID mapping

For troubleshooting, retain the test timestamp with its timezone, referral identifiers, offer and event references, request method, redacted request details, and response body. Compare these records at the sender and receiver to locate where the expected event stops appearing.

A request missing from receiver logs calls for a different investigation from a request rejected with a specific processing error. An accepted event with the wrong amount points toward value mapping or calculation settings.

Also check the attribution window in affiliate marketing and the platform’s identifier-retention rules. Receiving a callback does not automatically extend the period during which an action qualifies for credit.

What is S2S postback tracking
What is S2S postback tracking

Why might a postback fail to record correctly?

A timeout can leave the sender uncertain about whether the receiver processed an event. Agree on retry behavior and duplicate handling before launch. Follow the receiver’s documented event-key rules so a repeated notification does not become an unintended additional conversion.

Keep legitimate separate events distinguishable from retries. A lead submission and a later purchase may require different goals or references rather than being treated as copies of one event.

Use HTTPS and the receiver’s supported authentication controls, such as verification tokens or IP restrictions where available. Limit the transmitted fields to what the integration needs and keep credentials out of public examples and shared diagnostic screenshots.

Frequently asked questions

Does S2S tracking replace an affiliate tracking link?

The tracking link identifies the referral before conversion. The postback reports a subsequent event. In a click-ID-based setup, both parts must work together.

Does a successful postback mean the lead is approved?

Not automatically. A request can report an event that is pending, on hold, or subject to validation. Check the recorded status and the offer’s commission rules.

Can I use the same postback URL across all platforms?

Use the endpoint, parameters, macros, and authentication required by each receiving system. Similar-looking URLs can expect different identifiers or interpret an amount differently.

Can S2S report changing RevShare amounts?

An integration can support variable amounts when its fields and update behavior are configured for them. Confirm how initial values, later adjustments, and downstream notifications are handled before relying on the reported commission.