DebugView shows events from devices sending debug signals. If it stays empty, check the measurement ID and debug marking first.
Use a fresh test environment and make an intentional analytics-consent choice. If tracking is completely gated until acceptance, no outgoing requests beforehand are expected.
Follow the route to the diagnostic view
Inspect network requests for an event sent to the expected measurement ID. Then compare the selected GA4 property and debug marking. Google documents mechanisms including debug_mode; the appropriate method depends on the integration.
Change one condition at a time. If an extension or content blocker may interfere, compare controlled runs with and without it. Leave consent choices for regular visitors unchanged.
A fictional diagnostic record can stay compact:
Destination property checked: yes
Tracking permitted: yes
Event request observed: no
Next check: integration and blocking conditions
If requests exist without corresponding debug output, inspect marking, filters and the selected test instance. Keep real names, email addresses and form content out of test events. Select the test device in DebugView and open the expected event there.