# Facebook Pixel Destination Config Reference


> Complete Rudder CLI reference for the Facebook Pixel destination config keys, access token requirements, device mode settings, PII handling, and secrets.



[Facebook Pixel](https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/setup-guide/) is an advertising destination. RudderStack loads the Meta Pixel in the browser for web sources in device mode, and sends events to Meta's Conversions API from its servers in cloud mode.

In a Facebook Pixel destination spec:

- `type: facebook_pixel`
- `definition_version: 1`

## Sample configuration

```yaml
version: rudder/v1
kind: destination
metadata:
  name: fb-pixel-prod
spec:
  id: fb-pixel-prod
  display_name: Facebook Pixel Production
  type: facebook_pixel
  definition_version: 1
  enabled: true
  config:
    pixel_id: "{{ .FB_PIXEL_ID }}"
    access_token: "{{ .FB_ACCESS_TOKEN }}"

    standard_page_call: false
    value_field_identifier: properties.price
    advanced_mapping: true
    use_updated_mapping: true
    events_to_events:
      - from: Order Completed
        to: Purchase

    limited_data_usage: false
    test_destination: false
    remove_external_id: false
    blacklist_pii_properties:
      - property: email
        hash: true

    auto_config:
      web: true
    legacy_conversion_pixel_id:
      - from: Signed Up
        to: "{{ .FB_LEGACY_PIXEL_ID }}"

    connection_mode:
      web: device
      cloud: cloud
    consent_management:
      web:
        - provider: oneTrust
          consents:
            - marketing
```

