# Page Not Found

The URL `welcome/what-is-facebook-pixel` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Welcome: Why Zotek?](https://zotek.gitbook.io/facebook-multiple-pixel/welcome-why-zotek.md)
- [Why connect Catalog with Facebook Pixel (Important) ?](https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/catalog-manager/why-connect-catalog-with-facebook-pixel-important.md)
- [Setup TikTok pixel](https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/setup-tiktok-pixel-guide/setup-tiktok-pixel.md)
- [Setup TikTok Pixel Guide](https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/setup-tiktok-pixel-guide.md)
- [Create Meta Pixel](https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/set-up-meta-pixel-guide/create-meta-pixel.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://zotek.gitbook.io/facebook-multiple-pixel/welcome-why-zotek.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.

### Option 2 — Browse the documentation index

Full index: https://zotek.gitbook.io/facebook-multiple-pixel/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://zotek.gitbook.io/facebook-multiple-pixel/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/facebook-multiple-pixel/welcome-why-zotek.md`).

You may also use `Accept: text/markdown` header for content negotiation.