Skip to Content

Facebook Conversions API

https://garazd.biz/web/image/product.template/146/image_1920?unique=271f13a
Leave your feedback

285.15
285.15 62
285.1503498190591 USD

Not Available For Sale

  • Odoo Version

  • Price

This combination does not exist.

Price: Paid

Overview

What is Odoo Facebook Conversions API, it is a way to send your marketing data, such us website events, some customer information, directly from your Odoo server to Meta (Facebook). This is an alternative channel as opposed to integration using the Odoo Facebook Pixel script. The Facebook CAPI integration can extend your Facebook Pixel tracking or replace it completely.

This data is collected in Odoo when your website visitors and customers make their journey on your Odoo website. Collected data is complemented by product data, and customer data, like as country, e-mail, phone number, in case if you enabled Advanced Matching. Odoo periodically sends this tracking data in a batch via Facebook CAPI integration.

This solution is designed to track customers' visits to e-commerce web pages and their eCommerce actions.

Advantages of using Facebook Conversion API in Odoo

Improved connection

The Facebook Conversion API helps track and measure conversions more accurately, especially when traditional tracking methods like browser-based cookies are limited.

Extra events tracking

Extended tracking of events, that are happened on Odoo side, like as signing of a sale order on Odoo customer portal, or making a payment through the generated payment link, allow providing additional tracking data about a customer journey.

Enhanced Data Accuracy

With more reliable data, the Meta Conversion API helps accurately attribute conversions to the correct advertising campaigns, leading to better insights into the effectiveness of their marketing strategy.

Cross-Device Tracking

The Facebook CAPI facilitates cross-device tracking, enabling businesses to understand how users interact with their ads and complete conversions across multiple devices, providing a more comprehensive view of the customer journey.

Using this solution, you can integrate and configure a Facebook Conversion API with your Odoo, collect website analytics and send events data to Facebook Events Manager. It's quite easy to start and does not require involving of developers. Just add a Facebook Pixel ID and an access token in a tracking service on Odoo side and activate the Conversions API mode.

Key features

Multiple Pixels

One of the main features of this solution is supporting of multiple tracker adding, so you can activate and configure several Facebook Pixel ID for each Odoo website in your system.

Internal Logging

The second feature provides internal logging of tracking events for the Facebook Conversion API, thereby this data can be analyzed in convenient for your business way, and extend your company's analytics capabilities.

Advanced Matching

In addition to the above features, you will be able to activate and configure Advanced Matching for this Conversions API integration. Customer information, that will be added to tracking events, will help to provide relevant ads through Facebook Ads Manager.

The Odoo Facebook Conversions API app is a professional tool to promote your products and services on Facebook and Instagram. This module is a part of the Garazd Creation Marketing Apps which cover marketing needs for businesses and fully compatible with each other. The Facebook Catalog and Instagram Shopping app perfect complements the current solution.

Availability
Odoo Online
Odoo.sh
On Premise
Compatibility
Community
Enterprise
Technical Name website_sale_facebook_capi
Version 18.0.1.1.0
License OPL-1
Category
Support Free 60 days support and 360 days bug-fixing

Use Case

Jorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc vulputate libero et velit interdum, ac aliquet odio mattis. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos.

Forem ipsum dolor sit amet, consectetur adipiscing elit. Nunc vulputate libero et velit interdum, ac aliquet odio mattis. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos.

Dorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc vulputate libero et velit interdum, ac aliquet odio mattis.

It is a long established fact that a reader will be distracted by the readable content of a page

Korem ipsum dolor sit amet, consectetur adipiscing elit. Nunc vulputate libero et velit interdum, ac aliquet odio mattis. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos.

Korem ipsum dolor sit amet, consectetur adipiscing elit. Nunc vulputate libero et velit interdum, ac aliquet odio mattis.

Odoo App Installation

Upload modules

Upload modules from the ZIP archive to your Odoo hosting, or a GitHub repository connected there.

Place the unzipped modules in your custom add-on directory and restart the Odoo system service.

Update App List

After restarting, activate the Developer Mode, and go to the Apps menu.

Odoo Update App List

Click on Update Apps List to fetch the new modules in the list.

Activate the App

Install the new module, finding it by name and clicking on the Activate button.

Odoo App Installation

* If you don't see the module, try to remove the default Apps filter from the search bar.

Configuration

Follow the instructions in the module description to complete the installation process and start using the app.

View Odoo App Description

Manual


Enable Website Tracking
Go to the menu "Website" - "Configuration" - "Settings" and activate the related option in the "Tracking" section.
Odoo Website tracking activate in 18.0
Sensitive data cleaning up

The solution cleans sensitive tracking data such as payload, client IP address, and user agent. You can control the period after which the purging is performed. By default, it's 30 days.

Additionally, you can activate the "Completely delete log entries older than the specified period" option to remove all internal tracking log records after this time.

Configuration
Adding a tracking service

Click on the "Manage Tracking Services" link or go to the "Configuration" - "Tracking" - "Services" menu and create a new tracking service for your Odoo website.

Odoo Meta Conversions API - configure a tracking service in 18.0

Configure the tracking service in the following way:

  • Specify a website (if you have a multi-website environment).
  • Select the service type "Facebook Pixel".
  • Fill in your Facebook Pixel ID.
  • Activate the "Internal Logs" option.
  • Activate the "Conversions API" option.
Getting an access token

