Usage

When you finish, you know how much of the cycle you’ve used, and which event or rule is driving it.

Where usage lives

Usage lives in the This cycle card on Settings → Billing.

The two metered balances

Balance	Counts	Does not count
`Events`	Every event Datalyr accepts: pageviews, custom events, mobile events, and webhook events from Stripe, Shopify, Whop, RevenueCat, and Superwall	Events dropped by a filter, and events rejected over the rate limit
`Postbacks`	Every conversion Datalyr delivers to an ad platform with status `sent`	A conversion no rule matched, and a failed delivery

An event blocked by Settings → Filters is never billed, because filters run at ingest before metering. Both numbers lag ingest by about 5 minutes.

Find the cause of a spike

Confirm the workspace switcher shows the workspace you are investigating.
Open Events.
Group the last 24 hours by event name.
Compare the top event’s count with the real customer action it represents.
Open Conversions. Note every rule that is currently on.
Check what you deployed on the day the line changed.

These five causes cover most spikes.

Cause	Symptom in Events	Fix
The snippet and the npm package both load	Two `pageview` events per page load, two `visitor_id` values	Load one of them. See Web SDK.
`page()` called inside a re-rendering component	`pageview` count far above session count	Rely on automatic tracking. Call `page()` only with `trackPageViews: false`.
A bot or scraper hits your site	One IP producing thousands of events	Add the IP under Settings → Filters.
A staging or preview host runs the production workspace ID	Events with a `page_path` you do not recognize	Use a separate workspace for staging.
A conversion rule matches a broad event	`Postbacks` rising, `Events` flat	Narrow the rule’s event name in Conversions.

Do not remove the snippet to stop a spike. You lose attribution for every visit while it’s off, and those visits are gone permanently. Disable the duplicate event or the over-broad rule instead.

Verify the fix

Apply the fix.
Wait 10 minutes.
Open Live.
Confirm one customer action produces one event.

When it doesn’t work

Symptom	Cause	Fix
The number did not move after a test event	Billing data lags ingest by about 5 minutes.	Wait, then reload.
`Setting up your billing…`	The plan has no provisioned limit yet.	Contact [email protected].
`Events` counts more than Events shows	Events filters by your date range and by source. `Events` counts the whole cycle.	Match the range to the cycle before comparing.

Plans and billing: included volumes and overage rates.
Filters: drop unwanted traffic before Datalyr meters it.
Conversion delivery: what makes a postback.

Get started

Installation

Revenue

Using Datalyr

Advanced

Integrations

Account & billing

Troubleshooting

Where usage lives

The two metered balances

Find the cause of a spike

Verify the fix

When it doesn’t work

Next

​Where usage lives

​The two metered balances

​Find the cause of a spike

​Verify the fix

​When it doesn’t work

​Next

Where usage lives

The two metered balances

Find the cause of a spike

Verify the fix

When it doesn’t work

Next