Tracking Suite Component
Google Analytics & GTM
Configure GA4 and Google Tag Manager from one merchant-friendly page without duplicate Google tracking.
OpenCart 4Tracking Suite 4.0.0Customer Guide
Choose one Google installation path, then let HuntBee prepare GA4 ecommerce events without loading duplicate tags.
Choose one Google delivery mode
| Choice | Use when | What HuntBee does |
|---|---|---|
| Let HuntBee install the Google tag Recommended | You do not already load gtag/GTM. | Loads the Google tag and sends enabled GA4 / Google Ads browser events directly. |
| I already have a Google tag | Your theme or another extension already loads it. | Uses the existing tag and does not inject another copy. |
| Let HuntBee install my GTM container | You want HuntBee to load your GTM container. | Loads the configured GTM container and pushes ecommerce events to dataLayer. |
| I already have Google Tag Manager | GTM is already installed. | Injects no container; pushes normalized events to the existing dataLayer. |
Do not install Google twice. If GTM or gtag is already in your theme or another extension, use an existing-tag mode.
Settings explained
| Setting | Recommended use |
|---|---|
| Enable Google Analytics | Enable when you want HuntBee to prepare GA4 ecommerce events. |
| GA4 Measurement ID | Your Data Stream ID such as G-XXXXXXXXXX. |
| GTM Container ID | Needed only when HuntBee is loading your GTM container. Looks like GTM-XXXXXXX. |
| Item ID source | Product ID is safest for most stores. Use Model or SKU only when that matches your Merchant Center/catalog strategy. |
| GA4 DebugView mode | Optional Google-side debugging. This is different from HuntBee Debug Logging. |
| Measurement Protocol API secret | Only required for server-side GA4 refunds. |
| Use EU server endpoint | Optional setting for server-side refund delivery through Google's EU collection endpoint. |
GA4 refunds are different from browser events
Normal product/cart/purchase tracking is delivered in the browser according to your Google mode. A refund originates in OpenCart admin, so the Suite can send supported GA4 refund information through Measurement Protocol. The original GA client ID captured when the order was placed is required.
How to test
- Enable HuntBee Debug Logging temporarily.
- Open a category and product page.
- Add a product to cart and proceed through checkout.
- Check Diagnostics → Event Log for Captured/Prepared entries.
- Use browser developer tools or GA4 DebugView if you need provider-side confirmation.
Remember: “Prepared” means HuntBee created a browser payload. It does not prove Google received or processed it.
Explore HuntBee Suites