Cookie tracking and server-side tracking: what each one can and cannot see

Why browser cookies lose partner sales, and how a click ID stored on the server fills the gap.

A visitor clicks a partner link. The tracking script writes a cookie with the partner's ID. When the visitor buys, the script on the thank-you page reads the cookie and reports the sale. It is simple, and it works when the same browser makes the click and the purchase within the cookie's lifetime.

Where it breaks

Browsers now cap the lifetime of script-set cookies, sometimes to seven days or less. Ad blockers stop third-party scripts. People click on a phone and buy on a laptop. Each of these cases loses the sale, and the partner sees a click with no commission.

  • Short cookie lifetimes in some browsers
  • Blocked tracking scripts
  • Purchases on a second device
  • Subscriptions that renew months later

What server-side tracking adds

With server-side tracking, the click ID is passed to your site in the URL and stored with the customer record in your own database or billing system. When the sale or renewal happens, your server sends the click ID back in a postback. No browser is involved, so nothing can block or expire it.

Use both

The best setup records the click with a first-party cookie for quick attribution and also stores the click ID on the server. trackspot.ai accepts both and removes duplicates by order ID, so each sale counts once.

Try it on your own program

Start a 21-day trial with every feature on. No card needed. Or book a call and we set it up with you.