> 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/actions/set.md).

# Set persistent values

This action lets you [set persistent values](https://developers.google.com/analytics/devguides/collection/gtagjs/setting-values) to all accounts for the following page views and events. This is great for setting custom dimensions and metric values that should persist for every hit.

{% hint style="info" %}
**Note:** The data persistence model may not be intuitive, please be sure to learn more about setting [custom data fields](/analytics/adobe-launch/gtag/configuration.md#custom-data-fields) taking note of the "Data Persistence" section.
{% endhint %}

{% hint style="danger" %}
**Note:** There is a bug with the set command for GA4 in the native Gtag library (owned by Google). It is recommended that you add the event parameters for each event, rather than using the set persistent values action if you are using GA4.
{% endhint %}


---

# 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/actions/set.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.