Skip to main content
Scan analytics tell you that someone scanned a QR Code: when, where, on what device. They stop at the moment the page opens. Event tracking picks up from there, recording what the person actually did once they arrived. A page with two buttons — Book a demo and Download the brochure — gets the same scan count either way. Event tracking is what tells you which one people pressed.

​
Where it lives

Event tracking is part of Build a Page — it belongs to the blocks on a landing page, so a Quick Code has nothing to track. Select a block in the page builder and the panel on the right shows three tabs: Content, Design, and Event Tracking.
There is no switch to turn on. If your plan includes event tracking, the tab is there and filling in a label is all it takes — earlier versions of Scanova gated this behind a toggle, and that toggle is gone.

​
Which blocks support it

The tab appears on every block, but only blocks with something to press support it. Open Event Tracking on a block that doesn’t and it says so plainly: “This block does not support event tracking.” The pattern is the interactive element, not the block as a whole — on a Map block it’s the Get Directions button that’s counted, not the map itself.

​
Naming an event

Each supported block takes one label, described in the panel as “A label for this interaction in analytics”, with hero_cta_click offered as the example. That label is the only thing separating one interaction from another in your reports, so it’s worth a moment’s thought:
  • Name the thing and the place, not just the thing — pricing_cta_click beats button_1
  • Keep one convention across a campaign, so events group when you compare pages
  • Reuse the same label across pages when you want a combined figure, and vary it when you want them apart
The label is what creates the event, so a supported block left blank has nothing to report. Walk the interactive blocks before publishing rather than discovering the gap when you read the campaign’s numbers.