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 Shopify and Wix -- sandbox third-party scripts in ways that block resolution entirely. This page explains which platforms work, which don't, and how to check before deploying.

Quick Reference

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 can't read or write the cookies needed for identity resolution. The result is near-zero resolution -- not because the identity graph is missing data, but because the pixel can't access the browser data it needs.

flowchart TD
    A[Pixel loads on visitor's browser] --> B{Can pixel access cookies?}
    B -->|Yes| C[Cookie sent to identity graph]
    B -->|No - Sandboxed| D[Event recorded but no resolution]
    C --> E{Match found?}
    E -->|Yes| F[Resolved event with contact data]
    E -->|No| G[Raw event stored]

    style D fill:#ef4444,color:#fff
    style F fill:#22c55e,color:#fff
    style G fill:#6b7280,color:#fff

Fully Compatible Platforms

These platforms allow unrestricted pixel installation. Standard resolution rates apply.

Conditionally Compatible Platforms

These platforms work but have limitations that may reduce effective resolution rates.

Squarespace

• How to install: Settings > Advanced > Code Injection > Header
• Limitation: If the site has a cookie consent banner enabled, the pixel only fires after visitors accept cookies. Visitors who decline or ignore the banner are not tracked.
• Impact: 10-30% lower effective resolution than fully compatible platforms, depending on the site's consent acceptance rate.

BigCommerce

• How to install: Via Script Manager or custom code in storefront theme
• Limitation: Cookie consent compliance features (GDPR/CCPA) block third-party scripts until the visitor opts in.
• Impact: Similar to Squarespace -- consent acceptance rate determines effective resolution.

GoDaddy Website Builder

• How to install: Marketing > Tracking section, or custom HTML block
• Limitation: Cookie consent banner gates all third-party tracking. Custom HTML may 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.

Shopify

Shopify runs all third-party tracking pixels in a sandboxed iframe that restricts document.cookie access. The pixel loads and fires events, but resolution drops from 28-29% (Chrome desktop benchmark) to approximately 3% -- a ~90% reduction.

This is a platform-level restriction that affects all identity resolution vendors, not just Delivr. A Shopify-native integration is in development.

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.

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 a site built with one of these tools is deployed to a custom domain on standard hosting (Netlify, Vercel, AWS, etc.), the pixel works normally. 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?"

Step 2: Check the URL

Step 3: Check Page Source

If you have access to the site, right-click > View Page Source and look for platform indicators:

Common Questions

"Can you install your pixel on my Shopify store?"

Not at this time. Shopify recently changed how third-party tracking works on their platform, adding security restrictions that prevent identity resolution. This affects all identity resolution providers, not just Delivr. We're developing a Shopify-native solution and will notify you as soon as it's available. In the meantime, if you have a non-Shopify website (a blog, landing pages, or corporate site), we can deploy the pixel there.

"Why does it work on some platforms but not others?"

The pixel identifies visitors by matching browser data to our identity graph. Some platforms -- like Shopify and Wix -- run third-party scripts in a restricted environment that 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 can't 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're still using the builder's preview URL (like yoursite.lovable.app), the pixel won't resolve visitors because those URLs run through shared infrastructure that masks visitor identity. Once the site is deployed to your own custom domain on standard hosting (Netlify, Vercel, AWS, etc.), the pixel works normally.

"We're on Shopify but this is important to us. Are there alternatives?"

A few options while we develop the Shopify-native integration:

1. If you have a separate non-Shopify site (blog, landing pages, corporate site), we can deploy the pixel there.
2. If you run paid advertising, we can capture intent data through our off-domain advertising solutions.
3. We'll notify you as soon as the Shopify integration is ready.

"Will Shopify ever be supported?"

Yes. We're actively developing a solution that works within Shopify's requirements. We don't have a specific release date yet, but it's a priority.

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
• White Label Pixel Setup -- Host the pixel on your own domain