Set up your analytics plan
Define expected events and link them to VRT scenarios.
The analytics plan is the source of truth for what should fire on each page. VisualQ compares this plan against live browser output during audits.
Open the Analytics tab
Navigate to your project → Analytics. If you have no plan yet, VisualQ prompts you to create one.
Define events
Each event in the plan includes:
| Field | Description |
|---|---|
| Name | Event identifier (e.g. page_view, add_to_cart) |
| Trigger | When it should fire (page load, click, form submit, …) |
| Variables | Expected payload keys and optional validation rules |
| Pages | URLs or patterns where the event must appear |
You can import events from a CSV export, discover candidates with Audit discover (scans live pages), or add them manually.
Link scenarios
Pages (tc_vars variables)
On each VRT scenario, link pages from the plan. During a Full audit, Analytics compares page variables to hits captured during the VRT replay.
Events (eventVariables matrix)
On each event, link an FRT scenario (feature + scenario name). VisualQ replays the scenario once and automatically validates every linked event — no Gherkin analytics steps required. See Events via FRT scenarios.
During a Full audit, Analytics only runs when the scenario or event has linked coverage — otherwise it is skipped (other pillars still run).
Discover workflow
Discover crawls scenario URLs and suggests events based on observed dataLayer / tag manager activity. Review suggestions before promoting them into the plan.
Tips
- Start with high-value flows: homepage, product detail, checkout, signup
- One scenario per critical URL keeps audits fast and actionable
- Pair with Piano Analytics on Business+ for server-side confirmation