Skip to main content
Billing lives in Settings → Billing. Only admins can see or change it, and their access has to cover the whole account rather than a single site. Members get a 403 on every billing screen, including the read-only ones. See Team and roles.

​
Changing plan

The billing page shows your current plan. Click Change plan to compare every tier side by side: its monthly price, sites, seats, events, AI crawl hits, AI visibility prompts and pay-as-you-go overage rates. Your current plan is marked Current. Pick another and confirm. Before you commit, the dialog tells you what changes, what it costs, and when it takes effect.

Upgrades apply immediately

Your new limits are live as soon as the change goes through. The prorated difference for the rest of the current billing period is charged to your card right away, on its own invoice.

Downgrades apply at period end

You keep your current plan and its limits until your billing period ends, then move down. You aren’t charged anything today, and nothing you’ve already paid for is cut short.
If the upgrade payment doesn’t go through, because the card is declined or your bank asks to confirm the payment, nothing changes. You stay on your current plan and aren’t charged, and the billing page shows the reason with an Update card button. Update the card, then upgrade again. A scheduled downgrade appears under your plan with the date it takes effect and a Keep button. Selecting Keep cancels the downgrade and leaves you on your current plan; nothing else changes. If you’re on the free Starter plan and have never subscribed, choosing a paid plan takes you to Stripe Checkout to enter payment details.

​
Cancelling your subscription

On a paid plan, the row under your plan shows the date it renews and a Cancel subscription button.
1

Select Cancel subscription

The dialog shows what Starter includes: 60,000 events a month, one site and one seat.
2

Confirm

Select Cancel subscription in the dialog. Nothing changes today: you keep your plan and its limits until the end of the current billing period.
Until then the row reads Cancels on with the date, and a Resume button that keeps your subscription as it was. When the period ends, the account moves to Starter.

​
Cancelling with more than one site

Starter allows one site. If you have more, the dialog lists your sites and asks which one to keep.
1

Choose the site to keep

The other sites are marked as the ones that will be deleted.
2

Type the kept site's domain

This confirms which site stays.
3

Select Cancel subscription

Traceten deletes the other sites first, exactly as deleting a site does, and only then cancels the subscription.
If a site can’t be deleted, the subscription is not cancelled, and the dialog names the site that failed. Sites deleted before the failure stay deleted. Try again to delete the rest and cancel. Cancelling follows the same rules as a downgrade to Starter, and it is refused while the account is scheduled for deletion. A downgrade you had already scheduled is replaced by the cancellation. See When a downgrade is blocked. A cancellation made outside the dashboard, for example by our support team in Stripe, shows the same Cancels on row.

​
Cancelling outside Traceten

Cancelling from Traceten asks which sites to delete and keeps one. A cancellation made anywhere else, for example by contacting support or in Stripe, can’t ask. When it ends your subscription, Traceten keeps collecting on your oldest sites, up to the new plan’s site limit, and pauses collection on the rest. A plan change made outside Traceten that lowers your site limit works the same way when it takes effect.
  • Oldest first. Sites are kept in the order you created them, so on Starter only your oldest remaining site keeps collecting.
  • Paused, not deleted. A paused site keeps everything recorded before the pause and shows Paused in Settings → Sites. Nothing is collected while it is paused, so its reports have a gap for that time.
  • Resuming. Upgrade to a plan with room for more sites, or delete sites you no longer need. Paused sites resume automatically, oldest first, once they fit within your plan’s limit.

​
When a downgrade is blocked

A downgrade is refused if the plan you’re moving to allows fewer sites than you currently have. Traceten tells you how many sites are in the way. Letting the change through would leave your account permanently over its own limit, with no way to resolve it except deleting sites. Delete the sites you no longer need (see Deleting a site), then try again. Two other cases are refused:
  • An unpaid invoice. Upgrades are blocked until your payment method is updated. Downgrades are always allowed: if you can’t afford the current tier, moving down is the fix, not the problem.
  • A scheduled account deletion. Cancel the deletion first. See Deleting your account.

​
Usage

Traceten meters two things, separately, and Settings → Usage shows a card for each. Usage is counted per billing period, and your billing period is your Stripe subscription’s period. If you subscribed on the 17th, each period runs from the 17th to the 16th of the next month, and your allowances reset on the 17th. An account that has never subscribed uses the calendar month.

​
Events

