The Facebook Business Extension, v1 is currently only available to whitelisted Partners. Please contact your Facebook representative for access.
You get the pixel from the popup and install it where necessary. For example, if
Purchase events are done on www.yourstore.com/item1-purchase, you tell the popup which URL feed you will use to communicate it, to populate this product.
Follow these steps to insert the Facebook pixel ID into every page for any given store on your platform:
For example, see
Purchase events on your platform.
The diagram below shows how the pixel requirement was implemented in the plugin. In this specific example, there are two main components:
In order of importance (most to least), they should be listed as
PageView. Learn more about standard and custom events.
Purchase for a specific product, you must fire these events with a specific content ID to enable dynamic ads.
This must be the same content ID you used when you uploaded or created a feed file with that product. You can use the SKU or whatever is available, as long as you ensure consistency between pixel and catalog.
Purchase events specifically, you should pass back the transaction value.
For specific implementation details and examples, see sample code from the plugin:
Your implementation may differ slightly from this example. You need to include an agent string in every pixel fire that helps our systems analyze downstream pixel traffic; see example implementation.
The agent hash is the fourth parameter in the init pixel code.
[Optional] After setup is complete, you can direct users to a simple ads creation interface geared towards platform integrations, which Facebook has created to help users boost sales.