Pixel Platform Compatibility
Summary: Not all website platforms support the Delivr pixel equally. Platforms like WordPress and Webflow give the pixel full cookie access for identity resolution. Others -- like Wix -- sandbox third-party scripts in ways that block resolution entirely. Shopify works only when the pixel is installed in the theme code, and never on checkout pages. This page explains which platforms work, which platforms do not work, and how to check before deploying.
Quick Reference
| Compatibility | Platforms |
|---|---|
| Full | WordPress (self-hosted), Webflow, ClickFunnels, Unbounce, Leadpages, custom-built sites |
| Conditional | Shopify (theme code install only), Squarespace, BigCommerce, GoDaddy Website Builder, WordPress.com (Business+ plan) |
| Not Compatible | Wix, Google Sites |
| Not Compatible | AI builder preview URLs (Lovable, Bolt, Replit, v0) |
Before quoting pixel resolution to a prospect, ask: "What platform is your website built on?"
Why Platform Matters
The Delivr pixel identifies visitors by reading a cookie from their browser and matching it against our identity graph. For this to work, the pixel needs unrestricted access to document.cookie in the visitor's browser.
Some website platforms run third-party scripts in a sandboxed environment that blocks cookie access. When that happens, the pixel loads and fires events, but it cannot read or write the cookies needed for identity resolution. The result is near-zero resolution. The cause is not that the identity graph is missing data. The cause is that the pixel cannot access the browser data it needs.
Fully Compatible Platforms
These platforms allow unrestricted pixel installation. Standard resolution rates apply.
| Platform | Installation Method | Notes |
|---|---|---|
| WordPress (self-hosted / .org) | "Header and Footer Scripts" plugin or theme header | Best platform for pixel resolution. Full code control. |
| Webflow | Site-wide or per-page custom code injection (head/body) | Supports all event types: page view, click, scroll, exit intent. |
| ClickFunnels | Custom tracking code in page header/footer | Ideal for landing page and funnel tracking. |
| Unbounce | Custom script injection in head and body | Works well for landing page deployments. |
| Leadpages | Custom tracking scripts | No sandbox limitations. |
| Google Tag Manager (any site that allows it) | Delivr.ai Pixel tag template or a Custom HTML tag | Works only where the site itself allows third-party scripts. Platform limits below still apply. |
| Custom-built (for example, HTML, React or Next.js) | Direct code injection | Sites on Netlify, Vercel, AWS, or any standard hosting all work. |
Conditionally Compatible Platforms
These platforms work but have limitations that may reduce effective resolution rates.
Shopify
- How to install: Online Store > Themes > Edit code >
layout/theme.liquid. Paste the pixel script just before</head>. Code in the theme runs on the storefront page itself, with normal first-party cookie access. It resolves at rates comparable to other fully compatible platforms. - Do not install as a Customer Events custom pixel (Settings > Customer events > Add custom pixel). Shopify runs custom pixels in a sandboxed iframe without access to the storefront's cookies. The pixel fires events there, but resolution drops to roughly 3%, about 90% below a theme install.
- Limitation, checkout: Shopify no longer runs theme code or additional scripts on checkout, Thank you, or Order status pages. The pixel sees storefront pages (home, collections, products, cart) but not checkout steps or completed orders. A Shopify app that captures checkout and order events is in development.
- Limitation, consent: Shopify's cookie banner does not block scripts added to theme code. If the store needs to honor its banner, load the pixel only after the visitor's choice allows it, using Shopify's Customer Privacy API (
window.Shopify.customerPrivacy). - Impact: Storefront resolution is normal. Checkout and purchase activity is not captured.
Squarespace
- How to install: Settings > Advanced > Code Injection > Header
- Limitation: The built-in consent banner can gate custom scripts. If the pixel script is allowed to load, a custom integration must publish the banner's decision to the SDK. The SDK does not read the banner itself. A browser GPC signal is honored server-side: events still record, without identity. Express-consent regions wait for a grant. A US implied-consent or opt-out mode can start collection immediately and pass
falseafter an opt-out. - Impact: Effective resolution depends on the site's CMP configuration and regional traffic mix.
BigCommerce
- How to install: Via Script Manager or custom code in storefront theme
- Limitation: Cookie consent features can gate third-party scripts. If the script loads, your integration must publish the consent decision to the SDK. Express-consent regions wait for a grant. A correctly integrated US opt-out mode can collect until the visitor opts out and then pass
false. - Impact: Effective resolution depends on the configured regional consent mode.
GoDaddy Website Builder
- How to install: Marketing > Tracking section, or custom HTML block
- Limitation: The cookie consent banner may gate third-party tracking according to its regional mode. Custom HTML may also be placed inside iframes, which can prevent some event types from firing.
- Impact: Lower resolution than fully compatible platforms. Test with a small deployment before committing.
WordPress.com (Hosted)
- Limitation: Custom JavaScript requires a Business plan ($33/month) or higher. Free, Personal, and Premium plans do not allow custom code injection.
- Recommendation: Upgrade to Business plan, or switch to self-hosted WordPress (.org) for full pixel functionality.
Not Compatible
These platforms have technical restrictions that prevent identity resolution. The pixel may load and fire events, but it cannot access the cookie data needed to identify visitors.
Wix
Wix sandboxes all custom code elements and has removed the ability for third-party scripts to access cookies, localStorage, and sessionStorage. There is no workaround within the Wix platform.
Google Sites
Google Sites does not support custom JavaScript injection. There is no way to install the pixel.
AI Website Builder Preview URLs
This applies to sites accessed via the builder's default preview URLs, not custom domains.
| Builder | Default URL Pattern | Issue |
|---|---|---|
| Lovable.dev | *.lovable.app, *.lovableproject.com | Traffic proxied through shared infrastructure. Real visitor IPs are masked. |
| Bolt.new | *.stackblitz.io | Sandboxed browser execution environment. |
| Replit | *.repl.co | Sandboxed container environment. |
| v0.dev | Preview-only | No persistent hosting. |
These platforms proxy all traffic through shared cloud infrastructure, masking real visitor IP addresses. Combined with sandbox restrictions, the pixel cannot perform identity resolution.
Important: If you deploy a site built with one of these tools to a custom domain on standard hosting, the pixel works normally. Netlify, Vercel and AWS are examples of standard hosting. The restriction is on the builder's preview URLs, not the generated code itself.
How to Verify a Platform
Step 1: Ask
"What platform or hosting provider is your website built on?"
| Answer | Action |
|---|---|
| "WordPress" | Ask if self-hosted or WordPress.com. If .com, confirm Business plan or higher. |
| "Shopify" | Compatible on storefront pages with a theme code install (theme.liquid). Not as a Customer Events custom pixel, and not on checkout. |
| "Wix" | Not compatible. Suggest WordPress or Webflow as alternatives. |
| "Squarespace" | Compatible, but verify the site's CMP and regional consent modes. |
| "Webflow" | Fully compatible. |
| "Custom built" | Fully compatible. Any standard hosting works. |
| "I'm not sure" | Ask for the website URL and check (see Step 2). |
Step 2: Check the URL
| URL Pattern | Platform | Compatible? |
|---|---|---|
*.myshopify.com | Shopify | Conditional (theme code install, no checkout pages) |
*.wixsite.com or *.wix.com | Wix | No |
*.squarespace.com | Squarespace | Conditional |
*.godaddysites.com | GoDaddy | Conditional |
*.webflow.io | Webflow | Yes |
*.wordpress.com | WordPress.com | Conditional (Business+ required) |
*.lovable.app / *.lovableproject.com | Lovable | No (preview URL) |
*.netlify.app | Netlify | Yes |
*.vercel.app | Vercel | Yes |
Custom domain (e.g., www.company.com) | Check source | Usually yes -- verify with page source |
Step 3: Check Page Source
If you have access to the site, right-click > View Page Source and look for platform indicators:
| Look For | Platform |
|---|---|
cdn.shopify.com or myshopify.com | Shopify |
static.wixstatic.com or wix.com | Wix |
wp-content or wp-includes | WordPress |
squarespace.com or static1.squarespace.com | Squarespace |
webflow.com | Webflow |
Common Questions
"Can you install your pixel on my Shopify store?"
Yes, in the theme code. Add the pixel script to layout/theme.liquid (Online Store > Themes > Edit code), just before </head>. It then resolves visitors on storefront pages normally. Do not add it under Settings > Customer events as a custom pixel: Shopify sandboxes custom pixels, and resolution there drops to roughly 3%. Checkout, Thank you, and Order status pages do not run theme code, so purchases are not captured. A Shopify app for checkout and order events is in development.
"Why does it work on some platforms but not others?"
The pixel identifies visitors by matching browser data to our identity graph. Some platforms run third-party scripts in a restricted environment. Examples are Wix and Shopify's Customer Events custom pixels. The environment blocks access to the browser data we need. Think of it like trying to read a book through frosted glass: the book is there, but you cannot see the words. Platforms like WordPress and Webflow give us clear, unrestricted access.
"My developer built our site on Lovable / Bolt. Will the pixel work?"
It depends on where the site is hosted. If you are still using the builder's preview URL (like yoursite.lovable.app), the pixel will not resolve visitors. The reason is that those URLs run through shared infrastructure that masks visitor identity. Once the site is deployed to your own custom domain on standard hosting (for example, Netlify, Vercel or AWS), the pixel works normally.
"We installed the pixel on Shopify and resolution is near zero. Why?"
Check where it is installed. If it is under Settings > Customer events as a custom pixel, Shopify runs it in a sandbox without cookie access. Remove it there and add the script to layout/theme.liquid instead. Also confirm that a consent or cookie app is not blocking the script for every visitor.
"Can you track Shopify checkouts and orders?"
Not with the current theme install, because checkout pages do not run theme code. Shopify does send checkout and order events to Customer Events custom pixels. However, those pixels run in the same sandbox that drops identity resolution to roughly 3%. They can therefore record a purchase without identifying who made it. A Delivr Shopify app for checkout and order events is in development. The theme install covers storefront browsing until then.
Next Steps
- How Identity Resolution Works -- Understand the cookie-to-person pipeline
- Understanding Resolution Rates -- Why rates vary by browser and traffic mix
- On-Domain Events API -- Install a pixel and query visitor events
- Install with Google Tag Manager -- Use the Delivr.ai Pixel tag template instead of a Custom HTML tag
- White Label Pixel Setup -- Host the pixel on your own domain
Updated 11 days ago