FAQs

​

Why do my Piano Analytics numbers differ from the Piano Analytics (AT Internet) UI?

Small differences between an Adriel widget and the native Piano Analytics reporting interface are expected. Adriel reads from the Piano Analytics Data API and reflects the platform’s current processing state at the moment a dashboard loads, so a figure can shift as Piano Analytics finishes processing recent traffic. Most gaps trace back to how the two views are scoped rather than to a data error. Common causes:

• Date range or time zone — the widget’s date range and the account’s reporting time zone must match the native report for totals to line up. See Time zones and data freshness.
• Breakdowns and filters — a breakdown or filter applied in one view but not the other changes the totals.
• Metric definition — a metric that looks similar by name may be defined differently in the native interface (for example, a per-visit average versus a raw total).

For how often figures update, see the Piano Analytics data reference.

​

Why does a large query return a “too much data” error?

Piano Analytics accepts at most 50 columns in a single query, where columns are the combined count of breakdowns plus metrics. A widget that requests more than that limit returns a “too much data” error instead of loading. To resolve it, the query needs to be narrower:

• Reduce the number of metrics on the widget.
• Remove breakdowns that are not needed for the view.
• Split a very wide report across two widgets.

Separately, a single query returns results in pages of up to 10,000 rows, and the platform caps a query at 200,000 rows total. Very broad reports should be narrowed by a shorter date range or fewer breakdowns so the requested data stays within these limits.

​

Why did a widget hit a rate-limit error?

Piano Analytics limits how many queries can run at the same time — 20 concurrent calls per organization and 5 per user. When many widgets or dashboards load at once, or several people open Piano Analytics dashboards simultaneously, the platform can reject the extra calls with a rate-limit error. There is no automatic retry for these responses, so the fix is to reload the dashboard after a moment or stagger heavy dashboard loads rather than opening many at once.

​

Can I report on custom indicators defined in my Piano Analytics workspace?

The connector exposes a fixed catalog of metrics and breakdown properties, listed in the Piano Analytics data reference. Any metric or breakdown in that catalog is available on a widget without extra setup. Custom indicators created inside a Piano Analytics workspace are not part of that catalog, so they cannot be selected as additional fields in Adriel. Reporting is built from the standard catalog fields instead.

​

Why did Piano Analytics data stop loading when the connection still shows connected?

Piano Analytics credentials are verified when the data source is first created or updated, not on every load. If an access key or its permissions change later on the Piano Analytics side, the data source can still appear connected while queries begin to fail. When that happens, reconnecting the data source with a current key restores loading. See How to connect Piano Analytics to Adriel. If data still does not load after reconnecting, email support@adriel.com with the affected dashboard URL and the tracked Site.

​

Related