Excluding traffic
Clean numbers mean keeping the noise out — your own visits, a staging domain, the admin area, or a region that’s all bots. Statlark drops excluded hits beforethey’re counted, so they never touch your reports or your event total.
Exclude your own browser
The quickest one. Open any page of your site with ?statlark_ignore=1and that browser is skipped from then on — no rule to manage, and it takes effect immediately. There’s a one-click Copy link for this under Settings → Traffic exclusions.
# Open your site once with this query string in any browser you
# don't want counted. It sets a local flag and that browser is
# skipped from then on:
https://yoursite.com/?statlark_ignore=1
# Changed your mind? Clear it the same way:
https://yoursite.com/?statlark_ignore=0The flag is stored in that browser only (per site), so repeat it on each device or browser you want to leave out. It survives until you clear it with ?statlark_ignore=0.
Site-wide rules
For everything that isn’t “just my browser,” add a rule under Settings → Traffic exclusions. Every hit that matches an enabled rule is dropped. Three kinds:
- Path — a URL path, with
*as a wildcard./admin*drops the whole admin section;/wp-*covers WordPress paths. - Hostname — an exact host, like
staging.example.comor a Vercel preview domain, so pre-production traffic never lands in your live numbers. - Country — a two-letter country code (e.g.
RO), useful for shutting out a region that’s overwhelmingly bots.
Rules apply to page views and goals, but never to payments — a sale is a sale, so revenue is always recorded even from an excluded path.
A note on IP addresses: Statlark never receives your visitors’ raw IPs (that’s the privacy promise), so there’s no IP-based rule. The self-exclude link covers “ignore me,” and path / hostname / country cover the rest.