Perform the following steps to obtain a Pixel ID before adding the JS script to the website:

• 01
  Log in to the Meta Ads Manager account
• 02
  Navigate to Events Manager — Integrations — Meta Pixel


• 03
  Select an existing dataset or create a new one in the pop-up window
• 04
  Select the Add Meta Pixel code to website yourself option
• 05
  Skip the next steps by clicking Next

Navigate to the Datasets section and copy the Dataset ID:

After installing the module, go to the website settings and enable the Activate Tracking option in the Enhanced Website Tracking section. To test your website tracking and view tracking events in the browser console, temporarily enable the Debug Logging feature:

The module includes a cookie consent management feature for Meta Pixel, which integrates with the native Odoo cookie bar. To use this feature, enable the Cookies Bar:

By default, all Meta cookie consents are granted. To change this and revoke default consent for website visitors, enable the Facebook Pixel — Consent is Revoked (by default) option. Once enabled, Meta cookie consent is granted after a visitor clicks I agree and is revoked if the visitor clicks Only essentials.

To send eCommerce events to Meta Ads Manager, first add and configure a tracking service for your Odoo website.

Adding a Tracking Service

Go to the Website - Configuration - Tracking - Services menu and click New to add a new tracking service:

Firstly, fill in the following fields in the new tracking service:

• Specify a Website (if using multiple websites)
• Select Facebook Pixel as the service Type
• Paste your Pixel ID into the Key field

Then, specify the type of product identifier and product category sent to Meta Ads Manager:

If products have attributes and variants, choose Product Variant ID in the Item Type field; otherwise, select Product Template ID.

Select the desired Category Type: an eCommerce Public Category or an internal Product Category.

The next option is the Lead Value on the Options tab:

This field represents the monetary value of a lead generation, based on estimated evaluations.

Conversions API Setup

Enable the Internal Logs option:

Internal logging is required for API integration.

Before configuring the API in Odoo, obtain an access token in Meta Ads Manager:

• 01
  Open your dataset and navigate to the Settings tab
• 02
  Select the Set up with Dataset Quality API in the Conversions API section
• 03
  Click the Generate access token button
• 04
  Copy the access token

After that, return to Odoo and activate API mode by completing the following steps in the API section:

• Enable the Activate option
• Paste the copied Conversions API key into the Access Token field

The Advanced Matching feature optimizes your Meta ads by providing user data to Facebook. Enable Advanced Matching for Pixel events in both Meta Ads Manager and Odoo.

Activation in Meta Ads Manager

Navigate to Meta Ads Manager, open the Datasets menu, and select the Settings tab for your dataset:

Enable the Automatic website matching option and specify which customer information to share with Facebook.

Activation in Odoo

Return to Odoo and open the Advanced Matching tab in the Facebook tracking service. Replicate the settings for the user data sends to Facebook:

The module hashes customer information to comply with Meta requirements and sends it along with product tracking data to improve performance efficiency.

Customer Data Source

Use the Sales Order Partner value for Customer Data Source, as it provides more user details if visitors check out as guests without registration:

Internal logs record visitor actions on your Odoo website to assist with further analysis and monitoring. Click the Logs button at the top of the form:

Enable the State and API Sent Date columns to display a status and the date of event sending through the Conversions API:

Scheduled Actions

The module uses a scheduled action to send tracking events periodically. By default, this action runs every 30 minutes, but you can adjust this interval to meet your requirements:

To send tracking data manually, select tracking logs from the list or open a log and click on Send Event:

Sensitive Data Cleanup

Because tracking logs contain sensitive data such as IP addresses and user agents, configure a cleanup schedule. Go to the website settings and set the cleaning period. The default period is 30 days:

Enable the Unlink Logs After Period option to completely remove tracking logs older than the specified period.

The module includes additional settings available in Developer Mode.

Product Identifier

The solution uses the Product ID field as a unique product identifier. To use a different value, specify another product field containing the desired identifier on the Technical tab:

The specified product field should provide non-empty values and remain unique for each product. Otherwise, the tracking data for this product becomes unusable.

Purchase on Portal

To track portal purchases, enable the Track Purchase on Portal option:

Exclude Delivery

The next available setting for tracking services is Exclude Delivery. When enabled, the service excludes delivery lines from sales orders in tracking data transmissions:

Exclude Rewards

To exclude reward order lines from tracking data, enable the Exclude Reward option:

Add to Cart

By default, the module tracks the actual addition of a product to the cart. To track the event upon clicking the button without waiting for the actual addition to the cart, perform the following steps:

• Navigate to Website — Configuration — Websites
• Open the website on the Enhanced Tracking tab
• Enable the Add to Cart on Click option

Tracking the actual addition might fail if third-party modules modify the logic. In this case, this option allows for event tracking by binding it to button selectors used in native Odoo website templates.

Purchase

To track purchases only after a successful payment transaction, enable the Track Confirmed Purchases only option:

This option only affects the event transmission through the tracking service; the internal log records the event regardless.

If business logic considers an order with a Pending payment status as a purchase, enable the Track Pending Purchases too option as well.

For testing, log out of Odoo or use a different browser, as website tracking does not work for internal Odoo users.

Perform the following steps to verify the Meta Conversion API integration:

• 01
  Log in to your Meta Ads Manager account
• 02
  Open your dataset and navigate to the Test Events tab
• 03
  Select Website from the channel list
• 04
  Open the Confirm your server’s events are set up correctly section
• 05
  Copy the test_event_code

Next, return to Odoo and paste the copied Test Code into the tracking service options. Also, enable the Remove JS Script option to prevent the Pixel script from sending events to Meta before the Conversions API:

Perform a few actions on your Odoo website, such as viewing a product page or adding an item to the cart. Navigate to the logs list and send these events manually.

If the state is Warning or Error, review the API Response value on the Technical tab for detailed information:

The Sent state indicates that the Conversions API successfully transmitted the event:

Return to Meta Ads Manager and verify the results:

Once testing is complete, clear the Test Code field and disable the Remove JS Script option, as combining browser and server-side event tracking improves performance.