Consent & Privacy
Understand OpenCart, external CMP and no-gate consent modes used by HuntBee Tracking Suite.
Choose where consent signals come from and let one shared state control supported analytics and advertising integrations.
Consent source choices
| Mode | Use when |
|---|---|
| OpenCart cookie banner | Use OpenCart's built-in cookie policy banner. HuntBee maps the visitor's accept/decline choice to the supported storage/user-data signals. |
| External consent platform | Another CMP/banner is installed. HuntBee does not display a banner. Compatible Google Consent Mode updates on the dataLayer are detected automatically. |
| No consent gate | No HuntBee consent gating is applied. Use only when you are certain this is appropriate for the store. |
Signals modelled
- Analytics storage
- Advertising storage
- Advertising user data
- Advertising personalization
External CMP mode
External mode begins conservatively. HuntBee can observe standard Google Consent Mode default/update commands published through the existing dataLayer and update its own provider delivery state. For a custom platform that does not publish compatible signals, use the Advanced / Developer integration API.
What happens to events before consent?
Browser-safe event portions can be kept only in page memory while consent is unresolved or denied. When a later consent update permits delivery, the newly permitted portions can be released once. They are not stored in the database just to bypass consent.