# Incorrect trigger in GTM

#### Description

One or more tags are being fired **before consent has been initialized** or are using an **inappropriate trigger** in Google Tag Manager. This may prevent the CMP from sending the `default` or `update` signals in time, which **undermines the effectiveness of Google Consent Mode**.

#### Main cause

* The trigger used for the CMP tag (or Consent Mode setup) is **not** `"Consent Initialization"` (`gtm.init_consent`), or
* Other tags are **firing before or alongside** the `gtm.init_consent` event.

#### What to do

* In Google Tag Manager, open your CMP tag (e.g., **ABconsent – Sirdata CMP**) ;
* Make sure it uses **only** the trigger `"Consent Initialization"` (`gtm.init_consent`) ;
* Ensure that **no other tags** are fired using this trigger or before it ;
* Do **not fire any Google tags** (Analytics, Ads, etc.) before this event occurs.

<figure><img src="/files/JbZSLj4vEiXB7ZVjidfr" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://cmp.docs.sirdata.net/en/consent-transmission-standards/google-consent-mode/fix-implementation-errors/incorrect-trigger-in-gtm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
