# Facebook Conversion API vs. Facebook Pixel

### **Facebook Pixel**

* **Definition**: A script that tracks user activity on a website via the browser.
* **How It Works**: Client-side tracking via cookies.
* **Limitations**: Blocked by ad blockers and third-party cookie restrictions.

### **Facebook Conversion API (CAPI)**

* **Definition**: Server-side tracking for more accurate data.
* **Advantages**: Resistant to ad blockers and allows the use of first-party cookies.

### **Key Differences**

* **Client-side vs. server-side tracking.**
* **Data control**: CAPI offers more control.
* **Resilience to blockers**: CAPI is more robust.

### **Conclusion**

Using both solutions for comprehensive tracking is recommended.

### <br>


---

# Agent Instructions: 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:

```
GET https://server-side.docs.sirdata.net/sirdata-server-side/english-1/f.a.q-server-side/facebook-capi/facebook-conversion-api-vs.-facebook-pixel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.