> 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/channels/x/configuration.md).

# Configuration

Now that the basic onboarding is complete, let's review all fields in the form and how to use them. The Pixel ID, Ad Account ID and Mapping were already filled in during the basic onboarding, so we will skip those fields.

### Enable browser pixel?

The browser pixel is one of the key incase of twitter. By enabling this option, we will begin sending browser events alongside the server events that you receive automatically. We ensure that both the browser and server events share the same event ID (which is called conversion ID in twitter), allowing Twitter to deduplicate events and maximize the benefits from both sources. If you are using our browser integration or any of our apps, enabling this feature will work seamlessly. For headless applications, you will need to add our NPM package to your project to allow support—more on [NPM packages](/implementation/headless/browser-packages.md).


---

# 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/channels/x/configuration.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.