Facebook Pixel (Enterprise Destinations)
MetaRouter makes it easy to send your data to Facebook Pixel. Once you follow the steps below, your data will be routed through our platform and pushed to Facebook Pixel in the appropriate format.
Note: MetaRouter's Facebook Pixel destination consolidates what was previously Facebook's "Ads for Websites" suite, which consisted of both Facebook Custom Audiences and Facebook Conversion Tracking.
Facebook Pixel is an Ad system designed for conversion optimization and lead tracking. It allows you to manage all of your ads from one platform and uses prospecting tools to target your ads to lookalike audiences. By providing this dynamic service, Facebook Pixel allows marketers to optimize cross-platform ads for custom conversions and see when users view content, search for a product, interact with their wishlist, or add payment info.
To get started with this integration, you'll first need to create a Facebook for Business account. Follow the instructions for creating a Pixel.
You'll only create one pixel for your site (typically labeled with the name of your business). This pixel will replace all the functionality previously given to Facebook Audiences and Facebook Conversions (as well as allowing some additional features, such as custom conversions).
Once that's set up, identify your unique
pixelId, a 15 digit number that uniquely identifies your site.
Put your Facebook Pixel ID into your MetaRouter account and give your new connection a unique name.
With that, just click Save to activate your pipeline.
- name: "facebook-pixel" config: pixelId: "348149915804750" valueFieldIdentifier: "price" whitelistPII: - "email" - "phone" categoryToContentTypeMapping: 'Games': 'group' 'Lorem': 'ipsum' customEventsMapping: - event: "Custom Event 1" mapping: "ViewContent" - event: "Custom Event 2" mapping: "Subscribe" - event: "ViewCategory" mapping: "ViewContent" - event: "Order Updated" mapping: "ViewContent" valueFieldIdentifier: "revenueFORtest" customPropertiesForStandardEvents: - "prop1" - "prop23"
pixelId- the id you've got from the Facebook Dashboard
valueFieldIdentifier- if no
valueFieldIdentifieris set on standard events mappings or on any custom event mapped as custom, we’ll use this to get the value parameter.
whitelistPII- By default, we will strip any PII from the properties of track events that get sent to Facebook. If you would like to override this functionality, you can input each property you would like to whitelist as a line item in this setting.
categoryToContentTypeMapping- Enter your category value on the left, and the Facebook content type to map to on the right. Facebook recognizes certain event types that can help deliver relevant ads. If no category values are mapped we’ll default to product and product_group, depending on the event.
customEventsMapping- Enter your event on the
eventproperty, and the Facebook Standard Event to map to on
mappingproperties. Facebook recognizes certain standard events that can be used across Custom Audiences, custom conversions, conversion tracking, and conversion optimization. When you map an event to a standard Facebook event, we’ll send the event by that name. Any unmapped events will still be sent as Custom Events. According to Facebook Pixel Documentation, accepted Standard Events, with
mappingvalues as follows:
customPropertiesForStandardEvents- If you send a custom property with your
track()calls and you want to send it to your Facebook Pixel events you can add it here.
For all of the events sent to Facebook Pixel (including your
page() events) we map the following properties:
fbp- facebook cookie
ts- current timestamp
ud[em]- email, if it exits in traits
fullURLof the page.
referrerof the page
We'll map your
page() calls to the
UserProperties Pixel Standard event, without additional data
We'll map your
page() calls to the
PageView Pixel Standard event, without additional data.
By default, we map some of the Analytics.js Standard E-commerce events to Pixel Standard events, as following.
|Analytics.js||Pixel Standard Event||Pixel parameters|
|Product List Viewed||ViewContent||
|Payment Info Entered||AddPaymentInfo||
|Product Added to Wishlist||AddToWishlist||
All Pixel Standard Events will be mapped with the following properties.
||Array of Integers or Strings||Each id of your
||Array of Objects||Product details
||String||The currency for the specified value. Mapped from
||String||The field you've mapped for the event in your
To send Standard events, use the Analytics.js destination setting (from integrations.yaml ) named
customEventsMapping . Then, any time Analytics.js receives one of the events in that mapping, it will be sent to Facebook as the standard event you specified. All properties you included in the event will be sent as event properties.
To send Custom events, send any event that does not appear in either mapping. All properties you included in the event will be included as event properties.
Date object, it will be converted to this custom format:
Facebook enforces strict guidelines around sending Personally Identifiable Information (PII) as properties of Pixel events. In order to adhere to these guidelines, Analytics.js will automatically scan
track event properties for PII and remove any that get flagged from the event to Facebook. The following keys are currently filtered:
track events with properties containing those keys will be sent to Facebook with those properties omitted.
If you have events that use any of those keys for non-PII properties, you can manually whitelist them using the
whitelistPII object from your integrations.yaml file