Install Zijra

Google Tag Manager installation

Use one approved web-container tag to load Zijra after your consent policy allows it.

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 website’s web container

   Confirm the GTM container is already installed on the saved website. Choose Tags → New → Tag Configuration → Custom HTML and name the tag “Zijra analytics”.

2. Paste the Zijra loader

   Paste the supplied loader into the HTML field, retaining the script tags and site attributes. Do not also install the tracker directly in your CMS.

   Code exampleHTML

   CopyCopyingCopiedFailedCopy

   01020304050607080910111213

   <script>
   (function(){
     var script=document.createElement('script');
     script.defer=true;
     script.src="https://zijra.com/tracker.js";
     script.setAttribute('data-site-id',"YOUR_PUBLIC_SITE_ID");
     script.setAttribute('data-collection-mode',"aggregate");
     script.setAttribute('data-ignore-query',"true");
     script.setAttribute('data-ignore-hash',"true");
     script.setAttribute('data-respect-privacy',"true");
     document.head.appendChild(script);
   })();
   </script>

3. Configure one initialization and consent

   Use an All Pages trigger when your policy permits loading, or the consent manager’s approved trigger. Set tag firing to Once per page; do not reload the tracker on every History Change. Additional Consent Checks must match your site’s policy: Zijra is a custom tag and does not inherit Google’s built-in consent handling.

4. Preview, then submit and publish

   Use Preview to inspect firing and consent on your actual website. Publish the container version and check the received event in Zijra. A tag marked Fired is only a browser action, not proof of ingestion.

Platform reference: GTM Custom HTML tags · GTM consent settings

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.