A conversion-tracking destination isn't receiving events

CIQRA sends conversion events server-side (S2S), which is more reliable than browser-only pixels — but it means a destination needs to be enabled, correctly credentialed, and permitted by consent before anything arrives. If a destination shows no events, walk through the checks below.

Things to check

• Is the destination enabled? A destination that’s connected but not enabled won’t send events. Confirm it’s switched on — see Connect a destination.
• Are its credentials or secrets in place? Server-side sending needs the destination’s credentials/secrets to be configured. If they’re missing or wrong, events can’t be delivered. Check the required fields for that destination in Supported destinations.
• Has consent been granted? Tracking is consent-aware, so events are gated by shopper consent. Even a perfectly configured destination receives nothing if consent hasn’t been granted.
• Have you run the test event? The test event is how you verify the connection end to end. If you’ve never run it, do that first — it’s the fastest way to tell a real delivery problem from an untested setup.

Tip

Run the test event before anything else. It isolates the problem: if the test event arrives, your setup is sound and any gap in live data is about consent or volume; if it doesn’t, focus on enablement and credentials.

Note

Because CIQRA tracking is server-side, browser ad-blockers won’t be the cause — delivery depends on your server-side configuration, not the shopper’s browser extensions. See Why server-side tracking.