Your reports are only as right as your tracking.
The AI install and ready-made schema examples set up what to track. The schema then shows what is firing and flags what looks wrong.
Most of the setup is done with you
Install with AI in about 5 minutes. Ready-made schema examples set out which events and properties to track, and you confirm a role for each event in the schema or in the chat. What is left is review. A clean schema stops being a project you never get to.
Every event you fire, and the role it plays
The schema is the list of what you track, ranked by volume, with a status on each one. An event you expect with almost no volume is a tracking bug, and this is where you see it before it spoils a report.
- Every event ranked by real volume, with active, idle or stale status
- Drill into an event to see the properties and values it carries
- A stale event with no volume is flagged as a likely bug
Roles are what make the chat accurate
A role says what an event means for your business: product view, add to cart, checkout, signup, activation, conversion. It is what lets you ask for “my acquisition” and have the right events picked up. Without roles the chat has to guess from your event names.
- One set of words across every report and the chat
- Ask a vague question and get the right events used
- Change a role once and every report follows
Build UTM links that follow your naming rules
Most attribution problems are tagging problems. The UTM builder writes links to your own naming rules, one at a time or in bulk, and shows the channel each one will count under. A medium Kissmetrics does not recognize is a tagging gap, and it is far cheaper to catch before the campaign runs than in a quarterly review.
- Build single links or in bulk, to rules you define
- See the channel each link will count under before it ships
- Check existing links and fix what was mistagged
Try it on your own data. Free to start, no card.
Install with AI in about 5 minutes.
No card required. Free plan. No developer needed for your website.