How to stitch server-side events to recover missing ga4 revenue for subscription products
I ran into this problem last year while auditing a mid-market SaaS client: GA4 was underreporting revenue for subscription products by a worrying margin. The short story was that client-side events (browser / app) were getting blocked by ad blockers and ITP, while server-side events were firing without a reliable stitch to tie them to the original session or user. The fix was to stitch server-side events back to the client-side footprint so GA4...