Skip to content

S2S postback, pixel and Smart Tag: how to track conversions

To know which link sold, the sale has to come back to whoever recorded the click. There are three ways to do it, and each one fits a different situation. Here's how they work and when to use each.

Updated · 7 min read

From click to sale

  1. Someone clicks the trackable link. TrackPath records the click, with source, UTMs and sub1 to sub5, and creates a unique identifier: the click_id.
  2. They reach the destination. If the destination link has the {click_id} macro (for example, ?aff_sub={click_id}), the identifier travels along to the store or the network.
  3. The sale happens. The store or the network tells TrackPath via pixel, postback or Smart Tag, and the conversion is tied to the click.
  4. The commission is calculated from the event (fixed or percentage) and, if you set it up, TrackPath notifies the affiliate or partner with an outgoing postback.

Pixel: the simplest way

A pixel is an invisible image placed on the thank-you page. When the page opens, the browser loads the image and the conversion is recorded. TrackPath knows which click the sale came from through a cookie set on the click, valid for 30 days.

  • Upside: installs in minutes, no developer needed.
  • Limit: it depends on the buyer's browser. Ad blockers, private browsing or closing the tab before the thank-you page can lose the sale. And the purchase has to happen in the same browser as the click.

S2S postback: server to server

With a postback, the sale is reported by the store's, platform's or network's server, not by the buyer's browser. It calls TrackPath's postback URL with the click_id and the sale details.

  • Upside: it doesn't depend on browsers, cookies or ad blockers. It's the most reliable method, especially for high-value sales or sales confirmed later (payment approval, deposit).
  • Requires: the click_id to reach the destination, through the {click_id} macro on the link, and the sales platform being able to call a URL when the sale happens. Many networks and platforms have a "postback" or "webhook" field for this.

Smart Tag: one tag, many scripts

A Smart Tag is a script tag installed once on the site. Its content is the script you register in the TrackPath dashboard: a remarketing pixel, a partner's tag, a conversion. To change the script, you change it in the dashboard, and the site never needs editing again.

It can record the conversion, like a pixel, or just deliver the script without recording anything, which is useful for tags that fire on every page.

The three methods side by side
PixelS2S postbackSmart Tag
Where it runsThe buyer's browserThe store's or network's serverThe visitor's browser
Who installs itWhoever runs the site (one tag)Whoever runs the sales systemWhoever runs the site (one tag)
Ad blockersCan block itNo effectCan block it
Best forGetting started fastHigh-value sales and networksPartner scripts and remarketing

Outgoing postback: notify the affiliate

When you have affiliates, networks or sub-affiliates as channels, TrackPath can notify each of them of their sales. Every channel has its own postback URL, with macros filled in at send time:

  • {click_id}: the click identifier.
  • {payout}: the commission amount.
  • {status}: pending, approved, refused or paid.
  • {order_id}, {price} and {currency}: the order, the amount and the currency.
  • {af_sub1} to {af_sub5}: the parameters the affiliate sent on the click.

You choose which statuses trigger the notification. If the partner's server doesn't respond, TrackPath retries on its own and keeps a log of every delivery.

Which one to use?

  • Start with the pixel if you control the thank-you page and want results today.
  • Use an S2S postback whenever the platform or network allows it, especially with paid traffic and high-value sales.
  • Use a Smart Tag when partners ask for scripts on the site and you don't want to call a developer every time.
  • You can use all three in the same campaign: the type is chosen per event.

See how it works for affiliates, advertisers and agencies.

// CONTINUE THE PATH

Paid traffic

Step 2 of 3

  1. UTM builder
  2. 2S2S postback, pixel and Smart Tag: how to track conversions · you are here
  3. 3TrackPath vs UTMify: which one to choose?
Next step · GuideTrackPath vs UTMify: which one to choose?
See all learning paths
// IN THE TRACKPATH DASHBOARD

The full training on this, "Measure every ad: sub IDs, UTMs and postback", is in the dashboard from the Advanced plan up (in Portuguese).

See plans

Frequently asked questions

What's the difference between a pixel and a postback?

A pixel is fired by the buyer's browser; a postback, by the store's or network's server. A postback isn't affected by ad blockers and doesn't depend on cookies.

What is a click_id?

It's the unique identifier of each click. It goes to the destination through the {click_id} macro and comes back in the postback, so the sale is tied to the right click.

Do I need a developer?

For the pixel and the Smart Tag, you just paste a tag on the site. An S2S postback needs whoever configures the sales platform or network, usually in a postback URL field.

Can I send the sale to my affiliate?

Yes. Add their postback URL to the channel: on every sale or chosen status change, TrackPath sends the data with the macros you define.

Pixel, postback and Smart Tag in one dashboard.

  • 7 days free on any plan
  • no credit card
  • cancel anytime