> 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/onboarding/e-commerce/scaling-playbook/edgetag-gtm-implementation-guide-for-marketing-teams/phase-3-consent-and-privacy-week-2-3-parallel.md).

# Phase 3: Consent & Privacy (Week 2-3, Parallel)

### 7.1 Understand Consent Requirements

Before EdgeTag sends any data, users must have consented. This is non-negotiable for:

* ✓ GDPR (EU users)
* ✓ CCPA (California users)
* ✓ CPRA (California users, expanded)
* ✓ Platform terms (Meta, Google require explicit consent)

### 7.2 How Consent Works With EdgeTag

**Simple flow:**

1. User visits your site
2. Consent banner appears (your existing popup/banner)
3. User clicks "Accept" or "Reject"
4. You send their consent choice to EdgeTag via a GTM tag
5. EdgeTag **only sends data to ad platforms if user accepted**

#### **What Your Consent Tag Does**

When a user accepts the cookie banner, this tag fires:

```
Send consent signal to EdgeTag:
- "Marketing/Advertising: YES"
- "Analytics: YES"
- "Share PII with platforms: YES"
```

#### **For Your Dev/Analytics Team**

Integrate your existing cookie/consent banner CMP (like Termly, OneTrust, etc.) with EdgeTag:

1. When user accepts consent, fire EdgeTag consent tag
2. Specify which purposes they consented to (advertising, analytics, share\_pii)
3. If consent is missing, EdgeTag won't send data to ad platforms

{% hint style="warning" %}
**Critical for compliance:** You must capture and respect user consent. If you do not, regulators can fine you 1-4% of global revenue under GDPR. Set this up correctly from day 1.
{% 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 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/onboarding/e-commerce/scaling-playbook/edgetag-gtm-implementation-guide-for-marketing-teams/phase-3-consent-and-privacy-week-2-3-parallel.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.