Best practices for naming events and tags

Events and tags are how you slice feedback later, so name them as if someone else will read your reports.

Event IDs

• Name the moment, not the page: checkout-success, not page-17

• Use lowercase with hyphens, and keep IDs stable over time

• One event per question you want answered

Tags

• Use tags for context that cuts across events: new-user, mobile, experiment-b

• Keep a short shared list so the whole team uses the same words

• Filter by tag with the tag parameter of the listFeedbacks API

Avoid

• Personal data in event IDs or tags

• Near-duplicates like onboarding and on-boarding

• Creating a new event ID for every release