• contact@insightclickiq.com
  • Every click, every session, explained by AI
Request a demo
Executive reports

Dashboards are for working. Reports are for sending.

A report is a document: sections of panels over one date range, opened by an executive summary that the AI writes from the real numbers on the page.

AI insights & AskAgentsJourneysHeatmaps & zonesFormsReplaySegmentsReportsMCPMobileExperimentsSurveysComments & sharingAI agent analyticsData platform
The document

An executive summary that cites the page

Summary panels are written after every other panel has run, from their actual results; they compare the period with the previous one and name what moved. Below them: KPI rows, charts, ranked horizontal bars, tables, text you write, and maps by country, US state or city.

On the Insurance 360 demo, the 7-day executive usage report opens with 106 active users, up 2.9%, 93.4% of them returning; the most active manager’s team; the Client Dashboard as the most-used module; and the most-viewed client and broker.

clickiq.example.com/reports · Insurance 360
Insurance 360 executive usage report (last 7 days, 2026-10-19 → 2026-10-26) with a ‘Written by AI’ executive summary, four tagged callouts (Win, Anomaly, Up, Tip) and the first Users panels: a Top users bar chart and a Daily active users line chart.
The summary starts with ‘106 active users, up +2.9% on the prior period, with 93.4% returning’. The callouts flag ‘Weekend activity collapses’ (6 users against a weekday peak of 61). Download PDF and Print are in the toolbar.
Print and PDF

A4 that does not cut a chart in half

The print view drops the console around the report and lays it out for A4: panels never split across a page, a section that holds a map starts on a new page. The PDF is printed on the server by headless Chromium once every panel has painted; if Chromium is unavailable the browser’s own print-to-PDF takes over. Snapshots keep what was sent, with the PDF in your object store.

Print view · A4
Print view of the Insurance 360 executive usage report on a white page with an INSIGHTCLICKIQ header rule, period and comparison dates, the AI executive summary with four callouts, and the start of the Users section.
The same report rendered as a clean A4-style page, with no console around it. This is the page that becomes the PDF.
Build one

From a template, a sentence, or by hand

Four templates (executive usage, weekly product, acquisition, UX quality), “describe the report you need”, or a blank page. Add a panel by describing it: “top brokers viewed, horizontal bar”.

clickiq.example.com/reports
Reports list for Northwind Outfitters with two cards: ‘Executive usage report’ (Template, 9 panels, last 7 days) and ‘Checkout Health & Traffic Sources — We…’ (AI, 14 panels).
Reports come from a template or from a one-line prompt; the AI-built report here has 14 panels.
How it works

How a report renders: panels first, then the narrative that reads them

How a report renders: panels first, then the narrative that reads them 1Sections andpanelsQuerySpecs for KPIs,charts, bars, tablesand maps; text youwrite.2Run every panelOne date range andthe previous period,cached ten minutesper report and range.3AIWrite the summaryThe model sees everyother panel's resultand may only citethose numbers.4PrintA4 layout; the pagesignals ready onlyafter every panel andmap has painted.5Send and keepServer PDF, Share,and snapshots storedwith the PDF.No model: the summary panel is composed by rules from the same results.How a report renders: panels first, then the narrative that reads them 1Sections and panelsQuerySpecs for KPIs, charts, bars,tables and maps; text you write.2Run every panelOne date range and the previousperiod, cached ten minutes perreport and range.3AIWrite the summaryThe model sees every other panel'sresult and may only cite thosenumbers.4PrintA4 layout; the page signals readyonly after every panel and map haspainted.5Send and keepServer PDF, Share, and snapshotsstored with the PDF.No model: the summary panel iscomposed by rules from the sameresults.
Person traits from identify (manager, team, division, branch, role) are properties in every panel: user.manager works anywhere a property does.
What you can ask

Questions this answers

Type them into Ask, give them to an agent as a goal, or send them through MCP from your own assistant.

Build an executive usage report for the last 7 daysThe template, rendered with a summary
Add a panel: top brokers viewed, horizontal barOne panel from a sentence
Which team used the platform most?A breakdown by user.team
Where are our users?A map by country, state or city
Send last week's report as PDFThe server PDF, kept as a snapshot
Weekly product report for the checkout projectA template over your events
Outcomes

What teams do with it

The usage report leadership asks for

Who uses the platform, which modules, which clients, where, with the summary written.

No screenshot pasting

The PDF is the report, printed on the server with every chart intact.

A record of what was sent

Snapshots keep the range and the PDF for every send.

Where it stops. A report's summary is only as rich as its panels: it cites what the other panels computed, nothing else. Maps show matched geographies and list values that match none.
Insurance client-360 Docs: Reports Segments

See the executive report on your events

Instrument the events the template expects and the report renders with no further setup.

Request a demo