> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/debugging-monitoring/why-do-i-see-duplicate-or-extra-ga4-events.md).

# Why do I see duplicate or extra GA4 events?

Why GA4 shows extra or duplicate events with AdPage server-side tagging, such as events your website never sends, and how to find and remove the source.

You use AdPage server-side tagging, but GA4 shows more events than you expect. Typical examples are an extra `page_view`, `scroll`, `click`, `form_start`, `file_download` or `view_search_results`, or events your developer says the website never sends. Use this page to find the cause and fix it.

{% hint style="info" %}
**The key point:** not every GA4 event comes from your website or your dataLayer. GA4 can create events itself, through enhanced measurement or through event rules in the GA4 property. Those events never show up in your dataLayer, so your developer will not find them in the website code.
{% endhint %}

***

### Common causes

Extra or duplicate GA4 events usually come from one of these three sources:

1. **Enhanced measurement** in your GA4 web data stream.
2. **Create event or Modify event rules** in your GA4 property.
3. **Double tagging:** the same event is sent twice from the website.

***

### 1. Enhanced measurement

Enhanced measurement lets the Google tag collect events automatically in the browser, without a tag or dataLayer event of your own. These events travel along with your other GA4 hits, so they show up in GA4 on top of the events you built yourself. If you also track scrolls, clicks, forms or downloads with your own GA4 event tags, you get them twice.

Events created by enhanced measurement:

| Setting           | Events                                            |
| ----------------- | ------------------------------------------------- |
| Page views        | `page_view` (also on browser history changes)     |
| Scrolls           | `scroll`                                          |
| Outbound clicks   | `click`                                           |
| Site search       | `view_search_results`                             |
| Form interactions | `form_start`, `form_submit`                       |
| Video engagement  | `video_start`, `video_progress`, `video_complete` |
| File downloads    | `file_download`                                   |

**How to check and turn it off:**

1. In GA4, go to **Admin** > **Data collection and modification** > **Data streams** and open your web stream.
2. Under **Enhanced measurement**, click the gear icon.
3. Turn off every setting you already track with your own GA4 event tags, then click **Save**.

You can also switch enhanced measurement off completely with the main toggle.

{% hint style="warning" %}
The **Page views** setting cannot be switched off on its own. If you send `page_view` yourself, open **Show advanced settings** under Page views and turn off **Page changes based on browser history events**. That stops the extra `page_view` events on single-page or filter navigation.
{% endhint %}

***

### 2. Create event and Modify event rules

GA4 can create a new event from another event, or change an existing one. This is set up in the GA4 property, not on the website. A rule such as "create `generate_lead` when `page_view` has `page_location` containing `/thank-you`" produces events that your website never sent.

**How to find and remove them:**

1. In GA4, go to **Admin** > **Data display** > **Events**.
2. Click **Create event** and **Modify event** to see the existing rules. You can find the same lists in your web stream (**Admin** > **Data streams** > your web stream > **Create custom events** and **Modify events**).
3. Open every rule you do not recognise, check which event it creates or changes, and delete the ones you do not need.

Check with your team or agency before you delete a rule. Sometimes a rule was added on purpose, for example to create a conversion event.

{% hint style="info" %}
Removing a rule is **not retroactive**. Events that were already created stay in your historical data. Only new data is affected.
{% endhint %}

***

### 3. Double tagging

The same event is also counted twice when it is sent twice from the website. Common examples:

* GA4 is loaded both with a hard-coded `gtag.js` snippet and through Google Tag Manager.
* Two GTM containers on the page both send to the same GA4 property.
* The Google tag sends an automatic `page_view` **and** you have a separate GA4 `page_view` event tag.

For the last one, set `send_page_view` to `false` in your Google tag and use one GA4 `page_view` event tag. See [Setup GTM web container](https://docs.adpage.io/getting-started/setup-gtm-web-container) for the full setup.

***

### How to verify

* **GA4 DebugView** (**Admin** > **Data display** > **DebugView**): open your website in GTM preview mode and watch which events arrive, and how often.
* **GA4 Realtime** (**Reports** > **Realtime**): check the event counts while you click through the website.
* **Event counts per day:** in GA4, compare the daily count of the affected events before and after your change.
* **AdPage Monitoring:** open **Monitoring** > **Ruwe requests** in your container and filter on GA4. This lists the individual requests AdPage received over the last 7 days, so you can see which events actually came in through your server container. An event that is in GA4 but not in this list was not sent through AdPage. Look in GA4 itself (cause 2) or at a direct GA4 tag on the website.

{% hint style="warning" %}
Changes in GA4 only apply from the moment you save them. Give it **24 to 48 hours** before you compare the numbers in your standard GA4 reports. DebugView and Realtime show the effect right away.
{% endhint %}

***

### Still seeing duplicates?

If the extra events are still there after checking the above, contact our support team. Include the event names, the date you made the changes and a screenshot of the GA4 event counts per day.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/faq/debugging-monitoring/why-do-i-see-duplicate-or-extra-ga4-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
