S2S postback conversion tracking

What is a postback URL?

A postback URL is an endpoint one server calls to report an event to another. For S2S conversion tracking in Nevect, your affiliate network or offer sends a conversion to the Postback URL on your tracking installation. Nevect uses the returned click ID to match that conversion to a recorded visit.

This is the incoming direction. An outgoing postback sends a conversion from Nevect to a traffic source and uses that source’s external click ID. Configure and verify the two directions separately.

Before you configure it

You need a working campaign, an offer that accepts a sub-ID, and a partner that can return that value in a server notification. First verify a controlled click. Keep outgoing source postbacks disabled for the isolated test.

A partner macro and a Nevect token are expanded by different systems. Copy their exact syntax from the corresponding editor.

1. Pass the tracker click ID to the offer

In Offers, edit the destination URL and put {clickid} in a sub-ID parameter accepted by your partner. For example, if the partner supports sub1:

Saved offer URL:
https://offer.example/landing?sub1={clickid}

Illustrative destination after a visit:
https://offer.example/landing?sub1=NV_CLICK_001

NV_CLICK_001 is an illustrative value, not a valid test click. Use the actual ID from your installation. If the offer already has query parameters, append with & rather than a second ?. Check the final destination after redirects; the partner must receive the value, not literal {clickid} text.

2. Copy the incoming URL from Nevect

Open Settings → Tracking links and copy the generated Postback URL. Use the URL belonging to this installation and its reachable tracking domain. Preserve its generated path; do not substitute a campaign link, website account URL or an endpoint copied from another tracker.

The settings include a basic conversion URL and a URL with status parameters. Start with the variant matching the data you intend to send.

3. Map the partner’s return macros

In the partner’s postback configuration, replace the returned click-ID placeholder with the macro that returns your saved sub-ID. For a partner that documents {sub1} and {payout}, the parameter mapping would be:

cnv_id={sub1}&payout={payout}

These are illustrative partner macros. They are not portable between networks. Verify the partner’s current parameter names, macro syntax and supported notification events before saving.

If you configure a status, make sure a processing rule accepts the test value. A notification arriving at the server does not guarantee that a conversion was counted.

4. Verify one controlled conversion

1. Open your test Campaign URL once and find the visit in Clicklog.
2. Confirm that its offer URL carried the same Nevect click ID to the partner.
3. Copy the generated incoming Postback URL. Replace its click-ID and payout placeholders with this actual click ID and a known test amount.
4. For an isolated request, add disable_postback=1. Use only the test status that your processing scheme is configured to handle, or the basic URL when no status is needed.
5. Open the resulting test URL once, then inspect Clicklog and Conversions for that campaign and time range.
6. Confirm the click association, payout, currency and status. Check the relevant report as a separate step.

For example, the resolved query fields might read:

cnv_id=ACTUAL_TEST_CLICK_ID&payout=1.50&cnv_currency=USD&disable_postback=1

Put these fields on the generated endpoint, replacing its existing placeholders. Do not add duplicate cnv_id or payout parameters. An HTTP 200 alone is not attribution evidence.

Repeated, delayed and changed statuses

A network may send a pending lead, an approval and later a correction for one click. Decide which notifications should count as conversions and how revenue should change before enabling them. Check the offer’s Upsell setting and the selected processing scheme. Do not assume all repeated notifications are automatically harmless or that every status means another sale.

When a report differs from the partner, compare the same click, notification time, timezone and status policy. A conversion arriving after the original visit may appear differently under different report scopes.

Common failures

For browser-based conversion reporting, see conversion pixels. Continue with outgoing traffic source postbacks only after the incoming test is correct.

Evaluating Nevect for your campaigns? Review the tracking workflow and current license terms.