# Check GA4 recovery in three runs

Use a test page where you can enable and disable recovery. Keep analytics consent accepted for all three runs and use the same browser, page, and event.

## 1. Start with a working baseline

Turn Brave Shields off and recovery off. Open developer tools → Network before reloading the page. Trigger your event once.

Look for the GA4 `collect` request. In our test, it received HTTP 204. Then select your test device in GA4 DebugView and confirm the event and its parameters.

![Baseline Network panel](https://static.introtrace.net/blog/ga4-brave-baseline-network.png)

## 2. Check what blocking changes

Turn Shields on, leave recovery off, and repeat. In our test, the Google tag did not initialise and no GA4 collection request was observed.

A missing collect request is meaningful only with a working baseline and the same event, consent choice, and filter. It does not by itself prove absence from GA4.

![Blocking Network panel](https://static.introtrace.net/blog/ga4-brave-blocking-network.png)

## 3. Enable recovery and repeat

Leave Shields on and enable recovery. Repeat the event once.

Our direct GA4 requests were blocked, and the subsequent relay requests received HTTP 204. Open a request to check its hostname; relay rows can have long names.

![Recovery Network panel](https://static.introtrace.net/blog/ga4-brave-recovery-network.png)

Finish by checking the event in GA4 DebugView. If several debug devices are listed, choose the one used for this test. HTTP success is a browser observation; it does not establish that GA4 recorded the event.

## About these screenshots

Captured from actual desktop Brave DevTools on introtrace.net on October 3, 2026. Browser identifiers and relay request keys are obscured in the screenshots. The test event was `introtrace_walkthrough_test`, with `test_run` set to `baseline`, `blocking`, or `recovery`.

Recovery was disabled by replacing its loader response with empty JavaScript only in the test browsers. The public site stayed unchanged. These fresh runs have browser evidence, without a new GA4 DebugView receipt check. The full article includes separately dated GA4 evidence from the earlier test.

[Read the full checklist](https://introtrace.net/blog/test-analytics-recovery-ga4-checklist#screenshot-walkthrough) · [Get the Introtrace script](https://introtrace.net/#try-it)