
Lead Reporting
Part of Lead generation data hygiene
Recording source information when tracking data is missing
Keep observed, self-reported and unknown enquiry sources separate so missing tracking does not become invented attribution.
Why source information goes missing before it reaches your reports
Source information is lost when links to your site lack UTM parameters, or when your site isn't integrated with the marketing and advertising platforms that send the traffic.
Redirects can strip UTM parameters from the URL. This includes redirects from one site to another and from a secure site (https) to a non-secure site (http).
URL shorteners can also strip referral details before the visitor reaches you.
Traffic from people who type your URL straight into a browser, or who follow links from offline documents such as PDFs and Word documents, arrives with no referral source attached.
Key Sources of Missing Tracking Data
- Redirects stripping UTM parameters
- Common with HTTP→HTTPS or cross-site redirects
- URL shorteners removing referral data
- Especially when not configured to preserve parameters
- Direct visits (no referral)
- Users typing URLs directly or using offline documents
- Ad blockers interfering with cookies
- Can result in (direct) / (none) traffic despite campaign exposure
Recognising (direct) / (none) as a missing-source signal
In Google Analytics, the "(direct)" source and "(none)" medium represent website traffic that doesn't have a clear referral source.
Treat it as a signal that source data is missing, not as a source in its own right. It doesn't tell you which site, email or social post sent the visitor.
Google Analytics suggests using this traffic to determine whether campaigns are effectively driving traffic, to ensure traffic sources are credited accurately, and to address technical issues that affect the data and the user journey.
Using (direct) / (none) as a Source Indicator
- ProsHelps identify technical issues in tracking; signals missing data rather than a real source.
- ConsMisinterpreted as a genuine source if not managed properly; can lead to incorrect attribution.
Recording source at the link: a standard UTM approach
Adding UTM parameters to destination URLs lets you see which campaigns refer traffic. When a user clicks a referral link, the URL parameters are sent to Analytics and the values appear in the Traffic acquisition report.
Three parameters should always be present. utm_source is the referrer (for example, google or newsletter4). utm_medium is the marketing medium (for example, cpc, banner or email). utm_campaign is the product, slogan or promo code (for example, spring_sale).
Optional parameters add detail. utm_id identifies a specific campaign or promotion, utm_term records a paid keyword, and utm_source_platform names the platform directing the traffic. utm_content differentiates creatives — such as two call-to-action links in the same email.
utm_creative_format (display, native, video, search) and utm_marketing_tactic (remarketing, prospecting) are also supported, but neither is currently reported in Google Analytics properties.
A summer sale email campaign might use utm_source=summer-mailer, utm_medium=email and utm_campaign=summer-sale, so traffic from the mailer can be separated from the in-app campaign.
UTM parameters are omitted from the Landing page + query string and Page path + query string dimensions. The values are populated in the Page location dimension instead, so check that dimension when you verify tagging.
Standardise the UTM strategy across every marketing effort — consistent values, case and separators — so that user behaviour is attributed accurately rather than split across near-duplicate names.
Source Tracking Methods: UTM Parameters vs. Self-Reported Data
- UTM ParametersAutomatically captured via URL tags; requires proper implementation and protection from redirects.
- Self-Reported SourceCaptured through form fields (e.g., 'How did you hear about us?'); useful for residual traffic without tracking data.
Protecting source parameters from redirects and link handling
Check your marketing links, email campaigns and social media posts to confirm they include the correct UTM tags, and that the parameters remain intact when visitors arrive at your website.
Walk each redirect in the journey and confirm the parameters survive to the destination. Keep the destination on https where you can.
Open each short link and confirm the final address still carries the tags before you send it.
After each send, check the campaign in the Traffic acquisition report against the source and medium you intended. If it lands under (direct) / (none), work back through the link, the redirect chain and the destination page.
Residual gaps: direct visits, offline documents and ad blockers
Some traffic will always arrive without source information. Visitors who enter the URL directly, and clicks on links inside PDFs or Word documents, are classified as (direct) / (none).
Ad blockers can interfere with tracking cookies used to identify traffic origin, which also results in (direct) / (none).
For enquiries that arrive through these residual paths, the enquiry record needs a source value that reflects what is actually known. Capture a self-reported source where you can — for example, a 'How did you hear about us?' field on the form or a question asked at intake. Keep observed, self-reported and unknown source values in separate fields or under a consistent labelling convention so that reporting can tell them apart.
Where neither observation nor self-report is available, use a controlled unknown value, such as 'not set' or 'unknown', rather than leaving the field blank or defaulting it to (direct). A blank field is indistinguishable from an unrecorded field, and (direct) is a tracking label, not a source the enquirer used.
Document these known gaps against your campaign calendar. A residual block of untagged traffic then has a recorded explanation for your known channels instead of being read as a campaign that failed to perform.
Priority Actions for Handling Unknown Source Cases
- Capture self-reported source via form fieldUse 'How did you hear about us?' on enquiry forms
- Use controlled unknown value (e.g., 'not set')Avoid blank fields or defaulting to (direct)
- Document known gaps in campaign calendarPrevents misinterpretation of untagged traffic as underperforming campaigns
Recording source data without capturing personal information
Google's policies require that no data be passed to Google that it could use or recognise as personally identifiable information (PII), including email addresses, personal mobile numbers and social security numbers.
For source tagging, the practical check is that URL paths, URL parameters and page titles are free of PII. The basic Analytics page tag collects the page URL and page title of each page viewed, and PII is often sent inadvertently in these.
If there is any possibility of PII in your URLs, URL parameters or titles, remove it. Data redaction is configured in the Admin section and needs no code.
It removes email addresses on a best-effort basis and removes URL query parameters you specify; it is only available for web data streams. You can also modify the URL or the page title before it is sent to Analytics by adding code to your tracking implementation.
Privacy-Compliant Source Tracking Workflow
- Check URLs, parameters, and page titles for PIIRemove email addresses, mobile numbers, or other identifiers
- Configure data redaction in Google Analytics AdminAvailable for web data streams only; removes PII automatically
- Modify URL/page title via code if neededCustom implementation to prevent PII transmission
Privacy obligations when source tracking collects personal information
If your source capture collects personal information, Australian Privacy Principles 3 and 5 apply. They set out when you may collect it and what you must notify the individual about; see the OAIC's APP guidelines for the detail.



