> For the complete documentation index, see [llms.txt](https://documentation.freshpaint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.freshpaint.io/integrations/consent-management/freshpaint-consent-manager/managing-consent-for-site-scripts.md).

# Managing Consent for Site Scripts

Freshpaint Consent Manager (FPCM) can be utilized to manage consent for any scripts that appear on the site. Simply add the below attributes to an existing script block to allow or block tracking as designated by the user in FPCM.

### Available Attributes

| Attribute       | Required | Description                                     |
| --------------- | -------- | ----------------------------------------------- |
| `data-category` | Yes      | Name of the category                            |
| `data-type`     | No       | Custom type (ex. `"module"`)                    |
| `data-src`      | No       | Alternative to `src` to avoid validation issues |

**Example usage:**

```html
<script
    type="text/plain"
    data-category="analytics"
>/*...code*/</script>
```

### Managing Script Tags

To manage or block a script tag, add the following required attributes:

* `type="text/plain"`
* `data-category="your-category-name"`

#### **Before:**

```html
<script>
    // Always executed
</script>
```

#### After:

```html
<script
    type="text/plain"
    data-category="analytics">
    // Executed when the "analytics" category is enabled
</script>
```

#### Running Scripts When Category is Disabled

Prepend `!` to the category name to execute cleanup logic when the category was previously enabled and becomes disabled.

```html
<script
    type="text/plain"
    data-category="!analytics">
    // Executed when the "analytics" category is disabled
</script>
```

#### Custom Type

Use the `data-type` attribute to set a custom script type (ex. `module`).

```html
<script
    type="text/plain"
    src="my-service-module.js"
    data-category="analytics"
    data-type="module"
></script>
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.freshpaint.io/integrations/consent-management/freshpaint-consent-manager/managing-consent-for-site-scripts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.