> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Event tracking

> Name the interactions on a landing page — a button press, a directions tap, a form submit — so your analytics shows what people did after they scanned.

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](/page-builder/overview) — it belongs to the blocks on a landing page, so a [Quick Code](/qr-codes/create/quick-code-vs-page) 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**.

<Note>
  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.
</Note>

## 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."*

| Block           | What gets tracked  | Field                      |
| :-------------- | :----------------- | :------------------------- |
| **Button**      | The button press   | Button tracking            |
| **Map**         | The directions tap | Directions button tracking |
| **Custom Form** | The form submit    | Submit button 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

<Warning>
  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.
</Warning>

## Related

* [Page Builder overview](/page-builder/overview) — building the page the blocks sit on
* [Blocks reference](/page-builder/blocks-reference) — every block type and what it does
* [Analytics dashboard](/analytics/dashboard) — scan-level analytics, which event tracking sits alongside
* [Conversion Tracking](/conversion-tracking/introduction) — measuring what happens on **your own** website after a scan, which is a different product area