Tracking Suite Component
Meta Tracking
Configure Meta Pixel and Conversions API with browser/server modes, shared event IDs and test support.
OpenCart 4Tracking Suite 4.0.0Customer Guide
Use Meta Pixel, Meta Conversions API, or both with a shared event ID for supported browser/server deduplication.
Delivery mode
| Mode | Meaning |
|---|---|
| Browser only | Events are sent from the visitor's browser through Meta Pixel. |
| Server only | Supported events are queued and delivered from your server through Conversions API. |
| Browser and server Common choice | HuntBee uses the same semantic event ID so Meta can deduplicate supported copies. |
Settings
| Pixel / Dataset ID | The numeric ID from Meta Events Manager. |
|---|---|
| Content ID source | Match the identifier used in your Meta catalogue: Product ID, Model or SKU. |
| Conversions API access token | Required for server delivery. Stored as a protected secret in the admin. |
| Test event code | Temporary code from Test Events. Clear it before normal live operation. |
Performance: server delivery is queued. Customer-facing pages do not wait for Meta's API.
Consent
Browser and server delivery remain subject to the shared consent state. HuntBee only loads customer matching requirements for enabled server/matching modes that actually need them.
Testing
Use HuntBee Debug Logging for capture/preparation visibility, Meta Test Events for provider-side tests, and Diagnostics → Server Queue for server delivery status.
Explore HuntBee Suites