> For the complete documentation index, see [llms.txt](https://docs.acronym.com/analytics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides/google-gtag.md).

# Google Gtag

This section discusses how to migrate the Adobe-built Google Gtag extension to the Acronym-built  Google Site Tag (gtag) extension.

The Adobe-built Google Gtag extension injects the Google Global Site Tag (gtag) library on the page. Similarly, the Acronym version will inject the library on the page once a relevant rule action has been triggered.

## Extension Configuration

![The configuration screen for the Adobe-built Google gtag extension.](https://300935401-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LZeIQ01HvLIR6WO-wx1%2F-MMpnjhNlmnvg9emjjxL%2F-MMpovEruB4oUbew5w4N%2Fimage.png?alt=media\&token=a3917231-d5eb-48ab-b051-ab3196c977ee)

To migrate the extension configuration, simply take the account IDs (separated by commas) from the Adobe extension and [add each account ID](/analytics/adobe-launch/gtag/configuration.md) to the Acronym extension.

![Adding a new account within the Acronym-built gtag extension.](https://300935401-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LZeIQ01HvLIR6WO-wx1%2F-MMpnjhNlmnvg9emjjxL%2F-MMpq6q3oACjsbH_bTq6%2Fimage.png?alt=media\&token=cfb23f46-9f52-4f62-99db-3ef3accb350d)

If you have set the custom data layer option in the Adobe extension, you can copy this value to the advanced settings field: [Data Layer Name](/analytics/adobe-launch/gtag/configuration.md#data-layer-name).

## Rule Actions

The Adobe-built extension does not have any rule actions to migrate.


---

# 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://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides/google-gtag.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.