Getting Started

Install the Snippet

One line of code, under 2KB, and your dashboard starts filling in.

Everything Crafty Meerkat shows you — live visitors, top pages, campaign results, AI recommendations — starts with one line of code on your website. Install it once and you are done; there are no plugins to maintain, no settings to revisit, and no code changes needed when new features ship.

The snippet is a small script tag (a standard piece of web code that nearly every website platform accepts). It is under 2KB — smaller than most single images on your site — loads asynchronously so it never holds up your page, and has no dependencies. Your visitors will not notice it, and neither will your page-speed scores.

The only thing that makes your snippet yours is the site ID inside it. Your dashboard shows the complete snippet with your ID already filled in, so the safest path is always copy-from-dashboard, paste-into-site.

How it works

When a visitor loads a page, the snippet quietly records the visit — the page, the referrer (the site they came from), their country, and their device type — and sends it to your dashboard. It also captures useful actions automatically: outbound link clicks, file downloads, 404 hits, and internal site searches. No names, emails, or other personal details are collected, and raw IP addresses are never stored.

The complete snippet

<script async
  src="https://t.craftymeerkat.com/v1/t.js"
  data-site="YOUR_SITE_ID"></script>

Step by step

1
Copy your snippet from the dashboard
After you add a site, your dashboard displays your personal snippet with your unique site ID already in place. Copy it exactly as shown. If you are pasting the generic version below instead, replace YOUR_SITE_ID with the ID from your dashboard.
2
Paste it just before the closing </head> tag
Open your site’s HTML (or your platform’s custom-code box) and place the snippet right before </head>. The head section is loaded on every page view, which is exactly what tracking needs. If your platform has a dedicated “header code” field, that is the same thing.
```
<script async
  src="https://t.craftymeerkat.com/v1/t.js"
  data-site="YOUR_SITE_ID"></script>
```
3
Make sure it is on every page
If your site uses a shared template, layout, or theme file (most do), one paste covers the whole site. If pages are edited individually, add the snippet to each one — any page without it is invisible to your analytics.
4
Save, publish, and check
Publish your changes, open your site in a new tab, and watch Live Traffic View in your dashboard. Your visit should appear within a few seconds. The verify guide covers what to check if it does not.

Tips from the den

◆Always copy the snippet from your dashboard rather than retyping it — a single wrong character in the site ID means no data arrives.
◆Track one website per site ID. If you run two sites (say, a bakery site and an online store), add each as its own site in the dashboard so their numbers stay separate.
◆You can safely keep another analytics tool installed alongside Crafty Meerkat while you compare — the two do not interfere with each other.

See it live — no signup

The demo dashboard runs on a real site with real traffic.

Open the live demo →

Common questions

Does it matter where in the head the snippet goes?

Not much — anywhere inside the head works. Just before the closing </head> tag is the convention because it keeps the snippet easy to find later. Because the script loads asynchronously, its position never affects how fast your page appears.

Can I put the snippet in the body instead of the head?

It will still work in most cases, but the head is more reliable: it loads first on every page view, so visits are less likely to be missed when someone leaves a page quickly. Use the head whenever your platform allows it.

Do I need a cookie banner for this snippet?

Crafty Meerkat collects no names, emails, or other personal details, and raw IP addresses are never stored. It does use a persistent first-party identifier on Growth and Agency plans — depending on your audience and jurisdiction, your site’s existing consent policy may need to cover it. When in doubt, a quick check with your legal advisor settles it.