Guide · Reviewed 2026-09-03
How DISIAR filters bots, prefetches and rapid repeats before adding an outbound click to a public listing record.
A verified outbound click is an accepted navigation through DISIAR's outbound route after automated requests, prefetches, malformed clients and rapid repeats have been filtered. It represents an outbound action, not a lead or sale.
Browsers, link preview systems, security scanners and bots can request a URL without a person deliberately choosing it. Counting every request would inflate the public number and make comparisons meaningless.
DISIAR checks request method, navigation intent, browser signals, known automation patterns and rapid-repeat identity before accepting a new click. Rejected requests are retained only as a bounded integrity audit, not added to the listing total.
The click ledger proves that DISIAR accepted an outbound navigation under its published filtering rules. It does not prove that the destination loaded completely, that a unique person was identified across devices, or that the visitor converted.
The destination owner should compare tagged sessions in their own analytics. Privacy controls, browser blocking and attribution windows can produce legitimate differences between the two systems.
Synthetic monitoring must never call the public outbound route merely to manufacture health evidence. Technical checks should use separate endpoints and remain outside customer-facing totals.
Refunds and payment reversals affect commercial totals according to the Rules, while historical accepted clicks remain an account of past visitor actions.