Tie is built to respect your consent setup. However you collect consent on your site, the Tie Pixel can be set to fire only after a visitor opts in. This article covers the two common setups: Shopify's built-in consent, and a third-party consent management platform (CMP).
The short version
The Tie Pixel loads in the
<head>of every page.You gate it behind consent, so it runs only after the visitor grants marketing or analytics consent.
Before consent, Tie collects nothing on that visit. That is expected and correct, not a sign something is broken.
If you use Shopify's consent banner
If your consent banner uses Shopify's Customer Privacy API (Shopify's own cookie banner, or an app built on that API), the Tie Pixel honors the marketing consent category automatically. Install the pixel as normal and Tie begins firing once the visitor grants marketing consent. No extra wiring is needed.
If you use a third-party CMP
For OneTrust, Termly, Cookiebot, and similar platforms, configure the CMP so the Tie loader is blocked until the visitor accepts your marketing (or analytics) category:
Add the Tie loader to the
<head>of every page.Tag it with your CMP's marketing or analytics category, so the CMP treats it as a gated script. Most CMPs do this with a script-blocking rule or a
type="text/plain"plusdata-categoryattribute on the tag.The CMP then executes the Tie loader only after the visitor consents, and stops loading it on later visits if consent is withdrawn.
Match the category to how you already classify other marketing tags (for example your ad pixels), so consent behaves consistently across your site.
What "consent-gated" means for your numbers
Because Tie fires only after consent, you will see fewer Tie events than raw site sessions, especially from first-time visitors who have not answered the banner yet. This is the consent gate working as intended. A gap between total sessions and Tie events is expected and is not data loss.
Verify it is working
Open your live site in Chrome with DevTools open before the page loads:
Decline consent: you should see no network calls to your Tie subdomain (
zone.yourdomain.com).Accept consent, then reload: the loader should return 200 and Tie events should begin firing.
Full steps are in Verify your Tie installation.
Common issues
Nothing fires even after accepting consent. Your CMP may not be releasing the Tie script on consent. Confirm the script's category matches the category the visitor accepted.
Events fire before consent. The loader is not gated. Move it behind your CMP's consent gate so it cannot execute until consent is returned.
See Installed but not seeing data yet for the full troubleshooting path.