How do I inspect referrer collection in GA4 DebugView?

Definition: Referrer inspection in Google Analytics 4 (GA4) DebugView means opening a test event and examining its page_referrer parameter, the referring URL collected for that page. DebugView displays collected events and their parameters during a visit with debug mode enabled.

Key facts

• As of 17 October 2026, Google's DebugView documentation describes personal-device debugging through Google Tag Assistant and access through Admin, under Data display.
• Google's configuration reference specifies that page_referrer defaults to document.referrer and contributes to traffic-source computation.
• Google's pageview guide documents automatic page_view events on page loads and browser history changes.

How is a test visit prepared?

Google's DebugView guide recommends enabling debug mode on the personal device when troubleshooting a tag installation. Google Tag Assistant enables this mode for that device.

For an implementation using the Google tag's JavaScript interface, gtag.js, Google's troubleshooting guide provides this configuration example. G-XXXXXX is replaced with the measurement ID from the site's web data stream settings:

gtag('config', 'G-XXXXXX', { 'debug_mode': true });

The measurement ID in the configuration must match that stream's ID. The same guide says the Google tag snippet must be present on every page being measured.

Which event parameters need inspection?

A test visit follows the referring link to the site. In Google's documented DebugView interface, the report opens through Admin > Data display > DebugView. When several devices are debugging, DEBUG DEVICE selects the device under inspection. Clicking an event opens its associated parameters.

The test focuses on the landing page's page_view event. The parameter names to locate are:

page_referrer
page_location

Google's configuration reference defines page_location as the page's full URL, defaulting to document.location. It defines page_referrer as a URL identifying the referral source, defaulting to document.referrer. The test compares the collected page location with the destination visited and the collected referrer with the referring page.

Google's page-referrer definition allows the previous URL to belong to the site's own domain or another domain. An internal URL can therefore be a collected page referrer.

What should be checked when the expected event is missing?

Google's troubleshooting guide identifies incorrect measurement IDs and browser extensions that block Analytics scripts as possible causes. It also directs testers to inspect consent states in Tag Assistant and JavaScript errors in the browser console.

The pageview guide explains that send_page_view: false disables the default pageview sent by the configuration command. Browser-history pageviews have a separate enhanced-measurement setting, so that configuration parameter alone leaves history-based events enabled.

Related terms

• GA4 traffic acquisition
• Where is the page referrer stored in a GA4 BigQuery export?
• Referrer-Policy

FAQ

Can I use DebugView to confirm final acquisition attribution?

Google's DebugView documentation says its attribution analysis is limited and recommends acquisition reports for the most accurate attribution information.

Should I manually send another pageview for this test?

Google's pageview guide warns that sending manual pageviews while automatic pageview measurement remains enabled can produce duplicates.

Sources

1. Google Analytics Help, "Monitor events in DebugView", undated
2. Google for Developers, "Configuration", 5 October 2026
3. Google for Developers, "Measure pageviews", 13 October 2026
4. Google for Developers, "Verify and troubleshoot your Google Analytics setup", 14 October 2026
5. Google Analytics Help, "[TABLE] page_referrer", undated

---

Check how a page reads to answer engines. Open the GEO score analyzer