When tracking breaks, the usual advice is to open DevTools and look around. That rarely gets you far. Each panel answers a different question, and the order you use them in decides how quickly you find the fault. This is one repeatable check that follows a single action through the Console, the Network panel and browser storage.
As a hypothetical example, take a newsletter form that redirects to a thank-you page after submitting. The team reports that the newsletter_signup event appears in GA4 less often than expected. The steps below are a proposed method, not results from a live site.
Set up the browser so evidence survives
Open DevTools before you perform the action. Requests made earlier are not listed unless you reload. Then change three settings:
- In the Network panel, tick Preserve log. Otherwise the list clears when the redirect loads the thank-you page, and the request you need disappears.
- In Console Settings, tick Preserve Log too. The two settings are separate, and the Console also clears on each new page load by default.
- Tick Disable cache in the Network panel if you are checking script loading, so that the browser does not reuse an old file.
Test in a clean state as well. Ad blockers and browser extensions can change the result, and your own browser may hold an old consent choice. A window without extensions and a known consent state makes the result easier to explain.
Console: did the page report the action?
Submit the form, then read the data layer. Assuming the site uses the default name, this expression lists matching entries:
