How to Automatically Name and Label Autocaptured Events with Minimal Manual Effort

·May 04, 2026 01:45 PM·

We have chosen "autocapture" method for capturing events.. Is there a simple way to name/ label the events with less manual effort without touching the code and from the generated events.. I know there is an option of custom event, which involves lot of manual effort to tag event name. is there still a better way to do it?

1 comment

· Sorted by Oldest

kapa.ai
APP
·
(edited)·
Great question! Since you're using Autocapture, here are the options available to you for labeling/naming events with minimal manual effort:
What Autocapture Gives You Out of the Box
Autocapture automatically collects events with preset labels like [Auto] Page View, [Auto] Element Click, etc. These are standardized and require no manual effort. [Autocapture docs]
Naming/Labeling Options Without Touching Code
1. Custom Events (Virtual Events in the UI)
You can create Custom Events directly in Mixpanel's interface by combining or filtering existing Autocapture events and giving them a meaningful name — no code changes needed. For example, you could take [Auto] Element Click filtered to a specific button and name it "Sign Up Button Clicked". [Custom Events] This is done through the query builder in reports (Insights, Funnels, etc.) and doesn't require touching your implementation.
2. Lexicon — Display Name Renaming
In Lexicon (Mixpanel's data dictionary), you can change the display name of events for the UI without altering the underlying raw data. This makes events more human-readable for your team. [Lexicon merging]
⚠️ Important caveat: Autocapture events cannot be merged in Lexicon. The merge feature is only available for precision-tracked events. However, you can still use Lexicon to add descriptions and metadata to Autocapture events.

3. Merging Events in Lexicon (for non-Autocapture events)
If you later add some precision-tracked events alongside Autocapture, you can merge inconsistently named events (e.g., "Purchase" and "purchase item") into a single unified event via Lexicon — again, no code changes needed. [Lexicon merging]
Honest Assessment
The most practical no-code path for renaming/labeling Autocapture events is Custom Events in the UI. While you mentioned it feels like a lot of manual effort, it's worth noting that Mixpanel designed Autocapture specifically so you can:
"add semantic meaning only when it's useful—like creating a custom 'Sign Up' event—only when you know it will be reused." [Autocapture blog]
This means you don't need to label everything upfront — only define custom event names for the interactions that prove to be high-value over time, keeping the effort proportional to actual need.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
(edited)·
Great question! Since you're using Autocapture, here are the options available to you for labeling/naming events with minimal manual effort:
What Autocapture Gives You Out of the Box
Autocapture automatically collects events with preset labels like [Auto] Page View, [Auto] Element Click, etc. These are standardized and require no manual effort. [Autocapture docs]
Naming/Labeling Options Without Touching Code
1. Custom Events (Virtual Events in the UI)
You can create Custom Events directly in Mixpanel's interface by combining or filtering existing Autocapture events and giving them a meaningful name — no code changes needed. For example, you could take [Auto] Element Click filtered to a specific button and name it "Sign Up Button Clicked". [Custom Events] This is done through the query builder in reports (Insights, Funnels, etc.) and doesn't require touching your implementation.
2. Lexicon — Display Name Renaming
In Lexicon (Mixpanel's data dictionary), you can change the display name of events for the UI without altering the underlying raw data. This makes events more human-readable for your team. [Lexicon merging]
⚠️ Important caveat: Autocapture events cannot be merged in Lexicon. The merge feature is only available for precision-tracked events. However, you can still use Lexicon to add descriptions and metadata to Autocapture events.

3. Merging Events in Lexicon (for non-Autocapture events)
If you later add some precision-tracked events alongside Autocapture, you can merge inconsistently named events (e.g., "Purchase" and "purchase item") into a single unified event via Lexicon — again, no code changes needed. [Lexicon merging]
Honest Assessment
The most practical no-code path for renaming/labeling Autocapture events is Custom Events in the UI. While you mentioned it feels like a lot of manual effort, it's worth noting that Mixpanel designed Autocapture specifically so you can:
"add semantic meaning only when it's useful—like creating a custom 'Sign Up' event—only when you know it will be reused." [Autocapture blog]
This means you don't need to label everything upfront — only define custom event names for the interactions that prove to be high-value over time, keeping the effort proportional to actual need.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

1 comment

1 comment

What Autocapture Gives You Out of the Box

Naming/Labeling Options Without Touching Code

1. Custom Events (Virtual Events in the UI)

2. Lexicon — Display Name Renaming

3. Merging Events in Lexicon (for non-Autocapture events)

Honest Assessment

What Autocapture Gives You Out of the Box

Naming/Labeling Options Without Touching Code

1. Custom Events (Virtual Events in the UI)

2. Lexicon — Display Name Renaming

3. Merging Events in Lexicon (for non-Autocapture events)

Honest Assessment