Usage Tracking

Applies to: All

Overview

Usage under Billing shows where your organization’s credits went — which projects, environments, and actions consumed them. Finance leads use it before renewals; site owners use it to spot forgotten staging servers quietly spending credits.

Key concepts

  • Credits — FlexSite’s usage currency (see Credit System Overview).
  • Billing period — the date range on the usage chart, usually aligned to your invoice cycle.
  • Metered action — anything that spends credits: new environment, bigger Build Settings, backup, sync, Atom create, some publications.

Steps — open usage

  1. Open Billing.
  2. Click Usage (or Credit Usage Breakdown).
  3. Select a time range if filters are available (last 30 days, current period, etc.).
  4. Scan the chart for spikes — do they match a launch week or someone adding environments?

What counts toward usage (plain examples)

  • Environment created — “We added staging in March.”
  • CPU / RAM / cache upgrade — “Production felt slow; we moved sliders on Build Settings.”
  • Backup or restore — “We restored Tuesday’s snapshot.”
  • Sync — “We copied staging content to live.”
  • Atom site created — one-time deduction at provision time.

Is this usage normal?

  • Steady low usage on TRIAL with one sandbox — expected.
  • Production environment with moderate Build Settings — largest ongoing line item for many teams.
  • Sudden jump with no launch — check for duplicate staging environments or oversized dev copies left running.

Steps — reduce usage

  1. Delete unused environments on Environments.
  2. Lower Build Settings on idle dev copies.
  3. Remove abandoned test projects under Settings → delete project.

For finance reviews

Export or screenshot the usage table before renewal conversations. Pair with Trial, Frozen, and Plan States if status was FROZEN during the period.