We have a dashboard with data, where you can filter and use different combinations of tags, filters etc, that build the dashboard with the comibnations of things you prefere as a users. To be able to analyse stuff like most use combinations, similarities between dashboards etc - any advice on how to setup the tracking for this and what type of event to use?
If to use this with Claude, is this still the best way to structure?
Yes, this remains the best way to structure your data when working with Claude or other LLMs via tools like the Mixpanel MCP (Model Context Protocol) Server [When to use Mixpanel Agent, MCP server, and Headless]. Here is why this structure works well with Claude, along with best practices for querying it:
Why this structure works well with Claude
Clear, standard event and property naming: LLMs rely heavily on semantic clarity. Sticking to standard (Object) (Verb) event names (like dashboard_viewed) and clean property names allows Claude to accurately identify what events and properties mean without confusion [Events: Capture behaviors and actions; Mixpanel MCP: Get fast answers to product questions where you work].
Properties over dynamic events: Keeping the event unified and putting the tags/combinations inside properties prevents schema explosion [Events: Capture behaviors and actions]. This keeps your event catalog clean so the AI can quickly retrieve and navigate your schema [Mixpanel MCP: Get fast answers to product questions where you work].
Combination strings/lists make synthesis easier: Claude can easily inspect lists of tags, aggregate JSON-like filter structures, or parse combination strings to cluster similar dashboards and highlight recurring usage patterns [Model Context Protocol: How to use LLMs to query your analytics data].
Best Practices When Prompting Claude
When connecting Claude to your Mixpanel data via MCP, follow these recommended practices:
Lay the groundwork first: Ask Claude to inspect available events and properties before running complex aggregation queries (e.g., "Produce a list of all available events and properties for project X") [Mixpanel MCP: Get fast answers to product questions where you work].
Be exact with timeframes: Always provide concrete calendar dates rather than relative phrases (e.g., "Today is March 24, 2026. Pull the most common filter combinations from the last 30 days") [Mixpanel MCP: Get fast answers to product questions where you work].
Request specific metrics and visualizations: Ask Claude for specific metrics (e.g., total count of dashboard views, unique users) or request visual charts/tables to compare similarity between dashboards [Model Context Protocol: How to use LLMs to query your analytics data].
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
any downside with using lists?
Yes, there are a few important considerations and limitations to keep in mind when using list properties in Mixpanel:
Size and length limits:
For an event property, a list property has a size limit of 8 KB (or 256 KB if stored as a user profile property) [Supported Properties Data Type].
Individual items within the list are subject to their own data type limits (for instance, a list of strings is limited to 255 bytes per string) [Supported Properties Data Type].
For a List of Objects, there is a maximum of 255 keys, no nested objects are allowed, and the average recommended list size is about 50 objects [List of Objects].
Lists are unordered:
Mixpanel lists are not ordered—the position/index of an item in the array is not significant in reports [Supported Properties Data Type]. If the sequence or rank of an item matters, a list alone will not capture that order.
UI editing is not supported:
You cannot edit list properties directly within the Mixpanel UI. Any updates to list properties must be done via the Mixpanel API or SDKs [Supported Properties Data Type].
Cardinality limits and report truncation:
When you break down reports by a list property, Mixpanel evaluates each element as a separate segment [List Property Support]. If your lists contain many unique values across events, you may run into UI cardinality limits, which truncate report results to the top segments [Reports Overview].
Lookup table limitations:
While standard lists can be mapped to lookup tables, Mixpanel Lookup Tables do not support the List of Objects data type [Limits]. Additionally, keys inside an object/list of objects are not supported in Lexicon [List of Objects].
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
