Troubleshooting
Check what actually reached the server before changing your setup.
No traffic in Verify
Start in Site settings → Tracking. Check your connection distinguishes a missing or incorrect site key from a blocked connection and shows the latest recorded activity. Its website scan is cached for up to one minute; received activity refreshes every five seconds while the panel is open.
- Published code
- Inspect the live page and confirm the script is present exactly once. Preview and production may use different templates.
- Tracker URL
- In browser developer tools, check that /t.js loads JavaScript successfully rather than HTML or a 404 page.
- Site key
- Copy the key from this site's settings. A key from another site sends data to the wrong collector record or is rejected.
- Domain
- The browser origin must match the registered domain. The www variant is accepted, but unrelated subdomains and preview hosts need their own site.
- Network and consent
- Check requests to /api/collect. Browser blockers, a content security policy, a consent manager or connectivity can prevent them.
- Check again
- Visit a page, then ask Verify to check again. A copied snippet alone never completes verification.
Visits appear but leads do not
A pageview or form_submit event does not include contact answers. If your form already saves to your own backend, send the lead to Zowar only after that save succeeds; keep the original form working if analytics is unavailable. Confirm your form calls window.Pulse.submitLead after the tracker is ready, and check the returned response.ok before showing success. Look for rejected /api/leads requests, a wrong domain or key, or a rate-limit response.
Use a stable form key and matching field keys. A form definition configures how submissions are understood; creating it does not connect the website form automatically.
A lead arrived but no email did
Check the site’s alert address and the operator’s SMTP settings. Email delivery failure does not discard an accepted lead. The inbox is the source of truth; delivery can also be delayed or filtered by a mail provider.
Local server and sign-in
Run migrations before starting the API, use the same host consistently (localhost and 127.0.0.1 are different origins), and keep COOKIE_SECURE=false for plain HTTP development. A fresh installation has no tenant account until you run the bootstrap script. See Self-hosting.