Pricing Academy Blog

What is a postback URL?

How a postback URL reports a sale from one server to another, what goes in it, how it compares with a pixel, and a full worked example with RedTrack, a funnel and an affiliate network, plus the checks I'd run before buying traffic.

Summarize with:
Illustration: a loop of arrows runs from a click card to a cart card and back, and the monitor mascot points at the link tag returning on the lower arrow
The short answer

A postback URL is a web address that one server calls on another to say "this click just converted". It carries the click ID of the visit that bought, usually with the amount and the conversion type, so your tracker or network can credit the right ad.

Because a server sends it after the sale is recorded, it doesn't depend on the buyer's browser, cookies or ad blocker. It only works if the click ID made it onto your page and stayed with the visit.

I wouldn't spend a dollar on a campaign until one test click has made the full round trip.

On the about page I listed the things that leaked revenue between tools when I ran tracking for a direct-response company. One of them was "postbacks that broke when URLs changed". That's still the most common way they break. A postback is a simple request, and nearly every failure happens before it's sent, when the click ID gets lost on the way to the sale.

How a postback URL works

Every postback is one half of a round trip. The click ID goes out with the visitor and comes back with the sale.

Postback URL round trip diagram showing the click ID going from the tracker to the landing page, staying with the sale and coming back in a server GET.
Postback URL round trip: the tracker creates a click ID, the sale keeps it, and the postback hands it back so the tracker credits the right campaign.
  1. The ad click hits your tracker. It logs the click, with the campaign, ad and source it came from, and gives it an ID.
  2. The tracker redirects to your page with that ID in the URL, for example ?clickid=6710c2a94f1e8b0012d4a7f3.
  3. Your platform stores the ID with the visit. Whatever happens next, the sale is tied to that visit.
  4. The sale fires the postback. The platform puts the ID and the amount into the postback URL and sends one GET request.
  5. The tracker looks up the click and books the conversion on the campaign that sent it.

Steps 2 and 3 are where the work is. Step 4 is one line of configuration.

Postback URL parameters and macros

A postback URL is an ordinary URL with placeholders, called macros, that the sender fills in for each sale. RedTrack's format is a good example because it's so short (RedTrack, S2S conversion tracking):

https://track.example.com/postback?clickid={clickid}&sum={sum}&type={type}
Postback URL parameters diagram showing the tracking domain, the postback path, and the clickid, sum and type parameters of a RedTrack postback.
Postback URL parameters: the domain says which tracker, clickid says which click, sum says how much, type says which conversion.
PartWhat it doesWho fills it
track.example.comYour tracking domain in the trackerFixed, you paste it once
clickidWhich click to credit. Without it nothing is recordedThe sender, from the visit
sumThe payout or revenue to bookThe sender, from the sale
typeWhich conversion type, by nameThe sender, from your settings

The macro syntax belongs to the platform filling it in, which trips people up. In a tracker's postback URL the click ID macro might be {clickid}. On ClickBank's side the same idea is {tid}. On an ElasticFunnels page it's {click_id}. The names differ, but each one is that platform's way of saying "insert the ID here".

S2S tracking vs pixel tracking

S2S (server-to-server) tracking means the conversion is reported by a server calling a postback URL. Pixel tracking means a script in the buyer's browser reports it.

S2S tracking compared with pixel tracking in a diagram showing that a postback URL is sent by a server, while a pixel depends on the buyer's browser loading it.
S2S postback vs pixel: a postback is sent server to server after the sale, a pixel only fires if the buyer's browser loads it.

