Introduction to A/B testing with Mixpanel

In this video our Solutions Architect Alon walks you through best practices for analysing the impact of your A/B tests in your Mixpanel report. Including tips on how to implement, events and properties to select and how to do it you'll have everything you need.

[judenwachukwu]

Awesome, learnt something new, but how do I integrate with AB testing tools like Google Optimize?

[lukaojala]

Interesting! I would expect the best practice to be to register a test and a variant as a user property for every user as soon as they load the page/app code no matter if they see the page with an experiment or not. This way we could easily segment all our users by test&variant and understand their behaviour without registering a new event each time we introduce a test. Also, what about tests that are spanning across various pages and have multiple entry points? Would you instrument firing of that event N times ?

I'd argue that as soon as the user logs in/loads the web code we should identify() them with ab_tests: ["test_name--versionA", "test_name--versionC"] to capture the tests they've been exposed to as user property and then later in the analysis we can analyse any event or any funnel segmented by the test&version that user has been exposed to.