Tracking Pixel

A tracking pixel is a small piece of code, traditionally a one-by-one transparent image, that loads when someone opens a page or email. The moment it loads, the visitor's browser sends a request to a tracking server, and that request carries useful context:

• The page URL
• A timestamp
• Any identifiers already stored in the browser

In affiliate marketing, pixels are one of the oldest ways to confirm that a referred visitor completed a valuable action. A program places a conversion pixel on its signup or order confirmation page, and every time that page loads, the tracking platform learns a conversion happened and can credit the right affiliate.

How it works in B2B SaaS

The flow starts at the click. A visitor clicks an affiliate link, and the tracking platform stores an identifier: typically a cookie in the browser plus a click ID in its own database.

When that visitor later completes the action the program pays for, the confirmation page loads the pixel. The pixel request includes the stored identifier plus any values the page passes along, such as plan name or order amount. The platform matches the identifier to the original click and records a commission.

B2B SaaS adds a wrinkle: the money often arrives weeks after the click. A pixel can fire at trial signup, but the paid conversion happens later, often with no page load the visitor ever sees. That is why most SaaS programs pair pixels with server-side tracking such as postback URLs, which report conversions machine to machine.

A worked example

Imagine a project management SaaS, Planlio, that pays affiliates 20% recurring commission on a $50 per month plan. An affiliate sends 1,000 clicks in a month, and the tracking platform sets a cookie on each click.

Of those visitors, 40 start a free trial. The trial confirmation page fires the conversion pixel 40 times, each request carrying the cookie value from the original click. The platform successfully matches 36 of them; the other 4 are lost to ad blockers or cleared cookies, which is normal for client-side tracking.

Ten of the tracked trials convert to paid. At $50 per month and 20% commission, the affiliate earns $10 per customer, or $100 per month in recurring commission. Planlio also fires a server-side postback at the paid upgrade, so conversions the pixel missed can still be credited if the click ID survived.

Typical ranges and benchmarks

The pixel itself is typically a one-by-one transparent GIF or a few lines of JavaScript. Its size is negligible and it does not visibly affect page load.

Cookie windows in SaaS affiliate programs commonly run 30 to 90 days. That matters because some browsers now cap cookies set by JavaScript at around 7 days, so a pixel-and-cookie setup can undercount conversions in longer sales cycles.

Client-side tracking commonly loses a share of conversions to ad blockers and privacy features. There is no universal percentage, but programs that add server-side tracking typically recover conversions the pixel alone would have missed, which is why hybrid setups are now the norm.

Tracking Pixel vs Postback URL

These two are confused constantly because both report conversions. A tracking pixel is client-side: the visitor's browser fires the request, so it depends on the page loading, scripts running, and cookies surviving.

A postback URL is server-side: the advertiser's server calls the tracking platform directly when a conversion is recorded in its own database. No browser is involved, so ad blockers and cookie limits cannot interfere.

The practical rule: pixels are easier to install, often just a tag in a tag manager, while postbacks are more reliable and better suited to recurring SaaS revenue. Mature programs treat postbacks as the source of truth.

How it shows up in affiliate and partner programs

When you join a program or network, the setup checklist usually says something like "place the conversion pixel on your thank-you page." Networks generate the pixel code, and most marketing teams deploy it through a tag manager.

Program managers also meet pixels when running multiple networks at once. If two networks each have a pixel on the same confirmation page, one sale can trigger two commissions, so deduplication logic is required.

Consent management applies too. In many jurisdictions a tracking pixel should only fire after the visitor consents to tracking, so the pixel usually sits behind the consent banner rather than in the raw page source.

Common mistakes

• Placing the pixel on a page the user can reload or revisit, which double counts conversions unless the platform deduplicates by order or account ID.
• Firing the pixel at the wrong event. If commissions are paid on paid subscriptions but the pixel fires at trial signup, reporting and payouts will never reconcile.
• Relying on a pixel alone for a long B2B sales cycle. Between cookie caps and ad blockers, a meaningful share of legitimate conversions will go uncredited, which quietly demotivates good affiliates.

Frequently asked questions

Common questions about tracking pixels in affiliate programs.

Do tracking pixels still work with ad blockers and privacy features?

Partially. Ad blockers block requests to known tracking domains, and browser privacy features shorten the life of the cookies pixels rely on. Pixels still capture a large share of conversions, but serious programs back them up with server-side postbacks so a blocked pixel does not mean a lost commission.

Is a tracking pixel the same as a cookie?

No. The pixel is the mechanism that sends a request to the tracking server, while the cookie is the identifier stored in the browser. They usually work together: the click sets the cookie, and the pixel reads and reports it at conversion time.

Where should a SaaS company place its conversion pixel?

On the page that confirms the event you pay commission on. If you pay per trial, that is the trial confirmation page. If you pay on revenue, fire a server-side event at payment instead, because there is often no reliable page load at that moment.