Install Zijra

Vercel v0 installation

v0 defaults to Next.js; place the tracker in its persistent root layout.

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. Inspect app/layout.tsx in Code

   Open the Code tab and locate app/layout.tsx or src/app/layout.tsx. The current viewer is read-only; request the change in chat or edit the connected repository.

2. Request the exact Script placement

   Supply this code and ask v0 to add its import with the imports and the Script component inside the root body with afterInteractive. Keep all site and privacy attributes, and review the Diff tab.

   Code exampleTSX

   CopyCopyingCopiedFailedCopy

   010203040506070809101112

   import Script from 'next/script';
   
   // Add inside your root layout's <body>.
   <Script
     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"
     strategy="afterInteractive"
   />

3. Deploy and check the published domain

   Deploy the reviewed change, open its final domain and test a client navigation. If your v0 project uses another framework, select its matching installation guide instead.

Platform reference: v0 Code viewer and change review · v0 framework defaults · Next.js layout scripts

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.