Installation

Let your coding agent set it up

Open Settings → Tracking and choose Copy setup prompt. Paste it into your coding agent with your website repository open. The prompt already includes your site key and tracking URL, plus instructions to connect existing forms, phone, WhatsApp and email links, preserve your security policy, and verify the results. Review its changes, publish your site, and check the received activity in Zowar.

New visitors, existing visitors, and verified customers

Browser recognition works automatically. For consent controls, reliable form retries, optional authenticated customer linking and logout handling, follow the visitor identity guide. The setup prompt includes these steps.

Plain HTML

Copy the exact snippet from Site settings. Place it before the closing head tag in your shared page template. Replace the example host and key below with your own; the public site key permits collection, not reading your data.

<head>
  <script defer src="https://YOUR_ZOWAR_HOST/t.js" data-site="YOUR_SITE_KEY"></script>
</head>

The server snippet may use async; both async and defer are supported. Defer is useful in static HTML because execution waits for HTML parsing. Keep only one tracker per page, and publish the change.

Next.js App Router

Put the script in your root layout so it runs across routes. The tracker supports dynamically injected scripts by finding its data-site attribute and records client-side route changes.

import Script from "next/script";

export default function RootLayout({ children }) {
  return (
    <html lang="en">
      <body>
        {children}
        <Script
          src="https://YOUR_ZOWAR_HOST/t.js"
          data-site="YOUR_SITE_KEY"
          strategy="afterInteractive"
        />
      </body>
    </html>
  );
}

WordPress, Webflow and Squarespace

Use a site-wide header code setting or a header injection plugin. In WordPress, a shared theme header also works, but theme updates can replace direct edits. In Webflow and Squarespace, paste the snippet into the global head code area. Publish and check the live page rather than only the editor preview.

Verify before moving on

Open Site settings → Tracking → Check your connection. Zowar checks the published page for your site key, flags a security policy that blocks collection, and shows when activity last arrived. Open your website and navigate between pages; the status updates every five seconds. Tags injected by a consent manager or tag manager may only be visible in the browser. A pageview does not prove that a form is connected: send a separate test lead using the lead capture guide.

If your website uses Content-Security-Policy, allow the Zowar origin in both script-src and connect-src. Pass the page nonce to the script when your policy requires one. Configure your consent manager for your deployment. If the tracker is blocked or consent is withheld, events will not be recorded. See Troubleshooting.

Connect phone, WhatsApp and email links

<a href="tel:+201234567890">Call us</a>

<a href="https://wa.me/201234567890" target="_blank" rel="noopener noreferrer">
  Message us on WhatsApp
</a>

<a href="mailto:[email protected]">Email us</a>

Clear your setup tests

During the first 24 hours after adding your site to Zowar, go to Settings → Data and choose Remove test data and review the counts. Type your site’s domain to confirm permanent removal of the previewed events, leads, contact clicks, form drafts, and related team activity. This clears all collected data, including any real enquiries, manual or imported leads. New records received after the preview are kept. Your site key, forms, settings and integrations remain connected. Only use this when the existing records are safe to remove. After 24 hours, cleanup is unavailable and the API rejects it, even if you opened the preview earlier.