> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/freewheel/pixel.md).
# Pixel
Push audiences from your website into a FreeWheel remarketing account through a pixel.
The FreeWheel Pixel connector pushes audiences from your website into your FreeWheel remarketing account, through a pixel fired in the visitor's browser.
## Description
### What you can do with this connector
* Build a FreeWheel remarketing audience from users who visit your site while in a mediarithmics segment.
### Which identifiers are sent
**None.** The connector fires your FreeWheel pixel from the browser; mediarithmics sends no identifiers.
FreeWheel is reached by several connectors and they behave differently - [the comparison is on the FreeWheel page](/connectors/destinations/freewheel.md).
## Connector setup
### Prerequisites
* The mediarithmics tag installed on the site, calling `syncFeeds` - the call that enables client-side feeds. See the **Setup & Monitor** section, under *Collect & manage your data › Collect data in real time › Web tracking*.
* A **FreeWheel pixel created in FreeWheel**, and its **pixel ID**.
### Setup steps
{% stepper %}
{% step %}
**Create the pixel in FreeWheel and note its ID.**
{% endstep %}
{% step %}
**Select the FreeWheel Pixel connector in the client-side section and enter the pixel ID.**
{% endstep %}
{% endstepper %}
Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.
## Good to know
This is a client-side connector, so it carries the client-side constraints: volumes ramp up as users visit your site, a segment exit cannot be signalled to FreeWheel, and nothing is sent when the tag is blocked or consent is refused. See the **Audience & Activation** section, under *Activate your audiences › Set up a destination › Feed*.
## FAQ
#### Does mediarithmics send any identifier to FreeWheel through this connector?
No. The pixel fires in the user's browser; no identifier is sent by mediarithmics.
#### Where does the pixel ID come from?
You create the pixel in FreeWheel first, then enter its ID on the feed.
## Partner documentation
FreeWheel documents its own platform at . Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.
---
# 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.mediarithmics.io/connectors/destinations/freewheel/pixel.md?ask=&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.