How to Test and QA UTM Parameters in GA4 DebugView and Realtime

Test campaign links before launch with your browser tools, GA4 Realtime and DebugView. These checks help you catch missing parameters and collection problems early. Once the data has processed, check the campaign in acquisition reports too.

Start by pasting the link into the free UTM checker. It confirms the source, medium and campaign values are present and flags uppercase letters, spaces and broken delimiters in seconds. Then use the GA4 methods below to confirm the visit is actually collected.

What to Check Before Launch

Testing tracking links before launch can help you check whether:

• Query strings are not stripped by server redirects.
• utm_medium properly matches GA4 Default Channel Grouping rules.
• Form submission capture scripts grab the incoming parameters for your CRM.

Method 1: Testing with GA4 DebugView (Recommended)

DebugView shows events from devices with debug mode enabled. It does not automatically exclude those events from ordinary reports. Configure and test a developer-traffic filter separately if required. DebugView also performs limited attribution analysis, so confirm attribution later in acquisition reports.

1. Enable debug mode for your device with Google Tag Assistant or GTM Preview, then open a complete test link:

   https://example.com/demo?utm_source=newsletter&utm_medium=email&utm_campaign=qa_launch

2. Open the link in an Incognito browser window.
3. In GA4, go to Admin > DebugView.
4. Select your device from the Debug Device dropdown in the top-left.
5. Click the incoming page_view and session_start events in the waterfall timeline.
6. Inspect the landing event’s page_location for the expected campaign URL. Confirm events arrive at the intended property, then check campaign dimensions in processed acquisition reports.

Method 2: Testing with GA4 Realtime Reports

If you prefer not to use debug flags:

1. Open your test link in an Incognito window.
2. Navigate to Reports > Realtime in GA4.
3. Review the incoming events and user snapshot. First user source describes initial acquisition and may differ from the current visit.
4. Use this to check collection; verify Session source / medium and Session campaign in Traffic acquisition after processing.

Method 3: Inspecting Network Payloads in Chrome DevTools

For technical marketers who want to inspect the exact outgoing hit before it reaches Google's servers:

1. Open Chrome DevTools (F12) and select the Network tab.
2. Filter the request list by collect?v=2.
3. Refresh your landing page with UTMs.
4. Click on the request to google-analytics.com/g/collect.
5. Inspect the destination measurement ID and collected page URL. Confirm the landing URL includes the expected UTMs and the event reaches the correct property. Transport fields vary by implementation; do not require a fixed list of abbreviated campaign fields. Redact identifiers before sharing request captures.

Worked example: a newsletter launch

This is an illustrative QA scenario, not a measured customer result. A newsletter links to /demo?utm_source=newsletter&utm_medium=email&utm_campaign=october_demo&utm_content=hero. The email provider wraps that URL; the website then redirects /demo to /demo/.

1. Delivery: click the link in a delivered test email. Compare the final decoded campaign values with the four approved values above. If the wrapper adds a duplicate source, fix the provider’s tagging rule before continuing.
2. Collection: connect your device with Tag Assistant, confirm the intended measurement ID, and inspect the landing event’s page URL. If the final browser URL is correct but the collected URL is not, investigate tag configuration and consent timing.
3. Conversion: submit a test form and inspect the actual saved CRM fields. A success message alone does not establish campaign capture.
4. Reporting: after processing, inspect Session source / medium and Session campaign for the test period. First user source can describe an earlier visit, so it is not an interchangeable check.

Download the campaign launch QA record (plain text) to record the URL, device, consent state, evidence and remaining issues. For a delivery-specific problem, use the email tagging audit; for a changed destination, use the redirect query-string guide.

Official Google training and limits

Follow Google’s DebugView setup instructions, then watch the official Reporting in Google Analytics 4 YouTube series for reporting context. Collection checks do not prove final attribution, and privacy or consent controls may limit available events.

For the broader setup, read GA4 UTM Tracking Troubleshooting Guide: Root Causes, Debugging & Solutions. Browse the GA4 Attribution & Troubleshooting guides to choose another troubleshooting task.

References

• Monitor Events in GA4 DebugView (Google Analytics Help)

DJ

Written by

Dinesh Jeengar

Founder, UTMCraft

Founder of UTMCraft, an independent set of browser-based campaign URL tools and measurement guides.

Meet the author ↗