Documentation
How link monitoring works
How QuietLeaks checks affiliate links, what failure modes it detects, and how the alert system works.
The check process
When QuietLeaks checks a link, it does not just ping the URL for a status code. It runs a full browser-level check:
Initial HTTP request
QuietLeaks fetches the affiliate URL with realistic browser headers (Chrome/Firefox user agent, correct accept headers) to avoid being blocked as a bot.
Redirect chain following
Every redirect hop is followed and recorded — including JavaScript-rendered redirects that require a headless browser. The full redirect chain (original URL → hop 1 → hop 2 → final URL) is stored for each check.
Destination analysis
The final URL is analysed: is it the merchant homepage? A 404? A generic category page? Does it contain the expected affiliate tracking parameter? Each check produces a status: healthy, broken, redirected, or slow.
Status comparison
The new status is compared to the previous check. If the status changed from healthy to broken (or vice versa), an alert is triggered.
Alert delivery
Email (and Slack on Pro/Agency) alert fires within 60 seconds of status change detection. Alert includes the 30-day click count so you know the revenue impact immediately.
Failure modes detected
QuietLeaks detects 6 failure modes. Only the first is caught by standard link checkers.
The destination URL no longer exists. Product discontinued, page removed, or merchant shut down. Caught by all checkers.
Link returns 200 OK but redirects to the merchant homepage or a generic category page instead of the intended product. Affiliate tag lost. Standard uptime monitors report this as "healthy". QuietLeaks detects the destination mismatch.
Product page loads correctly but the redirect chain strips your affiliate tracking parameter (?tag=, &aff_id=, etc.). Sale is unattributed. Happens when merchants update URL structure or networks rotate link formats.
Modern affiliate networks (Impact, PartnerStack, newer ShareASale links) build the final redirect URL using JavaScript at click time. HTTP-only checkers can't follow this. QuietLeaks uses a full browser environment to execute JS and follow the real redirect chain.
Merchant server is down or returning errors. Typically temporary but still triggers an alert so you know revenue is at risk during the outage.
Link does not respond within 10 seconds. Retried 3 times with exponential backoff before flagging as broken.
Check schedule by plan
Alert types
Broken alert
Fires when a link goes from healthy to broken. Includes the link label, URL, failure mode, and 30-day click count.
Recovery alert
Fires when a previously broken link is detected as healthy again. No action needed — your link is back.
Silent redirect alert
Fires when a link starts redirecting to a homepage or incorrect destination even though it returns 200 OK.
Alert throttle: if a link is already flagged broken, no repeat alert is sent for 24 hours. Recovery alert is sent when the link passes its next scheduled check.