Puerta de enlace de etiquetas de Google para anunciantes: Carga secuencias de comandos propias de Google
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Este documento está dirigido a los desarrolladores que utilizan el etiquetado del servidor y desean publicar secuencias de comandos de Google en un contexto propio.
La puerta de enlace de etiquetas de Google para anunciantes te permite cargar secuencias de comandos de Google, como gtm.js, directamente desde tu infraestructura propia en lugar de desde los servidores de Google.
Esto te permite publicar datos en un contexto de origen, ya sea a través de tu servidor de etiquetado o de una CDN.
Antes de comenzar
En esta guía, se da por sentado que ya hiciste lo siguiente:
[null,null,["Última actualización: 2025-07-29 (UTC)"],[[["\u003cp\u003eThis article guides developers on serving Google scripts like gtm.js or gtag.js from their own servers using server-side tagging for a first-party data context.\u003c/p\u003e\n"],["\u003cp\u003eBefore starting, ensure you have a server container in Tag Manager, a tagging server setup, and a configured custom server domain.\u003c/p\u003e\n"],["\u003cp\u003eImplementation involves configuring the client to load Google scripts through your server, updating the script source domain to your server, and verifying the script source using browser developer tools.\u003c/p\u003e\n"],["\u003cp\u003eIf using consent mode, you can further enhance control by setting up region-specific tag behavior after completing the implementation.\u003c/p\u003e\n"]]],["Developers using server-side tagging can load Google scripts (gtm.js, gtag.js) from their own server for a first-party context. This requires setting up a server container, a tagging server, and a custom server domain. Steps involve configuring the client to load scripts through the server and updating the script source URL on the website to point to the custom server. Verification includes checking the browser's developer tools to confirm that `gtm.js` loads from the custom server, not Google's.\n"],null,["# Google tag gateway for advertisers: Load Google scripts first-party\n\n\u003e This document is for developers who use server-side tagging and want to serve\n\u003e Google scripts in a first-party context.\n\nGoogle tag gateway for advertisers lets you load Google scripts, such as gtm.js,\ndirectly from your first-party infrastructure instead of from Google's servers.\nThis lets you serve data within a first-party context either through your\ntagging server or through a CDN.\n\nBefore you begin\n----------------\n\nThis guide assumes that you have done the following:\n\n- [Set up a server container in Tag Manager](/tag-platform/tag-manager/server-side/overview#create_a_tag_manager_server_container)\n- [Set up a tagging server](/tag-platform/tag-manager/server-side/overview#set_up_a_tagging_server)\n- [Configured a custom server domain](/tag-platform/tag-manager/server-side/custom-domain?option=same-origin)\n\nTo get started, pick how you want to serve your Google scripts.\n\nCDN (recommended) Tagging server\nPick an implementation option to see instructions.\n\nNext steps\n----------\n\nIf you are using consent mode, you can set up [region-specific tag behavior](/tag-platform/tag-manager/server-side/enable-region-specific-settings) for even\nmore control."]]