The above example loads the Pixel on web sources in `device` mode and sends server-side events in `cloud` mode. Because a source connects in `cloud` mode, it needs `access_token` — see [Access token requirements](#access-token-requirements).

## Config keys

`config` accepts only the keys listed below. The [shared config key rules](https://www.rudderstack.com/docs/rudder-cli/destination-types/#config-key-rules) cover unknown keys, defaults, and immutability.

**Info:** In `cloud` mode Facebook Pixel accepts `identify`, `page`, `screen`, and `track` events. In `device` mode, web sources send `page` and `track`.

### Access token requirements

The Conversions API needs `access_token`; the Pixel in the browser doesn't. Rudder CLI checks for it twice:

- **On the destination.** `access_token` is required unless `connection_mode` is set and either maps `web` to `device` or leaves `web` out. A spec with no `connection_mode` at all, or with `web: cloud`, must carry it.
- **On each connection.** Connecting any source in `cloud` mode requires `access_token` — only `web` in `device` mode is exempt. See [Connect a source](#connect-a-source).

In practice: if anything connects in `cloud` mode, set `access_token`.

### Connection

<div class="rs-ckeys">
<div class="rs-ckey" id="pixel_id">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">pixel_id</p>RequiredSecret</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  ID of your Facebook Pixel, from the snippet on Facebook&rsquo;s Pixel creation page.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>At most 100 characters, and must not contain line breaks.</li>
<li>A <code>{{ path || fallback }}</code> template is accepted in place of a literal.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/setup-guide/#where-can-i-find-the-pixel-id" >Where can I find the Pixel ID?</a>.
</div>

</div>

<div class="rs-ckey" id="access_token">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">access_token</p>RequiredSecret</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Business access token from your Facebook Business account, used by the Conversions API in cloud mode.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Required when a source connects in <code>cloud</code> mode, or when <code>connection_mode</code> is absent or maps <code>web</code> to <code>cloud</code>. See <a href="#access-token-requirements" >Access token requirements</a>.</li>
<li>At most 300 characters, and must not contain line breaks.</li>
<li>A <code>{{ path || fallback }}</code> template is accepted in place of a literal.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/setup-guide/#where-can-i-find-the-business-access-token" >Where can I find the Business Access Token?</a>.
</div>

</div>

</div>

### Event settings

<div class="rs-ckeys">
<div class="rs-ckey" id="standard_page_call">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">standard_page_call</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Send a standard <code>PageView</code> event for every <code>page</code> and <code>screen</code> call.
</p>

</div>

<div class="rs-ckey" id="value_field_identifier">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">value_field_identifier</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>properties.price</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Event property RudderStack maps to Facebook&rsquo;s <code>value</code> field — used for events such as <strong>Product Viewed</strong> and <strong>Product Added</strong>.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>properties.price</code> or <code>properties.value</code>.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="advanced_mapping">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">advanced_mapping</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Turn on Facebook&rsquo;s advanced matching, sending user information with Pixel events. This is what the dashboard calls <strong>Enable Advanced Matching</strong>.
</p>

</div>

<div class="rs-ckey" id="events_to_events">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">events_to_events</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>array of objects</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Maps RudderStack event names to Facebook standard events.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>from</code> — RudderStack event name. At most 100 characters, and must not contain line breaks.</li>
<li><code>to</code> — one of <code>ViewContent</code>, <code>Search</code>, <code>AddToCart</code>, <code>AddToWishlist</code>, <code>InitiateCheckout</code>, <code>AddPaymentInfo</code>, <code>Purchase</code>, <code>PageView</code>, <code>Lead</code>, <code>CompleteRegistration</code>, <code>Contact</code>, <code>CustomizeProduct</code>, <code>Donate</code>, <code>FindLocation</code>, <code>Schedule</code>, <code>StartTrial</code>, <code>SubmitApplication</code>, or <code>Subscribe</code>.</li>
<li>The dashboard&rsquo;s dropdown offers only the first 13 of those. Rudder CLI accepts all 18, matching what the API accepts.</li>
<li>Both fields accept a <code>{{ path || fallback }}</code> template in place of a literal.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/device-mode/#standard-events" >Standard events</a>.
</div>

</div>

</div>

### Testing and privacy

**Warning:** The dashboard asks for `test_event_code` when `test_destination` is on. Rudder CLI doesn&#39;t enforce that pairing.

<div class="rs-ckeys">
<div class="rs-ckey" id="test_destination">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">test_destination</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Use this destination for testing, so events appear in real time under <strong>Test Events</strong> in your Facebook dashboard.
</p>

</div>

<div class="rs-ckey" id="test_event_code">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">test_event_code</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Test event code from your Facebook dataset&rsquo;s <strong>Test Events</strong> tab.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Applies when <code>test_destination</code> is <code>true</code>. Leave it unset otherwise.</li>
<li>At most 100 characters, and must not contain line breaks.</li>
<li>A <code>{{ path || fallback }}</code> template is accepted in place of a literal.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="limited_data_usage">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">limited_data_usage</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Forward the event&rsquo;s <code>context.dataProcessingOptions</code> to Facebook — Meta&rsquo;s Limited Data Use flags.
</p>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/setup-guide/#limited-data-usage" >Limited data usage</a>.
</div>

</div>

<div class="rs-ckey" id="remove_external_id">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">remove_external_id</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Stop sending <code>userId</code> or <code>anonymousId</code> as <code>external_id</code>. When <code>true</code>, neither is sent.
</p>

</div>

<div class="rs-ckey" id="blacklist_pii_properties">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">blacklist_pii_properties</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>array of objects</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Standard PII fields to drop — or, with <code>hash: true</code>, to SHA-256 hash and send. Standard PII fields are denylisted by default, so an entry here matters mainly to turn on hashing.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>property</code> — the PII field name. At most 100 characters, and must not contain line breaks. A template is accepted.</li>
<li><code>hash</code> — boolean. <code>true</code> hashes the field and sends it; <code>false</code> or unset drops it.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/setup-guide/#default-denylisted-pii-properties" >Default denylisted PII properties</a>.
</div>

</div>

<div class="rs-ckey" id="whitelist_pii_properties">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">whitelist_pii_properties</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>array of objects</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Standard PII fields to send as they are, when present in the event&rsquo;s properties.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>property</code> — the PII field name. At most 100 characters, and must not contain line breaks. A template is accepted.</li>
</ul>

</div>

</div>

</div>

### Web device mode

These keys configure the Pixel in the browser, so they apply only when `connection_mode.web` is `device`.

<div class="rs-ckeys">
<div class="rs-ckey" id="use_updated_mapping">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">use_updated_mapping</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Map user traits to Facebook&rsquo;s fields instead of sending them unmodified. Turn this on; the old mapping is being deprecated.
</p>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/setup-guide/#use-updated-mappings" >Use updated mappings</a>, including how it combines with <code>advanced_mapping</code> to pick <code>external_id</code>.
</div>

</div>

<div class="rs-ckey" id="auto_config">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">auto_config</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Let the Pixel send button clicks and page metadata to improve ad delivery — Meta&rsquo;s <a href="https://developers.facebook.com/docs/meta-pixel/advanced/#automatic-configuration" >automatic configuration</a>.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>web</code> — boolean. The dashboard defaults it to <code>true</code>; Rudder CLI doesn&rsquo;t fill it in.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="legacy_conversion_pixel_id">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">legacy_conversion_pixel_id</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>array of objects</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Sends specific events to a legacy conversion Pixel instead of <code>pixel_id</code>.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>from</code> — RudderStack event name. At most 100 characters, or a template.</li>
<li><code>to</code> — ID of the legacy conversion Pixel. At most 100 characters, or a template. <strong>Secret</strong> — see <a href="#secrets" >Secrets</a>.</li>
<li>A plain list, not keyed by <code>web</code>, though it applies only to web.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  <div class="rs-code">
  <div class="rs-code__head">yaml<button class="rs-code__copy" type="button">
      
      Copy
    </button>
  </div>
  <div class="highlight"><pre class="chroma"><code class="language-yaml" data-lang="yaml">legacy_conversion_pixel_id:
  - from: Signed Up
    to: &#34;{{ .FB_LEGACY_PIXEL_ID }}&#34;</code></pre></div>
</div><p>See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/device-mode/#legacy-events" >Legacy events</a>.</p>
</div>

</div>

</div>

### Event filtering

**Warning:** [Client-side event filtering](https://www.rudderstack.com/docs/sources/event-streams/sdks/event-filtering/) is applied by the RudderStack SDK, so it affects only web sources connected in `device` mode. Events sent in `cloud` mode aren&#39;t filtered by it.

<div class="rs-ckeys">
<div class="rs-ckey" id="event_filtering">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">event_filtering</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Restricts which <code>track</code> events the SDK passes to the Pixel, by event name.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>whitelist</code> — array of event names to allow; every other <code>track</code> event is dropped.</li>
<li><code>blacklist</code> — array of event names to drop; every other <code>track</code> event is allowed.</li>
<li>The two are mutually exclusive, and Rudder CLI enforces it — setting both fails validation.</li>
<li>Each name is at most 100 characters, or a <code>{{ path || fallback }}</code> template.</li>
</ul>

</div>

</div>

</div>

### Per-source keys

Both keys are objects keyed by the local source type — the tokens listed under [Source types](#source-types). A key naming a source type this destination doesn't support fails validation.

<div class="rs-ckeys">
<div class="rs-ckey" id="connection_mode">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">connection_mode</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Maps each source type you connect to the mode its events reach Facebook in, using the modes in <a href="#source-types" >Source types</a>. It also decides whether <code>access_token</code> is required.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>An entry is required for each source type you connect — see <a href="#connect-a-source" >Connect a source</a>.</li>
<li>A mode the source type doesn&rsquo;t support on this destination fails validation — for example <code>device</code> for <code>android</code>.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  <div class="rs-code">
  <div class="rs-code__head">yaml<button class="rs-code__copy" type="button">
      
      Copy
    </button>
  </div>
  <div class="highlight"><pre class="chroma"><code class="language-yaml" data-lang="yaml">connection_mode:
  web: device
  cloud: cloud</code></pre></div>
</div>
</div>

</div>

<div class="rs-ckey" id="consent_management">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">consent_management</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Consent provider configuration per source type. The entry shape, accepted providers, and the rules on <code>resolution_strategy</code> and <code>consents</code> are shared across all destination types — see <a href="https://www.rudderstack.com/docs/rudder-cli/destination-types/#consent-management" >Consent management</a>.
</p>

</div>

</div>

## Source types

Facebook Pixel accepts events from these source types in the mentioned connection modes:

| Source type | Connection mode |
| :-----| :-----|
| `android` | `cloud` |
| `android_kotlin` | `cloud` |
| `ios` | `cloud` |
| `ios_swift` | `cloud` |
| `web` | `cloud`, `device` |
| `unity` | `cloud` |
| `cloud` | `cloud` |
| `react_native` | `cloud` |
| `flutter` | `cloud` |
| `cordova` | `cloud` |
| `warehouse` | `cloud` |

Only `web` offers `device` mode, which loads the Meta Pixel in the browser. See [Facebook Pixel device mode](https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/device-mode/).

`warehouse` is the token a [Reverse ETL source](https://www.rudderstack.com/docs/sources/reverse-etl/) resolves to. Rudder CLI manages the destination’s `warehouse` entry — if the destination is connected to a Reverse ETL source, set `connection_mode.warehouse: cloud` in its spec, or `apply` removes it.

Rudder CLI can also declare the Reverse ETL connection itself, for the types listed under [Supported destinations](https://www.rudderstack.com/docs/rudder-cli/yaml-retl-connections/#supported-destinations) — see [Manage Reverse ETL Connections using Rudder CLI](https://www.rudderstack.com/docs/rudder-cli/retl-connections/).

**Info:** The dashboard additionally offers Facebook Pixel to AMP and Shopify sources. Rudder CLI doesn&#39;t manage those connections, so `amp` and `shopify` are invalid here.

## Connect a source

An event stream connection to this destination is checked against three rules at `validate` time.

**The source's type must be supported.** A source's type resolves to one of the tokens above before the check — a JavaScript source resolves to `web`, and webhook and server-side SDK sources resolve to `cloud`. Every type an event stream source can resolve to is supported here, so this check always passes.

**The destination config must carry a `connection_mode` entry for that source type.** This lives on the destination spec, not on the [connection spec](https://www.rudderstack.com/docs/rudder-cli/yaml-connections/). Without it:

```text
destination 'fb-pixel-prod' config has no 'connection_mode' entry for source type 'web'
```

**A source connecting in `cloud` mode needs `access_token`.** Every source type requires it in `cloud` mode; only `web` in `device` mode doesn't. Without it:

```text
destination 'fb-pixel-prod' config is missing fields required to connect a 'cloud' source: access_token
```

## Secrets

Rudder CLI treats three keys as secrets: `pixel_id`, `access_token`, and every `legacy_conversion_pixel_id` entry's `to` value. Write each one you use as a `{{ .VAR }}` reference and supply the value at apply time:

```yaml
config:
  pixel_id: "{{ .FB_PIXEL_ID }}"
  access_token: "{{ .FB_ACCESS_TOKEN }}"
```

```bash
export RUDDER_FB_PIXEL_ID="..."
export RUDDER_FB_ACCESS_TOKEN="..."
rudder-cli apply

# or
rudder-cli apply --var-file secrets.vars.yaml
```

Note that:

- `rudder-cli import` writes only the secrets the API returns, as `{{ .VAR }}` references, and leaves the others out. Add any secret key it leaves out, then supply the variables before you apply — see [Secrets](https://www.rudderstack.com/docs/rudder-cli/destination-types/#secrets).
- In device mode the Pixel IDs are embedded in the page's JavaScript, so masking them protects your YAML, not the values themselves.

See [How to Use Variable Substitution in Rudder CLI](https://www.rudderstack.com/docs/rudder-cli/variable-substitution/).

## Changes by release

<table>
  <thead>
    <tr>
      <th>Version</th>
      <th>Change</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Breaking:</strong> A <code>null</code> config value, written as <code>key: null</code>, <code>key: ~</code>, or <code>key:</code> with no value, fails <code>validate</code> with <code>'&lt;key&gt;' must not be null; set a value or remove the key</code>. Earlier releases accepted it: a top-level null planned an update on every <code>apply</code>, and a null inside a list item failed at the API.<br><strong>What to do:</strong> Remove the key to leave it unset, or give it a value.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Breaking:</strong> An empty string, <code>&quot;&quot;</code>, on a key that takes one of a fixed set of values fails <code>validate</code> with <code>'&lt;key&gt;' must be one of [...]</code>, unless <code>&quot;&quot;</code> is one of the key&rsquo;s values. Earlier releases accepted it, and the API rejected it at <code>apply</code>.<br><strong>What to do:</strong> Remove the key to leave it unset, or set one of the listed values.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Changed:</strong> <code>validate</code> warns when a secret key holds anything but one <code>{{ .VAR }}</code> reference with no default, and when one variable fills two secret keys. It also masks secret values in the lines it prints.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Changed:</strong> <code>rudder-cli import</code> writes each secret reference single-quoted, as <code>'{{ .VAR }}'</code>, so a value containing double quotes, like a JSON key file, substitutes as a string. A single quote in a value that fills such a reference is written as <code>''</code>.<br><strong>What to do:</strong> In a spec imported by an earlier release, quote each reference to a JSON value by hand: <code>'{{ .VAR }}'</code>.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Changed:</strong> <code>validate</code> reports a value of the wrong type once per key, such as <code>'email' must be a string</code>, instead of one raw decoding error.</td>
    </tr>
    <tr>
      <td>v0.28.0</td>
      <td><strong>Added:</strong> <code>warehouse</code> source type, for destinations connected to a Reverse ETL source. Set <code>connection_mode.warehouse: cloud</code> for such a destination, or <code>apply</code> removes the entry.</td>
    </tr>
  </tbody>
</table>

For changes across every destination type, see [Destination Type Changes by Release](https://www.rudderstack.com/docs/rudder-cli/destination-types/changes/).

## See more

- [Facebook Pixel Destination](https://www.rudderstack.com/docs/destinations/streaming-destinations/fb-pixel/setup-guide/) for the Pixel ID, access token, updated mappings, and `fbc` and `fbp` parameters
- [Facebook Conversions Destination Config Reference](https://www.rudderstack.com/docs/rudder-cli/destination-types/facebook-conversions/) for the server-side-only destination
- [Destination Type Reference for Rudder CLI](https://www.rudderstack.com/docs/rudder-cli/destination-types/) for the rules shared across destination types