Amazon Associates

How to Add Multiple Amazon Tracking IDs (and Structure Them Right)

$29in stock

Creating a new Amazon tracking ID is trivial — a two-minute job in Associates Central. Structuring your tracking IDs so they actually tell you something is the real skill, and it matters more than almost any other Amazon setup decision. Here's why, and how to do it right.

First, the mechanics

Your Store ID is your master account identifier — one per account, ending in the regional suffix (-20 for the US, -21 for the UK, and so on). Tracking IDs are additional tags you generate within that one account to segment performance. They all roll up to the same Store ID; they are not separate accounts.

To add one: in Associates Central, open your account menu and click Manage Your Tracking IDs, then Add Tracking ID. Name it, and you get a new tag alongside your main one — yoursite-20 might be joined by yoursite01-20 or yoursite-kitchen-20. When you build links (via SiteStripe or manually), you pick which tracking ID to attach, and Amazon's reports let you view all tags together or filter to one.

Two gotchas worth knowing before you start:

  • The limit is 100 tracking IDs per account. Plenty for most publishers; you can ask support to raise it, without a guarantee.
  • Tracking IDs cannot be deleted. Whatever you create is permanent, so a naming scheme beats improvising.

Also: don't solve multi-site tracking by opening multiple Associates accounts. That violates Amazon's terms and splits your sales across accounts. Tracking IDs within one account are the sanctioned way.

Why structure matters more than setup

Here's the part most guides skip. Amazon reports your earnings only by tracking ID — never per page, never per product for ordinary Associates. That single fact makes your tracking-ID structure the entire attribution granularity you get. Whatever segments you want to compare — sites, sections, placements — you can only compare them if they carry different tags. Miss it at setup, and that data is gone; Amazon won't reconstruct it retroactively.

Tracking-ID granularity: what each level revealsYour tag structure is your attribution granularityRECOMMENDED BASELINEcoarsegranular1 account tagtotal onlyPer sitewhich site earnsPer verticalwhich sectionearnsPer placementtable vs inline(CRO)Per pageestimate viaclick-share100-tag cap per account \u00b7 tags can't be deleted \u2014 plan your naming scheme before you start.
Amazon only reports earnings per tracking ID, so the tags you create decide exactly how finely you can see what earns. One tag per site is the non-negotiable baseline; per-vertical adds section-level insight; per-placement helps CRO tests. Per-page is the one level Amazon won't give you — that's where click-share estimation takes over.

So treat tags as a deliberate measurement plan, not an afterthought:

  • Per site — the baseline. One tag per site is non-negotiable the moment you run more than one site on an account. Without it, "which site earns?" is unanswerable.
  • Per vertical or section — the useful next step. On a broad site, a tag per major category (site-kitchen-20, site-outdoors-20) tells you which section of your content actually monetizes, which is often surprising.
  • Per placement — for CRO. Different tags on a comparison table versus inline links let you A/B test which placement earns, right down to the same page.
  • Per page — don't. Tagging every page would blow the 100-tag cap and become unmanageable, and it still wouldn't give you true per-page earnings. Per-page is the level Amazon simply won't report.

The trade-off is granularity versus manageability. More tags mean more insight but more discipline applying the right tag to every link — and the un-deletable 100-tag ceiling means you can't tag infinitely. For most operators the sweet spot is per-site everywhere, plus per-vertical on your bigger sites.

Closing the per-page gap

Structure gets you segment-level truth — which site, which section, which placement. What it can't get you, at any tag count, is which individual page earns, because that's the wall Amazon puts up for ordinary Associates. That last mile is where estimation comes in: with clean per-site or per-vertical tags feeding real earnings, you can push those figures down to the page by click share — a page's share of a tag's clicks approximates its share of that tag's earnings. It's an estimate, not a statement from Amazon, but it turns "this section earned $X" into a usable per-page EPC.

This is exactly the input Clickolytics is built to use: it imports your Amazon earnings by tag, maps tags to sites, and estimates per-page earnings from the click share it tracks first-party. Good tag hygiene on your end plus click-share estimation on ours is how per-tag reporting becomes per-page insight.

Turn per-tag earnings into per-page insight: Clickolytics imports your Amazon earnings by tracking ID and estimates what each page earns from click share. See how it works →

The bottom line

Adding tracking IDs is easy; the value is in structuring them before you need the data. Tag every site separately, add per-vertical tags on your larger sites, use per-placement tags for the tests you actually run, and write down your naming scheme so future-you isn't lost in a hundred permanent, cryptic tags. Do that, and Amazon's per-tag-only reporting stops being a limitation and starts being a measurement system — one that click-share estimation extends the rest of the way to the page.

Frequently asked questions

How do I add a tracking ID? Associates Central → account menu → Manage Your Tracking IDs → Add Tracking ID. It creates a tag alongside your main one; all roll up to one account.

How many can I have? 100 per account (ask support for more, no guarantee). They can't be deleted — plan naming first.

Separate tag per site? Yes — the baseline for multi-site accounts, since Amazon reports only per tag. Don't use multiple Associates accounts (TOS violation).

Multiple tags on one page? Yes — ideal for A/B testing placements (table vs inline). Keep it documented; every tag counts against the 100 cap.

Related reading