Workflows

Zolvio is designed as a closed loop: detect → prove → fix → measure. This page shows the highest-leverage workflows that combine audits, issues, recordings, heatmaps, A/B tests, and surveys.

Workflow 1: Fix the #1 conversion blocker

  1. Run an audit to detect issues and prioritize by severity.
    Fix next list on the dashboard
    After an audit, Fix next on the dashboard lists the issues to work on first.
  2. Open the top issue in Issues and review the evidence (affected pages, screenshots, and any available metrics).
    What's the problem card with an evidence screenshot
    An issue's evidence: what the audit found, with the problem outlined on a screenshot of the page.
  3. Use View heatmap and View recordings on the issue to confirm the real shopper friction behind it.
    Affected pages card with View heatmap, View recordings and Test this change
    Affected pages, with View heatmap, View recordings and Test this change.
  4. Follow the guided fix. Open <file> takes you to the exact file in your live theme’s code editor; duplicate your theme first if you want a restore point. Not sure the change will help? Click Test this change to A/B test it on that page first.
    A guided fix code step with Open templates/product.json
    A code step: the file, the exact line to find, the code to put in its place, and a button that opens the file in your theme's code editor.
  5. Click Verify fix. The next audit confirms the fix and updates your score.
    Verify fix results listing the theme files checked
    Verify fix reads your live theme's files. Here the change hasn't been pasted yet, so it lists the files it checked.
    Audits list with scores and the change per audit
    The Audits page: each audit's score and how it changed since the one before.

Guided fixes

Zolvio never edits your theme. Treat Zolvio as the “what to fix” and “how to fix it” layer — you make the change.

Workflow 2: Heatmap → Watch examples → Decide

Heatmaps are best when you can jump from an insight to real examples. Use heatmaps to spot patterns and recordings to validate the “why”.

  1. Open a heatmap for your highest-traffic page.
  2. Review Top clicked elements (switch the map to Rage clicks or Dead clicks to see where shoppers got stuck), Scroll depth and, once the page has enough data, the Insights card (dead zones, scroll drop-offs).
    Rage clicks layer on a sold-out board's page with the Join the waitlist button selected
    The Rage clicks layer on a sold-out board's page: Join the waitlist is the most-clicked element, with 36 rage clicks. Selecting it outlines it on the map and shows Watch rage clicks.
  3. Select an element and click Watch recordings, or use Watch examples on an insight, to open recordings of the shoppers behind that behavior.
    Recordings of the visitors who rage-clicked the Join the waitlist button
    Watch rage clicks opens the recordings of the visitors who rage-clicked that button on this page.
    The first recording at its rage click on Join the waitlist
    The first recording, at its rage click on Join the waitlist: each click was followed by a script error.
  4. Make the change (layout, CTA clarity, trust signals), or A/B test it first, then keep watching the page.

Workflow 3: A/B test with trust checks

Zolvio’s A/B testing focuses on trust: SRM checks, delivery health, deduping, and QA preview so you don’t ship broken experiments.

  1. Create a test with the visual editor and clear goal definition.
  2. Use Preview ▾ on the test page to confirm each variant applies correctly (see QA & Troubleshooting).
    Preview menu on a test page
    Preview on the test page opens each version on your storefront; preview visits aren't counted.
  3. Read the Checks list (variants showing correctly, enough visitors, no overlap) before trusting results, and follow the What to do next card at the top of the test page.
    What to do next card on a test page
    What to do next: one recommendation with the button that carries it out. Here some visitors aren't getting the change.
    Running for, progress and Checks
    The Checks list says why this result can't be trusted yet: the variant isn't applying reliably and another test overlaps this page.
  4. Use heatmaps + recordings by variant to explain why a variant won (or why it didn’t).

Workflow 4: Surveys → Themes → Fix

Use micro-surveys to capture the “why” behind drop-offs. Cluster open-text answers into themes, then validate those themes with recordings.

  1. Launch a survey on a targeted page.
  2. Click Find themes to group open-text answers into themes (paid plans).
    Themes card grouping open-text survey answers
    Themes groups open-text answers, each with its sentiment, how many shoppers said it and example quotes.
  3. For negative themes, jump to recordings for sessions linked to those responses.
    Recordings filtered to the shoppers behind a survey theme
    Watch related sessions opens the recordings of the shoppers who gave those answers.
  4. Fix what shoppers keep mentioning, then check whether the theme shows up less often.
    Issues on the pages shoppers answered from
    The survey page lists the audit issues on the pages the answers came from, each linking to its issue.