A shortened link that does not track has, in nearly every documented case, lost the referral parameter somewhere between the click and the final landing page. The redirect still resolves, the page still loads, and the affiliate identifier (for example ?ref= or ?via=) is no longer in the URL when the advertiser's tracking script runs. This article sets out the mechanisms that produce that outcome, a test sequence that isolates which one applies, and the point at which a manual check becomes an audit task.
TL;DR
- A shortened link fails to track when the referral parameter does not survive the full redirect chain, not when the short link itself fails to load. Tapfiliate's troubleshooting documentation describes cut-off parameters as a direct cause of undetected clicks.
- The parameter can be removed by the shortener, by a JavaScript redirect, or by a CDN, consent-management or security layer on the advertiser's side.
- Verification must be performed on the final landing page URL, and then confirmed with a test click logged in the affiliate platform.
- A link that returns 200 OK can still be commercially unhealthy (discontinued product, homepage redirect, unverifiable tracking path), which is why status-code checkers alone do not settle the question.
- Owned-domain redirects (for example
yoursite.com/go/product) remove dependence on a third-party shortener's redirect logic.
Table of Contents
- What "not tracking" means in practice
- How a shortened link carries (or loses) an affiliate ID
- Diagnostic sequence: isolating where the parameter disappears
- Comparison of causes, evidence and classification
- When the shortener itself is the risk
- Disclosure requirements do not change with link length
- Why a status-code check does not settle the question
- Our perspective: evidence before repair
- What an audit adds to a manual check
- Prevention: configuration choices that reduce failures
- FAQ
- Sources
What "not tracking" means in practice
Three separate failure states are routinely described with the same phrase, and they require different tests.
- The short link does not resolve. The shortener is offline, the link was deactivated, or the destination returns an error. This is a Broken link in the classification used throughout this article.
- The short link resolves, but the identifier is missing at the destination. The page loads normally, and the affiliate parameter is absent from the final URL. This is the most common state behind complaints of "clicks but no conversions," and it is typically classified as Needs Attention until the redirect chain is inspected.
- The identifier arrives, but the commercial path is no longer valid. The product is unavailable, the destination redirects to a generic homepage, or the program's tracking path has changed. The link is technically intact and commercially unhealthy.
The classification terms used here are Broken, Needs Attention and Healthy. A link is Healthy only when the destination is live, relevant to the anchor, and carries its identifier on the final page.
No link-level inspection can confirm that a commission was credited. Crediting is recorded inside the merchant's or network's system. What can be established from outside is the condition of the link: whether it resolves, where it ends, and whether the parameter is still present. The remainder of the decision stays with the publisher.
How a shortened link carries (or loses) an affiliate ID
An affiliate tracking link identifies the publisher through a query string appended to the advertiser's URL. AffiliateBase's documentation on tracking parameters states that a shortener is acceptable only if it passes query parameters through, and advises testing before wide distribution. A short link is a stored mapping from a short path to a full destination URL. When that mapping is configured correctly, the server answers with a redirect and the full destination, parameters included, reaches the browser. One shortener vendor's explainer makes the same point, with the qualification that this holds when the redirect is clean (a vendor's description, and therefore a statement of the design intent rather than an independent test).
The parameter is lost when something in the chain rewrites, truncates or discards the query string. The documented mechanisms are listed below.
Redirect services that do not forward the query string
Some redirect configurations store only the base URL. If a sub-ID or a campaign tag is appended to the short link at the time of sharing, the service may drop it instead of forwarding it. Tapfiliate's guidance identifies redirect services that do not pass query strings as a common cause, alongside incorrect URL syntax where parameters are placed after, rather than before, the redirect occurs.
Hashed network links with appended parameters
Some affiliate networks generate shortened links on their own side. TUNE, for example, offers a Generate Tiny URL option that replaces the visible parameters with a hashed version. Appending a sub-ID to an already-hashed link requires that the hash be preserved exactly and that the extra string be added with a standard question mark delimiter. An altered hash, or a second shortening layer placed over the hashed link, can break the mapping while the link continues to load.
JavaScript (client-side) redirects
Server-side 301 and 302 redirects pass the request, including the query string, to the next location. Client-side redirects behave differently: according to Tapfiliate's troubleshooting material, a JavaScript-based redirect may not forward the complete query string, so the referral parameter can disappear before the tracking script initializes on the landing page. Tracking that depends on a script reading the parameter on first load is exposed to this failure.
CDN, consent-management and security layers
A correctly configured shortener does not guarantee a correct outcome. AffiliateBase notes that a privacy-oriented CDN, a consent-management platform or a security layer such as Cloudflare can remove query parameters on the advertiser's side. The shortener has done its work; the advertiser's infrastructure then strips the identifier. This case cannot be fixed from the publisher's side, but it can be documented, and the evidence can be sent to the program manager.
Site changes after the link was created
Tapfiliate's guidance also names site changes such as SSL implementation or CDN updates as a frequent source of silent tracking failure for links that were not re-tested. A link that worked at publication in 2021 is not evidence of a link that works in 2026.
Diagnostic sequence: isolating where the parameter disappears
The sequence below moves from the cheapest check to the most conclusive. Each step produces a result that can be recorded (URL observed, status code, parameter present or absent) so that a pattern across many links becomes visible.
Step 1: Capture the full redirect path
Follow the short link and record every hop: the status code at each step, the URL it points to, and whether the query string is present. Redirect-path checkers display the complete chain for shortened links, and browser developer tools (Network tab, with "Preserve log" enabled) show the same information along with any JavaScript-initiated navigation.
Step 2: Compare the final URL with the intended URL
The test that Tapfiliate's documentation describes is whether the referral parameter persists on the final landing page. If it is present in the original destination but absent at the end of the chain, the redirect configuration is the likely cause. If it is present at the end of the chain, the problem is downstream (cookie handling, tracking script, program configuration).
Step 3: Test the unshortened destination directly
Paste the full tracking URL into a clean browser session, with no extensions that remove tracking parameters. Browser privacy extensions and some in-app browsers strip parameters on their own, which can mimic a shortener fault. Repeat with the short link. A difference between the two outcomes locates the fault in the shortener; identical outcomes point to the destination.
Step 4: Check the console and script timing
In the browser console, look for redirection errors and determine whether the advertiser's tracking script fires before or after the redirect completes. A script that initializes after the parameter has been removed cannot record the click, regardless of the link's appearance.
Step 5: Register a test click in the platform
Affiliates are advised to confirm that the tracking platform logs a test click before distributing a link widely, because programs differ in how they read parameters (some only on the initial page load, others through server-side configuration). A test click that does not appear in the dashboard, after the program's stated reporting delay, is a Needs Attention finding with evidence attached.
For teams that already count outbound clicks, comparing recorded clicks against page impressions with a CTR calculator offers a quick sanity check: a page that holds steady traffic while the click rate on a monetized anchor falls toward zero deserves inspection before a platform-side explanation is assumed.
Comparison of causes, evidence and classification
| Cause | Observable evidence | Typical classification | Who can act |
|---|---|---|---|
| Shortener drops query string | Parameter present before shortening, absent at final URL | Needs Attention | Publisher (change redirect type or domain) |
| Altered or double-shortened network hash | Link loads, network's click log shows no entry | Needs Attention | Publisher |
| JavaScript redirect | Parameter missing after navigation, no server redirect in the chain | Needs Attention | Publisher or advertiser |
| CDN, CMP or security layer strips parameters | Parameter present in request, absent in the URL the page script sees | Needs Attention | Advertiser or program manager |
| Shortener or short link deactivated | Error page or interstitial instead of destination | Broken | Publisher |
| Destination unavailable or sent to generic homepage | 200 OK, product absent, URL changes to site root | Broken or Needs Attention (review of product page needed) | Publisher |
| Clean chain, parameter intact, product live | Parameter on final page, test click logged | Healthy | None |
The distinction between Broken and Needs Attention is evidential. A link is Broken when the failure is confirmed (the destination does not resolve, or the product has been withdrawn). It is Needs Attention when the evidence is incomplete or the cause lies outside the publisher's visibility, such as a tracking path that cannot be verified from the page.
When the shortener itself is the risk
Dependence on a third-party shortening service adds a failure point that the publisher does not control. Google's goo.gl service is the most widely known case. Google announced in July 2024 that goo.gl links would stop working after August 25, 2025, and then revised the plan on August 1, 2025 to preserve actively used links, deactivating those that showed no activity in late 2024. Coverage of the revision notes that inactive links had displayed an interstitial warning since August 23, 2024. A goo.gl link in an older article is therefore one of two things: preserved and working, or deactivated. Visiting it is the only reliable check; a link that redirects without a warning page is operating.
The broader lesson is structural. When a provider sunsets a service or changes its redirect logic, every link built on it is affected at once. Redirects on a domain the publisher owns (for example /go/product-name) keep the redirect logic, and the parameter handling, under the publisher's control. A branded path also permits the publisher to update a single destination when a program changes its tracking URL, instead of editing every article that references it.
The shorter-link question is also covered in the compliance-first 80/20 audit of shortened affiliate links, which treats shorteners as one category within a broader link inventory.
Disclosure requirements do not change with link length
Shortening a link does not alter the disclosure obligation. The FTC's guidance for influencers states that disclosures are likely to be missed when they appear only on an About Me page, at the end of a post, or behind a "more" button, and that disclosures should not be buried in a group of hashtags or links. Because a short link obscures the destination from the reader, the disclosure placed next to it carries more weight, not less. The related audit procedure is documented in the six-step FTC affiliate disclosure audit.
Why a status-code check does not settle the question
Most link checkers report HTTP status codes. A 404 or a 410 is a clear Broken finding. A 200 OK, however, establishes only that a page was served. It does not establish that the page is the intended product, that the parameter is retained, or that the program still pays on that path.
Three patterns recur among links that return 200 OK and are nevertheless commercially unhealthy:
- Unavailable products. The page loads, but the product is discontinued or out of stock, so the monetized anchor sends a qualified reader to a dead end.
- Redirects to a generic homepage. The merchant retired the product URL and forwards all requests to its root. The click is delivered; the intent behind it is not.
- Unverifiable tracking paths. The identifier is absent or altered, or the program's tracking domain no longer matches the link structure, so the click path cannot be confirmed from outside.
These are the categories examined in more detail in the pieces on affiliate links that stop earning and on finding missing affiliate IDs.
Our perspective: evidence before repair
We approach a non-tracking short link as an evidence problem first. In the audits we run, the publisher's usual starting assumption is that the shortener is at fault. Sometimes it is. Often the redirect chain is intact and the loss occurs at the destination, or the destination no longer sells the product. Replacing every short link on that assumption costs time and may leave the real cause in place.
Three principles govern how we report these findings.
- Separate confirmed from unconfirmed. A confirmed Broken link and a Needs Attention link that requires manual review are listed separately, so the publisher does not treat uncertain items as proven failures.
- Evaluate links that still load. A link returning 200 OK is examined for product availability, homepage redirection and tracking-path integrity, because status codes alone leave these conditions invisible.
- Identify, do not repair. We do not alter links, and we do not claim to verify that commissions were credited or to quantify income that was lost. We report the condition of each link and the evidence for it, with suggested replacements where a better destination exists. The publisher decides what to change.
Our view is that prioritization matters more than completeness. A site with several hundred monetized anchors rarely has the time to inspect each one, but it can act on a ranked list in which pages with the most traffic and the clearest failures come first. Our research on affiliate link health and the 2026 benchmark describe how we structure that classification.
— Michael N.
What an audit adds to a manual check
The diagnostic sequence above is practical for a handful of links. It does not scale to an archive of several years of articles, where short links, network links and direct links coexist and where each program changed its structure at a different time.
Affiliate Link Audit performs manual and semi-automated audits of monetized links, classifies each finding as Broken, Needs Attention or Healthy, and delivers a prioritized action plan that separates clear fixes from items requiring manual review. The full audit is priced at $97 as a one-off purchase, and each engagement starts with a free sample so the evidence format can be assessed before any payment. The sample report shows the structure, and the publisher page describes the scope. To request the full audit, start from the Affiliate Link Audit homepage.
For publishers who want to work through the process themselves first, the guides on evidence-first affiliate link testing and on auditing affiliate tracking that is not working set out the procedure in more detail.
Prevention: configuration choices that reduce failures
The following practices follow from the documented failure mechanisms. They reduce exposure; they do not eliminate it, because advertiser-side changes remain outside the publisher's control.
- Use an owned-domain redirect path for recurring programs, so that destination updates are made in one place.
- Prefer server-side redirects (301 or 302) to JavaScript redirects wherever the platform offers the choice.
- Do not stack shorteners. A shortened link placed behind another shortener, or over a network-generated hash, adds hops where the query string can be altered.
- Preserve hashed links exactly and append sub-IDs only with the delimiter the network specifies.
- Re-test after site changes such as SSL migrations, CDN changes or consent-banner updates, on your own site and, where visible, on the merchant's.
- Log a test click in the affiliate platform before distributing a new link widely.
- Keep a link inventory with the short URL, the final destination, the program, the date last tested and the result.
- Place the disclosure beside the link, in clear language, as the FTC guidance describes.
Where a program has closed, the better course is often to replace the destination instead of repairing the link; the approach is outlined in the piece on replacing dead affiliate programs, and the broader process for locating failed links in prioritizing broken affiliate links.
FAQ
Why does my shortened affiliate link load but record no clicks?
The most common reason is that the referral parameter was removed during the redirect, so the page loads normally without the identifier. Check the final landing page URL for the parameter, then test the unshortened link in a clean browser session. If the parameter is present in one case and absent in the other, the shortener or an intermediate layer is the likely cause.
Do URL shorteners always strip affiliate parameters?
No. A shortener that stores the full destination URL and issues a clean redirect passes the query string through, and AffiliateBase's documentation permits shorteners on that condition. Problems arise with services that drop query strings, with stacked shorteners, and with client-side redirects. Each link should be tested before wide distribution.
Are old goo.gl links still working?
Partly. Google revised its plan on August 1, 2025, and deactivated only the goo.gl links that showed no activity in late 2024, while preserving those in active use. Visit the link: if it redirects without a warning page, it is operating. If it shows an interstitial or an error, it should be treated as Broken and its destination replaced.
Can a link return 200 OK and still earn nothing?
Yes. A 200 OK response confirms that a page was served, not that the product is available, that the parameter survived, or that the program's tracking path is current. Links in this state are typically classified as Needs Attention and reviewed individually. Whether a specific click earned a commission can only be confirmed in the network or merchant report.
Sources
- Troubleshooting: Why is a Conversion Not Being Tracked? (Tapfiliate Help Center)
- Affiliate Tracking URL Parameters (AffiliateBase)
- Generating Tracking Links (TUNE)
- Do Short Links Keep Your Tracking Parameters? (Flyn)
- We're updating our plans for goo.gl links (Google)
- Google changes course on goo.gl shutdown, preserves actively used links (PPC Land)
- Disclosures 101 for Social Media Influencers (FTC)
Recommended
- Shortened Affiliate Links: Compliance First 80/20 Audit for Marketers
- Publishers: 5 Tests to Find, Classify, and Fix Missing Affiliate IDs
- Audit First, Use Evidence to Fix Affiliate Tracking for Publishers
- Stop Losing Commissions: Audit Cloaked Affiliate Links for Publishers
This article was produced with AI assistance and reviewed for accuracy. Findings language ("Broken," "Needs Attention," "Healthy") reflects Affiliate Link Audit's evidence-based classification system.