> 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/overview/how-it-works.md).

# How it works?

### Overview

EdgeTag is a purpose-built first-party data infrastructure that optimizes every signal, powers every decision, and adapts automatically to the evolving privacy-first landscape. The platform delivers:

**Complete Zero-Code Data Infrastructure**

Automatic data capture, scalable ID graph, and real-time streaming to 50+ marketing and analytics channels, with built-in consent management, observability, and bot protection.

**Single Tenant Architecture for Enterprise Security**

Dedicated infrastructure where no resources are shared between customers, ensuring complete data isolation, predictable performance, and built-in GDPR/CCPA compliance with full audit trails.

**Service as Software with Done-For-You Implementation**

Zero-code deployment, managed infrastructure, and expert configuration—eliminating the need to hire teams for server-side implementation so you can focus on growth, not data maintenance.

<br>


---

# 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.edgetag.io/overview/how-it-works.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.
