> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/faq/google/probleme-gclid-google.md).

# Problème gclid google

Ma redirection redirige vers une URL erronée - gclid=1 \<input name="action" ?

Résolution du problème d'interaction inattendue avec GTM et `gclid`

Un problème a été identifié lorsqu'une interaction inattendue se produit entre **Google Tag Manager (GTM)** et certains éléments de formulaire lorsque le paramètre `gclid` est inclus dans l'URL. Voici une solution temporaire pour contourner ce problème :

#### Solution Proposée

* **Conseil de Google :** Évitez d'utiliser le nom `"action"` pour les balises `<input>` dans vos formulaires. Cette stratégie permet de résoudre le problème de manière fiable jusqu'à ce qu'un correctif officiel soit publié.

En suivant ces étapes, vous pouvez atténuer les effets indésirables liés à cette interaction. Assurez-vous de vérifier fréquemment pour toute mise à jour officielle de Google concernant ce problème.


---

# 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://cmp.docs.sirdata.net/faq/google/probleme-gclid-google.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.