Limitations of Mixpanel's Free Tier: Users and Tracked Events

Hi Filip O., 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> 👋

According to the knowledge sources provided, Mixpanel's free tier has the following limits:- Up to 100,000 Monthly Tracked Users (MTUs) Our Free Plan just got better - Up to 20 million events per month Plans that grow with you Part 1It's worth noting that this represents a significant increase from previous limits. Mixpanel increased the data limits of their free plan by 100x, going from 1,000 MTUs to 100,000 MTUs Our Free Plan just got better. This generous free tier is designed to allow startups and other users to grow significantly before needing to upgrade to a paid plan.

ℹ️ 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! 📚

I apologize for the confusion in my previous response. You are correct to point out this discrepancy, and I appreciate you bringing it to my attention. Let me provide you with the most up-to-date information based on the official Mixpanel website.According to the Mixpanel pricing page, the current Free plan offers:- Up to 100,000 Monthly Tracked Users (MTUs) - Up to 1 million monthly eventsYou are right that the website mentions 1 million events, not 20 million as I incorrectly stated earlier. I apologize for this error. The information I provided earlier was likely outdated, and the current offering has been adjusted.Thank you for catching this discrepancy. It's important to always refer to the official website for the most current information on pricing and plan details, as these can change over time.

ℹ️ 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! 📚

To answer your question about calling identify twice with different IDs and merging profiles, I need to clarify which version of Mixpanel's ID management system you're using, as the behavior differs between versions.For projects using the Simplified ID Merge API:Calling identify twice with different IDs will not automatically merge the profiles. Instead, you need to include both the $device_id (old ID) and $user_id (new ID) in the same event to trigger a merge. Here's how it works:1. When you include both $device_id and $user_id in the same event for the first time, Mixpanel will create a mapping to merge these IDs together, forming an identity cluster Identifying Users (Simplified).2. You don't need to call identify twice. Instead, you should include both IDs in an event like this::LBKSLBKS```LBKS{ "event":: "Some Event", "properties": { "user_id": "new_id" } }LBKSLBKSThis will trigger the merge of "old_id" and "new_id" [Understanding Simplified ID Merge](https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#understanding-simplified-id-merge).LBKSFor projects using the Original ID Merge API:LBKSYou would need to use the `$identify` event to merge the old and new IDs. Here's how:LBKS1. Send an `$identify` event with the old ID as `$anon_id` and the new ID as `$identified_id` [Identifying Users (Original)](https://docs.mixpanel.com/docs/tracking-methods/id-management/identifying-users-original#identify).LBKSLBKS{ "event": "identified_id": "new_id", "$anon_id": "old_id", "token": "YOUR_PROJECT_TOKEN" } }```This will merge the two IDs into one identity cluster.To determine which version you're using and for more detailed information, please check your project settings.Remember, the exact behavior may depend on your specific implementation and the version of ID management you're using. Always refer to the most recent documentation for your specific setup.

ℹ️ 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! 📚

