> 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/headless/browser-packages.md).

# Browser packages

With a Headless implementation, you have complete control over the code by utilizing our NPM packages. This also means that you can determine which browser pixel will be loaded. Regardless of your configuration settings in the channel to enable the browser pixel, it will NOT function until you add the specific NPM package for that channel.

Packages will still verify whether you have browser pixel enabled for a specific channel. They will only load third-party scripts if this feature is enabled. This means that if you have the pixel installed but it is disabled in our configuration, you will not experience any performance degradation.

Each channel's documentation will have a link to the package on the first page.

Now, let's look at how to add the browser package for the Meta channel.

{% code title="Initialization with browser pixel added" %}

```javascript
import { init } from '@blotoutio/edgetag-sdk-js'
import facebook from '@blotoutio/providers-facebook-sdk'

init({
  edgeURL: 'https://d.mysite.com',
  disableConsentCheck: true,
  providers: [facebook]
})
```

{% 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/headless/browser-packages.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.