Dashboard · Insights by Module

Insights by Module

One report per module: Chat, Library, Ads, Calendar and Intent. They are built the same way, so once you can read one you can read them all: a funnel from the window's engaged visitors through the module to the contacts it produced, a week-by-week matrix, and a click on any number to see the people behind it. Each has a button into that module's settings.

How every module report is built

Every module report: a funnel of people, then the same metrics week by week. Every count opens the list of people it counts.

Window

The same completed-ISO-week window as Traffic Insights, shared across the pages: last 1, 4, 8 or 16 weeks, or a custom range.

Engaged visitors

The first band of every funnel. Visitors who did more than bounce in the selected weeks: spent time, viewed multiple pages, chatted, or became a lead. The same definition as Traffic Insights' engageable visitors.

Became leads

The last band: of the people who used the module, those who then became a lead, as of now, split on a rail into direct (converted inside the module) and assist (the module helped, they converted elsewhere). Leads created before the person's first use of the module in the window are not counted.

Week by week

A matrix with a row per metric and a column per week, coloured by change against the row's average across the window. Hide values keeps only the colours.

Site lens

Show the report for one of your registered domains. A visitor counts under the site they visited most recently, so nobody is on two sites; visitors on an unregistered host appear under All sites only.

Device lens

Desktop, or mobile (phones and tablets). Every number and drill-down is then those visitors alone; visitors with no recorded user agent sit outside both lenses. A Partial badge means one week's per-visitor events did not fully reconcile.

Note

Counts are recorded as events happen and are not updated if a lead or meeting is later disqualified. The Contacts tab and the contact-based KPIs elsewhere do exclude disqualified people.

Chat

The chat funnel: engaged visitors → people who chatted (sent at least one message) → became leads, with total messages and the average per chatter, and the engaged → chat rate. Then five sections:

Contact form in chat

How often the assistant showed the in-chat contact form to people who chatted (offered, and the offer rate) and how often they filled it in (submitted, and the submit rate), plus the two gaps: chatted but never offered, and offered but did not submit. Only the assistant's own offers count; a visitor who opened the form themselves is not an offer. When Require the form before chatting is on, every visitor sees the form first and the offered band reflects only offers made in replies.

How people started their chat

Of the people who chatted for the first time ever in this window, how each opened that chat: a reply button under the welcome message, a conversation starter above the input, an ad's reply button, or a message of their own. Buttons are listed with the text the visitor saw, so a translated widget lists each language separately, and the kind is recorded at the click, so editing buttons later does not change history.

Chats by UTM campaign

For each utm_source / medium / campaign combination visitors arrived with: visitors, chatted, chat rate, became leads, and whether the campaign has a page-specific welcome message, with a button to draft one. Chat rate is chatters ÷ that row's visitors, so rows compare with each other, not with the funnel. Combinations under 3 visitors are left out.

Chat → meeting

Of the people who chatted, how many booked a meeting after that chat (on the Meeton calendar or recorded from the CRM), the median days from chat to booking, and whether the booking is what made them a lead or they were one already. A meeting booked before the chat does not count.

Top conversation topics and chat history

AI-grouped topics ranked by the conversations or visitors that touched them, and the list of every visitor who chatted in the window, each opening their record with the window's chats highlighted.

Library

The Library funnel: engaged visitors → unique Library visitors (opened, read or downloaded a document, or asked the Library a question) → became leads, where direct means their last conversion touch was a Library form. Page views count pages read; the funnel counts people. The weekly rows add page views, unique documents viewed, average page views per document, leads and CVR, and the question side: unique visitors who asked, the ask rate and questions asked. By document lists each published document with unique visitors, page views and leads.

The Ads funnel: engaged visitors → reached (shown at least one ad; people, not impressions) → clicked an ad (a call-to-action click) → ad-attributed leads, split into via Meeton and assisted, with meetings as a share of leads. A lead can convert without clicking, so the leads band can be larger than the clicks band. Weekly rows: reached, impressions, CTA clicks, CTR (clicks ÷ reached), leads, lead CVR (leads ÷ reached) and meetings.

By journey lists each journey, live or paused, with reached, CTA clicks and leads, expanding into its steps and placements with impressions and clicks each; per-placement leads are last-touch, so they add up higher than the row's Meeton-assisted count. By format and By trigger break the same numbers out by creative format and by what showed the placement. A placement that rotates several triggers is shown as Mixed triggers rather than guessed; placements since deleted are Removed placements; rows under the minimum reached show no rate. Journeys themselves are built in the Ads tab, see Meeton Ads.

Calendar

The booking funnel, in events counted once per visitor per week: opened the calendar (was shown it, from chat, the Library, a thank-you page or an email link) → started a booking (clicked in to pick a time) → booked. A rail shows booked leads, the booked people captured as a contact and first seen in the window, split into via the calendar and credited elsewhere. Weekly rows add CTR (started ÷ opened) and booking rate (booked ÷ started).

By surface breaks the funnel out by where the calendar was shown: Chat, Library, Thank-you pages, Email links and Other links (shared booking links and QR codes, journey CTAs, the book a meeting button after a form submit, and older events). Thank-you pages open the calendar automatically after a form submit, so a lower CTR there is expected; compare each surface against itself week over week. Click a surface to scope the whole report to it; lead outcomes are per person across surfaces, so they show for All surfaces only. A health chip says Booking live with the number of calendars, or warns that booking is off and visitors hit a no times available dead end.

Intent

The company-level report, the outbound half of Sales Insights on the weekly window. The funnel: engaged visitors → matched visitors (matched to an identified company) → companies identified, with how many are new to your team → companies that gained a lead, their first lead for your team. Weekly rows: matched visitors, identification rate and companies identified.

The company sections describe the window's last completed week as a snapshot, computed once: companies identified, those with a lead (account coverage), high intent, no lead (your call list) and the rest. Who these companies are facets them by industry, company size and region, for all identified or high-intent only. High-intent companies lists each with Has a lead or No lead yet; Lookalike targets are companies without a lead that match the profile derived from the companies where you already have leads; All identified companies is the full table with intent tier (Hot, Warm, Neutral), visitors, pages, lead and last seen.

Troubleshooting

Symptom	Likely cause	What to do
The leads band is bigger than the clicks band (Ads)	A lead can convert at any step without clicking a call-to-action	Expected; leads are shown against reached, not clicks.
Surface rows add up to more than All surfaces (Calendar)	A visitor who opened the calendar on two surfaces counts on both	Expected; use All surfaces for totals.
Booked leads lower than visitors who booked (Calendar)	A booking with no captured contact, or by a visitor first seen before the window	Expected; the rail explains the split.
No visitors on this site in this window (site lens)	The domain is registered but the tag is not installed there	Check the installation on that site.
A first chat shows Unknown for how it started	Chats from before this was recorded were matched to your buttons at backfill time	Nothing to do; new chats record the kind at the click.
No companies identified (Intent)	Too little traffic, or traffic from consumer networks	Try a wider window; company matching works best with more traffic.

Frequently asked questions

Why do the Chat report and Traffic Insights' chat panel differ?

They count differently. Traffic Insights counts conversations and contacts within the week; the Chat report follows people from their first chat in the window to a lead as of now, so a row can grow after its week closes.

Is a visitor who chats in two weeks counted twice?

In the weekly rows, yes, once per week. In the funnel bands and the drill-down lists, once per window, from their first use of the module in it.

Can I compare two sites side by side?

Not on one screen. Switch the site lens, or open the report twice in two tabs with different lenses; the lens is in the URL.