Dashboard · Insights
Insights
The reporting half of the dashboard. Four pages answer four questions: Traffic, how is the website doing; Sales, who should we call; ROI, what is Meeton worth; and, for a support agent, Support, how well does the agent resolve things. Insights by Module then gives each module its own report. This page covers what they share.
Windows and periods
Each page has its own notion of time, chosen to match how its data is produced.
| Page | Time control | Refresh |
|---|---|---|
| Traffic Insights, Insights by Module, Support Insights | A window of completed ISO weeks: Last week, Last 4, 8 or 16 weeks, or a custom from–to range of up to 16 weeks, back to the week your workspace was created. The current, unfinished week is never included. | Weekly reports are computed once a week closes; some sections add live data. |
| Sales Insights | Last 30 days or a completed calendar quarter. | Hourly or daily; the page header says which. |
| ROI Insights | Last 7, 30, 60 or 90 days, month or quarter to date, previous month or quarter, or a custom range, each compared with the period before it. | Live. |
An ISO week runs Monday to Sunday and is numbered within the year, so W21 is the same seven days for everyone. Week-based reports use it so that a week is a closed, comparable unit; it is why Monday's report covers up to Sunday, not up to this morning.
How multi-week windows add up
When a window spans several weeks, each metric says how it was combined, with a tag on the card: Σ SUM for counts summed across weeks, POOLED for rates recomputed from the summed numerators and denominators rather than averaged, unique for people counted once per window, and DISTINCT for the few counts that are re-counted over the whole window. A rate card also shows its weekly range and average as a spread signal, and a weeks seen badge says in how many of the weeks a row had data. Where a value cannot be pooled, the latest week's value is shown and flagged.
Drill-downs: the people behind every number
Almost every count in Insights is a link. Click it and a drawer lists the visitors or contacts it counts, newest first or by highest engagement, each opening its record. A drill-down over a multi-week window lists each person once even if the panel counted them in several weeks, so its total can be lower than the number you clicked; where the funnel counts events rather than people (calendar opens, bookings started) the note says so. The list also shows where each company name came from: the contact record, what the visitor entered in the chat, or the network.
Meeton assists only
Sales and Traffic Insights have a Meeton assists only toggle. On, contact metrics count only contacts with at least one Meeton conversion event: a chat, a form submission in the widget, an ad click, a calendar booking, a download or a call. Off, they include every contact, such as CRM-synced or imported ones. Visitor metrics (traffic sources, keywords, page views) and the AI analyst text are not affected.
Leaderboard across the DynaMeet platform
Traffic, Sales and Support Insights each rank a few rate-based metrics against the other teams on DynaMeet: the funnel rates in Traffic; contact-to-meeting rate, meeting-to-won rate, speed to lead, speed to meeting and cycle time in Sales; deflection rate and CSAT in Support. Only rates are compared and your raw data is never shared with other teams. Each metric shows your percentile and a tier (Elite, top 10%; Top 20%; Top 40%; Mid; Low), flags growth opportunities, and comes with an AI Key insight and Recommendation. Until enough teams have data, the leaderboard shows your own rates only; meeting-to-won needs deal outcomes from HubSpot or Salesforce.
Shared definitions
These words mean the same thing on every page.
Exports
- Traffic Insights: a PDF of the window as a multi-week overview, optionally with every weekly slide deck appended; for a one-week window, that week's deck.
- Sales Insights: a Pipeline Insights PDF with the inbound and outbound sections.
- Chat conversations: a CSV of every conversation in the window, or all conversations since the workspace was created, one row per message with the surface it happened on. The export is capped at the most recent 50,000 rows and may contain personal data.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| This week's numbers are missing | Week-based pages show completed ISO weeks only | Wait for Monday, or use the Visitors and Contacts tabs for live counts. |
| A window cannot be made longer | The maximum is 16 weeks, and the start cannot precede the workspace's creation | Export two windows, or use the quarter view in Sales Insights. |
| A drill-down lists fewer people than the count | Unique people across the window, or an event count, or sessions that have since merged | Expected; the note in the drawer says which. |
| Contact numbers dropped after flipping a toggle | Meeton assists only is on | Turn it off to include imported and CRM-synced contacts. |
| Leaderboard says Not enough data | Too few participating teams, or too little of your own data for a rate | Nothing to do; your own rate still shows. |
Frequently asked questions
Do the Insights pages agree with Google Analytics?
Close, not exactly. Visitors are recognised by the widget's cookie per browser, kept up to a year, so a new device or cleared cookies starts someone over; Safari's storage limits shorten it further. Definitions such as first-time versus returning follow GA4's, and the report says where they differ.
Can I share a report with someone without a login?
Export the PDF. Every PDF footer points back to the interactive report at app.dynameet.ai for those who do have access.
Why is a count not updated after I disqualified a contact?
Module funnel counts are recorded as events happen and are not revised when a lead or meeting is later disqualified. The Contacts tab and the contact-based KPIs do exclude them.