Install Zijra

Wix installation

Wix allows third-party custom code on an eligible published, connected-domain site.

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 your site’s Custom Code settings

   From the site dashboard, open Settings → Development & integrations → Custom Code → Add Custom Code. Confirm the site is published and has its domain connected.

2. Add a global Head snippet

   Paste the full snippet, name it “Zijra analytics”, select All pages, choose loading once per visit, set Place Code in: Head and apply.

   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. Test the published domain with consent

   Open the live site, use your actual cookie-banner choice and navigate two pages. Verify a received event rather than assuming all third-party tracking scripts behave like Wix’s native integrations.

Wix documents platform-specific tracking limits. If your approved setup uses Tag Manager, connect its container through Marketing Integrations, then select Google Tag Manager in these installation guides; do not inject a second GTM container through Custom Code.

Platform reference: Wix custom-code settings · Wix third-party app options

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.

Check an internal navigation and Back as well. Zijra observes normal browser history changes after loading; it does not turn an unchanged URL, a tab switch or a component render into a new pageview. Hash-only routes are excluded unless you deliberately enable hash reporting.

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.