Analytics & Tracking Events
Event naming conventions
Event naming conventions — documentation pending.
Complete
Every analytics event uses a strict `{module}_{noun}_{verb}` snake_case pattern. No camelCase, no dashes, no PascalCase. The naming discipline keeps GA4 / GTM dashboards readable and groupable by module prefix.
The 3-part formula
- module
- One of: home, editorial, showcase, opportunity, founder, file, calendar, event, coverage, docs, footer, header, auth, admin. Lowercase, single token.
- noun
- The thing acted on: card, button, link, form, field, modal, drawer, tab, filter, badge, signal, image. Single token.
- verb
- The action: view, click, open, close, submit, expand, collapse, change, focus, blur, copy, download, share, retry, dismiss, scroll, hover.
Examples
- `opportunity_card_click` — user clicked an opportunity card in a listing or related-signals block.
- `founder_file_download_click` — user clicked the Download CTA on a file card.
- `event_filter_change` — user toggled a sector/country/audience filter on the events listing.
- `docs_topic_view` — user viewed a documentation topic (auto-emitted by router).
- `header_lang_change` — user switched the language via the header dropdown.
