Facebook Pixel

overview chord’s facebook integration works best when both browser and server events are sent to facebook we recommend configuring two facebook segment destinations a https //segment com/docs/connections/destinations/catalog/facebook pixel/ , connected to your website front end segment source a https //segment com/docs/connections/destinations/catalog/actions facebook conversions api/ , connected to your server segment source alternatively, you can connect a second facebook conversions api destination to your website front end segment source and omit the facebook pixel destination this setup results in pre checkout events (ex product added ) and one post checkout event, order completed , being sent to facebook from your website front end source, and post checkout events (ex order completed ) being sent to facebook from your server source order completed is duplicated from both sources for maximum reliability for chord tracking events, facebook https //developers facebook com/docs/marketing api/conversions api/deduplicate pixel and server events by comparing the event name and the external id property, which should be set to segment’s userid (or anonymousid if not present) see instructions below for how to configure your facebook pixel and conversions api destinations to use userid / anonymousid as facebook’s external id facebook pixel destination this destination loads the facebook pixel javascript library in the browser and sends chord events to it client side, without hitting segment’s servers first first, configure the facebook pixel destination https //segment com/docs/connections/destinations/catalog/facebook pixel/#getting started event mapping to map chord segment events to standard facebook events, create the mappings in the destination setting “map your events to standard fb events” the following mapping is recommended as a minimum order completed , which segment sends to facebook as purchase product added , which segment sends as addtocart product list viewed , which segment sends as viewcontent product viewed , which segment sends as viewcontent products searched , which segment sends as search checkout started , which segment sends as initiatecheckout in segment, this should look like segment event mapping you can add additional mappings here if you need them, too external ids enable two settings under advanced settings “enable advanced matching” and “use user id or anonymous id as external id” enabling both of these sends the segment userid (or anonymousid if not present) as the external id to facebook, which improves facebook’s ability to connect segment events from various sources to the same user implementation checklist connect facebook pixel destination to website front end source create event mappings in the destination setting “map your events to standard fb events” enable the destination settings “enable advanced matching” and “use user id or anonymous id as external id” facebook conversions api destination the https //segment com/docs/connections/destinations/catalog/actions facebook conversions api/ sends chord events to facebook via facebook’s conversions api chord events are sent to segment, and then segment sends the events to facebook this destination can be connected to either browser or server event sources if connected to a browser event source, the facebook pixel destination should not be used for that same browser event source, because that will gather duplicate data first, configure the facebook conversions api destination https //segment com/docs/connections/destinations/catalog/actions facebook conversions api/#getting started next, the facebook conversions api destination requires you to map chord segment events to facebook standard events using with chord’s server source at a minimum, we recommend mapping the following chord server source events to facebook standard events order completed , which segment sends as purchase when you’re creating event mappings, you’re required to provide a value for the action source property in the select mappings section select “system generated” as the action source see https //developers facebook com/docs/marketing api/conversions api/parameters/server event of the action source property for descriptions of the different options using with chord’s website front end source at a minimum, we recommend mapping the following chord website front end events to facebook standard events order completed , which segment sends as purchase product added , which segment sends as addtocart product list viewed , which segment sends as viewcontent product viewed , which segment sends as viewcontent products searched , which segment sends as search checkout started , which segment sends as initiatecheckout when you’re creating event mappings, you’re required to provide a value for the action source property in the select mappings section select “website” as the action source see https //developers facebook com/docs/marketing api/conversions api/parameters/server event of the action source property for descriptions of the different options select "website" as the action source external ids by default, the conversions api destination correctly maps facebook’s external id property to segment’s userid (or anonymousid if not present) don’t make changes to this configuration map to externalid implementation checklist connect the facebook conversions api destination to the server source if not using the facebook pixel destination, connect the facebook conversions api destination to the website front end source as well create event mappings, following the minimum recommended mapping listed above, and remember to specify the correct “action source” property for each mapping