Try it on your own data
Every report in this article is in the free plan. One snippet for web and apps, up to 10 sites.
Start freeTracking plans stall at the naming step, not the code. This guide sets out an event naming convention that holds up, the mistakes that quietly break one, and how TapCub’s event inbox turns autocaptured interactions into candidates you accept, merge or ignore under your own rules.
What you will learn
- A six-rule convention: object_action, past tense, snake_case, variants in properties
- The naming mistakes that split counts, with a fix for each
- How the inbox suggests names, and why a person still accepts each one
What changed · Nov 3, 2026
Rewritten as an event naming guide: six rules, a mistakes table and the inbox workflow as it works today (accept, merge, ignore).
Event naming conventions: where tracking plans stallThe convention we recommendMistakes that break a conventionHow the event inbox drafts namesAccept, merge or ignoreWhat autocapture never recordsKeep the vocabulary healthyFAQ
Event naming conventions: where tracking plans stall
New section
Event naming conventions sound like housekeeping until you try to build a funnel. Ask a team with a half-finished tracking plan where it stopped, and the answer is the spreadsheet: forty rows of proposed events, half of them named three different ways, waiting for a meeting. Autocapture removed the engineering dependency by recording interactions without code, but it moved the problem. The data is there, under labels like a button selector with “Start free” in it, and nobody wants to build a funnel on a CSS selector.
A convention fixes the meeting: when the rules are written down, naming an event is a lookup, not a debate. This guide gives the rules we recommend, the mistakes that break them, and how the TapCub event inbox drafts names from autocaptured interactions so you review them instead of inventing them.
The convention we recommend
New section
Pick one structure and keep it. Segment’s widely used guidance is the Object + Action framework (“Blog Post Read”), with the advice to “pick a convention and stick to it”, keep values out of event names and put them in properties instead (Segment docs). Segment writes event names in Title Case; TapCub requires snake_case for registered names, so the same idea becomes blog_post_read. The rules:
- object_action, in that order.
signup_completed,plan_selected,demo_requested. Sorting by name then groups everything about one object. - Past tense for the action. The event records something that happened:
completed, notcomplete. - snake_case, starting with a letter, at most 40 characters. These are TapCub’s rules for names in the event catalog, along with no
$,_ortc_prefix;$is reserved for app presets and a double underscore for autocapture. - Variants go in properties. One
plan_selectedevent with aplanproperty, notpro_plan_selectedandvip_plan_selected. - One name across platforms. The same action on web, app and mini program uses the same name, so cross-platform analysis can put them together.
- Never rename a live event. In TapCub the event name cannot change after it is created; the display label can. Decide the name once and fix wording in the label.
The calls below follow the convention:
// object_action, snake_case, past tense; variants in properties
tapcub.track('signup_completed', { method: 'email' });
tapcub.track('plan_selected', { plan: 'pro', billing: 'yearly' });
tapcub.track('demo_requested', { source_page: '/pricing' });
// not: 'Clicked Start Free Button', 'signup-v2', 'pro_plan_selected', 'tc_signup'Mistakes that break a convention
New section
Most broken vocabularies are not chaotic; they drift through a handful of repeat mistakes. The table lists the ones we see most and the fix for each.
| Name you will see | What goes wrong | Better |
|---|---|---|
| Clicked Start Free Button | Verb first, spaces, UI wording that changes with the copy | signup_started |
| signup / sign_up / SignUp | Three names for one action split every count | signup_completed, everywhere |
| pro_plan_selected | Variant in the name; a new plan means a new event | plan_selected + plan property |
| checkout_2026_q3 | Date or campaign in the name | checkout_started + campaign property |
| button_click | Too generic; every button is the same event | object_action per meaningful action |
| tc_signup / _signup | Reserved prefix; cannot be registered | signup_completed |
How the event inbox drafts names
New section
With autocapture on, the event inbox tidies the previous day’s interactions overnight; you can also click Generate candidates now. It clusters interactions by element and page, so the “Start free” button on five pages becomes one candidate, and suggests a name. A Rule or AI tag next to the suggested name says where the name came from; the counts beside it are real hits.
Each candidate shows hits and visitors over 7 days and when it was last seen. You can filter by high or low confidence or by “not seen in 3 days”, sort by hits, visitors or last seen, and expand a row for the 7-day trend, pages and neighbouring actions. The sample below is from the demo project.
Event inbox · Pending candidates
Sorted by hits, 7 dayssignup_startedRule · button “Start free” · 5 pages2,318Pendingplan_selectedAI · button “Choose Pro / VIP” · /pricing1,104Pendingdocs_search_usedAI · input “Search docs” · /docs/*1,940Pendingnewsletter_subscribedRule · form “newsletter” submitted · /blog286Accepteddemo_requestedRule · form “demo” submitted · /demo58Acceptedfooter_social_clickedRule · link · footer · 3 targets72Ignored
Accept, merge or ignore
New section
Every candidate gets one of three decisions, and nothing becomes an official event until a person makes it:
- Accept: enter a name that follows your convention, a label, a category and a description. This creates a match rule and backfills the last 90 days of autocapture, so a funnel built today has history.
- Merge: add the interaction to an existing event’s match rules, for example a second “Start free” button that should count as
signup_started. The increment is backfilled. - Ignore: the candidate moves to the Ignored tab and can still be accepted later.
The inbox suggests; your convention decides. Treat the suggested name as a draft and correct it against the rules above before you accept, because the name is permanent. Accepted events are ordinary events: they appear in funnels, segments, goals and monitors like events sent from code. Events you already send with track() are not renamed by any inbox rule. Generating, accepting, merging and ignoring need the Analyst role or above.
What autocapture never records
New section
Autocapture records clickable elements, not what people type. It never captures password fields, anything inside a data-tc-ignore subtree, or the chat window. Text capture is off by default and only takes effect at the highest collection tier. Form tracking stores the form’s id, name and action, not field values. If you need a value, such as an order total or a plan name, send it explicitly with track(), where you control exactly what leaves the page. The full list is in the docs on custom events and autocapture.
Keep the vocabulary healthy
New section
A convention decays unless someone checks it. Three habits keep it intact:
- Read the Unplanned list monthly. A
track()name that was never registered shows up as unplanned. Register it under the convention, or block it if it should not exist; skipping Accept does not stop storage, only Blocked does. - Hide instead of delete. Hiding removes a name from query pickers and can be undone; deleting removes the definition and its rules but not the stored events.
- Keep the tracking plan next to the inbox. If your plan lives in a spreadsheet, accept the candidates that match it under the names you already use, and treat the rest as interactions your plan did not know about. The autocapture glossary entry and the conversion funnel checklist show what the vocabulary is for.
FAQ
New section
What is a good event naming convention?
object_action in snake_case with a past-tense verb, for example signup_completed. Put variants such as plan or source in properties, use the same name on every platform and never rename a live event.
Should event names be snake_case or Title Case?
Either works if you enforce it everywhere. TapCub requires snake_case for names registered in the event catalog, so use snake_case there; property keys in snake_case as well.
Does the event inbox create events automatically?
No. It suggests candidates with names from a rule or a model. An event exists only after someone accepts a candidate or merges it into an existing event.
What happens to history when I accept a candidate?
Accepting creates a match rule and backfills the last 90 days of autocaptured interactions, so funnels and trends built on the new event have history from the start.
Can I rename an event later?
Not the event name; it is fixed once created. You can change the display label, or hide the old name and register a new one, keeping in mind that analyses on the old name do not move over.
Update history1
- Major updateRewritten as an event naming guide: six rules, a mistakes table and the inbox workflow as it works today (accept, merge, ignore).
- First published
Was this article helpful?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Technical Engineer
Focuses on tracking code, SDKs, and API integrations, with practical guidance on implementation checks and troubleshooting.