The two overlap more than vendor posts admit. Ad platforms like Meta now take server events too (that's what the Meta Conversions API is), and many setups run a pixel and a postback for the same sale. For an affiliate tracker, though, S2S is the default. The sale often happens on a network's checkout, where you can't place a pixel at all, and refunds happen days later with no page for a pixel to load on.

Where the click ID rides: sub IDs

When the sale happens on someone else's checkout, the click ID has to travel through their system and come back. Networks give you free parameters on the affiliate link for this, usually called sub IDs. You put your ID in, the network stores it with the order, and its postback hands it back.

  • ClickBank: tid on the hoplink, returned as {tid} in its postback (ClickBank, postback macros).
  • Other networks call them subid, sub1 or aff_sub. Same job, different spelling.

I'd put the click ID in the sub ID rather than a campaign name. The tracker already knows the campaign of every click, so the ID gives you the campaign and the ad and the source in one value. If you need both, most networks offer more than one sub ID.

Worked example: a RedTrack postback URL in ElasticFunnels

Here is the setup end to end: RedTrack sends paid traffic to a page built in ElasticFunnels, and ElasticFunnels posts every sale back to RedTrack. RedTrack's screens are described from its help centre. The ElasticFunnels screens are the real app on a demo brand.

1. In RedTrack: create the conversion types

RedTrack only files a conversion under a type name you've set up under Tools → Conversion tracking → Conversion type, and the names are case-sensitive (RedTrack, conversion types).

  • A type for the first sale, for example Purchase.
  • A type for upsells, for example Upsell.
  • refund and chargeback, lowercase. ElasticFunnels sends those two names as written.

Then check the duplicate mode. An upsell arrives on the same click as the first sale, so a mode that ignores duplicate postbacks drops it. RedTrack lets you set the mode per type, and a type's mode overrides the offer source's default. For the upsell type I'd use "Create new conversion", which books it as its own row.

2. In RedTrack: put the click ID on the offer URL

In the offer that points at your page, add the click ID macro to the URL, for example https://yourpage.com/presell?clickid={clickid}. RedTrack swaps in the real ID on every redirect. Copy the postback URL RedTrack gives you for your tracking domain while you're there.

3. In ElasticFunnels: add the RedTrack integration

Open Apps → Integrations → New integration and pick RedTrack.

RedTrack postback URL screenshot in ElasticFunnels showing the postback domain, the clickid parameter, the URL with clickid, sum and type, and Purchase and Upsell type names
RedTrack postback URL setup in ElasticFunnels: the tracking domain, the click ID parameter, the postback URL with its macros and the conversion type names (demo brand).
  • Postback Domain: your RedTrack tracking domain. The URL below updates with it.
  • Click ID Parameter: the name you used in step 2, here clickid.
  • Postback URL: paste RedTrack's URL, or build it in the parameter list, where each row maps a RedTrack parameter to an ElasticFunnels value: click ID, amount, type, order ID, customer and location fields, a timestamp and sub parameters.
  • First sale sends / Upsell sends: the type names from step 1. Left empty, both send conversion, and RedTrack can't tell a first sale from an upsell.

4. Decide which sales go to this RedTrack

Below the URL are two optional filters. Merchants limits the postbacks to the merchants you pick, and Affiliate Filtering takes a whitelist or a blacklist of affiliate IDs. If you run two RedTrack accounts, add a second integration with its own URL and filters.

What reaches RedTrack from there:

Event in ElasticFunnelsSent to RedTrack as
First sale on your checkoutYour "First sale sends" name
Upsell on your checkoutYour "Upsell sends" name
Refund on your checkoutrefund
Chargeback on your checkoutchargeback
Sale from a ClickBank, BuyGoods or JVZoo postbackYour "First sale sends" name
Upsell from a ClickBank or BuyGoods postbackYour "Upsell sends" name
Refund or chargeback from a ClickBank or BuyGoods postbackrefund or chargeback
Abandoned cart, decline, failed paymentNot sent

sum is the amount on the record: the order total for a sale on your checkout, and for a ClickBank sale your commission.

Network sales: ClickBank, BuyGoods and JVZoo

If you promote offers as an affiliate, the sale doesn't happen on your checkout. It happens on the network's, and the network reports it in its own postback. RedTrack's ClickBank guide covers the direct route: tid={clickid} on the offer URL, and ClickBank posts straight to RedTrack (RedTrack, ClickBank S2S). That works when RedTrack redirects straight to the hoplink.

With a presell page in between, the hoplink sits on your page, and tid holds one value. So ElasticFunnels relays it.

ClickBank S2S postback diagram showing tid on the hoplink, the ClickBank sale posted back, and the postback URL crediting the RedTrack click.
ClickBank to RedTrack postback through a presell page: tid carries the visit to ClickBank, the S2S postback brings the sale back, and the RedTrack postback credits the original click.
  1. RedTrack sends the visitor to your presell with ?clickid={clickid}, as in step 2.
  2. The CTA on the presell carries the visit's own ID: add tid={click_id} to the hoplink by hand. ElasticFunnels replaces {click_id} on every page view and doesn't add anything to affiliate hoplinks on its own.
  3. Add the ClickBank postback in ClickBank. In ElasticFunnels, add the ClickBank affiliate integration (Clickbank (Affiliate Postback S2S) in the app) and copy its Conversion URL. In ClickBank, open Integrations, Postback/Pixels, add one Custom Postback/Pixel for your affiliate account with the events Initial Purchase and Upsell Purchase, and paste the URL (every screen, step by step). Refunds and chargebacks arrive on the same URL, and ElasticFunnels reads their event type. If you copied the URL before 15 October 2026, copy it again: the current one also tells ElasticFunnels which sales are upsells.
  4. The sale comes back. ClickBank posts the receipt, the tid and your commission (its {affiliate_earnings} macro). ElasticFunnels matches tid to the visit.
  5. RedTrack hears about it. The visit still holds the RedTrack click ID from step 1, so the sale goes to RedTrack with the commission as sum, through the same integration as above. Upsells go under your upsell type, refunds under refund and chargebacks under chargeback. No automation to build.

BuyGoods and JVZoo sales take the same path, each with its own tracking parameter on the affiliate link (the integration page shows which). For JVZoo, the JVZoo tracking guide walks through tid, vtid and the refund URL. BuyGoods refunds and chargebacks reach RedTrack under their own types too. In BuyGoods the two URLs go in as postback pixels, inside one offer's account or in your profile for every offer (the BuyGoods screens), and the URL's {CONV_TYPE} macro tells ElasticFunnels which commissions are upsells. If you're still building the page in the middle, how to build an affiliate landing page covers it from template to tracked click. If you sell your own product on ClickBank rather than promote one, that's the vendor side, with a different integration: ClickBank funnel setup for vendors.

How to test a postback URL

Test with one real click before any traffic. It takes a few minutes, and it's the only proof that every link in the chain holds.

Postback URL test checklist diagram showing six checks, from the click ID on the landing URL to the conversion showing up in the tracker.
Postback URL test: follow one test click from the landing URL to the log row to the tracker's conversion report before you spend on traffic.
  1. Click your own RedTrack campaign link and read the address bar on your page. The click ID should be there under the name you chose.
  2. Buy once from that same visit, in the same browser. For a network offer, buy through the hoplink on your presell.
  3. Open Settings → Logs → External Postbacks in ElasticFunnels. Each RedTrack send is a row with the full URL and RedTrack's response code.
  4. Read the URL in the row. The click ID, the sum and the type should all be filled in, with no leftover {macro}.
  5. Find the conversion in RedTrack, on the campaign you clicked. A 200 in the log means RedTrack received the request. Its own reports tell you it counted it.
Postback URL log screenshot in ElasticFunnels showing RedTrack postbacks with clickid, sum and type filled in, a refund row and 200 response codes
Postback URL log: each RedTrack postback ElasticFunnels sent, with the full URL and the response code. The upsell shares its click ID with the first sale above it (demo brand).

Why postbacks fail

Most postback failures happen before the request is sent, so there's usually no error to see.

  • No click ID on the landing URL. A redirect, a link shortener or an offer URL without the macro drops it. Nothing is sent, and a skipped send leaves no row in the External Postbacks log. An empty log after a test sale points here first.
  • The wrong parameter name. RedTrack puts the ID in clickid, the integration reads sub1. Use the same name in both places.
  • A filter excludes the sale. A merchant or affiliate filter that leaves the sale out skips it the same silent way, with no log row.
  • No tid on the hoplink. The network sale comes back with nothing to match, so it can't find the visit or its RedTrack click.
  • A type name RedTrack doesn't know. purchase is not Purchase. Copy the names from RedTrack instead of typing them.
  • Upsells ignored as duplicates. The postback arrives and RedTrack drops it because the click already converted. Check the duplicate mode on the upsell type.

The first one causes most of the trouble, which is why the test starts at the address bar.

Postback URLs in ElasticFunnels

In ElasticFunnels the page, the checkout and the order record sit in one place, so the server that records the sale is the one that sends the postback. That's included on every plan.

  • RedTrack: sales, upsells, refunds and chargebacks from your checkout, and the same from ClickBank postbacks, each under the type name you set. BuyGoods sales, upsells, refunds and chargebacks go too, and JVZoo sales. See the RedTrack integration.
  • Network postbacks in: each sale lands on the click, page and split test that sent the buyer, so you also see which presell earns.
  • One log: every outgoing postback with its URL and response code, under Settings → Logs.
My take
  • Name your RedTrack types before you write a single postback URL. Fixing type names after a week of traffic means a week of conversions under the wrong label.
  • Send the network's commission as sum when you're the affiliate. Revenue you never receive makes every campaign look more profitable than it is.
  • An empty postback log after a test sale is good news in disguise. It tells you the click ID got lost on the way in, and that's usually fixed in the offer URL.
  • Re-run the test click whenever you change a URL: a new domain, a new presell, a new offer link. That's when postbacks break.

Postbacks look like the boring end of a campaign, a single line of URL that nobody reads once it's set. But that line decides what your tracker believes, and the tracker decides where the next dollar goes. Get one click through the full round trip, look at the row in the log, and you'll know your numbers are the real ones before you scale.

FAQ

Postback URL FAQ

What is a postback URL?

A web address one server calls on another to report a conversion. It carries the click ID of the visit that converted, usually with the amount and the conversion type, so the receiving tracker or network can credit the campaign that sent the click. It works without the buyer's browser.

How does a postback work?

The tracker gives each ad click an ID and passes it to your page in the URL. Your platform stores it with the visit. When the visit turns into a sale, the platform fills that ID and the amount into the postback URL and sends one GET request to the tracker, which looks up the click and credits its campaign.

What is the difference between a tracking URL and a postback URL?

They point in opposite directions. A tracking URL is the link people click: it goes out to your page and carries the click ID forward. A postback URL comes back after the sale: it is called by a server and carries the same click ID back to the tracker, plus the payout and type.

What does S2S mean in tracking?

Server to server. The conversion is reported by one server calling another, usually through a postback URL, instead of by a pixel in the buyer's browser. Ad blockers and closed tabs do not stop it, but it needs the click ID to be stored on the visit.

What is a sub ID in affiliate tracking?

A free parameter on an affiliate link where you put your own value, such as a click ID or a campaign name. The network stores it with the sale and hands it back in its postback. On ClickBank the main one is tid; other networks call them subid, sub1 or aff_sub.

Why is my postback URL not firing?

Most often the click ID never reached the landing page, or it arrived under a parameter name the platform does not read, so there is nothing to send. Other causes are a filter that excludes the sale, a missing tid on the hoplink, and a type name the tracker does not know. Start with a test click and read the address bar.

Can a postback URL report refunds?

Yes, if the sender supports it and the tracker has a conversion type for it. In ElasticFunnels, refunds and chargebacks from its own checkout and from ClickBank and BuyGoods postbacks go to RedTrack with the type refund or chargeback, so create those two type names in RedTrack exactly as written.

How do I test a postback URL?

Click your own tracker link, check that the click ID is on the landing page URL, buy once from that same visit, then look for the row in your platform's postback log and for the conversion in the tracker. In ElasticFunnels the log is Settings, Logs, External Postbacks.

Send every sale back to your tracker

Pages, checkout and RedTrack postbacks in one place, with a log of every send. Start a 14-day free trial.