Install Zijra

React Router installation

Choose placement from the router mode your app actually uses.

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. Find the document shell

   Framework mode uses app/root.tsx; Vite apps using BrowserRouter or RouterProvider use their root index.html.

2. Install once in that shell

   In HTML, paste into head. In app/root.tsx, keep the script attributes inside the shared document’s head and express defer as a JSX boolean. Convert any HTML comment to a JSX comment; keep React Router’s own Scripts component.

   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 and navigate without reloading

   Test an internal link and Back. Do not add another tracker for every location update. For a hash router, decide whether to enable hash reporting in Zijra; hashes are excluded by default.

Platform reference: React Router root route · Vite document placement

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.