Plans, usage and limits

This page explains how Clear Saga is sized and metered, so you can pick a plan, read the usage meter and know in advance what happens at the limit. Prices are on the pricing page.

One product, sized by events #

There is one product. Every plan has every feature, and members are not limited. The only thing that differs between plans is the monthly event allowance: how many events all sites of a workspace may record in a calendar month.

A plan belongs to a workspace, not to a site. The events of every site in the workspace are added together.

What counts as an event #

One event is one thing a site recorded:

• each page view,
• each custom event,
• each visit to a missing page (a 404),
• each performance report, when web vitals are switched on for the site.

Options that record more also count more: hash-based page paths, automatic conversion events and section visibility events all add events of their own.

Not counted:

• hits filtered as bots, see bot filtering,
• hits left out by a site's exclusion rules, see excluding visits,
• invalid requests and anything refused because of the plan,
• orders,
• the two small hits of returning visitors: the one that ties a running visit to its visitor once consent arrives, and a visitor's withdrawal. A withdrawal is acted on even while the workspace is over its allowance or has no active plan.

Funnels, conversion goals and campaigns add nothing of their own. They reuse events that were already counted.

Usage is counted per calendar month in UTC and starts over on the first day of the month. A site that was deleted during the month still counts for that month.

The trial #

A new workspace starts on a trial of 15 days. The trial does not start when you sign up. It starts when a site of the workspace records its first page view, so the days are not used up while you are still installing the tag.

During the trial you can add up to 5 sites. The trial runs on the plan size you picked on the pricing page before signing up, or on the smallest one if you picked none. Its allowance is the one of that plan.

When the trial ends without a plan, the dashboards lock. See "When a trial or plan runs out" below. No reminder is written when a trial is about to end: that is not built, see what works today. Settings, Billing and the sidebar show the days that are left.

Choosing, changing and cancelling a plan #

Only the owner can choose, change or cancel the plan, under Settings, Billing. Admins can read the plan and the usage. Viewers see neither.

A change applies at once. If this month's count is already at or above the allowance of the plan you pick, the dashboards lock straight away, and the screen warns you before you confirm.

The usage meter #

Settings, Usage shows this month's events against the allowance, the day the count starts over, and the events of each site, largest first. A small usage card in the sidebar shows the same total. Each member can hide that card for themselves on the Usage screen.

Three things happen as the count grows. They are the same on a plan and during a trial.

The warning and the notice are emails, and email delivery is not connected, so neither reaches an inbox today. Watch the meter instead. See what works today.

At 100 percent #

When the month's count reaches the allowance, the dashboards lock for everyone in the workspace until the first day of the next month (UTC).

• Visits are still counted. Nothing is lost. When the dashboards open again, the visits recorded during the lock are all there.
• What closes. The reports of every site, the Realtime screen, shared dashboard links, and the API, the MCP server and the command line. Embed widgets show a dash in place of their number. Alert rules are not checked and call no webhook while the lock lasts, and the weekly digest, the monthly report and traffic alerts are not written.
• What stays open. Settings, installation, team and billing, and the CSV export on a site's Data tab, so your data is never held back.

The dashboards open again with the new month, or at once when the owner changes to a plan whose allowance is above this month's count.

The safety ceiling #

Counting past the allowance does not go on without end. Collection itself pauses at a safety ceiling:

• On a plan: at 5 times the allowance.
• For any workspace: never later than 12,000,000 events in one month, whatever the plan.
• During a trial: at 500,000 events, whatever plan size the trial runs on. On the larger plans this comes before the allowance.

Visits that arrive during a pause are not recorded and cannot be added later. Collection starts again with the new month, or at once after a change to a plan whose ceiling is above this month's count.

Site limits #

The demo site does not count against the limit.

When a trial or plan runs out #

This is separate from the monthly allowance. It happens when a trial ends without a plan, or when the owner cancels the plan.

1. The dashboards lock at once, for everyone in the workspace.
2. Visits are still recorded for 14 days. Choose a plan in that time and nothing is missing.
3. After those days, collection stops. Visits are no longer recorded until a plan is chosen.

Nothing is deleted by any of these steps. Choosing a plan opens the dashboards and starts collection again. Data is removed only by the retention periods described in privacy: cookieless by default.

To use fewer events #

• Add exclusion rules for traffic you do not need, such as an admin area or a staging hostname. An excluded hit is not counted. See excluding visits.
• Switch off options you do not read. Web vitals and section visibility events each add events.
• Check the events by site on Settings, Usage to see where the volume comes from.

Next: Excluding visits, Bot filtering, What works today