Consulting
Webfleet

Improving tracking accuracy with Dual server-side and client-side tagging

icon - analytics graph
100%

Avoiding data loss

icon - metrics

icon - analytics

icon - analytics graph
100%

Avoiding data loss

icon - metrics

icon - metrics

icon - analytics

Challenges

Addressing data loss and inaccuracies with client-side Facebook Pixel tracking

The existing setup utilized traditional client-side JavaScript tags for Facebook Pixel, which were becoming increasingly unreliable due to factors like ad blockers, enhanced browser privacy settings, and the impending phase-out of third-party cookies in Chrome. These client-side tags were also susceptible to network issues, which could lead to data loss or delays in reporting.

‍

Approach

Implementing server-side Conversions API for more precise tracking

Our goal was to implement the Conversions API (CAPI) on the server-side to address these challenges, ensuring more reliable and precise tracking of user interactions and conversions. We mapped user actions and conversion events from the website to corresponding server-side events, setting up HTTP POST requests from the server to the third-party vendor's endpoint whenever a user action or conversion occurred. We maintained the client-side Pixel implementation to track the same events, allowing for a direct comparison between the two methods. Both client-side and server-side events were logged with unique identifiers to avoid duplicating events and enable accurate analysis.

‍

Solution

Dual tracking environment for seamless transition and enhanced data capture

Partnering with Programmads enabled Webfleet to establish a dual tracking environment effectively, ensuring continuous tracking of user interactions and conversions, even during the transition from client-side to server-side tracking.

‍

Results & Insights

Improved data reliability and accuracy through server-side tracking

Server-side tagging demonstrated an increase in captured events compared to client-side tagging. It resulted in more consistent data, with fewer discrepancies and no missing events, leading to more reliable reporting and insights. While one of the client-side collected events ceased collecting, the server-side events continued as expected, preventing data loss. Implementing Facebook's CAPI on the server-side proved to be a highly effective solution, overcoming the limitations of client-side tagging and significantly enhancing data accuracy, reliability, and overall marketing performance. The dual tagging approach allowed for a smooth transition and provided valuable insights that guided further optimization of the tracking and analytics setup.

‍