Case study:
server side tracking success story for skincare company
Our team worked with a rapidly growing skincare brand rooted in organic beauty principles, this company has built a strong reputation for its clean formulations and results-driven products. With a focus on authenticity and sustainability.
As part of its continued digital growth, the team has placed increasing emphasis on data-driven marketing, using performance insights to refine campaigns, optimize spend, and strengthen customer acquisition.
Operational Context
Operating primarily through Shopify, like many eCommerce companies, they rely heavily on paid advertising across Meta and Google Ads to drive conversions and scale revenue.
However, with tracking frameworks built largely on outdated client-side data collection, the data accuracy faced growing challenges with event attribution, and visibility across platforms, leading them to explore more advanced tracking solutions to future-proof their performance measurement. One major requirement was for the company to be able to see attribution reporting in GA4 accurately, which was not possible before we began working together. We partnered with Stape in order to setup a first-party data environment using a server-side google tag manager container.
The Challenge: Tracking Limitations Before Server-Side Implementation
The use of client-side tracking led to blockages in the data which were preventing marketing success:
- Incomplete and inconsistent data due to client-side tracking only – this mostly affected the companies ability to measure users across sessions.
- Loss of visibility into key events (purchases, add to carts, product views).
- Inaccurate session tracking and double-counting between Google and Facebook integrated shopify apps.
- Poor event match quality, little to no match data available before google tag manager implementation. .
- Difficulty tracking UTM parameters and campaign effectiveness.
- Challenges amplified by privacy and consent issues around the same time.
why did the brand opt for server-side tracking?
Server side tracking allows for one cohesive source of truth for the companies data. It allows greater control over the flows of information sent to and received from ad platforms. This allows ad campaigns to optimise fuelled by accurate data, driving data led marketing strategies. It avoids duplication of events, and also allows a more accurate picture of attribution path reports, to see which platforms are driving awareness and incrementality.
The implementation of server side tagging allows for improved event match quality, ensuring accurate and complete data to be sent to meta, google and various ad platforms. This also allowed us to clean up duplication of events to ensure we were reporting on accurate data to understand campaign reporting.
We opted to use Stape for its seamless integrations with Shopify and Google Tag Manager, the ease of set-up, maintenance and scalability made it a vital implementation.
How does server side tracking work? and what is the implementation process?
The server-side tracking implementation was rolled out at the start of the year, shifting the brand toward more reliable and privacy-resilient data collection.
The project was executed using Stape’s server container, seamlessly integrated with Google Tag Manager (GTM) server-side. This setup allowed the brand to centralise data processing, ensuring cleaner, faster, and more secure event handling before sending information to ad platforms.
To strengthen attribution and improve data flow, the Stape container was connected directly to Meta’s Conversions API (CAPI) and Google’s Ads API. This connection ensured that conversion events including: add_to_cart, view_cart, and purchases were transmitted accurately and in real time, from one organised and enriched source of truth. Enhancing both reporting precision and algorithmic learning in the platforms, but also in GA4. This helps avoid the trap of having over-inflated reporting in platforms, and helps GA4 have a more holistic picture of each event fired.
The implementation also focused on UTM parameter tracking, providing the marketing team with clearer insight into which specific campaigns and channels were driving the highest-quality traffic and conversions. Aligning with the goal of data-driven attribution to fuel their marketing strategy and the GA4 Attribution Paths Report.
An essential part of the process involved de-duplicating client-side and server-side events, ensuring that metrics remained accurate and free of double-counting. Early in the rollout, minor discrepancies between Google and Meta event tracking were identified and quickly resolved through adjustments in GTM configuration.
Following these refinements, the brand achieved a stable and fully operational server-side setup, laying the groundwork for improved event accuracy, higher match quality, and stronger campaign attribution across all platforms.
immediate results
Within days of the implementation the brand saw measurable improvements in data accuracy and reporting visibility. We picked up on a notable spike in paid-search sessions post-deployment, coinciding with the consent adjustment period indicating improved data capture and event consistency.
One of the most impactful outcomes was the dramatic increase in event match quality in Meta, which rose from 0–5 to consistently above 9. This improvement signalled a much stronger connection between on-site user activity and ad platform identifiers, enabling Meta and Google to optimise campaigns more effectively as they can more effectively match users who are engaging with the brand.
How does server side tracking affect google analytics?
Over in Google Analytics 4 (GA4) tracked purchases showed a significant uplift following deployment:
This jump not only reflected cleaner, more complete data but also confirmed that the brand had been under-reporting conversions prior to implementation.
Server-side event counts often exceeded browser-reported figures, reinforcing the effectiveness of the new setup in capturing conversions that were previously lost due to browser restrictions or consent limitations.
These early results indicate that server-side infrastructure allowed for stronger data-attribution signals, improved ad optimization, and a more reliable foundation for future campaign analysis.
1,724
Purchases
before deployment
4,512
Purchases
After Deployment
long term results
Over the months following implementation, the brand saw improvements in marketing performance and decision-making. With accurate, high-quality data flowing into Meta and Google, the marketing team can trust the data-attribution models to make smarter, evidence-based optimizations.
One of the most impactful outcomes was the dramatic increase in event match quality in Meta, which rose from 0–5 to consistently above 9. This improvement signalled a much stronger connection between on-site user activity and ad platform identifiers, enabling Meta and Google to optimize campaigns more effectively.
server-side tracking led to Improved conversion efficiency
One of the clearest indicators of progress came from Google Ads, where Cost per Purchase dropped significantly following the server-side deployment and subsequent consent stabilization:
£18.15
January
Cost Purchase
£19.42
February
Cost Per Purchase
£11.97
↓ 39.39% April
Cost Per Purchase
This consistent decline highlighted not only improved tracking but also more efficient ad delivery and better signal feedback into Google’s optimisation systems, translating into higher ROI and more cost-effective growth.
conversion rate optimization
Once tracking stabilised, the brand’s conversion rate surpassed 10%, driven by cleaner attribution, more reliable event capture, and improved customer retargeting accuracy. This also fuelled better insights into strategic decisions regarding ad budgets within platforms.
Enhanced campaign optimisation
The uplift in event match quality rising from roughly 5 to 9+, also allowed Meta’s algorithms to learn faster and target more effectively, resulting in more qualified traffic and higher-performing campaigns.
Together, these results demonstrate how server-side tracking fundamentally strengthened the brand’s marketing infrastructure, fuelling decisions about campaign performance and scaling.
How Server-Side Tracking Improved Meta Ads Performance
By implementing the Meta Conversions API, through Stape’s server-side container, the client was able to pass cleaner, more complete conversion data directly to Meta, significantly improving signal quality and algorithmic learning.
Between 1 December and 11 March (pre-implementation), Meta campaigns generated 611 purchases from a total spend of £27,721, resulting in a £41.44 cost per purchase. Engagement remained modest, with a 0.94% click-through rate (CTR).
Following the server-side implementation on 12 March, performance improved dramatically. Over the period from 12 March to 1 June, the brand achieved:
3,807
purchases
(INcreased from 1724)
£14
cost per purchase
(down approx -40%)
+3.01
ROAS
(Return on Ad Spend)
+1.47%
CTR
(Click Through Rate)
How did server-side tracking improve meta ads performance?
Server-side tracking improved the Meta ads performance by providing the algorithm with cleaner, more complete data. This data allows the algorithms to learn from the data and better target users likely to convert.
Previously, many purchases and add-to-carts were lost due to browser side tracking limitations, such as ad blockers, iOS privacy changes, and consent restrictions. With server-side tracking in place these events were accurately captured directly from the server and sent via the Meta Conversions API (CAPI) ensuring conversions were read more accurately.
Algorithmic learning
This provides Meta with a stronger feedback loop allowing its algorithm to better understand which audiences and ad creatives were driving actual purchases. As a result, ads were served to more qualified users, leading to a sharp drop in cost per purchase and a substantial increase in total tracked conversions.
Beyond fixing tracking gaps, this improved data quality leading to smarter campaign optimisation. The higher event match quality allows meta to connect more on-site actions to real users, improving the efficacy of targeting. This allowed meta to find an audience more likely to convert, in turn increasing the CTR and overall ROAS.
This improvement allows Meta’s algorithm to more accurately identify and retarget high-intent audiences, turning tracking accuracy into a tangible performance advantage.
The measurable impact of server-side tracking
The transition to server-side tracking with Stape enabled the skincare brand to unlock cleaner data, stronger attribution, and a measurable uplift in marketing performance.
As privacy regulations evolve and browser restrictions tighten, the implementation demonstrates how server-side tracking is becoming essential for modern eCommerce brands seeking to maintain accuracy, efficiency, and growth in their marketing operations.
