Create project-migration.md

pages/docs/migration.md

@@ -62,6 +62,8 @@ To perform a successful historical data load, we recommend:
 - Load a limited subset of the data into a test project (for example, a single day or data or a sample of the entire dataset) to get started. This will help you identify any errors in the end to end process before you do a full historical data load.
 - Load a year’s worth (or less) of historical data during your migration. This will allow your team to review year-over-year trends easily and do historical analysis as needed, without sending a bunch of data which is stale and unlikely to be used.
 
+For a more in-depth look into the steps required for a successful project migration, check out our [project migration playbook](/guides/playbooks/project-migration). 
+
 ## Change management migration of end users
 
 Once data is live, shift our focus to change management and migrating the existing users. You can mitigate risk here by:

pages/guides/_meta.ts

@@ -7,6 +7,6 @@ export default {
 	"plan": "Plan",
 	"implement": "Implement",
 	"launch": "Launch",
-	"beyond-onboarding": "Beyond Onboarding",
-    "analytics-strategy": "Analytics Strategy Workshop"
+	"playbooks": "Playbooks",
+	"beyond-onboarding": "Beyond Onboarding"
 }

pages/guides/plan/tracking-strategy.mdx

@@ -141,6 +141,26 @@ Now that you have an understanding of Mixpanel's Data Model, let's walk you thro
 
    ![image](/tutorials/event-depth.png "Designing Event Depth")
 
+Where events are too broad, you’d end up having to create filters for every single disparate action you want to measure. Conversely, where events are too narrow, you need to do a lot of work every time to compare the actions against one another.
+
+**In general, we advise customers to group together the same *******actions******* that users take across your site / platform, and group them to the level of the most commonly asked questions.**
+
+Consider the event `Start Signup`. Top questions we might want to answer with this:
+
+- Which page / screen did users most commonly click start signup from?
+- Which signup platform was the most popular?
+
+Here’s an example of an implementation we *don’t* recommend.
+
+![bestpractices2](/bestpractices2.png)
+
+Here, the question you’d want to answer most is: Which signup platform drives the most sign ups? If our events are too narrow, e.g. homepage/start_signup/apple, we’d have to manually add every single event where the signup occurs in order to do a comparison. It’s much easier to capture it as the event Start Signup and use event properties to describe the different originating pages / screens and signup platforms:
+
+![bestpractices3](/bestpractices3.png)
+
+
+To get all signup starts via the ideal state structure, the user only needs to query the single signup event and apply the flow and platform breakdowns. Once that's complete, the user can easily see that the homepage flow drives the most traffic with Apple out-performing other platforms across the board.
+
    It is important to adhere to best practices when managing personal information (PI) that you might potentially capture in the properties you define. Refer to our [Privacy](https://docs.mixpanel.com/docs/privacy) documentation for details on how Mixpanel respects and protects people’s fundamental online privacy and data rights.
 
    Having specific questions (eg hypothesis, influencing factors, current / target numbers) around the metrics you're measuring also helps you decide on the events and properties to include. Think of the answers you want to arrived at, and how an action (event), an information of an action (event properties), or a recent state (user property) can help lead you to that answer.