On this page
Key takeaways
- Define the outcome before launch, then track adoption, completion, handoffs and gaps against it.
- Friction signals such as rage clicks, dead clicks and abandoned forms show where the page itself is the problem.
- Analytics should respect privacy: record page paths, not what visitors type.
An AI agent that nobody opens, or that opens and does not help, looks identical to a working one until you measure it. The aim of measurement is simple: find the one thing to fix this week.
Six measures that matter
| Measure | What it tells you | What to do if it is low or high |
|---|---|---|
| Adoption | The share of visitors who open the agent and who start a call | Low: move the entry point, change the invitation, test the page |
| Funnel completion | How many visitors reach each step you named and where they are lost | A step that loses half your visitors is the first thing to rewrite |
| Handoff rate and reason | How often a person is needed and why | Group by reason, then fix the largest group |
| Lead capture rate | Share of conversations that leave contact details (paid plans) | Low: ask earlier, or at the moment of value |
| Unanswered questions | What visitors ask that the knowledge base cannot answer | Write the missing document |
| Friction | Rage clicks, dead clicks, idle or abandoned forms | Fix the page, not the agent |
Name your funnel steps
Avarole Insights shows a funnel for the milestones you define with one HTML attribute or one line of code. A typical sign-up funnel might be: viewed pricing, opened the agent, started a call, clicked sign-up, completed sign-up. Read it per agent, over the last 7, 30 or 90 days.
From a number to a fix
- A step that loses half your visitors is the first thing to rewrite.
- A page full of dead clicks usually hides a button that does not respond.
- A form that people abandon is a form with one field too many.
- A question the agent keeps answering is one your page should answer.
Compare fairly
To learn whether the agent changes behaviour, compare like with like. Use similar pages with and without the agent, or the same pages across two periods that do not include a campaign or a holiday. Run long enough to cover your weekly cycle. Seasonality, ad spend and traffic mix can hide or invent an effect, so change one thing at a time.
Keep it private
- Only page paths are recorded, never query strings or what visitors type.
- A random visitor id lives in the visitor's own browser.
- It stays off when the browser sends Do Not Track or the page opts out.
- You can switch it off per agent whenever you like.
- Events are kept for 180 days.
A weekly rhythm
- Open Insights and read the funnel for the last 30 days.
- Pick the biggest drop and read ten transcripts from that step.
- Ship one change: a page edit, a new document or a new action.
- Write down the number you expect to move, and check it next week.
Frequently asked questions
Does Insights work in mobile apps?
Yes. The React Native SDK sends the same events from your app, tagged as mobile, so one view covers web and app.
Will analytics slow my pages?
Events travel in small batches and a failed send is dropped, so analytics do not slow down or break a page.
Is visitor data stored?
Only page paths and the actions the agent took, never what visitors type or click. Details are on the Insights page.
See where visitors leave.
Avarole Insights shows the funnel, the exit pages and the friction, with privacy built in.
