A messy tracking plan is one where the same action is logged three different ways. This tool generates analytics event names in a consistent object-action convention and your chosen case style, so your events sort cleanly, read unambiguously, and stay maintainable as the plan grows.
How it works
Each event pairs an object (the thing acted upon, such as button, page, order, form) with a past-tense action (clicked, viewed, completed, submitted). The generator filters actions to those that make sense for the chosen object, so it produces order_completed rather than order_scrolled. You can choose object-action or action-object word order, and snake_case, camelCase, or Title Case. Each batch is de-duplicated.
Tips and example
Sample output in snake_case with object-action order:
checkout_started
payment_completed
signup_submitted
video_played
- Pick one convention and enforce it. Mixing
Button Clickedandbutton_clickedfor the same action fragments your data and breaks funnels. - Keep the object and action vocabulary small and shared. Reuse
viewedeverywhere instead of inventingseen,opened, andloadedfor the same idea. - Names answer what happened; properties answer the details. Put the button label or page path in event properties, not in the event name itself.