Marketing and analytics integration
Google Analytics 4
What it does
- Loads the gtag snippet on your storefront and sends standard e-commerce events such as view_item, add_to_cart, and purchase.
- Tags traffic from price-comparison feeds and campaigns with UTM parameters so channels are separated in GA4 reports.
- Sends the same events server-side through the Measurement Protocol, so purchases are counted even when an ad blocker stops the browser script.
Google Analytics 4 is part of Kambloo's launch catalog, together with Meta Pixel and the Google Merchant feed. It gives every store a working measurement base from day one: page views, product views, cart actions, checkout steps, and purchases, all reported under your own GA4 property. The integration is an Internal Module and is included; the GA4 property is free from Google.
How it works with Kambloo
The client side uses gtag. Once you paste your measurement ID, the storefront theme injects the snippet through its script slot and fires GA4's standard e-commerce events at the right moments: view_item on product pages, add_to_cart from the cart, begin_checkout and purchase on the checkout path. Event parameters follow GA4's schema, with item IDs, names, prices, and quantities taken from the order. The purchase event carries the order ID and value so revenue reports reconcile with your admin panel.
Scripts are loaded in a way that respects the theme's JavaScript budget. Analytics and pixel tags are deferred or served through a worker proxy, and the storefront remains server-rendered HTML that does not depend on them.
Traffic sources are labeled. Links generated by Kambloo for external channels carry UTM parameters, so visits from the Çimri and Akakçe feeds, email campaigns, and recovery messages appear as separate channels in GA4 rather than as untagged referrals.
The Measurement Protocol is the server half. Kambloo sends the same events from its queue, keyed to the client session, so purchases are counted when an ad blocker or a closed tab stops the browser from reporting. The Meta and TikTok integrations use the same server-side pattern.
Search Console is handled alongside GA4. The SEO panel includes a verification wizard for your store domain.
Requirements
- A GA4 property and its measurement ID.
- A published storefront; events are recorded from live pages only.
- Optional: Search Console ownership for the verification wizard.
Setup steps
The short version. The screens in your store admin follow the same order.
- Create a GA4 property in Google Analytics and copy the measurement ID.
- Paste the measurement ID under Settings > Marketing > Google Analytics 4.
- Place a test order and confirm the purchase event in GA4's real-time view.
- Optionally run the Search Console verification wizard from the SEO panel.
Questions about Google Analytics 4
Does the GA4 script slow down my store?
Third-party scripts are loaded deferred or through a worker proxy so they stay outside the theme's JavaScript budget. Storefront pages are server-rendered and do not wait for analytics.
What does the Measurement Protocol add?
It sends events from Kambloo's servers rather than the browser, so purchases are recorded even when a blocker stops the client script. Server events carry the same IDs as the browser events, so GA4 counts each once.
Do I need GA4 for Google Ads?
Not strictly, but the Google Ads integration builds on the same event set. Setting up GA4 first makes conversion tracking consistent.