> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/settings/page-presets.md).

# Page Presets

Find account-wide Action Page code in Settings > Page Presets of your Anedot fundraising account, including Custom Code for your header and body scripts.

The **Page Presets** section of Settings holds code that applies to every Action Page in your fundraising account. Go to **Settings > Page Presets** to find **Custom Code**. Pick a topic below to get started.

{% hint style="info" %}
**Page Presets** appears in the Settings menu only after Anedot turns on custom code for your account. It's different from the presets you save in the Page Builder. See [Presets in the Page Builder](https://docs.anedot.com/action-pages/page-builder/presets-in-the-page-builder.md).
{% endhint %}

| Topic                                            | Article                                                                     |
| ------------------------------------------------ | --------------------------------------------------------------------------- |
| Add header and body scripts to every Action Page | [Custom Code](https://docs.anedot.com/settings/page-presets/custom-code.md) |

## Tracking Codes

Settings doesn't have an account-wide tracking codes screen. You add tracking codes, such as Google Analytics, Google Tag Manager, and the Meta Pixel, to each Action Page in the Page Builder under **Setup > Settings**, or to the Settings preset your pages use. See [Tracking Codes for Action Pages](https://docs.anedot.com/action-pages/advanced-features/tracking-codes-for-action-pages.md) and [Presets in the Page Builder](https://docs.anedot.com/action-pages/page-builder/presets-in-the-page-builder.md).

## Related Articles

* [Settings](https://docs.anedot.com/settings.md)
* [Presets in the Page Builder](https://docs.anedot.com/action-pages/page-builder/presets-in-the-page-builder.md)
* [Tracking Codes for Action Pages](https://docs.anedot.com/action-pages/advanced-features/tracking-codes-for-action-pages.md)


---

# 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.anedot.com/settings/page-presets.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.
