# Google Gtag

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.](/files/-MMpovEruB4oUbew5w4N)

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.](/files/-MMpq6q3oACjsbH_bTq6)

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: 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:

```
GET https://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides/google-gtag.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.