What events does TrackBee send to GA4?

TrackBee sends five Shopify ecommerce events: page_viewed, product_viewed, product_add_to_cart, checkout_started, and payment_info_submitted. Each event includes complete Shopify product data (SKU, category, variant, price, quantity, discount) and attribution parameters from all ad platforms.

Will TrackBee cause duplicate events in GA4?

No. TrackBee uses unique transaction IDs for deduplication. If both your existing GA4 setup and TrackBee report the same purchase event, GA4 will only count it once. You can safely run both in parallel during the transition period.

TrackBee × GA4 — Preview

Trustworthy conversion data for GA4

GA4 isn't broken — it's just missing data. TrackBee feeds GA4 with first-party, server-side Shopify events so your analytics finally match reality.

Start Free Trial Book a Demo

Server-side Measurement Protocol No GTM required Live in 5 minutes

The problem

GA4 isn't broken — it's just blind

GA4 relies on client-side tracking that's structurally incomplete for Shopify. The result: analytics you can't trust and decisions you shouldn't make based on them.

Traffic labelled "(unassigned)" or "(not set)" because attribution parameters are lost client-side
Revenue in GA4 doesn't match Shopify, eroding trust in every report
Inflated "direct / none" traffic hides which channels are actually driving results

Shopify ecommerce events

All standard Shopify events captured server-side and delivered to GA4: page_viewed, product_viewed, product_add_to_cart, checkout_started, payment_info_submitted and purchase.

Product & order context

Every event is enriched with first-party Shopify catalogue data — product name, SKU, variant, category, price, quantity, discount, transaction ID, shipping, tax and currency.

Cross-platform attribution

Click IDs and UTM parameters are captured server-side and forwarded to GA4: gclid, gbraid, wbraid, fbp, ttclid, epik plus full UTM source, medium, campaign and ad data.

Data source

Client-side (browser)

Server-side (first-party)

Revenue accuracy

Doesn't match Shopify

Matches Shopify

Attribution

"Unassigned" / "(not set)"

Click IDs + UTMs preserved

Product context

Generic events

SKU, variant, category

GTM dependency

Required + fragile

Not needed

Maintenance

Per-client GTM fixes

Zero. Fully automated

Server-side conversion stitching

Every Shopify event is sent to GA4 via the Measurement Protocol with a stable transaction ID. GA4 deduplicates against your existing tag, so purchases reconcile against Shopify revenue — even when client-side tracking fails.

First-party UTM persistence

TrackBee captures gclid, gbraid, wbraid, fbp, ttclid, epik and full UTM parameters on first touch and persists them across the session — so GA4 attributes the purchase to the right channel instead of "(unassigned)".

How to enable it

1 Open your TrackBee dashboard and select your store
2 Go to your GA4 integration settings
3 Paste your GA4 Measurement ID and API Secret
4 Toggle on "Server-side conversion stitching"
5 Recovered events appear in GA4 Realtime within minutes

Note: TrackBee runs alongside your existing GA4 setup. Transaction IDs guarantee deduplication, so there's no double-counting during the transition.

No. TrackBee sends all ecommerce events directly to GA4 via the Measurement Protocol, independent of GTM. You can keep your existing GTM setup running alongside, but TrackBee handles all Shopify ecommerce tracking server-side without any tag configuration.

TrackBee sends the full Shopify ecommerce set: page_viewed, product_viewed, product_add_to_cart, checkout_started, payment_info_submitted and purchase. Each event includes complete Shopify product data (SKU, category, variant, price, quantity, discount) and attribution parameters from all ad platforms.

No. TrackBee uses unique transaction IDs for deduplication. If both your existing GA4 setup and TrackBee report the same purchase, GA4 will only count it once. You can safely run both in parallel during the transition.

You enter your GA4 Measurement ID and GA4 API Secret in TrackBee, and the integration is live. No GTM containers, no custom event mapping, no developer required. Setup takes under 5 minutes.

TrackBee sends all attribution parameters (gclid, fbp, ttclid, epik, UTM values) server-side with every event. GA4 receives the context it needs to attribute traffic correctly, significantly reducing "(unassigned)" and "(not set)" sessions caused by lost client-side parameters.

Yes. TrackBee's server-side events complement your existing client-side tracking. GA4 deduplicates events using transaction IDs, so there's no double-counting. Over time, your GA4 data becomes more complete as TrackBee fills the gaps left by browser-side limitations.