Feature Flag Migration Playbook#95
Conversation
- Updated docs/what-is-mixpanel.mdx - Created images/FeatureFlagSetup.png - Created images/ExperimentSetup.png - Created images/ExperimentSetupMetrics.png - Created guides/strategic-playbooks/feature-flag-migration-playbook.mdx - Updated docs.json Mintlify-Source: dashboard-editor
kurbycchua
left a comment
kurbycchua
left a comment
There was a problem hiding this comment.
Overall comment is we need to make sure we fact check these as we do not want a customer ending up in messing up their experiment / FF data in mixpanel. Migrating the exposure of $experiment_started I find it the easy part, the challenging part is the Experiment report and the FF report of which underlying drives the analysis and the gates
- Updated docs/what-is-mixpanel.mdx - Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
|
|
||
| ## Step 1. Migrate past experiment exposure events | ||
|
|
||
| An exposure event records that a user was enrolled in an experiment, and was bucketed into an experiment variant. To keep your historical data, export your existing exposure events from your current vendor and ingest them to Mixpanel as `$experiment_started` events. |
There was a problem hiding this comment.
@xinlintanmp @amymadden-bit nitpick: This statement "An exposure event records that a user was enrolled in an experiment, and was bucketed into an experiment variant." might imply to readers that exposure events (ie feature gate, dynamic config) not related to experiments need not be migrated.
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx - Created images/Screenshot-2026-07-21-at-4.36.21-PM.png Mintlify-Source: dashboard-editor
kurbycchua
left a comment
kurbycchua
left a comment
There was a problem hiding this comment.
Resolved a couple of comments and kept those that seems unresolved open, @xinlintanmp once you edit something do you mind replying in the comment so I'd know which one you already accounted for?
kurbycchua
left a comment
kurbycchua
left a comment
There was a problem hiding this comment.
@russell-loube-mixpanel tagged you in 2 comments
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
- Updated guides/strategic-playbooks/feature-flag-migration-playbook.mdx Mintlify-Source: dashboard-editor
| "data_group_id": null, | ||
| "serving_method": "client", | ||
| "experiment_id": 12345, | ||
| "experiment_id": 12345, // an ID assigned in Mixpanel when you create the feature flag. Ensure your IDs do not conflict with any existing feature flags in Mixpanel |
There was a problem hiding this comment.
@xinlintanmp should this be: an ID assigned in Mixpanel when you create the experiment instead of feature flag?
| "data_group_id": null, | ||
| "serving_method": "client", | ||
| "experiment_id": null, | ||
| "experiment_id": null, // an ID assigned in Mixpanel when you create the feature flag. Ensure your IDs do not conflict with any existing feature flags in Mixpanel |
There was a problem hiding this comment.
@xinlintanmp should this be: an ID assigned in Mixpanel when you create the experiment instead of feature flag?
| "data_group_id": null, | ||
| "serving_method": "server", | ||
| "experiment_id": null, | ||
| "experiment_id": null, // an ID assigned in Mixpanel when you create the feature flag. Ensure your IDs do not conflict with any existing feature flags in Mixpanel |
There was a problem hiding this comment.
@xinlintanmp should this be: an ID assigned in Mixpanel when you create the experiment instead of feature flag?
1. Cleaned up Equivalent events table 2. Fixed "This guide walks through migrating your feature flags and experiments to Mixpanel from another platform."
kurbycchua
left a comment
kurbycchua
left a comment
There was a problem hiding this comment.
@xinlintanmp left 3 comments the reset resolved can you double check on
"experiment_id": null, // an ID assigned in Mixpanel when you create the feature flag?
5 participants
Summary
This update introduces a new guide for migrating feature flags and experiments from other platforms to Mixpanel. It outlines a five-part process to ensure a smooth transition, covering exposure events, configurations, and verification.
Changes
guides/strategic-playbooks/feature-flag-migration-playbook.mdx.images/FeatureFlagSetup.png,images/ExperimentSetup.png, andimages/ExperimentSetupMetrics.png.docs.jsonnavigation structure.Mintlify
0 threads from 0 users in Mintlify