$ 278.32
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) • eCommerce (website_sale) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2062 |
| Technical Name |
website_sale_brevo_api |
| License | OPL-1 |
| Website | https://garazd.biz/shop/odoo-brevo-events-api-261 |
| Versions | 16.0 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) • eCommerce (website_sale) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2062 |
| Technical Name |
website_sale_brevo_api |
| License | OPL-1 |
| Website | https://garazd.biz/shop/odoo-brevo-events-api-261 |
| Versions | 16.0 17.0 18.0 |
- Community
- Enterprise
Server-side Brevo integration for Odoo e-Commerce tracking via Events API
When your clients interact with your Odoo eCommerce, it would be great to get these events when a visitor views your product, adds it to the Cart or Wishlist, begins the checkout, completes the order. These tracking events can be provided to the Brevo.com marketing service via Events API and help you successfully close this sale and make new sales.
Brevo Events API - is a server-side integration to provide tracking data from Odoo to Brevo.com.
With the current solution, tracking events can be sent as via Brevo Tracker, JS snippet, as through the API. Events contain product details and contact data for identifying on the Brevo side.
Follow these steps to configure the solution:
How to get the Brevo Tracker API Key Enable Website Tracking Configuration in Odoo Contact Identifying
Integrate in minutes
Compatible with Odoo CE and EE
Free 30 days support and 180 days bug-fixing
Demo & Test. Click on the "Live Preview" button
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.
When you are going to use the Advanced Matching and send your website customers' names in the tracking data, specify the order of the first and the last names. As, in some countries, a partner name can start with the first name, and with the last name in others.
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.
The following settings should be applied:
- Specify a website (if you have a multi-website environment).
- Select the "Brevo Tracker" service type.
- Fill in your Brevo API Key.
- Activate the "Internal Logs" option.
Internal logging must be enabled for Brevo Events API integration.
Additionally, it provides internal tracking analytics that can be viewed by clicking on the "Logs" button at the top of the form.
- Activate the "API" option.
- With the "Remove JS Pixel script" you can manage to use the Brevo Tracker JS implementation or not.
If you deactivate the Tracker JS snippet, tracking data will be sent only by Events API.
To provide contact identifiers and properties to Brevo, activate the "External ID", "Customer Name", "Email", and "Phone" options on the "Advanced Matching" tab.
This contact data is transferred via Events API to identify the user, and can be used in Brevo.com for automations, SMS and Email campaigns, transactional emails.
To view these identified contacts, open the "Contacts" - "Lists" menu in your Brevo account, and select the identified_contacts list.
In case when you allow guest checkouts without registering on the Odoo portal, it can cause a lack of user data for advanced matching.
By selecting the Sale Order Partner option, you can supplement user data by customer details from their previous sales orders.
-
16.0.1.0.0 2025-02-10
- Init version.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module