About RN Strong Health
RN Strong Health is a health products store at rnstronghealth.com, built on WooCommerce with Bengali-language product pages and orders priced in BDT.
Project overview
RN Strong Health sells through a short WooCommerce checkout, and many customers also order by phone or WhatsApp. The store needed purchases and these contact actions to reach Meta reliably, together with GA4 ecommerce data for the checkout funnel.
I built paired browser and server Meta events in the web GTM container, routed them through a server-side GTM container with a Conversions API tag, and added GA4 checkout events and custom listeners for phone and WhatsApp clicks. Every step was checked in GTM preview, GA4 DebugView and Meta Events Manager.
Goals
- Send PageView, Initiate Checkout, Add Payment Info and Purchase to Meta from browser and server
- Deduplicate browser and server events so each order is counted once
- Track phone calls and WhatsApp clicks as Meta and GA4 events
- Deploy GA4 ecommerce events from checkout to purchase
- Pass customer data at purchase for advanced matching
Challenges
- Browser-only Pixel events are lost to ad blockers and tracking prevention
- Buyers who call or message on WhatsApp were invisible to ad platforms
- The purchase event fires on the thank-you page after a short one-page checkout
- Meta and GA4 needed consistent event names and order IDs
Strategy
I used a hybrid setup: each browser Meta Pixel tag has a matching "Fb - Server" GA4 event tag that sends the same action to a server-side GTM container, where a Conversions API tag forwards it to Meta with a shared event ID for deduplication. GA4 checkout events run from the same data layer, and custom HTML listeners turn phone and WhatsApp clicks into trackable events.
What I implemented
Web GTM container
- Meta Pixel tags for All PageView, Checkout, Purchase, Phone_Call and WhatsApp_Click
- Matching "Fb - Server" GA4 event tags for the same five events
- GA4 Add Shipping Info and Add Payment Info tags plus a GA4 config tag
- Custom HTML listeners for phone call and WhatsApp clicks
Server-side GTM
- Fb Conversions API Tag fired from the incoming GA4 stream
- Google Analytics GA4 - Ecommerce Tracking tag on the same stream
- Server events sent with action source "website", external ID, browser ID, IP address and user agent
GA4 eCommerce
- begin_checkout, add_shipping_info, add_payment_info and purchase events
- WhatsApp_Click and Phone_Call as lead events alongside the funnel
- Verified in GA4 DebugView during a test order
QA in Meta Events Manager
- Test purchase checked with BDT currency, content ID, product name and order ID
- Browser purchase advanced matching: city, email, first and last name, phone, state, ZIP, IP and user agent
- PageView, Initiate Checkout, Add Payment Info, Phone_Call, WhatsApp_Click and Purchase confirmed as deduplicated
Tools used
Results
- All 15 web GTM tags fired on the thank-you page during a test purchase
- Server GTM preview showed the Conversions API and GA4 ecommerce tags each firing 13 times
- Purchase, Initiate Checkout, Add Payment Info and PageView received from browser and server in Meta, with the duplicate removed
- Phone_Call and WhatsApp_Click received from browser and server and deduplicated in Meta
- GA4 DebugView recorded purchase, begin_checkout, WhatsApp_Click and Phone_Call during the test order