To implement the Simplified ID Merge strategy in Flutter for Mixpanel, you can use the Mixpanel Flutter SDK. Here's how you can do it:1. First, make sure you're using the latest version of the Mixpanel Flutter SDK that supports Simplified ID Merge. According to the documentation, you should use version 2.1.0 or higher Migrating to Simplified ID Merge.2. For the Simplified ID Merge strategy, you don't need to explicitly call an identify method twice. Instead, you'll include both $device_id and $user_id in your events when the user transitions from an anonymous to an identified state.Here's an example of how you might implement this in Flutter:LBKSimport 'package:mixpanel_flutter/mixpanel_flutter.dart';LBKS// Initialize Mixpanel final Mixpanel mixpanel = await Mixpanel.init("YOUR_PROJECT_TOKEN", optOutTrackingDefault: false);LBKS// When the user is anonymous, track events with just the $device_id mixpanel.track('View Anonymous Page');LBKS// When the user logs in or signs up, include both $device_id and $user_id mixpanel.track('Sign Up', properties: { '\$device_id': 'anonymous_device_id', '\$user_id': 'user_email@​[example.com](http://example.com)' });LBKS// After this, you can continue tracking events with just the $user_id mixpanel.track('Completed Profile', properties: { '\$user_id': 'user_email@​[example.com](http://example.com)' });LBKSIn this example:1. We initialize the Mixpanel instance. 2. For anonymous users, we track events normally. The SDK will automatically include the $device_id. 3. When the user signs up or logs in, we track an event that includes both $device_id and $user_id. This will trigger the identity merge in Mixpanel. 4. After this, we can continue tracking events with just the $user_id.Remember, you only need to include both $device_id and $user_id once to trigger the merge. After that, you can use either $device_id or $user_id in your events, but using $user_id is recommended for identified users Understanding Simplified ID Merge.Also, note that you don't need to manually generate or manage the $device_id. The Mixpanel SDK will handle this automatically for you.This approach should work for the Simplified ID Merge strategy in Flutter. Always refer to the most recent Mixpanel Flutter SDK documentation for any updates or changes to this process.

ℹ️ 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! 📚

Based on the previous conversation and the information provided in the knowledge sources, I can explain how to merge IDs using the Simplified ID Merge strategy in Flutter.With the Simplified ID Merge strategy, you don't need to explicitly call a separate method to merge IDs. The merging happens automatically when you include both $device_id and $user_id in the same event. Here's how you can do this:1. When a user transitions from an anonymous state to an identified state (e.g., when they log in or sign up), you should track an event that includes both $device_id and $user_id.2. This single event with both IDs is sufficient to trigger the identity merging in Mixpanel.Here's an example of how you can do this in Flutter:LBKS// When the user logs in or signs up, include both $device_id and $user_id in an event mixpanel.track('User Logged In', properties: { '\$device_id': 'anonymous_device_id', // This is typically managed by the SDK '\$user_id': 'user_email@​[example.com](http://example.com)' // This is the user's identified ID });LBKSThis event will trigger the merging of the anonymous $device_id with the identified $user_id Understanding Simplified ID Merge.After sending this event, Mixpanel will automatically merge the profiles associated with these two IDs. You don't need to do anything else to complete the merge.Remember: - You only need to include both $device_id and $user_id once to trigger the merge. - After this merge event, you can continue tracking events with just the $user_id for this identified user. - The Mixpanel Flutter SDK typically manages the $device_id automatically, so you usually don't need to provide it manually.This approach ensures that all previous anonymous events (associated with the $device_id) will be linked to the user's identified profile (associated with the $user_id) in Mixpanel.

ℹ️ 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! 📚

To get the $device_id in Mixpanel when using the Flutter SDK, you don't typically need to manually retrieve or manage it. The Mixpanel Flutter SDK automatically generates and manages the $device_id for you. However, if you need to access the $device_id for any reason, you can use the getDistinctId() method provided by the Mixpanel Flutter SDK.Here's how you can retrieve the $device_id:LBKSimport 'package:mixpanel_flutter/mixpanel_flutter.dart';LBKS// Assuming you've already initialized Mixpanel Mixpanel mixpanel = await Mixpanel.init("YOUR_PROJECT_TOKEN", optOutTrackingDefault: false);LBKS// Get the distinct ID (which is the $device_id for anonymous users) String distinctId = await mixpanel.getDistinctId(); print('Distinct ID: $distinctId');LBKSIt's important to note:1. For anonymous users, the distinctId returned by getDistinctId() will be the $device_id Identifying Users (Simplified).2. After a user is identified (i.e., after you've set a $user_id), getDistinctId() will return the $user_id instead of the $device_id.3. The $device_id is automatically included in all events sent by the SDK for anonymous users, so you don't need to manually add it to your events Identifying Users (Simplified).Remember, in the context of the Simplified ID Merge strategy, you typically don't need to manually handle the $device_id. The SDK takes care of including it in events for anonymous users, and when you identify a user, you only need to provide the $user_id. The merging of anonymous and identified data happens automatically when both IDs are present in an event, as explained in the previous response.If you find yourself needing to manually manage the $device_id, it might be worth reviewing your implementation to ensure you're following the recommended practices for the Simplified ID Merge strategy.

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