Tracking Diagnostics
Use Health, Event Log, server queue and scheduler tools to diagnose HuntBee Tracking Suite safely.
The main place to see what is enabled, what is misconfigured, what events HuntBee captured, and what the server queue is doing.
Health
Use Health for a quick view of Suite status, Google delivery mode, consent source, registered OpenCart events, configured integrations and server queue state. It can also surface failed/uncertain server deliveries and GA4 refund gaps.
Event Log
The Event Log loads only when you open its tab. Debug rows are written only when HuntBee Debug Logging is enabled.
| Captured | The OpenCart action was normalized by HuntBee. |
|---|---|
| Prepared | A browser payload was created. This does not prove the provider received it. |
| Queued | A supported server event was stored for background delivery. |
The Safe Summary intentionally contains only a small allowlist such as currency, value, item count and limited item IDs. Tokens, secrets and unnecessary customer identity data are not shown.
Settings
| Browser debug logging | Writes [HuntBee Tracking] console messages and bounded Event Log rows. Turn it off after testing on a live store. |
|---|---|
| Observe non-jQuery AJAX | Compatibility option for themes that do not use jQuery for cart requests. Leave off unless you need it. |
| Send customer ID as user ID | Optional measurement user ID using the OpenCart customer ID—not email or name. |
| Map a refunded order status | Optional full-refund automation. Manual refund history takes priority so mapped status cannot duplicate an already recorded refund. |
Schedule
Browser GA4 page/product/cart events do not wait for cron. The scheduler is mainly needed for server-side delivery such as Meta CAPI, TikTok/Pinterest server events and GA4 refunds.
Server Event Delivery
Queue & Log Cleanup
Running the scheduler every minute is recommended when server-side tracking is enabled. OpenCart's own cron can run it; the raw Cron URL and copyable command are provided as alternatives.