Install Zijra

Next.js installation

Use Next.js Script in the layout that owns all tracked routes.

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 root layout

   For the App Router, open app/layout.tsx or src/app/layout.tsx. Locale-specific root layouts need the tracker in each root that serves a tracked domain.

2. Add the Script import and component

   Put import Script from 'next/script' with your imports, then place the supplied Script component inside the existing body, beside your children. Keep strategy="afterInteractive"; no new client component is required.

   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 test a client navigation

   Open a public route, follow an internal Link, then use Back. Install in the persistent layout rather than every page or a route-change effect. Pages Router projects can place the same imported component in pages/_app.tsx.

Platform reference: Next.js layout scripts · Pages Router 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.