An event is one measurement your site sends us. Four things produce them, and they are counted together as one number with no split by type:
  • Pageviews. One per page load, plus one per route change in a single-page app. (If a visitor who first declined later grants consent, that first event is recorded as a session_start instead. It replaces the pageview, it isn’t added to it.)
  • Custom events and goals. Every traceten.track() call, and every declarative goal (data-traceten-goal, data-traceten-scroll). A goal is a track() call underneath, so a goal on its own is one event rather than two.
  • Tracked clicks. Every click on an element you have marked with data-traceten="label". Repeat clicks on the same element are ignored for one second, so an impatient double-click records once. data-traceten and data-traceten-goal are independent, so an element marked with both records a tracked click and a goal (see Browser SDK).
  • Engagement reports. When a visitor leaves a page, or switches away from the tab, the snippet sends an exit event carrying engagement measurements such as how long they read, how far they scrolled, and how they moved the pointer. These are the events Traceten classifies, and they are where your engagement and bounce numbers come from. Repeat reports back off as a visit goes on, and are capped per page load, so a visitor moving between tabs does not generate one per switch.
Events sent from a server SDK count exactly like events from the browser snippet. Settings → Usage shows the event count for your current period, so you can see where you stand against your allowance at any time. Three things do not count against your event allowance:
  • AI crawler hits. Metered separately, on their own allowance. See AI crawl hits below.
  • Revenue. Charges and orders that arrive from Stripe, Shopify, Lemon Squeezy, Polar or Paddle, and payments you post to the Payment API, are recorded as revenue, not as events, and are never metered. Refunds are not metered either. If you also send your own track('purchase') for the same sale, you are billed once, for the track() call.
  • identify() calls, and the snippet’s own error reports. Neither reaches the event meter.
Within that, the meter counts every event on your sites, AI-referred and everything else: Traceten classifies all of your traffic to find the AI slice, so the meter reflects the work done rather than the subset you’re most interested in. This is a cap. When you reach your plan’s event allowance, new events are rejected at the edge unless you’ve enabled pay-as-you-go event overage.

​
AI crawl hits

A crawl hit is a request from an AI crawler (GPTBot, ClaudeBot, PerplexityBot and others) reported by the AI-crawler middleware. Crawler traffic is not something you control, so it is metered separately and never counts against your event allowance. What happens past the allowance depends on your plan. On a paid plan, going past your included crawl allowance never blocks anything and never loses a count:
  • every hit is still counted, so your totals and any charges stay exact
  • what changes is per-crawl detail. The reverse-DNS verification pass is skipped and individual crawl records are not kept, so crawls are recorded at lower confidence
  • turning on crawl overage keeps full verification and bills the excess hits
On the free Starter plan there is no pay-as-you-go crawl overage to fall back on, so measurement pauses at the limit instead of continuing and billing you for it. New crawl hits stop being recorded for the rest of the billing period. Enforcement is checked every few minutes, so a small number of hits just past the limit may still be counted, in your favour, and never billed. Everything captured before the limit stays available and stays accurate. Your allowance resets at the start of your next billing period, and upgrading resumes recording within a few minutes. Your usage page shows which of these you are in, and the API reports it as crawl_allowance_state. Both figures are calculated by a rollup that runs every few minutes, so neither is ever live to the second. Each card shows when it was last updated.

​
Pay-as-you-go overage

Overage is opt-in, and the two meters have separate, independent switches. Turning one on does not turn the other on. All four combinations are valid: Rates are shown per unit on the pricing page and on the toggle itself. Overage is not available on the free Starter plan. Switching a meter on or off only ever affects usage from that moment onward:
  • Turning it on mid-period does not bill you for what came before. Whatever had already gone past your allowance while the toggle was off stays unbilled. We record the figure at the moment you switch on and only charge for what accrues after it. (The figure comes from a usage rollup that runs every few minutes, so in the worst case a few minutes of earlier usage is included.)
  • Turning it off stops the charge from that moment. Usage that accrued while it was on is still billed, because that volume was processed for you, but nothing after the switch is, for the rest of the period.

​
Payment method and invoices

The Payment section shows your next invoice and the card Stripe will charge: its brand, last four digits and expiry date. That is all Traceten ever receives about a card. The number itself is handled entirely by Stripe. If you pay with Stripe Link, the section shows Link, because Stripe doesn’t share the card behind it. Select Update to change the card in the Stripe billing portal. The portal is for your payment details and invoices. Plan changes and cancellation happen on the billing page, where the site limit is checked. Invoices are listed on the billing page, with a PDF link for each.