Guide

Why your Amazon affiliate links stop earning

Amazon affiliate income rarely stops with a bang. It leaks — link by link, video by video — while your dashboard still shows clicks. Here are the failure modes, roughly in order of how much money they cost creators, and how to catch each one.

1. The product was delisted (and your shortlink hides it)

Products disappear from Amazon constantly — sellers exit, models get replaced, listings get consolidated. When that happens, a retired amzn.to shortlink usually redirects to Amazon's homepage rather than showing an error. Your viewer lands on Amazon, shrugs, and either leaves or buys something unattributed. Nothing in your analytics screams "broken"; the clicks still count. This is the single most deceptive failure mode because every layer — YouTube, the shortener, Amazon — reports success.

2. The tag= parameter is missing

Your Associates tag (tag=yourname-20) is the only thing connecting a purchase to your account. Links lose it more often than you'd think: copying a URL before the tag was appended, sharing from the Amazon app, pasting a link a sponsor or editor sent, or trimming "ugly" URL parameters for a cleaner description. The product page loads perfectly. Every click sends Amazon free traffic. We wrote a whole guide on the missing-tag problem — it's the highest-value five-minute fix in affiliate marketing.

3. The product is out of stock — indefinitely

"Currently unavailable — we don't know when or if this item will be back in stock." The page exists, renders, and looks fine at a glance; a human has to actually read it. Sometimes stock returns; often "temporarily" means forever, especially for discontinued electronics and accessories — the exact things creators review. Checking this at scale requires product data, which is why Channel Workbench queries stock status through Amazon's official Creators API using your own free Associates credentials — never by scraping.

4. The 24-hour cookie found nothing to attach to

Even working links earn less than creators expect: the standard Associates cookie is about 24 hours (90 days only for items added to cart during the session). A viewer who clicks Tuesday and buys Friday earns you nothing. You can't fix Amazon's cookie policy — but it makes the fixable leaks above proportionally more expensive, because working links already convert a smaller slice than you'd hope. Losing attribution on top of that is the double hit.

5. The product's reviews collapsed

A product you recommended at 4.6★ can drift to 3.2★ two years later — quality changes, counterfeit sellers move in, or the model ages badly. The link works, the product's in stock, and your conversion rate quietly craters because buyers read reviews before purchasing. Worse, the recommendation now reflects on you. This one is invisible to every link checker that only tests liveness; it needs rating data from the API.

How to catch all five

One link: paste it into our free link checker — it follows the redirect chain, flags homepage fallbacks, and checks for a missing tag, no signup needed. A whole channel: a Channel Workbench scan reads every description over read-only YouTube access, checks every link, verifies Amazon stock and ratings through the official API with your credentials, and ranks findings by estimated revenue at risk — so you fix the leak that's costing $80/month before the one costing $0.40.

Check your whole channel in one scan

Channel Workbench connects to YouTube with read-only access — we can't edit, upload, or post anything — scans every description in your back catalog, and hands you a prioritized fix queue with an estimate of the revenue at risk. The Starter plan is free forever: one scan a month, top findings included, no credit card.

Related: How to find broken affiliate links on your channel · The missing tag= problem · Channel Workbench vs Youfiliate

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.