Ask Scout about Insights

Scout can read your project's Insights data. Ask it an analytics question the way you would ask an analyst, and it queries the data and answers from what it measured.

This matters most for the questions the dashboard has no widget for. The dashboard covers the metrics teams look at every day; Scout covers the specific one you need right now.

Scout has access to the full Insights surface:

  • Traffic, sessions, and page views
  • Conversions and goals
  • A/B test and personalization results
  • Signals, audiences, and intents
  • Enrichments
  • Device breakdowns
  • Traffic sources, referrers, and UTM campaigns
  • Visitor language and time zone

Any of these can be scoped to a specific piece of content: a composition, a project map page, a set of dynamic input values, or a literal URL pathname.

Scout works best with a question that names the metric, the period, and what it is about. Some examples:

  • "Sessions and bounce rate for the pricing page over the last 30 days, compared to the prior 30 days"
  • "How is the 'B' variation of the homepage hero A/B test performing against control?"
  • "Conversion rate for the 'Add to cart' goal, broken down by device type, this month"
  • "Compare traffic for the Home composition with locale en against locale da over the last 7 days"
  • "Which audience segments make up the most sessions on the blog this quarter?"
  • "Which traffic sources sent us sessions in the last 7 days that sent none the week before?"
  • "How do sessions from the fall_launch email campaign convert compared to organic search?"

Identify content as specifically as you can

Analytics data is filtered by ID, not by name. Asking about "the pricing page" works, but naming the composition Scout is already looking at (or one you can point it to) gets a more precise answer than a pathname alone, especially for dynamic compositions where many URLs resolve to one composition.

If you do not name a period, Scout answers over the date range currently selected on the Insights dashboard, defaulting to the last 7 days.

Scout returns the measured results and writes the answer from them, rather than handing you a table to interpret. When the shape of the answer warrants it, it renders a chart in the conversation alongside the numbers.

Scout never estimates analytics figures. If it cannot measure something, it says so instead of guessing.

Scout distinguishes between three reasons an analytics question comes back empty, and tells you which one applies:

  • Insights is not set up for this project. No tracking connection exists, so there is no data to read. See activate Insights.
  • You do not have permission. Insights is set up, but your role lacks the View insights permission.
  • Insights could not be reached. A transient problem. Retrying is worthwhile.

Asking Scout about Insights needs the same View insights permission as opening the dashboard, plus a project with a tracking connection and collected data.

Last modified
Next
How significance works