> For the complete documentation index, see [llms.txt](https://docs.rhym.io/rhym-help-guide-and-faqs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhym.io/rhym-help-guide-and-faqs/integrations/facebook-pixel.md).
# Facebook Pixel
You can easily add your Facebook pixels to any Rhym campaign
There are a couple of benefits for adding pixels to your Rhym experiences! Adding pixels will allow you to track views, completions and leads on each screen. Tracking pixel events also allows you to create segments based on consumer responses, which will help you with retargeting efforts!
## Click on Add Integration in Editor Header
For every campaign, as you enter the editor. You can enable relevant integrations by clicking on **“Add Integration”** in the header. You will see all eligible integrations there.
## Connect with Facebook Pixel
Add your pixel ID & save. We will start passing on data to your Facebook Ad account
#### How to get Pixel ID?
1. Login to your FB account and navigate to your [Ads Account manager.](https://www.facebook.com/ads/manager)
2. Click on All Tools and select Events Manager
3. One in Event Manager, Select Data Sources
4. You will see Pixel ID once in the Data Sources tab. Copy the same for integration
---
# 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.rhym.io/rhym-help-guide-and-faqs/integrations/facebook-pixel.md?ask=&goal=
```
`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.