The following steps will show how to get a Facebook Conversions API access token on the Facebook Events Manager side.

  • Open the "Data Sources" section in Facebook Events Manager and generate access token on the "Settings" tab in the "Conversions API" section.
  • Then copy this token and paste it to the related field in Odoo.
Odoo Facebook Conversion API access token generate for 18.0
Advanced Matching

Enabling Advanced Matching for Facebook Pixel events should be done on both sides, in Facebook Events Manager and in Odoo.

Open the "Data Sources" section in Facebook Events Manager and activate the "Automatic Website Matching" option on the pixel's "Settings" tab. Then, specify what kind of customer information will be shared with Facebook.

Meta Pixel Advanced Matching settings for Odoo

Repeat the related settings in Odoo, you can perform it on the "Advanced Matching" tab of the tracking service.

Odoo Facebook Pixel tracking with Advanced Matching in 18.0
Customer Data Source

In case when you allow guest checkouts without registering on the portal, it may not be enough data about the visitor for advanced matching.

You can use a customer data from the customer order, that provides more details for advanced matching. Select the "Sale Order Partner" value in this case.

Testing
Testing Particularities

As a website activity of internal users is not tracked and should not be sent to Meta (Facebook), there are several testing tips:

  • You will not see any internal tracking logs if you are logged in to Odoo and you have an internal user access rights.
  • Log out from the system, or use the incognito mode, or other browser to test tracking of website events.
Testing with Internal Logging

After completing of the tracking service settings, use another browser to make an order on your Odoo eCommerce.

Go through all checkout steps: from viewing the product list, adding products to cart, initiating a checkout process and finishing the confirmation page.

Switch back to initial browser and open the tracking service logs, you should see appropriated log records for all eCommerce events.

Odoo Meta CAPI tracking logs in 18.0
Testing with Facebook Events Manager

Foremost, get a test code from the Test Events tab in the Facebook Events Manager.

Odoo Facebook CAPI test events in 18.0

Put this code to the "Test Event Code" field in the tracking service in Odoo.

Than you need to send tracking events by Facebook Conversions API, to do this run a scheduled action "Website Tracking: Facebook CAPI - Send Tracking Events".

Odoo Facebook Conversions API send tracking events in 18.0
Tracking events will be sent via Meta CAPI to see the results, go to Facebook Events Manager:
Odoo Facebook Conversion API tracking events testing results 18.0
Monitoring events tracking
Monitor your website tracking on Facebook Events Manager to get analytics and get informed about performance and issues.
Odoo Facebook Pixel tracking events monitoring for 18.0

Changelog

16.0.1.3.2 2025-01-14

  • Improve user data processing.
  • Add demo data.

16.0.1.3.1 2024-10-18

  • Refactor fields "Deactivate Pixel" and "Test Code", make them common for all tracking services.

16.0.1.3.0 2024-10-09

  • Refactor API fields, make them common for all tracking services.

16.0.1.2.3 2024-04-04

  • Improve the form view of tracking services.

16.0.1.2.2 2024-02-16

  • Fix getting a visitor data from a request.

16.0.1.2.1 2024-02-09

  • Improve the tracking service form view.

16.0.1.2.0 2023-12-22

  • Implement a special case when tracking data lacks a customer data, mark this event as warning.
  • Implement a logic to allow working of both ways to pass tracking data to Facebook, via FB JS script and Facebook Conversions API. Users can remove the JS script from a website by the related setting.

16.0.1.1.0 2023-11-22

  • Improve advanced matching - add new params.

16.0.1.0.0 2023-07-13

14.0.1.1.1 2024-02-16

  • Fix getting a visitor data from a request.

14.0.1.1.0 2024-02-05

  • Implement a special case when tracking data lacks a customer data, mark this event as warning.
  • Implement a logic to allow working of both ways to pass tracking data to Facebook, via FB JS script and Facebook Conversions API. Users can remove the JS script from a website by the related setting.
  • Improve advanced matching - add new params.

14.0.1.0.0 2023-07-22

15.0.1.1.2 2024-04-05

  • Improve the form view of tracking services.

15.0.1.1.1 2024-02-16

  • Fix getting a visitor data from a request.

15.0.1.1.0 2024-02-07

  • Implement a special case when tracking data lacks a customer data, mark this event as warning.
  • Implement a logic to allow working of both ways to pass tracking data to Facebook, via FB JS script and Facebook Conversions API. Users can remove the JS script from a website by the related setting.
  • Improve advanced matching - add new params.

15.0.1.0.0 2023-02-27

  • Init version.

17.0.1.3.0 2025-08-04

  • Add the "fbclid" parameter to provide Facebook with the proper "fbc" value when Click ID passed through URL query.

17.0.1.2.0 2025-01-14

  • Refactor API fields, make them common for all tracking services.

17.0.1.1.4 2024-11-25

  • Improve demo data.

17.0.1.1.3 2024-09-03

  • Improve the user data "IP address" and "User Agent" passing.

17.0.1.1.2 2024-08-28

  • Improve the log form view, add "fbp" and "fbc" fields.

17.0.1.1.1 2024-05-13

  • Fix the tracking service form view.

17.0.1.1.0 2024-02-24

  • Improve the tracking service form view.

17.0.1.0.0 2023-11-07

  • Migration from 16.0.

18.0.1.1.0 2025-01-14

  • Refactor API fields, make them common for all tracking services.

18.0.1.0.0 2024-10-10

  • Migration from 17.0.

Reviews

Our customers have already appreciated the quality, reliability, and performance of the solutions we offer

Login to leave a comment

FAQ