> 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.md).

# Migration Guides

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

## [Google Gtag](/analytics/adobe-launch/gtag/migration-guides/google-gtag.md)

The Google Gtag extension by Adobe injects the Google Global Site Tag library on the page. It does not provide any additional actions, nor is it required to work with the Acronym Google Site Tag extension. [Migrate this extension](/analytics/adobe-launch/gtag/migration-guides/google-gtag.md).&#x20;

![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-MMpraBV66dwHZ6ITho0%2Fimage.png?alt=media\&token=561f34a3-516b-48dd-9dca-345e37ba2508)

## [Google Ads](/analytics/adobe-launch/gtag/migration-guides/google-ads.md)

The Google Ads extension by Adobe sends conversion data to the Google Ads servers and requires the Adobe-built Google Gtag extension. [Migrate this extension](/analytics/adobe-launch/gtag/migration-guides/google-ads.md).&#x20;

![The Adobe-built Google Ads extension](https://300935401-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LZeIQ01HvLIR6WO-wx1%2F-MMpnjhNlmnvg9emjjxL%2F-MMpsULJ0k1ZcK7vBf9W%2Fimage.png?alt=media\&token=dfbe983b-5e46-4c21-a306-4576e9c3176e)

## [Google Analytics](/analytics/adobe-launch/gtag/migration-guides/google-analytics.md)

The Google Analytics extension by Adobe uses the Universal Analytics library to send data to Google Analytics. The existing extension does not use the Google Global Site Tag (gtag) library to send data, thus this is not exactly a one-to-one migration. [Migrate this extension](/analytics/adobe-launch/gtag/migration-guides/google-analytics.md).&#x20;

![The Adobe-built Google Analytics (Universal Analytics) extension](https://300935401-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LZeIQ01HvLIR6WO-wx1%2F-MMpnjhNlmnvg9emjjxL%2F-MMptaFvEm0gAtEl6qXv%2Fimage.png?alt=media\&token=a48539f0-3789-4826-ab95-d8c6a49cf87d)


---

# 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.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.
