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

# Adobe Tags (Adobe Launch)

- [Google Tag (gtag)](https://docs.acronym.com/analytics/adobe-launch/gtag.md): An Acronym built Adobe Tags extension that sends data to Google Analytics, Google Ads, and the Google Marketing Platform via Google Tag, or gtag.js.
- [Configuration](https://docs.acronym.com/analytics/adobe-launch/gtag/configuration.md): Configure the gtag extension with your Google products, as well as advanced gtag.js settings.
- [Actions](https://docs.acronym.com/analytics/adobe-launch/gtag/actions.md)
- [Preload the gtag.js library](https://docs.acronym.com/analytics/adobe-launch/gtag/actions/load.md)
- [Set persistent values](https://docs.acronym.com/analytics/adobe-launch/gtag/actions/set.md)
- [Send a page view](https://docs.acronym.com/analytics/adobe-launch/gtag/actions/pageview.md)
- [Send an event](https://docs.acronym.com/analytics/adobe-launch/gtag/actions/event.md)
- [Release Notes](https://docs.acronym.com/analytics/adobe-launch/gtag/release-notes.md): The changes made for each release of the gtag extension.
- [Frequently Asked Questions](https://docs.acronym.com/analytics/adobe-launch/gtag/faq.md): Here are some frequently asked questions about the gtag extension for Adobe Tags.
- [Consent Management](https://docs.acronym.com/analytics/adobe-launch/gtag/faq/consent-management.md)
- [Error Codes](https://docs.acronym.com/analytics/adobe-launch/gtag/faq/error-codes.md)
- [Migration Guides](https://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides.md): This section covers how to migrate from the Adobe-built Google extension to the Acronym-built Google Site Tag (gtag) extension.
- [Google Ads](https://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides/google-ads.md): This section discusses how to migrate the Adobe-built Google Ads extension to the Acronym-built Google Site Tag (gtag) extension.
- [Google Universal Analytics](https://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides/google-analytics.md): This section discusses how to migrate the Adobe-built Google Analytics (Universal Analytics) extension to the Acronym-built Google Site Tag (gtag) extension.
- [Google Gtag](https://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides/google-gtag.md): This section discusses how to migrate the Adobe-built Google Gtag extension to the Acronym-built  Google Site Tag (gtag) extension.
- [Developer Documentation](https://docs.acronym.com/analytics/adobe-launch/gtag/developer-documentation.md): This page covers advanced topics for both site developers and Adobe Tags extension developers.


---

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