Pixels and install tags

The two things

A pixel is where your data lands. It has a name and it owns every report you see. Most people use one pixel per site.

An install tag is a key you paste into a page. One pixel can have several tags, and every tag feeds the same pixel’s reports.

The value in your snippet after ?s= is the tag key, not the pixel:

<script defer src="https://10.vidstats.top/js/p.js?s=THIS_IS_A_TAG_KEY"></script>

Why they are separate

So you can replace a key without a gap in your data.

If the key were the pixel, rotating it would mean starting a new pixel and losing every report before the switch. With tags, you mint a new one, deploy it, and retire the old one once traffic has moved. The pixel and its history are untouched.

Rotate a key

Open Pixels and add a tag to the pixel. Name it after where it goes, like prod-2026.
Copy its snippet and deploy it.
Watch the new tag’s visit count until it matches your traffic.
Retire the old tag.

Retiring a tag stops it collecting. Data it already sent stays in the pixel’s reports.

When to use one pixel or several

Situation	Do
One site	One pixel, one tag
Staging and production of the same site	One pixel, two tags. Same reports, and you can tell them apart
Two unrelated sites	Two pixels. Their reports should not mix
Same site on several domains	One pixel, one tag. Add the domains to filter by them later

Domains

Domains on a pixel are a display filter, not a gate. The pixel collects from wherever your snippet runs. Adding a domain lets you filter reports to it and labels it in the dashboard; leaving it out does not block anything.

If someone copies your snippet onto their site, their traffic lands in your pixel. Rotate the tag if that happens.

Tracking domain

The domain your snippet sends to, set in Settings. Switch it and the install code on Pixels updates to match, so copy your snippet again afterwards.

This is also the host your content security policy must allow. If you have a CSP, update it at the same time or data stops arriving.