Facebook Conversion

Using Facebook Server Events

Installing only the Facebook Pixel is rapidly losing its impact:

1. The average global adblocking rate in early 2018 was estimated at 27 percent. (source)
2. Browsers are blocking Facebook cookies (i.e. Firefox) or set a 7-day expiration date (i.e. Safari)
3. iOS14 impact placing even more importance on the 8 conversion events being accurate

There are a lot of discrepancies between Craft Commerce orders and Facebook purchases. Facebook Server Events can't be blocked and will track 100% of all purchases.

The best practice is to use Conversions API in addition to the Facebook pixel. The Facebook pixel continues to be an effective Business Tool in cases where your customers have unblocked cookies on their web browsers, or if they use web browsers that have not yet blocked cookies by default. Conversions API doesn’t use cookies, so web browser settings don’t impact your ability to send data from customers that have provided you with all necessary consents (if any). Used together, the pixel and Conversions API will maximize the effectiveness of your website customer data.

Features:

• When a user clicks on an external link in Facebook a Click-ID is added via the fbcid parameter. The parameter gets stored in the session and will be used to identify the user on later events, even when all Cookies are blocked.
• Send user search queries to Facebook as web event
• Send Craft Commerce purchase events to Facebook
• Send Craft Commerce cart events to Facebook
• Send Mollie Payments purchase events to Facebook
• All events are logged by using the preferred logger
• Facebook Pixel implementation via template hook