kapa.ai

The knowledge sources don't explicitly state whether a single Mixpanel Feature Flag can be connected to only one experiment report at a time. I can't confirm or deny this with certainty based on the available documentation.

The good news is that Mixpanel does allow you to change experiment settings mid-run, with some important caveats:

"Mixpanel analyzes your experiment on the fly, so you can adjust settings at any time if needed. If you notice a configuration mistake — like selecting Frequentist when you meant Sequential — feel free to correct it, even if the experiment has been running for weeks." [Changing Settings Mid-Experiment]

So for genuine configuration mistakes, you can fix them retroactively without the report being permanently "contaminated."

The key warning is around p-hacking — don't adjust settings because you don't like the current results:

"The one thing to avoid is changing settings because the current results aren't what you hoped for. If you adjust the confidence level, metrics, or duration in search of a significant result, you're more likely to find something that looks meaningful but is actually noise." [Changing Settings Mid-Experiment]

If you want to test a fundamentally different configuration rather than correct a mistake, the recommended approach is to restart the experiment:

"If you want to test a different configuration, restart the experiment instead. This resets the data and ensures your analysis starts fresh." [Changing Settings Mid-Experiment]

In summary: Genuine mistakes can be corrected on the fly. The report won't be permanently contaminated as long as you're fixing real errors rather than chasing favorable results. For deeper reconfigurations, restarting is the clean path forward.

Unfortunately, Mixpanel does not currently support selectively disabling individual geolocation properties. The three properties — City, Region, and Country — are always derived and set together. As the documentation states:

"There is currently no means to selectively disable one or two of the three geolocation properties."

[Default Properties] Your options are:

The manual approach (option 2) is likely your best path if you only want country-level data.

Yes, there are a few ways to prevent the $city property from being sent, depending on your setup:

Since $city is derived from IP-based geolocation, the most straightforward approach is to disable geolocation tracking. Note that this will also disable $region and mp_country_code (Country) — there is currently no way to disable only one or two of the three geolocation properties. [Default Properties] Here's how to do it per SDK: JavaScript

mixpanel.init("YOUR_TOKEN", { ip: false });

[JS SDK] iOS (Swift)

let options = MixpanelOptions(token: "YOUR_PROJECT_TOKEN", useIPAddressForGeoLocation: false)
Mixpanel.initialize(options: options)

[Swift SDK] Android

<meta-data android:name="com.mixpanel.android.MPConfig.UseIpAddressForGeolocation" android:value="false" />

[Android SDK] Node.js

const mp = Mixpanel.init('<YOUR_TOKEN>', { geolocate: false });

[Node.js SDK] PHP

$mp = Mixpanel::getInstance("YOUR_PROJECT_TOKEN", array(
    "events_endpoint" => "/track?ip=0"
));

[PHP SDK]

If you're using the JavaScript SDK and want to prevent $city from being sent as a default property, you can use the property_blacklist config:

mixpanel.init("YOUR_TOKEN", {
  property_blacklist: ['$city']
});

[Blacklisting Properties]

You can also block the $city property in Lexicon from the Mixpanel UI. This will prevent any new data for that property from being stored going forward (though previously ingested data will remain). Only project owners can do this. [Blocking Data]

Recommendation: If your goal is full privacy compliance, Option 1 (disabling geolocation at the SDK level) is the most thorough approach.

I'm sorry, but the knowledge sources do not contain enough information to explain why a project Owner would be blocked from editing a shared custom event in Lexicon, even when it is used in multiple reports. This does not appear to be expected behavior based on the documented permissions. I'd recommend reaching out to Mixpanel Support directly, as this is likely either a bug or an edge case that isn't covered in the available documentation. When contacting support, it would be helpful to mention:

I'm sorry, but the knowledge sources do not contain enough information to explain why a project Owner would be unable to edit a custom event they created. Based on the permissions table, project Owners should have full Create/Edit Custom Events permissions. [Project Roles] Since your role shouldn't be the issue, here are a few things worth checking:

For a definitive answer on why an Owner cannot edit their own custom event, I'd recommend reaching out to Mixpanel Support directly, as this may be a bug or an edge case not covered in the available documentation.

Based on the knowledge sources, editing custom events in Lexicon requires at least a Project Admin role. Here's the relevant permission breakdown:

The most likely reason you can't edit a custom event even as its creator is your project role. Specifically:

What you can do:

This is a perfect use case for Funnels combined with Formulas in Insights. Here are two approaches:

Build a funnel with your three events to visualize the conversion and drop-off:

[Funnels Overview]

Use Event Comparison at Step 2 to compare both outcomes side by side:

This will show you what percent of users who started the form ended up with a success vs. an error submission. [Comparison Events] docs.mixpanel.com/_next/image?w=3840&q=75

If you want a custom calculated percentage, use the Formula feature in Insights:

[Insights Formulas]

💡 Tip: You can save the Formula as a Saved Metric and add it to a Board so your team can monitor form success/error rates over time without rebuilding the report. [Saved Metrics]

Formulas allow you to make calculations using simple arithmetic operators across your metrics in the Insights report. Each metric in your report is assigned a letter (A, B, C...) which you can combine with operators to create more advanced queries. [Insights Formulas] Mixpanel supports the following operators:

Example use cases:

Yes, partially! For list of objects properties, Mixpanel provides built-in property computations: [List of Objects]

Returns the length/count of items in the list — equivalent to a record count.

Prompts you to select a numeric property within the objects of the list and returns the total sum across all items in the list.

Returns the number of unique values for a selected property within the list.

docs.mixpanel.com/_next/image?w=3840&q=75&… [List of Objects]

If you need more complex calculations (e.g., combining price * quantity), you can use Custom Properties with numeric operators to compute new properties on the fly: [Custom Properties]

price * quantity

This creates a new computed property you can then use in your Insights report metrics.

There are several common reasons why user counts may differ between Mixpanel and your database:

This is the most common cause. If the totals match but unique user counts differ, it likely points to an ID management issue. [Debugging Discrepancies]

Here are the relevant resources on how to create a Borrowed Property in Mixpanel:

A few key things to keep in mind: