What counts as a tracked event?
An event is any action our pixel captures on your site — pageviews, custom goals, payment hints, and (on the Plus bundle) clicks, form submits, add-to-cart, and more. Server-side identify calls and CAPI traffic don't count.
Admaxxer AI Analytics is a marketing analytics platform for ecom and SaaS teams.
What is a tracked event?
A tracked event is any discrete action that our client-side pixel captures on your site or store. Each event counts once toward your plan's monthly events allowance.
What counts
- Pageviews — every page load or single-page-app route change. SPA routers using
pushState,replaceState,popstate, orhashchangeare detected automatically. - Custom goals — anything you tag with
data-admx-goal="signup"or fire programmatically viawindow.admaxxer('goal', 'lead'). Useful for marking conversions that don't have a natural URL. - Payment hints — when a visitor returns from a checkout flow with
session_id,payment_intent, or equivalent in the URL (Stripe, Polar, Paddle, LemonSqueezy). Used to associate revenue with the originating click. - Plus bundle auto-captures — if you've enabled the Plus bundle (one extra script tag), we also auto-capture: clicks on tagged elements, form submits, add-to-cart, initiate-checkout, 404s, outbound link clicks, downloads, and rage-clicks.
What doesn't count
identify()calls — used to attach an email or user ID to a visitor for cross-device stitching. Not metered.- Server-side CAPI traffic — events you send directly to Meta or Google from your server. We pass them through but don't bill them as pixel events.
- Internal product telemetry — events the Admaxxer dashboard itself fires (e.g., chart-loaded). We track these in a separate datasource.
- Webhook revenue events — when Stripe or Shopify fires a webhook to us, we attribute the revenue to the originating pageview rather than counting it as a new event.
A worked example
Imagine your store gets 1,000 visitors next month. They each browse 5 pages on average. That's 5,000 events. Of those:
- 100 add an item to cart (Plus bundle adds 100 events)
- 30 complete checkout (Plus bundle adds 30 initiate-checkout events; the 30 actual payments count as payment hints, +30)
Total events for the month: 5,000 + 100 + 30 + 30 = 5,160 events.
The Starter plan covers 25,000 events/month — you're well under.
What happens if you go over
We email you at 80% and again at 100% of your monthly quota. Events keep being recorded — we don't drop them — but a non-blocking upgrade prompt appears on the dashboard. You can upgrade to a higher plan or contact us about a usage-based add-on.
Why we count events this way
Pricing on actions that touch the analytics layer (and thus consume analytics-warehouse query capacity) keeps costs predictable for both sides. Authenticated server-side traffic and identity-only calls scale linearly with infrastructure that isn't event-based, so we don't bill them as pixel events.
See also
Related Questions
Do server-side CAPI events count toward my Admaxxer event quota?
No. Events sent directly to Meta or Google via CAPI from your server are not metered as pixel events. Only client-side pixel actions count toward your plan's monthly events allowance.
Does identify() count as a tracked event?
No. identify() calls attach an email or user ID to a visitor for cross-device stitching and are not metered. Only pageviews, custom goals, payment hints, and Plus-bundle auto-captures consume your event quota.
What happens if I exceed my monthly event quota?
Admaxxer emails you at 80 percent and 100 percent of your quota. Events keep being recorded with no drops, and a non-blocking upgrade prompt appears on the dashboard. You can upgrade or request a usage-based add-on.
Still have questions?
See the full documentation or start a 7-day free trial — no credit card required.
Try Admaxxer Free