Install Zijra

Replit installation

Install in the generated app’s document, then publish the updated application.

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 app’s source files

   Inspect package.json to identify the frontend. A static HTML app uses its main HTML file; a common React/Vite app uses client/index.html or root index.html.

2. Add the snippet in the shared head

   For HTML/Vite, paste before </head>. Keep the file’s existing app-entry script. If it is Next.js, select the Next.js guide and use next/script in the root layout instead.

   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. Run, review and republish

   Review the app in its development preview, then publish the saved version and test the published domain registered in Zijra. A successful Run session does not update an existing published deployment.

Platform reference: Replit apps and project access · Replit publishing · Vite entry-point 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.