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

# Meta

Meta integration helps connect your Facebook dataset with your website. We manage both browser and server event streaming for you. The integration also enables you to send custom events easily through the user interface. Getting started with our integration is straightforward; you simply need to complete a simple authorization, and you’re ready to go.

### Details

Channel name: facebook

NPM package: [@blotoutio/providers-facebook-sdk](https://www.npmjs.com/package/@blotoutio/providers-facebook-sdk) 

Server API version: [24.0](https://developers.facebook.com/docs/graph-api/changelog/version24.0)

### Event Flow

Our Meta integration covers both browser (which you need to enable) and server events. Events are working in tandem (have the same event ID), which means that Meta can deduplicate them. Custom events that we generate for you on the fly are server-side only.

### Useful links

{% embed url="<https://developers.facebook.com/docs/marketing-api/conversions-api/>" %}

{% embed url="<https://developers.facebook.com/docs/meta-pixel/support/pixel-helper/>" %}


---

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