URLTO GUIDE
Record requests, sessions and signups as separate metrics
Keep separate collection stages when comparing link activity with destination results. Combining them hides where a journey problem might occur.
URLTO editorial · Updated
Click activity · series08 / 10
Input and processing example
Compare it yourself · Illustrative example
설명용 표 / Illustrative columns URLTO 요청 / Requests: 120 목적지 세션 / Destination sessions: 별도 분석값 / separate analytics value 신청 완료 / Signups: 원본 시스템 기록 / original-system record
Steps to verify
- Name each metric and collection location.
- Compare time windows and tagging conventions.
- Test the signup completion journey.
How to interpret the result
The 120 is a request example, not a basis for inventing session or signup counts. Review collection rules, repeats, periods and destination behavior when values differ.
Deciding what to do next
More requests without more signups can prompt questions about forms, audience or exposure. Do not report redirect growth as revenue growth.
Feature scope
Clicks count short-URL redirect requests, not unique people, confirmed human scans, signups or revenue. Tests and repeat requests can be included.
Frequently asked questions
Does URLTO automatically collect destination conversions?
This activity measures redirect requests. Check conversions in the destination’s separate analytics or completion records.