Reduce usage

Use Billing to compare monthly usage with the plan allowance.

What to review

Each accepted pageview and custom event uses event allowance. Web Vitals use a separate sample allowance. Review billing and usage before changing collection.

Avoid duplicate collection

Install one tracker snippet per page. In single-page apps, route changes are handled automatically; do not also send a pageview on every route unless you deliberately replace that behavior.

Keep custom events tied to meaningful actions. A handler attached twice can send two events. Avoid emitting an event on every scroll movement or animation frame.

Exclude test activity

Use traffic exclusions for your own browser, admin paths or staging hostnames. Rules apply to new collection and do not remove existing history.

Reaching the allowance

Collection pauses at the limit. Upgrade the event tier or wait for the monthly reset; rejected events are not buffered for later recovery. Removing old data does not recreate already consumed allowance.

Something unclear? Contact support.