The drop by chapter, quantified, with the comparison period.
Piano Analytics, read with everything else.
You chose Piano to measure properly. Kyras reads it in French, alongside your ad platforms and Search Console, and tells you every Monday what moved.
What Kyras reads in Piano.
Taken from the connector. Kyras reads your site's data model: the properties and events you have defined.
Metrics
- Visits and visitors
- Page views
- Bounce rate and average visit duration
- Events and conversions
- Any named event in your data model
Breakdowns
- Page and chapter
- Device type
- Country
- Source and source type
Piano answers. Kyras translates.
The day's figure, the gap from normal, and an alert if the gap is abnormal.
Sources ranked by conversions, and each one's share.
With your other sources.
Piano measures the site. Kyras sets it against what Google shows and what you spend.
From query to conversionSearch Console names pages by their URL, Piano often by their title. Kyras bridges the two, and says when the match is uncertain.
The real costYour Piano conversions next to your Google Ads and Meta Ads spend, without adding up what does not add up.
Two measurements, one decisionIf you have both, Kyras never compares Piano and GA4 figure for figure: their definitions of a visit differ.
Piano's AI, or Kyras?
Piano offers its own AI features in the tool, to explore your Piano data. Kyras does not replace them, it does something else.
Piano's AI
- WhereIn the Piano interface.
- SourcesPiano.
- CadenceWhen you open the tool.
- Who it's forThe teams that use Piano.
Kyras
- WhereIn Kyras, in your emails, in Claude.
- SourcesPiano with your ad platforms, Search Console, Shopify.
- CadenceDaily alerts, and a report every Monday.
- Who it's forLeadership, marketing, everyone who never opens Piano.
What you should know before connecting Piano.
What Kyras does not do with this source, or does with a caveat. You know it before you connect.
- Piano alerts currently watch visits and conversions, day by day, without a breakdown by device, channel or source, and without comparison with the previous year.
- Regular-expression filters are not supported.
- A Piano visit is not a GA4 session. Kyras does not add them up.
A read key, and that's all.
Kyras only calls the aggregated-data read and two metadata reads. It writes nothing to Piano.
An API key, checked before it is kept.
Create it in Piano, under Administration then API keys. Kyras checks it, then stores it encrypted. Labels that look like personal data are masked before any answer.
In Claude too.
Once Piano is connected, Claude can ask it the same questions through the Kyras MCP server, and receive figures that are already verified.
Frequently asked questions
What people ask us before connecting.
How do I connect Piano Analytics to Kyras?
Create an API key in Piano (Administration, then API keys), then enter it in Kyras with your site ID. Kyras checks the key before saving it.
Can Kyras change my Piano data?
No. Kyras reads aggregated data and your site's metadata. It writes nothing to Piano.
Can I query Piano Analytics from Claude?
Yes, through the Kyras MCP server, once Piano is connected. Claude.ai and Claude Code are tested; ChatGPT is being validated.
How is it different from Piano AI Reveal and the AI in Data Query?
Those are Piano's AI features, in the Piano interface, on your Piano data alone. Kyras reads Piano alongside your ad platforms and Search Console, and comes to you through the Monday report and alerts.
Does Kyras replace Piano?
No. Piano measures, Kyras reads. You keep Piano, its settings and its reports.
Ask Piano your first question.
Connect a source: Kyras shows you its figures and answers two of your questions before you pay.