<head> section. The tracker works on any website platform including WordPress, Next.js, Webflow, Shopify, and via Google Tag Manager. Once installed, it automatically captures pageviews, sessions, and identifies companies visiting your site.
Quick Start
- Log in to your Snitcher Dashboard
- Navigate to Settings → Tracker → Installation Instructions
- Copy your unique tracking script
- Paste it into the
<head>section of your website
Your Tracking Script
Your tracking script looks like this (with your uniqueprofileId):
Installation Methods
Direct HTML Installation
Direct HTML Installation
Add the tracking script directly to your website’s HTML:
- Open your website’s HTML template or CMS settings
- Locate the
<head>section - Paste the tracking script immediately before the closing
</head>tag - Save and publish your changes
Google Tag Manager
Google Tag Manager
Deploy Snitcher via Google Tag Manager:
- Log in to Google Tag Manager
- Create a new Custom HTML tag
- Paste your Snitcher tracking script
- Set the trigger to All Pages
- Save and publish your container
WordPress
WordPress
Option 1: Using a PluginUse a header script plugin like “Insert Headers and Footers”:
- Install and activate the plugin
- Go to Settings > Insert Headers and Footers
- Paste your tracking script in the “Scripts in Header” section
- Save changes
- Go to Appearance > Theme Editor
- Select
header.php - Add the script before
</head> - Update the file
Webflow
Webflow
- Go to Project Settings > Custom Code
- Paste the script in the Head Code section
- Save changes
- Publish your site (changes won’t appear until published)
Shopify
Shopify
- Go to Online Store > Themes
- Click Actions > Edit Code
- Find and open
theme.liquid - Paste the script just before
</head> - Save the file
Wix
Wix
- Go to Settings > Custom Code
- Click + Add Custom Code
- Paste your tracking script
- Set placement to Head and pages to All Pages
- Apply and publish
Squarespace
Squarespace
- Go to Settings > Advanced > Code Injection
- Paste the script in the Header section
- Save changes
HubSpot CMS
HubSpot CMS
- Go to Settings > Website > Pages
- Click Templates or go to the specific page
- Add the script to the Site Header HTML section
- Publish changes
Next.js
Next.js
App Router (Next.js 13+)Create a client component for the tracker:Add to your root layout:Pages RouterAdd to Identifying Users
_app.tsx:React (Vite, CRA)
React (Vite, CRA)
For React apps without Next.js, add the script to your Or load it dynamically in your app:TypeScript TypesAdd type declarations for Snitcher:
index.html:Verify Installation
After installing the script:- Visit your website in a new browser tab
- Open your browser’s Developer Tools (F12 or right-click > Inspect)
- Go to the Network tab
- Look for requests to
radar.snitcher.comorcdn.snitcher.com - In your Snitcher dashboard, you should see data appear within a few minutes
What Gets Tracked Automatically
Once installed, Snitcher automatically tracks:| Event | Description |
|---|---|
| Pageviews | Every page load and client-side navigation |
| Sessions | Visitor sessions with engagement time |
| Referrer | Where visitors came from |
| UTM Parameters | Campaign tracking data |
| Device Info | Browser, OS, and device type |
Optional Features
Enable additional tracking by adding feature flags to your script configuration:Feature flags are configured in your Snitcher dashboard. Changes apply automatically without updating your tracking script.
Content Security Policy (CSP)
If your website uses a strict Content Security Policy, you’ll need to allow Snitcher’s domains for the tracker to work properly.Required CSP Directives
Add these endpoints to your CSP: Forscript-src:
connect-src:
Example CSP Header
Using a Nonce
If you use nonces for inline scripts, you can either:- Add the nonce to the Snitcher script tag
- Use the external script approach instead of inline
If you’re using first-party tracking, update your CSP to use your proxy domains instead.
Cross-Subdomain Tracking
Snitcher automatically tracks visitors across subdomains of the same root domain:| Domain | Tracked Together? |
|---|---|
example.com + app.example.com | ✅ Yes |
example.com + docs.example.com | ✅ Yes |
example.com + otherdomain.com | ❌ No (different root domains) |
How It Works
When you install the tracker on multiple subdomains, Snitcher:- Sets cookies on the root domain (
.example.com) - Shares the device ID across all subdomains
- Links sessions from different subdomains to the same visitor
Installation Across Subdomains
Install the same tracking script on all subdomains. Use the sameprofileId:
Different Root Domains
For completely different domains (e.g.,yourcompany.com and yourblog.io), visitors are tracked separately. They’ll be merged if the same user identifies on both domains.
Troubleshooting
How do I verify the tracker is installed?
How do I verify the tracker is installed?
- Open your browser’s Developer Tools (F12)
- Go to the Console tab
- Type
Snitcherand press Enter - You should see an array or object—not “undefined”
cdn.snitcher.com.Events are not appearing in my dashboard
Events are not appearing in my dashboard
- Clear your browser cache and try again
- Check if an ad-blocker is blocking requests to
*.snitcher.com - Verify your
profileIdmatches what’s in your dashboard - Look for JavaScript errors in the Console tab
Tracker conflicts with another library
Tracker conflicts with another library
If Then access the tracker via
Snitcher conflicts with another global variable, you can use a custom namespace:window.MySnitcher instead.CSP errors in the console
CSP errors in the console
If you see Content Security Policy errors:
- Add
https://cdn.snitcher.comto yourscript-srcdirective - Add
https://radar.snitcher.comto yourconnect-srcdirective