Measure results
Understand analytics
Read redirect counts and date ranges without mistaking them for unique people or verified sales.
Current product guide · Reviewed October 28, 2026
What is counted
An eligible GET redirect increments the lifetime visits counter and the UTC daily redirect count. Bots, repeat requests and your own tests can contribute. A HEAD request does not increment counts, choose an experiment variant or generate a conversion receipt. A password challenge that has not unlocked the link is not a completed destination redirect.
There are no unique-visitor, geographic, device or referrer breakdowns in the current product. Do not label redirect totals as people, impressions or confirmed destination-page loads. A 302 response records the redirect decision, not proof that the browser loaded the destination.
Read the right time window
Analytics defaults to the latest 30 UTC dates including today. You can select a link and an inclusive date range of at most 91 dates, ending no later than today. Today is incomplete. Compare equally sized, completed periods when you need a fair trend.
Lifetime visits and a selected period are different measures. Daily metrics are retained for approximately 90 days under the published cleanup policy; lifetime totals are separate. Older dates with no retained daily rows do not reconstruct historic traffic. Deleting a link is not an analytics archiving feature.
Conversions are submitted events
Conversions represent accepted, deduplicated lead, signup or purchase submissions associated with a valid receipt. They are not verified revenue, payment settlement or fraud-screened purchases. A visitor may generate more than one distinct event; conversion counts are not necessarily distinct people or a percentage bounded by 100%.
When numbers look unexpected
- Check UTC dates and whether you are comparing lifetime with period counts.
- Check whether your test used GET or HEAD and whether a password, expiration or moderation block prevented redirecting.
- Include bot/repeated visits in your interpretation; there is no bot-filtered audience metric.
- For conversions, check receipt expiry, token scope, the event UUID and whether recorded was false because the event was already accepted.
Still need a hand?
Use Help & support in your dashboard or support@li2.li. Share the action and a sanitized error, never a password, token or private reset link.