> 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/en/faq/google/google-gclid-issue.md).

# Google gclid Issue

Resolution of the unexpected interaction issue between GTM and <kbd>gclid</kbd>

An issue has been identified where an unexpected interaction occurs between **Google Tag Manager (GTM)** and certain form elements when the <kbd>gclid</kbd> parameter is included in the URL. Here is a temporary solution to bypass this problem:

**Proposed Solution Google's advice:** Avoid using the name <kbd>"action"</kbd> for `<input>` tags in your forms. This strategy allows you to resolve the problem reliably until an official fix is published.

By following these steps, you can mitigate the undesirable effects related to this interaction. Make sure to check frequently for any official updates from Google regarding this issue.


---

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