zijra.Documentation
Get started

Install Zijra

Use your website’s actual public ID and collector origin.

Give your agent the complete setup task

Open your website repository in Cursor, Claude Code, Codex or another coding agent. Choose your saved website to copy the complete installation task or download its Markdown file. It preserves public tracker settings and includes framework detection, real action and consent examples, and a newly received visit check.

Choose your platform

Shopify installation

This installs storefront analytics; verified order revenue is a separate connection.

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 theme’s code editor

    In Shopify Admin, open Online Store → Themes, duplicate the theme for a recoverable copy, then choose its menu → Edit code.

  2. Add the tracker to theme.liquid

    Open layout/theme.liquid and paste the snippet immediately before </head>. Keep {{ content_for_header }} and the theme’s existing markup.

    Code exampleHTML
    <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>
    Preparing code…
  3. Publish the theme and test the storefront

    Publish the edited theme when ready. Visit a product and a collection on your saved storefront domain. Theme code does not run in Shopify’s isolated checkout or customer-account surfaces.

The native Shopify revenue integration is coming soon. Stripe is the live payment connection. A storefront visit or thank-you page is not a verified payment. Recheck the tracker when switching or updating themes.

Platform reference: Shopify theme code editor

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.

Save a website to verify

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.