A referrer is request context indicating the previous page. Direct traffic is usually a bucket for events without a usable referrer; it does not prove that somebody typed or bookmarked the short URL.
Plan before publishing
Referrers can disappear when traffic moves between apps and browsers, privacy policies suppress data, a platform opens an external browser, security software rewrites the request, or the source intentionally removes the header.
- Tag campaigns before shortening.
- Test inside the real source application.
- Document what your analytics tool labels as direct.
Build and test the workflow
A newsletter link opened inside a mail app may reach the redirect with no useful referrer. If the destination carries utm_source=newsletter and utm_medium=email, the campaign context remains available even when the referrer is blank.
Worked example
Publish one tagged test link per meaningful channel, open each through the real app or placement, and record redirect source, final URL and destination report. Test copied links separately because sharing changes context.
Measure the right outcome
Use referrer as supporting evidence and UTM values as explicit campaign labels. Compare source reports over the same period, and do not overwrite acquisition data by adding campaign UTM parameters to internal navigation.
Troubleshooting checklist
- Direct traffic rises: inspect apps and privacy changes.
- Source is fragmented: normalize UTM naming.
- Internal traffic changes attribution: remove campaign UTM tags.
Product limits and responsible use
A referrer can be missing, truncated or misleading, and UTM values can be copied or altered. Neither proves a person’s identity or a conversion; destination-side events remain necessary for outcomes.