> For the complete documentation index, see [llms.txt](https://server-side.docs.sirdata.net/sirdata-server-side/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://server-side.docs.sirdata.net/sirdata-server-side/english-1/f.a.q-server-side/tracking/verifying-ga4-data-collection-blocking-by-an-adblocker.md).

# Verifying GA4 Data Collection Blocking by an Adblocker

**Procedure for Verifying GA4 Data Collection Blocking by an Adblocker**

1. **Open the Network Console**\
   In your browser, open the Developer Tools (shortcut `F12` or right-click → *Inspect*), then go to the **Network** tab.
2. **Filter Data Collection Requests**\
   In the Network panel search bar, type **collect** to display only tracking requests.\
   Then, locate the calls to the following URL:

{% hint style="info" %}
<https://region1.google-analytics.com>
{% endhint %}

3. **Verify the Presence of the Collection Signal**\
   Select one of the listed requests and open the **Headers** tab.\
   In the **Payload** section, look for the **G100** indicator, confirming that GA4 is active and data collection is functioning correctly.
4. **Activate the Adblocker Extension**\
   Enable your adblocker (for example, **Ghostery**, **uBlock Origin**, or any equivalent tool).
5. **Observe the Impact on Data Collection**\
   In the Network panel search bar, type again :&#x20;

{% hint style="info" %}
<https://region1.google-analytics.com>
{% endhint %}

then refresh the page (**Ctrl + R** on Windows or **Cmd + R** on Mac).\
You will notice that no data collection requests appear anymore, confirming that the adblocker effectively blocks the tracking signals sent to Google Analytics 4.

If you would like our assistance in optimizing your tracking on adblocked inventories, please contact us at **<support@sirdata.com>**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://server-side.docs.sirdata.net/sirdata-server-side/english-1/f.a.q-server-side/tracking/verifying-ga4-data-collection-blocking-by-an-adblocker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.