← Docs Reference

Affiliate Link Glossary

June 27, 2026 · ValidateLinks

Definitions for redirect chain, hop, postback, aggregator, attribution leak, zombie link, double redirection, and other ValidateLinks terms.

Definitions for terms used across ValidateLinks documentation and validation reports.

Note

Terms are ordered from the building blocks of a redirect chain to the failure modes that cost payouts. Each definition matches the labels you'll see in ValidateLinks reports.


Redirect chain#

The sequence of HTTP redirects between the initial affiliate URL and the final landing page. Each step is a hop. ValidateLinks follows server-side redirects (301, 302, 303, 307, 308) and shows status, URL, and query param changes per hop.


Hop#

A single step in a redirect chain. One hop is one HTTP request that returns a redirect status code with a Location header pointing to the next URL.


Primary network (affiliate program)#

The system of record for click tracking and payouts in a performance marketing stack. Examples include CJ Affiliate, Impact, Awin, and PartnerStack. ValidateLinks labels detected networks as program on each hop.


Aggregator (sub-network)#

A gateway layer that sits between the publisher and the primary network, often used for commerce content or simplified integrations. Examples include Skimlinks and VigLink. ValidateLinks labels these as aggregator when detected.


Attribution cascade#

The ordered path a click must follow so the network and advertiser can attribute a conversion: publisher link → aggregator (optional) → primary network → advertiser landing page with tracking params intact.


Attribution leak#

When tracking or query parameters are lost somewhere in the redirect chain before the final URL. Conversions may not attribute back to the publisher. Page Scan flags these links; the link validator shows param deltas per hop.


Double redirection (double tracking)#

When two independent tracking layers both try to register the same click—for example publisher pre-track plus network redirect. Often causes cookie overwrite, click ID mismatch, and lost query params. See Double redirection and conversion loss.


Direct linking#

Pointing a link straight at the advertiser and manually appending query parameters, bypassing the network or aggregator. Usually results in zero attribution because the system of record never sees the click.


Parameter persistence (delta params)#

Whether query parameters are added, modified, or dropped at each hop. ValidateLinks compares params between hops and warns when mandatory program params disappear on the final URL.


S2S postback (server-to-server)#

A server-side callback from the advertiser to the affiliate network when a conversion occurs, using a click ID generated during the redirect. Preferred over pixel-only tracking for high-payout CPA offers when the click ID survives to the advertiser.


A URL that returns HTTP 200 OK but the page content indicates the offer is dead—e.g. "Out of Stock" or "Page Not Found". Users see a working link; conversions do not happen.


A URL our validator could not complete (timeout, 403, or similar). May work in a real browser; treat as "could not verify" rather than definitively broken.


A URL that returned a clear error (4xx other than typical bot blocks, or 5xx). The resource is missing or the server failed.


Geo-IP routing#

Merchant-side redirect logic that sends users to a regional store or currency based on IP. Normal after the primary network hop; distinct from double tracking when no second tracker registers the click.


Canonical attribution path#

The single intended redirect path where the network generates the click ID and all required params reach the advertiser. Validation confirms this path is intact.


Open interactive version · Validate a link · Page Scan