Install Zijra

Squarespace installation

Use the site-wide Header field in Code Injection.

This is an example, not a connected installation. Sign in and select a saved website to get its real public ID and collector origin. Replace all example values before publishing.

1. Open the Code Injection panel

   Find Code Injection in your site settings. Squarespace currently offers it on Core, Plus, Advanced and eligible legacy plans; verify your existing plan before proceeding.

2. Paste into Header and save

   Use the global Header field with the complete script tags, rather than a page’s Code Block or Custom CSS field.

   Code exampleHTML

   CopyCopyingCopiedFailedCopy

   010203040506070809

   <script
     defer
     src="https://zijra.com/tracker.js"
     data-site-id="YOUR_PUBLIC_SITE_ID"
     data-ignore-query="true"
     data-ignore-hash="true"
     data-respect-privacy="true"
     data-collection-mode="aggregate"
   ></script>

3. Check the public site outside the editor

   Open two pages of the saved domain. Code may be disabled in editor preview. Squarespace checkout pages do not accept injected code, so do not expect the Header field to cover checkout.

Platform reference: Squarespace Code Injection and checkout limits

Confirm a received visit

Open a published page on the domain saved in Zijra, keep it open briefly, then check installation. Success requires a pageview stored for this website. A loaded script, a green publish status or a fired tag alone does not establish that.

If no visit arrives, check the published domain, collection status, excluded paths and whether the browser blocked the script or collector. Do Not Track and Global Privacy Control intentionally prevent collection when respected. Do not disable a visitor’s privacy choice to make verification pass.

Consent and additional domains

The snippet preserves the website’s saved collection mode. For visitor attribution, connect your consent manager to Zijra’s consent API and reapply the visitor’s current decision on each visit; granting access to a page is not attribution consent. Read the privacy and identity guide before sending names or profile images.

To collect from another subdomain or website domain, add its exact HTTPS origin in Website settings and install the same selected-site snippet there once. Allowed origins permit collection; they do not automatically join visitor identities across domains. Browser storage and consent do not transfer between unrelated origins.

Need a first-party collector path? Follow the proxy installation guide. Record successful actions through custom events, and connect verified sales separately through your payment provider.