Piano 3-way verification

When Piano Analytics is connected, VisualQ extends the Tracking pillar with a 3-way comparison:

Plan (expected)  ↔  Browser (dataLayer)  ↔  Piano (server hits)

This surfaces issues invisible to browser-only checks:

• Ad-blockers or ITP dropping client hits
• Wrong site_id on staging vs production
• Schema rejections in Piano's ingestion pipeline
• Variables present in the browser but never ingested server-side

Prerequisites

1. Tracking plan configured with linked scenarios
2. Piano integration saved under Settings → Integrations
3. Business plan or above

How it works

1. VisualQ runs the standard browser-side tracking audit
2. After completion, an async job queries Piano's Data API for matching hits
3. The report flags mismatches across all three layers

Setup Piano

Full setup steps: Piano Analytics integration.

Viewing results

Open the tracking run from Activity or the Tracking tab. Piano comparison rows appear when credentials are valid and hits exist in the queried time window.

MCP

Use tracking_get_plan to read the plan, then run tracking via CI or dashboard. Piano-specific drill-down is in the dashboard report today; MCP exposes structured plan and latest audit metadata.