Total clicks count eligible redirect events. Unique clicks reduce repeated activity using privacy-conscious request signals. The first metric answers how much redirect activity occurred; the second estimates how many distinct visitors produced it.
Plan before publishing
Pick the denominator before comparing campaigns. Use total human clicks for delivery volume, estimated uniques for reach and repeat rate, bot clicks for automated inspection, and destination events for signups or purchases.
- State whether a chart uses humans, bots or all requests.
- Keep date range and time zone fixed.
- Use destination events for business outcomes.
Build and test the workflow
If a link records 1,500 human clicks and 1,050 estimated uniques, the difference suggests repeat activity. It does not prove that exactly 1,050 people clicked or that 450 people returned once. One person can use several devices, while several people can share network signals.
Worked example
Compare identical date ranges, time zones, link ownership and traffic filters. Social previews, security scanners, retries and browser prefetch can raise request counts; DrutoLink keeps classified traffic visible instead of silently treating every request as a person.
Measure the right outcome
A useful review pairs total clicks, estimated uniques, device and geography breakdowns with destination sessions and outcomes. Differences are expected because the redirect and landing page observe different stages.
Troubleshooting checklist
- Unique count jumps: inspect devices and privacy resets.
- Totals disagree: compare filters and funnel stage.
- Repeat rate looks extreme: investigate previews, retries and sharing.
Product limits and responsible use
Unique identification is an estimate, not identity verification. Guest links do not collect analytics, and a unique click does not establish consent, lead quality, installation, purchase or revenue.