> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/implementation/browser/consent.md).

# Consent

Consent is essential to us because we respect users' privacy and strive to protect it. This commitment is one of the primary reasons we developed this product. All events sent from our system are protected by consent, meaning we do not share any data without proper consent.

The consent function should be called every time the user changes the consent.

{% hint style="warning" %}
You need to provide consent for each provider or consent category. At least one needs to be provided!
{% endhint %}

### Parameters

| Name       | Type                             | Required | Description                                                                        |
| ---------- | -------------------------------- | -------- | ---------------------------------------------------------------------------------- |
| consent    | Record\<string, boolean> \| null | Yes / No | Tells which provider was consented to and which not.                               |
| categories | Record\<string, boolean>         | Yes / No | No Tells which categories are consented to and which are not. See categories below |
| options    | { destination?: string }         | No       | See below                                                                          |

#### Categories

* necessary
* advertising
* analtyics
* share\_pii
* functional

#### Options

**Destination**: We recommend specifying the destination, especially if multiple EdgeTag instances exist on the website. If you do not, we will trigger the same event to multiple destinations. The destination value should be the EdgeTag URL.

### Examples

{% code title="Accepting all channels" %}

```javascript
edgetag('consent', { all: true })
```

{% endcode %}

{% code title="Accepting only specific channels" %}

```javascript
edgetag('consent', { facebook: true, googleAnalytics4: false })
```

{% endcode %}

{% code title="Specific channels and categories" %}

```javascript
edgetag('consent', 
  { all: false, facebook: true, tiktok: true, googleAnalytics4: false }, 
  { all: false, necessary: true, advertising: true, analytics: false }
)
```

{% endcode %}

{% code title="Specifying only categories " %}

```javascript
edgetag('consent', null, { all: false, necessary: true, advertising: true })
```

{% endcode %}


---

# 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://docs.edgetag.io/implementation/browser/consent.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.