How to track custom events in web analytics
TL;DR: Custom events turn important actions into measurable data. Name them clearly, implement with a small JS call or data attributes, verify in realtime, then use them in funnels and goals.
Full API detail: custom events docs. Concepts: what is event tracking?.
Step by step
1. List the actions that change the business
Signup started/completed, plan selected, checkout started, purchase, demo booked. Ignore vanity clicks.
2. Pick a naming convention
Use consistent names like signup_completed. Never put emails or user IDs in event names.
3. Implement the event
Follow Reignat custom events for your stack — script helper, framework hook, or attribute-based triggers.
4. Verify in realtime
Trigger the action on production or a staging project and confirm the event appears. See realtime docs.
5. Wire into funnels and revenue
Add events as funnel steps and connect payments if the event is commercial. Funnels · Revenue.
Reignat is the events-metered, revenue-aware option with journeys, funnels, realtime, and an AI assistant on every plan. Start a free 7-day trial — no card required.
Keep reading
- Custom events docs
- How to set up a conversion funnel
- What is event tracking?
- How to track Stripe revenue
Frequently asked questions
How do I track a button click as an event?
Call the tracker with an event name on click, or use a data attribute if your tool supports it. In Reignat, see the custom events docs for the supported APIs.
Do custom events require cookies?
Not with cookieless analytics. Events are just hits your script sends — no marketing cookie required.
Will events burn my plan faster?
On event-metered plans, yes — each tagged action counts. Track what you will actually use in dashboards and funnels.