Sub-ID Tracking

A sub-ID (also written as SubID, SID, or s1 depending on the platform) is an extra parameter an affiliate appends to a tracking link. The tracking platform stores whatever value is passed and shows it back in reporting, right next to the clicks, conversions, and commissions that link produced.

It matters because affiliates rarely have just one placement. Without sub-IDs, a month of commissions is one blended number. With them, you know exactly which article, email, button, or ad drove each conversion, which turns guesswork into optimization.

How it works in B2B SaaS

An affiliate takes their base tracking link and appends a label, for example ?subid=crm-comparison-table. When the click passes through tracking, the platform stores the sub-ID with the click record and its click ID.

When a conversion later fires, whether through a pixel or a postback, the sub-ID rides along with it. Reports can then be segmented by sub-ID: clicks, trials, paid customers, and commission per label.

This is especially valuable in B2B SaaS because the metric that matters is not clicks but paid conversions weeks later. A placement that wins on traffic can lose badly on revenue, and only sub-ID level reporting reveals that.

A worked example

A niche review site promotes a CRM product that pays 25% recurring commission on a $100 per month plan, so each paid customer is worth $25 per month to the affiliate. The site tags its links with three sub-IDs: best-crm-listicle, crm-deep-review, and newsletter.

After a month, the three placements reported the following:

• The listicle sent 600 clicks, 12 trials, and 3 paid customers.
• The deep review sent 300 clicks, 15 trials, and 6 paid customers.
• The newsletter sent 100 clicks, 5 trials, and 2 paid customers.

The listicle looks strongest on traffic, but the review converts 2% of clicks to paid against the listicle's 0.5%, and now earns $150 per month recurring from half the traffic. The affiliate responds by linking more prominently to the review and rewriting the listicle's call to action. That decision was only possible because of sub-IDs.

Building a sub-ID convention that scales

Most platforms support at least one sub-ID field, and many support several, commonly up to five. Decide early what each field means, for example: field one for the site or channel, field two for the page, field three for the position on the page.

Keep values short, lowercase, and URL-safe: letters, numbers, and hyphens. A value like pricing-cta-top is a good sub-ID; a full sentence with spaces and punctuation is not.

Never put personal data in a sub-ID. Names, emails, and user IDs of your visitors do not belong in a tracking parameter, both for privacy reasons and because many programs prohibit it.

Sub-ID Tracking vs UTM Parameters

These get mixed up because both are labels appended to URLs. The difference is who reads them. UTM parameters are read by the advertiser's own analytics tool and describe incoming traffic for the site owner.

Sub-IDs are read by the affiliate tracking platform and flow back into the affiliate's own reporting, attached to commission records. The advertiser's analytics never needs your sub-IDs, and your affiliate dashboard never shows their UTM breakdowns.

The two coexist on one link: the advertiser's analytics reads the UTMs while the tracking platform reads the sub-IDs. Neither interferes with the other.

How it shows up in affiliate and partner programs

Platforms name the parameter differently: subid, sid, s1 through s5, or similar. The mechanics are the same everywhere: pass a value on the click, get it back in reporting.

Program managers read sub-ID data too. It shows which placements a top affiliate relies on, informs placement negotiations, and helps spot fraud, since a single sub-ID with wildly abnormal conversion rates deserves a closer look.

Sub-affiliate networks run entire businesses on one sub-ID slot: they place their own publisher's ID in it so commissions can be split correctly downstream.

Common mistakes

• Inconsistent naming. Values like blog-post, Blog_Post, and blogpost become three different rows in every report, and cleanup afterward is painful.
• Losing sub-IDs in redirects. Link shorteners and cloaking plugins sometimes strip query parameters, so test that your sub-ID actually survives the full journey to the tracking platform.
• Using one generic sub-ID everywhere, which defeats the purpose. If every link says subid=site, you have gained nothing over using no sub-ID at all.

Frequently asked questions

Common questions about sub-ID tracking.

Can I put anything I want in a sub-ID?

Technically most strings work, but keep values short, URL-safe, and free of personal data. Platforms may truncate long values or reject unusual characters, and personal data in a URL parameter is a privacy problem you do not want.

Do sub-IDs affect how commissions are attributed?

No. Attribution is handled by the click ID and cookie; sub-IDs are purely descriptive labels. Changing a sub-ID changes how a conversion is reported, never whether or to whom it is credited.

How many sub-ID fields do I need?

Start with one field and a strict convention that encodes channel, page, and position, such as blog-crm-review-top. If your platform offers multiple fields, split those components across fields for cleaner filtering later.