> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runconverge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Meta Ads (Facebook Ads)

> An introduction to the Meta/Facebook Ads Destination

## Overview

Destination Type: Client-side  and Server-side

* Includes support for the [Facebook Conversions API](https://www.facebook.com/business/help/2041148702652965)

***

## Installation instructions

1. Navigate to your [Facebook Events Manager](https://business.facebook.com/events_manager2).

2. From your Events Manager, **click on the Facebook Pixel** you would like to connect.

3. In the Facebook Pixel menu, choose the **Settings** subtab.

4. From this subtab, you can find your **Pixel ID**, and copy it -- you will need it in a later step.

> [!WARNING]
>
> Ensure that the **Track events automatically without code** setting is turned off in the **Event Setup** subtab.
> This can lead to over-reporting of events and incorrect conversion values.

5. Scroll down in the Settings subtab until you find **Generate access token**, and click on it. Copy this token as well.

6. In the Converge sidebar, click on **Destinations** > Conversion tracking and then click **Create new destination**.

7. Select the **Meta Ads (Facebook Ads)** destination and click **Next**.

8. Give your destination a **name** (e.g. Meta Ads Destination) and click **Next**.

9. Fill in the **Pixel ID** and **Access Token** you copied from **Facebook** and click **Next**.

10. Fill in your homepage domain name in the **Your Domain name** field, it does not need to include `https://`. Click **Next**.

11. Select **Use default mapping** and click **Next**.

> [!NOTE]
>
> You can find the Default mapping for the Meta Ads (Facebook Ads) destination [here](#event-mapping). For more information on setting up Custom mappings, look [here](https://docs.runconverge.com/destinations/event-mapping.md).

12. Select the sources you want to forward events from, then click **Next**.

13. Review any issues and click **Submit**.

> [!WARNING]
>
> Set this destination to **Deactivated** while you remove your existing Facebook tracking setup. Running both in parallel leads to duplicate conversion data. Follow the **Turn off your old Facebook tracking** instructions below, then set the destination to **Active** when you're ready.

***

## Turn off your old Facebook tracking

### Turning off the Shopify Facebook Sales Channel data sharing

1. Navigate to your [Shopify Admin Dashboard](https://admin.shopify.com/).

2. Click on **Sales channels** and choose **Facebook & Instagram** from the *Installed sales channels* menu.

3. Click on **Settings**.

   ![settings-facebook](https://mintcdn.com/converge/zWlDFBz7l1F_0PFn/images/guides/turn-off-tracking/shopify-facebook-sales-channel/shopify-facebook-sales-channel-0.png?fit=max\&auto=format\&n=zWlDFBz7l1F_0PFn\&q=85\&s=5934881238367ac999117fdd7790c707)

4. Click on **Change** in the **Share data** submenu.

   ![settings-facebook-1](https://mintcdn.com/converge/zWlDFBz7l1F_0PFn/images/guides/turn-off-tracking/shopify-facebook-sales-channel/shopify-facebook-sales-channel-1.png?fit=max\&auto=format\&n=zWlDFBz7l1F_0PFn\&q=85\&s=e6adc3d11db43dfe2f4cd6da456dbca4)

5. Turn the **Share data** switch **off** (it should be gray) and press **Save**.

   ![settings-facebook-2](https://mintcdn.com/converge/zWlDFBz7l1F_0PFn/images/guides/turn-off-tracking/shopify-facebook-sales-channel/shopify-facebook-sales-channel-2.png?fit=max\&auto=format\&n=zWlDFBz7l1F_0PFn\&q=85\&s=f94d6b3b12cd6ae1ab143662dd7dbfed)

***

## Modify your Content ID

The Converge Meta Ads Destination will use the **Default** content mode to define the Content ID forwarded by default.
However, you can configure the destination to use explicitly the **Product ID**, the **Variant ID** or **SKU** instead.

1. Navigate to your Meta Ads Destination, click on **Configuration**.
2. Click on the **Configuration**-subtab
3. Open the **Advanced configuration (optional)** section
4. Pick your desired Content ID, and click on **Save**

**List of Content ID Modes**

| Content ID Mode | Behavior |
| - | - |
| Default | Use the `variant_id` if available, otherwise use the `product_id` |
| Product Id | Always use the `product_id` |
| Variant Id | Always use the `variant_id` |
| SKU | Always use the `sku` |

***

## Converge functionality

This integration supports the following Converge destination functionality.

| Converge Feature | Supported |
| :- | :-: |
| [Custom Events](https://docs.runconverge.com/destinations/event-mapping.md#event-mapping-modes) | |
| [Filters](https://docs.runconverge.com/destinations/filters.md) | |
| [Server-side Conversions](https://docs.runconverge.com/destinations/event-mapping.md#forwarding-modes) | |
| [Conversion amount](https://docs.runconverge.com/destinations/conversion-amount.md) | |

***

## FAQ

> [accordion] Why do I see a Duplicate Pixel ID warning in my console?
>
> If you are a Shopify store, Converge needs to load both a `theme.liquid` pixel and a Shopify Custom Pixel to track reliably.
> See the [FAQ in the Shopify Integration](https://docs.runconverge.com/sources/website-integrations/shopify.md#faq) for more detailed information.
>
> Converge makes sure that no duplicate events get sent, even though the Facebook Pixel needs to be loaded in two separate places for complete event coverage.
>
> > [!NOTE]
> >
> > If you are not using the Shopify Web integration, you might have an old pixel installed using a different tracking method, and you should turn this one off.

> [accordion] Why do I see "increase coverage"-warnings in my Events Manager?
>
> ![increase-coverage](https://mintcdn.com/converge/dh0K_Fgr0_qazJsh/images/destinations/facebook/facebook-increase-coverage.png?fit=max\&auto=format\&n=dh0K_Fgr0_qazJsh\&q=85\&s=101913d455597a6ea68c4ebbbe76f04a)
>
> Meta is warning you here that not all of your events are receiving identifiable information (e.g. `email`).
> Ideally, Facebook would have an email for every Added To Cart that ever happens on your website so they can easily attribute it.
>
> However, many people on the website are anonymous (they have never given their email to your store and thus Converge cannot track it). If the user never gives their email or address, then we can never send that email back.
>
> **Converge sends as many of these parameters as there are available.**
>
> The only events where you'd expect a very high email match rate are events where the user always has to give an email (e.g., `purchase`).
>
> For all events where certain parameters are not always available (e.g., you don't expect all `AddToCart` or an `InitiateCheckout` to have an `email`), you can safely ignore this warning.

> [accordion] Why is my Click ID (fbc) percentage low?
>
> ![Facebook Click ID (fbc)](https://mintcdn.com/converge/dh0K_Fgr0_qazJsh/images/destinations/facebook/facebook-click-id.png?fit=max\&auto=format\&n=dh0K_Fgr0_qazJsh\&q=85\&s=8e46fb5382e4e932fb998e76a16c0911)
>
> When inspecting the Event match quality score in Meta Events Manager, it's common to see a low percentage for the `Click ID (fbc)` parameter. In most cases, this is an expected value given how the `fbc` parameter works.
>
> The `Click ID (fbc)` is a parameter generated by Meta that's added to the URLs of your ads and used by Meta to track and identify events and conversions. See [ClickID and the fbp and fbc Parameters](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc/) for additional information.
>
> In an extreme scenario where all of your visitors arrive from a Meta ad, the `Click ID (fbc)` parameter would be present in 100% of your events.
>
> Not all your traffic will originate from Meta, though. Users can reach your store through, for example, search engines, other ad platforms, or even directly. This traffic won't contain the `fbc` parameter in the URL, as it's exclusive to Meta ads.
>
> Given that, consider another extreme scenario where none of your traffic originates from Meta ads—it's expected that `Click ID (fbc)` would be zero.
>
> Overall, you should expect the percentage of `Click ID (fbc)` to be directly related to the percentage of traffic your store receives that originates from Meta ads.
>
> In summary, if your store uses multiple marketing channels with no particular focus on Meta, it's expected to see low percentages for the `Click ID (fbc)` parameter. On the other hand, if your store relies heavily on Meta with a majority of your traffic coming through it, you should expect higher percentages.

> [accordion] How do I use the NewCustomerPurchase event?
>
> Converge automatically sends the `NewCustomerPurchase` event to Facebook. To start using it for reporting and optimization, you need to create a custom conversion in Facebook Events Manager.
>
> We have a guide on setting up this custom event in the Meta Ads Manager [here](https://docs.runconverge.com/guides/set-up-nc-purchase.md).

> [accordion] Why do I see "update recommended" warnings about IPv6 addresses in the Events Manager?
>
> ![update-recommended](https://mintcdn.com/converge/dh0K_Fgr0_qazJsh/images/destinations/facebook/facebook-update-recommended.png?fit=max\&auto=format\&n=dh0K_Fgr0_qazJsh\&q=85\&s=b086aa48c9201b86e1fec7b0b053545f)
>
> Meta asks you to send an IP Address as part of the Event Matching parameters when you send over events. There are currently two versions of IP addresses in use: IPv4 and IPv6.
>
> Both are still widely in use, but the IPv6 standard is newer, which is why Meta flags that it's still receiving IPv4 addresses. Converge supports IPv6 and sends IPv6 addresses whenever they're available.
>
> However, there's not always an IPv6 address available. In that case, Converge sends the IPv4 address instead. The IP address version is dependent on the customer's browser and network configuration. If the customer's network configuration and browser only support IPv4, then Converge will need to send an IPv4 address as well.
>
> Note that Meta does accept IPv4 addresses—it just wants to make sure that all advertisers support IPv6 as well. Therefore, you can safely ignore this warning.

> [accordion] The Facebook Ads manager is over-reporting conversions and/or the conversion value is wrong.
>
> Confirm the following steps to troubleshoot:
>
> * The Facebook pixel is correctly configured. When the Facebook **Automatic Events** are enabled, Facebook tracks purchases automatically across your website—typically with a wrong AOV. This is a common source of over-reporting. You can turn this off in the Facebook Events Manager under **Settings** > **Event setup** > **Track events automatically without code**.
> * Converge is the only active Facebook integration. In the Converge destination logs, you can recognize it as **External** pixel events. Make sure all other Facebook tracking integrations other than Converge are turned off. See [here](#turn-off-your-old-facebook-tracking).
> * Converge tracks the correct number of `Placed Order` events. Compare the **Attribution** > **Orders** numbers with your backend.
> * The correct dataset is linked to your Facebook ads. The dataset ID should match your Converge destination configuration.
>
> If none of the above provides a solution to your problem, take a closer look at the **Facebook Events Manager**. Verify the Purchase event by looking at the number of events arriving from the server and browser, and the sampled activities.

***

## Event mapping

Converge automatically maps the following events from the [Converge event spec](https://docs.runconverge.com/sources/converge-spec.md) to the Meta spec.

| Converge Event Name | Meta Event Name |
| - | - |
| [\$page\_load](https://docs.runconverge.com/sources/converge-spec.md#page-load) | `PageView` |
| [Viewed Product](https://docs.runconverge.com/sources/converge-spec.md#viewed-product) | `ViewContent` |
| [Viewed Collection](https://docs.runconverge.com/sources/converge-spec.md#viewed-collection) | `ViewContent` |
| [Added To Cart](https://docs.runconverge.com/sources/converge-spec.md#added-to-cart) | `AddToCart` |
| [Added To Wishlist](https://docs.runconverge.com/sources/converge-spec.md#added-to-wishlist) | `AddToWishlist` |
| [Started Checkout](https://docs.runconverge.com/sources/converge-spec.md#started-checkout) | `InitiateCheckout` |
| [Added Payment Info](https://docs.runconverge.com/sources/converge-spec.md#added-payment-info) | `AddPaymentInfo` |
| [Placed Order](https://docs.runconverge.com/sources/converge-spec.md#placed-order) | `Purchase` |
| [Started Subscription](https://docs.runconverge.com/sources/converge-spec.md#started-subscription) | `Subscribe` |
| [Activated Subscription](https://docs.runconverge.com/sources/converge-spec.md#activated-subscription) | `Subscribe` |
| [Placed Recurring Subscription Order](https://docs.runconverge.com/sources/converge-spec.md#placed-recurring-subscription-order) | `RecurringSubscriptionPayment` |
| [Cancelled Subscription](https://docs.runconverge.com/sources/converge-spec.md#cancelled-subscription) | `CancelSubscription` |
| [Subscribed To Newsletter](https://docs.runconverge.com/sources/converge-spec.md#subscribed-to-newsletter) | `Lead` |
| [Searched](https://docs.runconverge.com/sources/converge-spec.md#searched) | `Search` |
| [Searched for Store](https://docs.runconverge.com/sources/converge-spec.md#searched-for-store) | `FindLocation` |

This integration also auto-tracks some additional events that are not part of the Meta Base Spec but are so heavily requested that we automatically forward them.

| Converge Event Name | Meta Event Name |
| - | - |
| [Placed Order](https://docs.runconverge.com/sources/converge-spec.md#placed-order)  (New Customers Only) | `NewCustomerPurchase` |
| | |

> [!WARNING]
>
> To track custom conversion events in Converge, you must first set up the corresponding custom conversions in the [Facebook Ad Manager](https://www.facebook.com/events_manager2/custom_conversions). Without setting up these custom conversions, Converge will be unable to display the associated metrics.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.