> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datalyr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage

> Understand event and postback usage for the current billing cycle.

Open **Settings → Billing** and find **This cycle**. Datalyr tracks two balances:

* **Events:** billable activity collected by the workspace, including pageviews, custom events, and supported source activity such as orders or payments.
* **Postbacks:** conversions Datalyr sends to connected ad platforms.

The page shows used, included, and remaining amounts. Billing data can lag ingestion by about five minutes, so a brand-new test may not change the total immediately.

## Investigate unexpected growth

1. Confirm you are viewing the correct workspace and billing cycle.
2. Open **Events** and group recent activity by event name and source.
3. Look for an event firing more often than the customer action it represents.
4. Review enabled conversion rules if postbacks are growing unexpectedly.
5. Check recent deployments and newly connected sources.

Common causes include page tracking mounted twice, a manual event called inside a repeated render, both client and server events sent without a shared idempotency ID, or a conversion rule that matches a broad event.

## Near or over the limit

Datalyr shows a warning as usage approaches the plan allowance. Current plans do not cut off collection at the limit; overage is billed according to the active plan. Review the current pricing and billing portal for the terms that apply to your workspace.

Do not delete tracking just to stop a short spike before finding its cause. First disable the specific duplicate event or overly broad conversion rule, then verify the rate returns to normal.