Free Affiliate Sub-ID Generator

A sub-ID is a short value you append to an affiliate tracking link so the click and any resulting commission show up in the network dashboard under a label you chose. Every major network reserves a parameter for it, but each one spells it differently: Impact uses subId1, Rakuten Advertising uses u1, eBay Partner Network uses customid, Awin uses clickref, CJ uses sid, and ShareASale uses afftrack. The value itself is yours to invent, most affiliates encode the placement, page, or campaign that hosted the link.

No. The identifiers that get you paid are already on the tracking link, such as the campid on an eBay Partner Network link or your publisher id on an Awin click URL. The sub-ID rides along purely as a reporting label. It tells you which placement drove the click and the sale, it does not change whether the sale is credited to you.

Because a network only reads the parameter it documents, and there is no error message when you use the wrong one. Append utm_campaign to a ShareASale link and ShareASale records nothing, the reporting slot it reads is afftrack. Same story on every network: subId1 on Impact, u1 on Rakuten, customid on eBay, clickref on Awin, sid on CJ. This tool exists so you never have to remember which spelling belongs to which network.

On Impact it does. Impact treats the sub-ID value as case sensitive, and its postback macro {SubId1} is documented as case sensitive too, so summer-Sale and summer-sale are two different rows in your reporting. The safest habit across every network is to pick one casing convention, usually all lowercase, and never deviate from it.

Visibility. Impact documents the Sub ID parameters (subId1, subId2, subId3) as values only you can see in your reports. The sharedid parameter is a custom partner tracking value that is exposed to the brand and included in reports both sides can see. Use sharedid when the advertiser needs your placement split, and keep everything you would rather not share in the subIds.

Awin documents clickref2 to clickref6 (and pref2 to pref6) as non-public parameters that cannot be transmitted to the advertiser landing page. They still appear in your own Awin reporting, so they work fine for private splits, but any setup that expects to read them on the merchant side is broken by design. Put the value you need downstream in clickref itself, the one reference that does reach the landing page.

Impact documents letters and numbers only, up to 255 characters. Awin documents any combination of letters and numbers, up to 50 characters. eBay documents the Custom ID as an alphanumeric identifier of up to 256 characters. ShareASale documents an alphanumeric tracking string with no spaces or special characters, up to 255 characters. Rakuten documents the u1 value as up to 72 alphanumeric characters in its member ID documentation. CJ does not publish a hard limit on the public pages we could verify, so keep that value short and alphanumeric too. The tool warns you when a value falls outside a documented rule.

Inside each network dashboard, not in your own analytics. Impact reports them under Performance by Sub ID and Shared ID. eBay Partner Network has a Performance by Custom ID report plus a Custom ID column on the Transaction Detail report. Awin returns click references in its reporting, ShareASale shows afftrack in your reports, CJ shows the sid, and Rakuten returns u1. If you want the click in your own dashboard too, wrap the tagged link in a short link that counts clicks.

They answer the same question in two different dashboards. UTM parameters are read by your own analytics on your own site. Sub-IDs are read by the affiliate network and reported next to clicks and commissions in its dashboard. On an affiliate link the visitor lands on the merchant site, not yours, so your analytics never sees the pageview and the sub-ID slot is the one that matters. For links pointing at your own pages, use our UTM builder instead.

The sub-ID makes the round trip. You send your value out with the click, and when the network approves a conversion it substitutes the value back into your postback URL through a macro, {SubId1} on Impact, !!afftrack!! on ShareASale. That loop is what ties a specific sale back to a specific placement. Sub-IDs are for your reporting inside the network dashboard, and they pair naturally with server postbacks, which is what Flyn Pro conversion tracking provides on the links you shorten.

It should, because a shortener redirects to the exact destination URL you gave it, sub-ID included. The failures happen further down the chain, when an intermediate redirect rebuilds the URL and drops parameters. That is worth testing rather than assuming: paste the final tagged link into our affiliate link checker and it traces every redirect and tells you which parameters reached the destination.

Detection only covers host patterns we can verify: Impact click domains such as sjv.io and pxf.io plus goto.walmart.com and goto.target.com, click.linksynergy.com for Rakuten, awin1.com, the CJ click domains (anrdoezrs.net, dpbolvw.net, jdoqocy.com, kqzyfj.com, tkqlhce.com), shareasale.com, and eBay URLs that already carry campid. Anything else shows as not recognised. Pick the network from the dropdown and the correct parameter is still appended.

No. The tagged link is built with client side JavaScript in your browser, nothing you paste reaches our servers, and there is no server log of your links or sub-IDs. Pressing Generate fires one product analytics event containing the tool name, the action, and the detected network name, nothing from your link or value is in it. Successful generations are saved to a history list in your browser localStorage, capped at the last twenty entries, which you can clear from the panel.