Install Zijra

Webflow installation

Use site-wide custom code so existing and new pages share the tracker.

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 Site settings → Custom code

   Your site or Workspace must have access to custom code, and your role must allow editing it. Use Site settings for global coverage rather than individual Page settings.

2. Paste in Head code and save

   Add the full snippet to Head code and choose Save changes. Keep the supplied defer attribute.

   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. Publish the saved domain

   Publish to the domain saved in Zijra and check a static page and a CMS item page. Designer or preview behavior does not establish collection from the published site.

Platform reference: Webflow site-wide custom code

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.