Client: Tea of Sylhet · Direct-to-Consumer eCommerce
Every sale, verified back to real revenue.
Full-funnel hybrid tracking and revenue attribution for a premium tea brand — combining browser and server-side measurement so no purchase signal gets lost to cookies, ad-blockers, or browser restrictions.
Industry
Direct-to-Consumer eCommerce
Core Channel
Paid Acquisition / Google Ads
Scope
GA4 · GTM Web + Server · Stape · Google Ads
1. Client
Tea of Sylhet - Direct-to-Consumer eCommerce Brand
Tea of Sylhet is a direct-to-consumer eCommerce brand selling premium regional tea blends. The brand relied heavily on paid acquisition and needed tracking it could trust to guide spend.
2. Project Overview
Sales were happening. The revenue picture wasn't.
Tea of Sylhet relied heavily on paid acquisition but lacked reliable measurement. Key funnel events were tracked inconsistently and revenue values were not reliably sent to Google Ads, making it hard to know which campaigns actually drove sales.
The project rebuilt tracking from the ground up: a hybrid browser + server setup with Google Analytics 4, Google Tag Manager, and a server container (Stape) using a custom tracking domain so events are delivered reliably even when browsers block cookies or scripts.
3. Direction
Goal vs. reality
Project Goal
The primary goal was to implement a complete analytics ecosystem that could:
- Implement 100% accurate GA4 Enhanced eCommerce tracking
- Track all product & funnel events: view → cart → checkout → purchase
- Enable full Google Ads conversion attribution
- Capture WhatsApp clicks, scroll events & form submissions
- Create a data-driven reporting system for revenue and ROAS
Challenges
Several major tracking and reporting issues existed before implementation:
- Purchase events lacked revenue values and product details in Ads reporting
- GA4 didn't follow enhanced eCommerce mapping across the funnel
- Browser-only tracking suffered signal loss from cookie expiry, ITP and ad-blockers
- Remarketing lists were generic, not behavior-driven, so conversion potential was low
- Decision-making relied on fragmented data rather than verified revenue signals
Strategy
A hybrid, client + server tracking approach
We adopted a hybrid approach: keep client-side events for immediate UI signals and DebugView visibility, and add server-side processing to validate and forward purchases as authoritative events. A custom tracking domain was used to reduce blocking and treat events as first-party where possible.
- Conversion accuracy
- User engagement tracking
- Funnel visibility
- Campaign attribution
5. Implementation
What was actually built
GA4
Trigger Configuration
form submissions
CTA clicks
phone clicks
email clicks
scroll-depth
WhatsApp interactions
GA4
Custom Parameters
page_category
service_type
lead_type
form_location
GA4
Enhanced Measurement
Enabled enhanced measurement inside GA4 for baseline site interactions.
GA4
Conversion Mapping
Mapped high-intent actions as GA4 conversions.
GA4
Google Ads Integration
Synced GA4 with Google Ads for conversion tracking and audience creation.
GA4
Validation
GA4 DebugView
Tag Assistant
cross-device testing
Tools Used
Google Tag Manager (GTM)
Google Analytics 4 (GA4)
Google Ads
Meta Pixel (future-ready)
Before → After
Summary
What Tea of Sylhet can do now
The hybrid tracking setup with a server container and custom domain fixed the core problems: data loss, missing revenue, and weak audiences. Tea of Sylhet can now see which campaigns truly drive sales, create precise remarketing lists, and scale Google Ads with confidence because the numbers are verified.
- Track every purchase and product interaction with full accuracy
- Attribute revenue back to the exact campaign that drove it
- Feed Google Ads real conversion data for smarter bidding
- Make marketing decisions on ROAS, not guesswork
Still have questions?
Feel free to reach out directly. I'm always happy to help.
