| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Email Marketing (mass_mailing) • Sales (sale_management) • Calendar (calendar) • Contacts (contacts) • Discuss (mail) • Invoicing (account) |
| Lines of code | 593 |
| Technical Name |
lt_server_side_tracking |
| License | OPL-1 |
| Website | https://www.lumitec.solutions |
| Versions | 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Email Marketing (mass_mailing) • Sales (sale_management) • Calendar (calendar) • Contacts (contacts) • Discuss (mail) • Invoicing (account) |
| Lines of code | 593 |
| Technical Name |
lt_server_side_tracking |
| License | OPL-1 |
| Website | https://www.lumitec.solutions |
| Versions | 17.0 18.0 |
Server-Side Tracking: Turn User Data into Action
Ensure every user action is captured, even with browser restrictions like ad blockers, by tracking directly from the server for more accurate insights and higher conversions.
Facebook Server-Side Tracking
Enhancing User Engagement and Event Tracking with Meta Pixel Server-Side
Google Server-Side Tracking
Track your lead, event registration, and purchase Events from Google Analytics
In this guide, you'll discover how to set up and leverage the power of Facebook Server-Side Tracking and Google Server-Side Tracking to monitor user interactions with unmatched accuracy. By implementing Server-Side tracking, you can effectively capture key events such as event registrations, lead generation, checkouts, subscriptions, and purchases, seamlessly integrating them with Google Analytics and Meta Pixel.
Meta Server-Side Tracking
Meta Server-Side Tracking enables more accurate and reliable data collection, ensuring that all user actions on your website are tracked, even when browser restrictions limit traditional tracking methods. This results in improved marketing strategies, increased conversion rates, and optimized ad spend by providing deeper insights into user behavior and campaign performance.
Pixel id from pixel => setting => Dataset ID
Access token from the setting of the Pixel, on clicking the generate access token
Test
events â run the test with code
Configure the events from the Server-side Tracking App
To effectively track events such as leads, purchases, checkouts, and subscriptions in the Server-Side Tracking app, use Meta Pixel as the target for Facebook and GA4 (Google Analytics 4) as the target for Google Analytics.
If we review the Facebook events, we can see the events along with the data we have sent.
User successfully register for an event
On registering the event the
complete_registration event gets sent
On clicking confirm purchase events gets sent
purchase events gets sent
Copy the Pixel id from pixel => setting => Dataset ID
Generate access token from the setting of the Pixel, on clicking the generate access token
If you want test the configuration you can use the test code by copy the test event code
Enter credentials of Pixel Id, Access Token and Test Event Code (only if you like to run a test)
Configure the events from the Server-side Tracking App
To effectively track events such as leads, purchases, checkouts, and subscriptions in the Server-Side Tracking app, use Meta Pixel as the target for Facebook.
Source: In this step, you will select the type of event you wish to monitor. Example:
Lead: Triggered when a new lead is generated.
Purchase: Triggered upon confirmation of a sales order.
Complete Registration: Triggered when a new event registration is completed.
Checkout: Triggered when a sales order is created.
Subscription: Triggered when a new mailing list contact is added.
Data: Here, you'll define the specific data that should be collected and sent to the target platform. This could include user details, order information, or other relevant data points necessary for tracking and analyzing the event.
Target: You must choose where the event data will be sent. The available options typically include platforms like Google Analytics (GA4), and Meta Pixel.
Currency: In this field, you'll specify the currency in which the transaction or event value is to be reported.
Value: Lastly, assign a value to the event, this value represents the monetary worth of the event.
Example: Create a Lead in the system and test the server side tracking in meta
If we review the Facebook events, we can see the events along with the data we have sent.
User successfully register for an event
On registering the event the
complete_registration event gets sent
On clicking confirm purchase events gets sent
purchase events gets sent
Google Analytics Server-Side Tracking
Google Analytics 4 Server-Side Tracking allows for more precise and comprehensive tracking of user activity on your website, ensuring data is captured even when traditional tracking methods are limited. By using the Measurement ID and API Secret, you gain access to deeper insights into user interactions, enabling you to refine your marketing strategies, enhance user engagement, and make data-driven decisions that improve overall website performance and conversion rates.
Opening the datastream and copy Measurement ID
From google analytics => admin => data stream
Copy the Measurement Protocol API secrets from the data stream
Enter credentials of Measurement Id and Api Secret in Odoo/Configuration
Configure the events from the Server-Side Tracking App
To effectively track events such as leads, purchases, checkouts, and subscriptions in the Server-Side Tracking app, choose GA4 (Google Analytics 4) as the target for Google Analytics.
Source: In this step, you will select the type of event you wish to monitor. Example:
Lead: Triggered when a new lead is generated.
Purchase: Triggered upon confirmation of a sales order.
Complete Registration: Triggered when a new event registration is completed.
Checkout: Triggered when a sales order is created.
Subscription: Triggered when a new mailing list contact is added.
Data: Here, you'll define the specific data that should be collected and sent to the target platform. This could include user details, order information, or other relevant data points necessary for tracking and analyzing the event.
Target: You must choose where the event data will be sent. The available options typically include platforms like Google Analytics (GA4), and Meta Pixel.
Currency: In this field, you'll specify the currency in which the transaction or event value is to be reported.
Value: Lastly, assign a value to the event, this value represents the monetary worth of the event.
When a lead is created, we can see the lead event in Google Analytics 4 as its shows below.
DO YOU NEED HELP OR HAVE EXTENSION REQUESTS?
We are glad to provide you with a great experience. If you need assistance, have questions, or want to express extension request, we are always here for you. For assistance with our Odoo Apps, visit our webiste or email us for support.
Are you a Company Looking for a High-Performance Partner to Grow Your Business
https://www.lumitec.solutions
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