Data8 min readJul 7, 2026• By Amit Singh

GA4 + Meta Pixel for E-Commerce: Conversion Tracking That Actually Fires

Half the e-commerce sites we audit have analytics 'installed' that has never recorded a single event. Before you spend ₹1 on ads, here's how to wire GA4 and Meta Pixel properly — and prove they work with one real test order.

Here's an uncomfortable pattern from our audits: a store owner says "we have Google Analytics and the Facebook Pixel installed," we open the reports, and there's nothing there. Zero events. The tag was pasted into the site months ago and has never fired once. They've been running ads blind — Meta and Google optimising toward nothing, budgets spent on guesswork. Conversion tracking isn't an analytics nicety; it is the steering wheel of every rupee you spend on ads. This is the setup that actually works, and the one test that proves it.

Why 'installed' so often means 'not working.'

Modern storefronts are JavaScript apps — React, Next.js, Vite, Shopify themes with heavy scripting. A raw `<script>` tag pasted into a component can get stripped, rendered but never executed, or executed once and lost on client-side navigation. We found exactly this on a site whose GA4 property showed "No data received" weeks after 'installation' — the framework was silently discarding the inline script. The fix is framework-appropriate loading (e.g. Next.js's Script component, or injecting via the HTML template in Vite) and then *verifying in the network tab* that requests to google-analytics.com and facebook.com actually leave the browser.

The four events that matter for e-commerce

Don't drown in event taxonomies. For a store, four events drive everything: ViewContent / view_item (product page seen), AddToCart / add_to_cart, InitiateCheckout / begin_checkout, and Purchase / purchase with value and currency attached. These four give GA4 a full funnel report, give Meta the signals for Advantage+ optimisation and retargeting audiences, and give Google Ads the conversion data Performance Max learns from. Everything else is decoration until these four are flowing.

Fire events from one place, driven by configuration

Our implementation pattern: a single analytics module that initialises both GA4 (gtag) and Meta Pixel from environment variables, exposes one `track(event, payload)` function, and maps each store action to both platforms' event names. The store code calls `track('purchase', {...})` once; the module tells GA4 *and* Meta in their respective dialects. Config-driven IDs mean staging environments don't pollute production data, and swapping an account never touches application code.

SPA navigation: the silent page-view killer

Single-page apps don't reload between pages, so the default page-view tracking fires once on first load and never again. Both GA4 and Meta need explicit page-view calls wired to your router's navigation events. Symptom that you have this bug: sessions with exactly one page view each, bounce rate near 100%, and product pages that show zero views despite real traffic.

The one test that settles everything: a real order

After wiring, we don't trust dashboards — we place a genuine small test order (a ₹149 COD order works fine) and trace it through every system: the purchase event visible in GA4 Realtime, the Purchase event in Meta Events Manager's test/live feed, and — after linking — the conversion recorded in Google Ads. Only when one real transaction has appeared in all three do we call tracking 'done.' This 15-minute test has caught wrong pixel IDs, events firing with zero value, currency mismatches, and duplicate firing that would have silently doubled reported revenue.

Connecting the pipes to your ad accounts

GA4 alone doesn't feed Google Ads. Link the GA4 property to the Ads account, mark `purchase` as a key event in GA4, then import it in Google Ads → Goals and set it as primary. Mark add_to_cart and begin_checkout as key events too and import them as secondary — extra learning signal without corrupting what the campaign optimises for. On the Meta side, verify your domain in Business Manager and confirm the Purchase event shows as active in Events Manager; Advantage+ Shopping campaigns won't optimise properly without it.

Expect these gotchas

Ad blockers block both tags — always verify in a clean/incognito browser, and don't panic if GA4 undercounts Meta by 5–15%. GA4's "data collection isn't active" banner is cached and can show for 24–48 hours after a correct install — trust Realtime, not the banner. `curl` or view-source won't show client-injected tags — use DevTools Network. And log your test orders somewhere: months later, that ₹149 order sitting in your revenue reports will confuse someone.

Tracking is the foundation, not the finish line

Once events flow, the same data powers everything downstream: GA4 audiences (cart abandoners for Performance Max audience signals), Meta retargeting, abandoned-cart recovery automation, and honest weekly reports. At HowAutomate we wire and *verify* the full tracking stack for D2C brands — GA4, Meta Pixel, Google Ads linking, and the automations on top. Book a free call and we'll tell you within a day whether your tracking is real or decorative.

Want this done for your business? See how we implement it end-to-end.

E-Commerce Automation & Ads

Frequently Asked Questions

How do I verify that GA4 and Meta Pixel are actually working?

Place one real small test order (a ₹149 COD order works) and trace it end-to-end: the purchase event in GA4 Realtime, the Purchase event in Meta Events Manager, and the conversion in Google Ads after linking. Dashboards and 'tag detected' banners can mislead; a single real transaction visible in all three systems is proof.

Why does my GA4 property show no data even though the tag is installed?

On JavaScript-heavy sites (React, Next.js, Vite, custom themes), a raw script tag pasted into a component often gets stripped or never executes. Use the framework's proper script-loading mechanism, then confirm in the browser DevTools Network tab that requests to google-analytics.com actually fire. Also note ad blockers suppress the tag — always test in a clean or incognito browser.

Which events does an e-commerce store actually need to track?

Four: view_item/ViewContent, add_to_cart/AddToCart, begin_checkout/InitiateCheckout, and purchase/Purchase with value and currency. These give GA4 a full funnel, give Meta the signals for Advantage+ optimisation and retargeting, and give Google Ads its learning data. Everything beyond these four is optional refinement.

How do I send GA4 conversions to Google Ads?

Link the GA4 property to your Google Ads account, mark purchase as a key event in GA4, then import it in Google Ads under Goals and set it as primary. Import add_to_cart and begin_checkout as secondary conversions for extra learning signal — but never as primary, or campaigns will optimise for cart-adds instead of sales.

Why do GA4 and Meta report different purchase numbers?

A 5–15% gap is normal. Ad blockers affect the two tags differently, attribution windows differ, and iOS privacy features hit Meta harder. Watch for larger gaps though — they usually indicate duplicate event firing, a currency/value mismatch, or events firing on page load instead of actual purchase confirmation.

Amit Singh

Founder, HowAutomate — Data Engineering, AI Automation & Cloud Infrastructure

Amit has 6+ years of experience building data pipelines, AI agents, and automation systems for businesses across India and globally. He founded HowAutomate to make enterprise-grade automation accessible to growing businesses.