Every plan includes web analytics, goals, funnels and revenue attribution. Choose the monthly event volume, team size, retention and collection setup you need.
For one site and one person who needs clear web and revenue analytics.
For small teams managing several sites, campaigns and funnels.
For larger portfolios that need first-party collection, custom properties and longer retention.
Pageviews, custom events, goals, checkout handoffs, normalized revenue events, imports, and proxy requests count toward your monthly volume.
Revenue events count after normalization. Duplicate webhook deliveries are ignored through idempotency.
The service keeps collecting through a 10% grace buffer and pauses at the hard limit shown in the dashboard.
If you process more than 10M monthly events or need to review deployment, data handling, or security requirements before buying, contact us with the expected volume and workflow.
Pageviews, custom events, goals, checkout handoffs, normalized revenue events, imports, and proxy requests count toward monthly event volume. Bot-filtered traffic does not count.
Stripe and Payment API revenue events count after normalization. Duplicate Stripe webhook deliveries are rejected idempotently, so retries do not create duplicate revenue events.
No. Stripe is supported directly, and teams can also send normalized purchases, renewals, refunds, cancellations, and churn through the Payment API.
The current service includes a 10% collection buffer above the selected monthly limit. The dashboard shows usage and the hard limit; collection pauses when the buffer is exhausted.