Facebook Conversions API¶
The add-on provides the ability to transfer the site events information directly to Facebook via Conversions API service.
This system allows collecting and tracking analytical, event and order data from your server, evading the browser limitations. Event transferred via Conversions API are connected to Facebook Pixel and processed the same way. That means that Conversions API events can be used in analytics, reports and optimization processes just as Facebook Pixel ones.
Observe the more detailed information about Facebook Conversions API here.
- Evade browser and ad block limitations
- Use Conversions API to collect data directly from the server
- The add-on is compatible with Facebook Pixel
- Data transfer to Facebook Ads
The add-on is compatible with CS-Cart and Multi-Vendor 4.9.x and above. The minimum PHP version should be at least 7.2. Don’t know what archive to download to install the add-on? Read here.
There are three tabs in the add-on settings:
- Conversions Tracking
Identifier Facebook Pixel - identification number of your Facebook Pixel the event information is sent to. Observe the detailed instruction for Facebook Pixel here.
Facebook Conversions API token - token for event data transferring to Facebook Pixel via Conversions API. Token can be generated in Facebook Pixel settings in the Conversions API paragraph.
Display personalized Facebook Pixel and Conversions API for vendors - this setting allows vendors to insert their Identifier Facebook Pixel and Facebook Conversions API token, so they could receive data concerning their products
Log requests - option allows logging of the requests to and answers from Conversions API into the event log.
Conversion Tracking Tab¶
The tab contains the list of events to be tracked and sent to Facebook.
|Event title||Activated when||Transferring to vendor||Note|
|One Click Buy||One Click Buy form is sent from the product page||Yes||“Purchase“ event type in Facebook Pixel|
|Initiate Checkout||The Checkout Page is opened||Yes||
When the option is activated, the initiation stages can be selected for tracking
“All stages“ - the event will be transferred every time
“After authorizing or filling out the address only“ - the event will be transferred if the customer is authorized or filled out the address only
|Request call||The Request Call form is sent||Yes (when is sent from the product page) No (in any other case)||The event data will be classified as “Purchase“ type in case it was sent from the product page. In any other case the event will be classified as “Lead“|
|Add to Cart||The product is added to the cart||No||Quantity of the products in the cart is not tracked|
|Page View||Viewing any page||No||Isn’t displayed in the add-on settings, always activated|
|View Content||Product Page is viewed||Yes||–|
|Search||The product is searched||No||–|
|Add to Wishlist||The Product is added to Wishlist||Yes||–|
|Add Payment Info||The checkout is fixed and payment data are inserted||Yes||–|
|Purchase||The checkout is complete||Yes||–|
|Lead||The product page is viewed||Yes||–|
|Complete registration||The user is registered||No||–|
Facebook Pixel and Facebook Conversions API add-on are similar in purpose and different in the data transferring method
In order to prevent data duplication, the Facebook Conversions API add-on includes the Facebook made event deduplication mechanism. Hence, the simultaneous use of two add-ons is possible.