Add an Analytics event name on supported components (e.g. Button, SmartLink). Analytics → Events lists configured events and how often they fired. Use Configured to audit setup and Activity to see raw trigger counts.
What events measure
Page analytics counts views automatically. Events count intentional actions — CTA clicks, outbound links, signup attempts — that you label yourself.Each event has a name you choose (e.g. cta_click, pricing_view).
Configuring events in the editor
On components that support tracking, set Analytics event in the customize panel:
Open a page in Visual mode.
Select a Button or SmartLink (and other components with the field when available).
Enter an event name in Analytics event — use lowercase with underscores for consistency.
Save — the MDX stores a trackEvent attribute.
When a visitor clicks the element on the published site, Aveiro sends a custom event.Example MDX shape:
Events dashboard
Go to Analytics → Events. Two tabs:
Configured
Lists every trackEvent found in your site MDX — scanned across org sites (respecting the site filter):
Column
Meaning
Event
Event name you configured
Element
Component type (Button, SmartLink, etc.)
Page
Page where the component lives
Triggers
Count in the selected date range
Last seen
Most recent trigger timestamp
Use this tab to verify tracking is wired before a launch and to find orphaned event names.Awaiting / Linked indicators show whether activity exists in the period for each configured event.
<Button href="/signup" variant="primary" trackEvent="hero_signup">
Get started
</Button>
Activity
Lists event types that actually fired in the date range, aggregated by name — including events that might not appear in the configured scan (if added manually in MDX).
Shows total triggers and last seen per event name.
Filters
Site and date range filters match Overview. Configured-event discovery respects the site filter; activity counts use the same window.
Empty states
No events configured — no components with trackEvent in MDX for the filtered sites. Add analytics event names in the editor.
No event activity — events exist but nobody triggered them in the period. Test on the live site.
Naming conventions
Pattern
Example
verb_object
click_pricing, submit_newsletter
section_action
hero_cta, footer_contact
Stable over time
Keep names when redesigning so history compares
Avoid spaces and special characters — stick to letters, numbers, underscores.
Programmatic tracking
Published sites expose window.magic.track(eventName, eventData) for custom scripts. Elements with data-track-event also auto-track on click. Most users should prefer the editor Analytics event field instead.
