​
Overview

Destination Type:

Client-side
and
Server-side

​
Installation Instructions

  1. Navigate to your Facebook Events Manager.

  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.

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.

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

  2. In the Converge sidebar, click on

    Event streams
    and then click Create new Destination.

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

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

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

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

  7. Select Use default mapping and click Next.

You can find the Default mapping for the Meta Ads (Facebook Ads) destination here. For more information on setting up Custom mappings, look here.

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

  2. Review any issues and click Submit.

Once you have installed your Converge Destination, you should pause or remove all existing Facebook tracking. Leaving these on will lead to duplicate tracking. Check the Turn off your old tracking setup guide for additional instructions.

​
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 explicity 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 ModeBehavior
DefaultUse the variant_id if available, otherwise use the product_id
Product IdAlways use the product_id
Variant IdAlways use the variant_id
SKUAlways use the sku

​
Converge functionality

This integration supports the following Converge destination functionality.

Converge FeatureSupported
Custom Events
Filters
Server-side Conversions

​
FAQ

​
Event Mapping

Converge automatically maps the following events from the Converge Event Spec to the Meta spec.

Converge Event NameMeta Event Name
$page_loadPageView
Viewed ProductViewContent
Viewed CollectionViewContent
Added To CartAddToCart
Added To WishlistAddToWishlist
Started CheckoutInitiateCheckout
Added Payment InfoAddPaymentInfo
Placed OrderPurchase
Started SubscriptionSubscribe
Activated SubscriptionSubscribe
Placed Recurring Subscription OrderRecurringSubscriptionPaymentSucceeded
Cancelled SubscriptionCancelSubscription
Subscribed To NewsletterLead
SearchedSearch
Searched for StoreFindLocation

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 NameMeta Event Name
Placed Order (New Customers Only)NewCustomerPurchase

Was this page helpful?