Configure consent (GDPR/CCPA)

The Zalify Pixel can hold tracking until a visitor grants consent, so you stay compliant with GDPR and CCPA. Pick the option that matches how your site collects consent today.

Option 1 — Shopify (zero config)

If your store exposes Shopify's customer-privacy API (window.Shopify.customerPrivacy.analyticsProcessingAllowed), the Pixel wires into it automatically: it reads consent at boot, subscribes to Shopify's visitorConsentCollected events, and ignores manual consent parameters.

Option 2 — Tell the Pixel from your banner

If you have your own consent banner, call the Pixel's API when the visitor accepts:

window.zalify('consent', { analytics: 'granted' });

This unblocks the Pixel's boot synchronously and persists the choice to localStorage, so the visitor doesn't have to re-consent on their next visit.

Option 3 — Point the Pixel at an existing storage key

If a consent tool already writes the visitor's choice to localStorage, tell the Pixel which key to read by adding two parameters to the script URL:

<script src="https://cdn.zalify.com/pixel.js?wid=YOUR_WORKSPACE_ID&consentRequired=true&consentStorageKey=consent_state" defer></script>

With consentRequired=true, the Pixel:

• checks that localStorage key at boot,
• listens for cross-tab storage events so consent granted in another tab takes effect, and
• polls roughly every 500 ms for up to 5 minutes, waiting for the choice to appear.

Grant consent from a popup

You can also let visitors opt in from inside a Zalify popup using a grant_consent button, so a popup can double as your consent prompt. See Create your first popup.

Testing consent

Next steps

• Send conversions to Meta, Google, TikTok & more — forwarding respects the same consent gate
• Create your first popup — add a grant_consent button