Meta Ads (Facebook Ads)
An introduction to the Meta/Facebook Ads Destination
Overview
Destination Type:
- Includes support for the Facebook Conversions API
Installation Instructions
-
Navigate to your Facebook Events Manager.
-
From your Events Manager, click on the Facebook Pixel you would like to connect.
-
In the Facebook Pixel menu, choose the Settings subtab.
-
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.
-
Scroll down in the Settings subtab until you find Generate access token, and click on it. Copy this token as well.
-
In the Converge sidebar, click on
Event streamsand then click Create new Destination. -
Select the Meta Ads (Facebook Ads) destination and click Next.
-
Give your destination a name (e.g. Meta Ads Destination) and click Next.
-
Fill in the Pixel ID and Access Token you copied from Facebook and click Next.
-
Fill in your homepage domain name in the Your Domain name field, it does not need to include
https://. Click Next. -
Select Use default mapping and click Next.
-
Select the sources you want to forward events from, then click Next.
-
Review any issues and click Submit.
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.
- Navigate to your Meta Ads Destination, click on Configuration.
- Click on the Configuration-subtab
- Open the Advanced configuration (optional) section
- 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 | |
| Filters | |
| Server-side Conversions |
FAQ
Event Mapping
Converge automatically maps the following events from the Converge Event Spec to the Meta spec.
| Converge Event Name | Meta Event Name |
|---|---|
| $page_load | PageView |
| Viewed Product | ViewContent |
| Viewed Collection | ViewContent |
| Added To Cart | AddToCart |
| Added To Wishlist | AddToWishlist |
| Started Checkout | InitiateCheckout |
| Added Payment Info | AddPaymentInfo |
| Placed Order | Purchase |
| Started Subscription | Subscribe |
| Activated Subscription | Subscribe |
| Placed Recurring Subscription Order | RecurringSubscriptionPaymentSucceeded |
| Cancelled Subscription | CancelSubscription |
| Subscribed To Newsletter | Lead |
| Searched | Search |
| 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 (New Customers Only) | NewCustomerPurchase |