Answers to common questions for this project.
This document describes how to implement Server-side events tracking. With this implementation we can significantly improve data accuracy, enhance data privacy, and optimize our marketing campaigns. This will lead to more effective ad spending, improved conversion rates, and a competitive advantage in our marketing efforts.
We observe that our current client-side tracking setup is susceptible to data inaccuracies, impacting the reliability of our conversion reporting for GA4, Google Ads, and Meta Ads. This hinders our ability to make data-driven marketing decisions and optimize our campaigns effectively.
This implementation is to be carried out when starting a new ProfitCo, PortCo, and existing Feasibility test at Mechanism for which event tracking is required. Moreover, this implementation can also be carried out for existing ProfitCo and PortCo at Mechanism, at the request of their respective leadership teams.
This procedure is to be executed by the Lead or Senior Engineers within the Product team at Mechanism OR by Growth team members such as Tiger Team Leads (TTLs) during the execution of their Feasibility tests.
Expected benefits from server-side events tracking.
Reduce the risk of losing valuable tracking data needed for personalized marketing and accurate analytics.
Ensure complete and accurate analytics even when ad blockers prevent essential tracking scripts from running.
Attribute conversion to Social Media campaigns even if tracking in the browser or app is not allowed or was blocked.
Ensure user privacy and GDPR compliance and easily anonymise or remove user data.