For Shopify

Consentry: consent-gated server-side tracking for Shopify

Send Shopify conversion events to Meta CAPI and GA4 server-side, but only when the shopper has consented. EU edge infrastructure, per-event consent enforcement, full GDPR audit log.

Coming to the Shopify App StoreTalk to us

The gap Consentry closes

Since Shopify deprecated checkout scripts, serious tracking has to run server-side. But server-side events fired without consent are now a real liability in the EU. Consentry is the layer that makes the consent decision before any event leaves your store.

How it works

  1. 1

    The shopper sets their consent in your cookie banner.

  2. 2

    Consentry reads that consent and the Shopify Customer Event, then sends both to an EU edge worker.

  3. 3

    The worker forwards the event to Meta CAPI and GA4 only for destinations the shopper allowed, and logs every decision.

Frequently asked

How is this different from a cookie banner?
A banner collects consent in the browser. Consentry enforces it on the server, before any event reaches Meta or Google. Most setups collect consent in one tool and fire server-side events in another, with nothing connecting the two.
Where is my data stored?
On Cloudflare infrastructure pinned to the EU. The audit log keeps only hashed identifiers, and deletion requests are honored through Shopify's GDPR webhooks.
Will it double-count my conversions?
No. Each event carries an event_id so Meta and GA4 deduplicate the server-side event against the browser pixel.
PrivacyTermsSupport