Marketing & Tracking

Accurate marketing data is what lets you spend confidently. CIQRA’s standout here is server-side (S2S) conversion tracking — sending conversion events from your store’s server, not just the shopper’s browser, so ad blockers, cookie limits, and closed tabs stop quietly eating your best conversions.

You manage it all under Pixels & tracking in the admin: a grid of destinations, each a secure, testable connection to an ad or analytics platform.

Why server-side trackingHow S2S measurement works and why it beats a browser pixel.

Connect a destinationConfigure, test, and save a conversion destination.

Set up Google Analytics 4A field-by-field walkthrough of the GA4 destination.

Verify tracking with test eventsConfirm a destination is wired before you rely on it.

Pause or turn off a destinationStop forwarding without losing your setup.

Supported destinationsEvery platform CIQRA forwards conversions to.

Consent and product feedsRespect shopper privacy and keep your catalogue in sync.

Start here

New to this? Read Why server-side tracking first — it explains the differentiator everything else builds on.

Frequently asked questions

Why do my server-side conversion counts differ from the platform’s own dashboard?

Some difference is normal. Ad platforms deduplicate server-side events against any browser pixel, apply their own attribution windows, and only process conversions that carry a valid consent signal. CIQRA forwards conversions reliably from your server; each platform then counts them by its own rules, so the totals rarely match to the exact event.

Do I need to connect every destination?

No. Connect only the platforms you actually advertise or measure on. Each destination is independent, so you can start with one — many stores begin with Google Analytics 4 — and add others as your marketing grows.

Are my API secrets safe?

Yes. Secrets are stored encrypted at rest and are never shown back to you — after saving, the field displays only a masked hint. Keep your own copy of any key from the provider until you’ve confirmed the connection works, because you can’t read it back from CIQRA.

Does server-side tracking replace my browser pixel?

It complements it rather than replacing it. Server-side tracking sends conversions from your store’s server so ad blockers, cookie limits and closed tabs can’t quietly drop them. Ad platforms deduplicate the two so a conversion isn’t double-counted. See Why server-side tracking.

How do I know a destination is actually working?

Use the Send test event flow in the destination editor. It fires a single test conversion server-side that you confirm in the platform’s own console — proof your credentials are right and events are landing. See Verify tracking with test events.

Does server-side tracking respect shopper consent?

Yes. The conversions CIQRA forwards are meant to reflect the consent a shopper has given, so your measurement stays both accurate and compliant. Consent rules differ by region and platform — treat your own legal guidance as the source of truth. See Consent and product feeds.

What’s the difference between Paused and Not set up?

A Paused destination is fully configured but switched off, so it keeps its saved credentials and sends nothing until you turn it back on. A Not set up destination has never been configured — you can’t enable it until you’ve entered valid settings and saved. See Pause or turn off a destination.