Answers your customers can trust, inside your product.
Embed a dashboard, a chart or the question box itself. Every customer sees only their own data, decided by who they signed in as.
Net revenue by region
Quarter to date
The analytics tab you keep postponing.
Your customers keep asking for charts they can question. Embedding that is a smaller job than building it.
Embed a view
Drop a dashboard, a single chart or the full question box into your application, with a signed token that says which customer and which person is looking.
Styled as yours
Theme, type and density follow your product rather than ours, so the view reads as a feature you shipped and not a window into someone else's tool.
Your customers ask
The people using your product ask their own follow-up questions instead of filing a request with you for another variation of the same report.
No second data stack
The embedded view runs against the source you already connected, under the same read-only access and the same definitions your own team uses.
Revenue analytics
Saved results. Every tile shows what it got when it last ran.
Net revenue
Monthly, trailing 12 months
Orders
12,847
+11.2%vs the prior 90 days
Average order value
$333.30
+4.0%vs the prior 90 days
Revenue by channel
Quarter to date
- Organic search37.0%
- Paid social24.0%
- Email19.0%
- Referral12.1%
- Direct7.9%
Revenue by region
Quarter to date
Why it is safe to show customers
Who is asking decides what they see.
An embedded agent talks to people who are not your employees. What they can see comes from the sign-in, never from what they type.
Scoped by the sign-in
The embed token carries the customer and the person. What they are allowed to see is decided from that, so nothing typed into chat can widen it.
Read only, end to end
Embedded questions can only read. Nothing a customer does can change or delete their data, and every question runs under a time limit.
It refuses in public
A number your customer reads cannot be a near-enough guess. When iDash cannot stand behind it, the view shows the reason instead of a plausible figure.
Every run recorded
Each embedded question is logged with the customer, the wording and where the number came from, so you can answer anyone who asks how a figure was reached.
The question
What was revenue by campaign last quarter?
Two ways to connect the data
- Through the last ad someone clicked
- Through where their visit came from
Both ways are valid and they give different numbers. Rather than pick one and hand you a total that looks fine, iDash stops and tells you.
How to get an answer
- Ask for one of them by name, for example revenue by last touch campaign.
- Or decide once which of the two should be the default, and it stops asking.
Beyond a reporting tab.
The same governed foundation serves your product, your support team and your customers, without a second copy of the logic.
Per customer, same definitions
Your customers see the definitions your own team uses, so a support conversation and a customer dashboard cannot disagree about the number.
Query it from your code
The same governed questions can be asked from your own backend, so a number you can trust renders anywhere in your product, not only in an iframe.
Digests under your brand
Send your customers a scheduled summary from inside your product, with the chart and the number, on the cadence each of them chooses.
Show your customers the working.
Connect a source, build the view your customers keep asking for, and embed it under your own brand.