kapa.ai

You can’t apply arbitrary string functions directly inside standard report filter UI fields, but there are two supported ways to do “length/count”-style string logic based on the docs:

Create a Custom Property that computes what you need, then filter on that new property.For example, to get the length of a string property A: text len(A)LBKSlen returns the length of a string (or list), so this custom property becomes numeric and can be used in filters and breakdowns (e.g. len(A) > 10).[Custom property functions]Other useful string operations in custom properties: - left(A, 3) – first 3 characters - right(A, 3) – last 3 characters - mid(A, 1, 4) – substring from position 1, length 4 - split(A, "/", 2) – 2nd piece after splitting on /[Custom property functions]You then use this custom property in any report filter as you would a normal property.

If you are using the Query API (/segmentation, /funnels with where / on), you can write an expression (not just a simple equals filter) using the expression grammar. Supported operations include: - arithmetic: + - ** / % - comparisons: == != > > = < <= - logical: and or not - regex / in - typecasts: boolean() number() string() - floor, round, ceil<https://github.com/mixpanel/docs/blob/main/reference/Mixpanel%20APIs/segmentation-expressions.md|[Segmentation expressions>]However, in the segmentation-expression grammar there is no len() or substring function documented, so you cannot directly compute string length there; you would still need to precompute length (e.g., as a property or via custom properties in the UI) and then reference that numeric property in the where clause.---So to “apply string operations like length count on property filters” in the UI: define a *Custom Property using len, left, right, mid, or split, then filter on that derived property. There is no direct len() in plain filter fields or in segmentation-expression grammar per the provided docs.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Hi Tobias, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

Yes. To see retention by Week 0, Week 1, Week 2, … for users who joined on launch day: 1. In Retention, set your A event to the “join”/“signup” event and restrict the date range so that only launch day users are included (e.g. fixed date = launch day). [Basic features] 2. In the time unit toggle, select Week instead of Day/Month.With Week selected, each bucket (Week 0, Week 1, Week 2, etc.) represents retention in weekly intervals since that A event, which is what you’re looking for. [Retention overview; Retention criteria]

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

Here are some of the latest Mixpanel updates mentioned in the provided sources: - Session Replay enhancements: - General availability of Mixpanel Session Replay for all customers, including mobile (iOS & Android), with tight integration into funnels and other reports so you can jump from metrics to replays. [Session Replay available; Latest features] - New AI Summaries to auto-summarize sessions, Frustration Signals (rage/dead clicks as events), and Heatmap Comparison Mode for side‑by‑side variant/segment/device comparisons. [3 Session Replay updates]- Warehouse Connectors & Mirror mode: - Easier syncing from Snowflake, Redshift, Databricks, BigQuery into Mixpanel, plus Mirror mode to keep Mixpanel in sync with warehouse changes automatically. [Latest features] - Billing note: warehouse-ingested events are billed like any other events; “Updates” from Mirror syncs are counted as events in the month they occur. [Warehouse billing FAQ]- JSON Pipelines: - Incremental export system rolled out (EU/IN first, then US), and new JSON pipelines now have sync enabled by default—no manual toggle. [JSON pipelines changelog]- Marketing Analytics: - New capabilities for marketers: data tables view, multi-touch attribution (beta), identity resolution, custom buckets, ad-network data support, and Google Tag Manager integration, plus a Marketing KPIs template and public Marketing Analytics Board. [Marketing Analytics]- Onboarding & starter experience: - New guided tracking-plan builder and automatic Starter Board with key metrics (DAU, WAU, retention, geo, etc.), plus ready-made templates for deeper analysis. [Onboarding updates]- Saved Metrics & Behaviors: - You can now update definitions and either push changes globally, save as new, or clear changes. [Saved metrics updating]If you’re interested in updates for a specific area (e.g., Session Replay, marketing analytics, data pipelines), tell me which and I can narrow it down.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Please stand by A. G. as I search the knowledge base. I normally take about 15 seconds or so. 👋

The knowledge sources only describe what the First Time Ever filter does, not how to access it in the current UI, and they don’t mention it being removed or relocated. [Reports filters]Historically, you could add it as an inline filter on an event (e.g. in Insights/Funnels) via the event’s ... menu, choosing something like “First time ever” for that event, but I cannot confirm this still matches your current UI from the docs alone. [Reports filters]Because the documentation doesn’t state: - whether the First Time filter has been deprecated or renamed, or - the exact current click-path to apply it,I can’t give a definitive, up‑to‑date UI path. I recommend: 1. Checking the inline filter menu on an event in a report (click the ... next to the event name and look for options mentioning “First time”). [Reports filters] 2. If you still don’t see it, contacting Mixpanel Support or your CSM and referencing the “First Time Ever Filter” section of the docs so they can confirm whether it’s been removed, gated, or moved in your specific workspace.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Hi Khushi L., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

Since your events are less than 2 hours old and visible in Data → Events, ingestion is working; this is almost certainly a Lexicon visibility/UI issue, not a tracking issue.Run through these Mixpanel‑specific checks: 1. Check if the events are hidden in Lexicon - Go to Data Management → Lexicon → Events. - Use the search box with the exact event name (case‑sensitive). - Turn on “Show hidden events/properties” if you see that option. - If the event’s Status is “Hidden”, select it and click Unhide.[Hiding data]2. Check for Event Approval (Enterprise only) - If Event Approval is enabled, all new events arrive hidden by default until an admin approves them.[Event approval] - In Lexicon, look for an “Event Approval” / “View New Events” section. - If your event shows with a “New” tag and is hidden, have an Admin/Owner mark it Visible.[Event approval]3. Confirm it’s not an “inactive” name mismatch - In Lexicon search, type the event name exactly as it appears in Data → Events (including case and whitespace). [Check hidden] - If a slightly different name (extra space, different casing, etc.) exists, that’s a different event in Lexicon and will not show your new one.If you’ve confirmed: - the event is not hidden, - Event Approval is off (or it’s been approved), - you’re searching with the exact event name, and it still doesn’t appear in Lexicon after a few minutes, then the docs don’t describe another UI‑side reason for such a short delay. In that case, take a screenshot of: - Data → Events showing the event name and timestamp - Lexicon search results for that same name and contact Mixpanel Support so they can inspect your specific project state (this kind of Lexicon indexing lag is not documented in the sources above).

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.