> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/integraciones-y-herramientas/marketing-automation-and-crm/google-ads.md).

# Google Ads

Etiqueta de conversión en Google Ads

**Google Ads** permite mostrar anuncios de tu tienda cuando los usuarios buscan productos en Google o navegan por sitios web.

Es una de las formas más efectivas de captar clientes con intención de compra.

***

## **Credenciales necesarias:**

* Cuenta de Google Ads
* ID de cliente de Google Ads (formato: `XXX-XXX-XXXX`)
* Permisos de Administrador o Estándar
* Sitio web vinculado
* Configuración de conversiones activa, incluyendo:
  * ID de conversión
  * Label de conversión
* Etiqueta global de sitio (gtag.js)
* Etiqueta de conversión
* (Opcional) Vinculación con:
  * Google Merchant Center (para campañas de productos)

***

### ¿Por qué es importante?

Trabajar con Google Ads te permite:

* Aparecer en búsquedas relevantes (ej: “championes en oferta”)
* Generar tráfico calificado a tu tienda
* Promocionar productos específicos
* Medir resultados y optimizar campañas
* Escalar tus ventas de forma controlada

***

### ¿Cómo se configura?

Para ver el paso a paso actualizado, podés seguir la documentación oficial de Google:

* Primeros pasos con Google Ads:\
  <https://support.google.com/google-ads/answer/6146252>
* Configurar conversiones:\
  <https://support.google.com/google-ads/answer/6095821>


---

# 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://guia.fenicio.help/integraciones-y-herramientas/marketing-automation-and-crm/google-ads.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.
