Domain Slots

Each account may register up to ten sites at once. Every registered hostname uses one slot. All sites share the same visit pool. Removing a site frees its slot immediately.

What counts as a domain slot

A domain slot is one active site registration on your account. When you add a site in the dashboard, you supply a hostname and receive a site key tied to that hostname. The registration occupies one slot until you delete it. example.com and www.example.com registered as separate sites use two slots. A subdomain registered on its own uses its own slot even if it shares infrastructure with the root domain.

Slots measure registrations, not domain names you own elsewhere. Parking a domain without a StatelessID registration does not consume a slot. A test registration you created and forgot about does consume one. The account settings page shows how many of the ten slots are in use and how many remain available.

Each registration is a hostname-and-key pair. When a page loads your script, the server checks that the beacon's key matches the origin. Two sites on the same server still need separate registrations if you want separate boards for each hostname. The visit pool, however, is account-wide — slots divide where data is collected, not how much capacity you bought.

Managing slots you already use

Review your site list periodically for hostnames you no longer track. Retired projects, old staging domains, and redirects you replaced months ago still hold slots if the registrations remain. Deleting a site frees its slot the moment the deletion confirms. You can register a new hostname immediately afterward if you still have capacity within the ten-slot maximum.

Before deleting, copy any board figures you want to keep. Deletion removes the site's historical counts, referrers, resolution classes, and the site key. There is no recycle bin and no export. Renaming a site in the dashboard is cosmetic — it does not free a slot or issue a new key. Only create and delete operations change slot usage.

Agency and multi-client operators should decide deliberately which hostnames need their own boards. Canonical redirects can sometimes mean tracking only the destination hostname if every visitor ultimately lands there. That reduces slot pressure without hiding real traffic — but only when your publishing setup honestly consolidates to one countable origin.

When all ten slots are full

There is no larger plan with more slots. The subscription includes up to ten simultaneous registrations. If you need an eleventh hostname, you must remove one you no longer need or run a separate account with its own subscription and its own visit pool. Each account is identified by its own access key and billed independently.

Choosing which site to remove is a judgment call the dashboard cannot make for you. Prefer deleting registrations whose boards you have not opened in months, whose keys are no longer installed, or whose domains now redirect elsewhere. Keep registrations that still carry live script tags on production pages.

If creation fails with a no-slots error, reload account settings after any recent deletion. A cached settings view can show the old count for a moment. After a hard reload, the freed slot should appear. If creation still fails, verify you are logged into the account that actually holds the registrations you deleted.

What deletion does to data and keys

Deleting a site is immediate and irreversible. All counts for that hostname vanish from the board. The site key deactivates at once. Pages that still embed the old tag will fire beacons that the server drops silently — no browser error, no effect on other accounts.

If you recreate the same hostname later, you receive a new site key. Update every template that still carried the old data-k value. Old keys are not reissued. This matters after cleanup mistakes: deleting production data to free a slot cannot be undone by re-adding the hostname.

Slot limits and visit limits are separate constraints on the same subscription. You might have four slots in use and still approach the visit pool ceiling because traffic is heavy. Conversely, you might use only one slot and still need to manage pool usage on a busy site. Account settings shows both numbers so you can see which constraint is binding.

Troubleshooting

If you deleted a site to free a slot but cannot create a new registration, hard-reload account settings and confirm the slot count dropped. If it did not, the deletion may not have completed — try again from the domains section of the dashboard.

If you accidentally deleted a production site, contact support quickly with your access key and the hostname. Recovery is not guaranteed and windows are short, but rapid reports are easier to act on than requests filed days later.

If you need more than ten live hostnames long term, plan for a second account rather than expecting a slot upgrade. There is no mid-subscription path to raise the slot cap on a single account.