Can you suggest custom events and properties for https://www.fitsprompt.ai/? Here are my ideas: Custom Events: - Page Viewed Custom (backend event, to make sure it's tracked, the other events should also all be backend events to make sure everything is tracked) - Register properties: type (email/google), - Login - Button Clicked properties: name, - Subscription Started properties: amount,
Hi Moritz H., 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> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
Great start! Your list covers the core journey. Based on Mixpanel best practices, here’s a concise, scalable event schema (with suggested properties) and when to use Custom Events vs regular events: Guiding principles - Keep events as actions; use properties for context (e.g., single Page Viewed with page details). [Best practices] - Start with Sign Up and a Value Moment, then expand. [What to track] - Prefer server-side tracking for reliability; manually track page views server-side. [What to track; Server-side page views] - Use consistent naming (snake_case, Object Verb), avoid dynamic names, and define identity management. [Best practices; Tracking plan methodology]Recommended core events (server-side)1) page_viewed - Properties: - page_path (e.g., /, /pricing, /playground) - page_title - referrer - utm_source, utm_medium, utm_campaign, utm_term, utm_content - device, os, browser (if parsing UA server-side) - Notes: Track only on successful responses; keep it one event with properties. [Server-side page views; Best practices]2) sign_up - Properties: - method (email, google) - country - source (Referral, Organic, Paid) if known - This is one of the two “start here” events. [What to track; Events overview examples]3) login - Properties: - method (email, google) - success (boolean) if you emit attempts vs successes separately (recommended: only successful logins)4) button_clicked - Properties: - button_name (e.g., “try_now”, “generate”, “pricing_cta”) - page_path - context (e.g., “hero”, “modal”, “navbar”) - Use only if you truly need granular CTA analytics; otherwise prefer feature-specific events. [Best practices]5) subscription_started - Properties: - plan_id or plan_name - billing_interval (monthly, annual) - amount - currency - trial (boolean) if applicable6) subscription_canceled - Properties: - plan_name - reason (if collected) - effective_date7) ai_prompt_sent (value-moment candidate for an AI product)
- Properties: - model (e.g., gpt-4o, llama3) - tokens_prompt (int) - prompt_length (chars) or category (e.g., “fitness_plan”, “meal_plan”) - context_source (e.g., “template”, “freeform”) - Rationale: captures user input action central to your product. [Adding your events (AI templates)]8) ai_response_sent - Properties: - tokens_completion (int) - api_cost (decimal) - response_time_ms - model - success (boolean) - Rationale: track cost/latency for efficiency and UX. [Adding your events (AI templates)]9) api_error - Properties: - error_code - error_message - model - stage (prompt, response, billing) - Helps diagnose reliability issues. [Adding your events (AI templates)]10) user_feedback_submitted - Properties: - sentiment (up, down, 1–5) - feedback_text - relates_to_event_id (if tying to a specific response) - Useful for quality loops. [Adding your events (AI templates)]Which should be Custom Events? - Use Custom Events to merge or filter existing events for analysis across Mixpanel (funnels, cohorts). [Custom events; Lexicon custom events] - Examples for Fitsprompt: - engaged_with_ai = ai_prompt_sent OR ai_response_sent (quick “engagement” metric). - successful_ai_response = ai_response_sent where success = true and response_time_ms < 3000. - paid_user_actions = any of {subscription_started, plan_upgraded} to analyze paid conversion in funnels.Data quality and governance tips - Identity: ensure distinct_id uses your backend user ID post-login/signup and link anonymous to identified correctly. <https://docs.mixpanel.com/guides/plan/tracking-strategy#tracking-plan-methodology|[Tracking plan methodology>] - Naming: snake_case, clear Object Verb; avoid dynamic names/values like per-date events. [Best practices] - Limit event/property sprawl: Mixpanel has soft limits (e.g., 5000 event names; 255 properties per event). [FAQ limits] - Server-side: favors completeness; parse UTMs/referrer at request time. [What to track; Server-side page views]Minimal “start here” set for immediate value
- sign_up (with method, source, country). [What to track] - ai_prompt_sent and/or ai_response_sent as your Value Moment. [Adding your events (AI templates)] - page_viewed (for acquisition/attribution context). [Best practices; Server-side page views] - subscription_started (to tie monetization to engagement). [What to track]If you’d like, I can turn this into a lightweight tracking plan (event names, properties, example values) you can share with your team.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
