> 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/validation.md).

# Validation

Validating implementations is crucial, which is why we developed several tools to assist you in the process. Let's explore them.

### Browser validation

A good starting point for validating integration is to begin in the browser. The following video offers valuable insights on how to get started, what to check, and how to proceed.

{% embed url="<https://www.loom.com/share/bf0918070dc54455af4bd2d64161c470>" %}

### Server validation

In the video below, we demonstrate how to test events as they arrive at our edge server.

{% embed url="<https://www.loom.com/share/38edb4f89835451aae234215660d773c>" %}

### Payload Validation

If you want to enable automated payload validation while adding support for EdgeTag to your site, consider adding a [Payload Validator](https://docs.edgetag.io/channels/payload-validator.md) channel to perform these checks automatically.

{% hint style="warning" %}
Please ensure that you remove it after implementation is complete.
{% 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 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/implementation/validation.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.
