Usage and billing

Read the usage charts, understand when your allowance resets, and manage your plan, invoices and payment method.

The usage page

Team settings → Usage is where you see what you are consuming against your plan.

It charts three series over time:

Events — everything the tracking script sends
Orders — completed orders posted through the API
AI usage — Clakta AI consumption against your monthly budget

Alongside the chart you get totals for the selected period, a per-project breakdown, and the date your allowance resets. Filter to a single project, a subset, or all of them.

Export any view as CSV with Export → Download as CSV when you need the numbers outside Clakta.

The billing cycle

Allowances are monthly and reset on your team's billing cycle date — shown as "Usage resets on …" on the usage page. That is your team's own cycle day, not the first of the calendar month, so a mid-month signup resets mid-month.

Nothing carries over. An unused allowance does not accumulate.

Managing your plan

Team settings → Billing is where you change plan, switch between monthly and annual, update your payment method and download invoices.

Upgrades take effect immediately. All data and configuration survive a plan change in either direction.

Downgrading shortens retention

Retention follows the plan you are currently on. Moving from Business (730 days) to Pro (365 days) makes anything older than the new limit unavailable. Export what you need first — see Data retention.

Who can manage billing

Team owners have full access. The Billing role exists specifically for a finance contact who needs invoices and plan management without access to performance data — see Members and roles.

When you exceed a limit

The API returns an explicit limit error rather than silently discarding data. That matters for your integration: log it and alert on it, rather than swallowing the failure and losing orders quietly.

If you are close to a cap:

Check the per-project breakdown on the usage page — one noisy project is often responsible
Review which auto-tracked events you have enabled under Project settings → Script. Scrolls in particular generate high volume; turn off what you do not analyse
Upgrade if the consumption is genuine growth

Look at the usage page at the start of each cycle, not the end. Discovering a cap on the last day leaves you no room to act.

Activity and API logs

Two nearby pages help when something looks wrong:

Team settings → Activity — a log of changes made in the team, useful for answering "who changed this and when"
Team settings → API logs — the requests made with your API keys, the first place to look when an integration starts failing

Members and roles

Invite people to your team, understand what each of the four roles can do, and control which projects a member can see.

API keys

Create scoped keys for programmatic access, authenticate your requests, and keep keys safe once they are issued.

Plans and limits

What each plan includes, which limit you are most likely to hit first, and how to decide when to upgrade.