From c4a018de052484880a242994264a44133bbb91ac Mon Sep 17 00:00:00 2001 From: myronkaifung <97630035+myronkaifung@users.noreply.github.com> Date: Mon, 25 Nov 2024 06:40:44 -0800 Subject: [PATCH] Myronkaifung move revenueanalytics (#1645) * move revenue analytics to Guides>Playbooks * move to Guides>Launch instead * rename file, update meta.ts * fix links --------- Co-authored-by: Myron Fung --- pages/guides/launch/_meta.ts | 3 ++- .../launch/revenue-analytics.mdx} | 6 +++--- 2 files changed, 5 insertions(+), 4 deletions(-) rename pages/{docs/features/revenue_analytics.mdx => guides/launch/revenue-analytics.mdx} (95%) diff --git a/pages/guides/launch/_meta.ts b/pages/guides/launch/_meta.ts index 654a62119d..6d4a964c19 100644 --- a/pages/guides/launch/_meta.ts +++ b/pages/guides/launch/_meta.ts @@ -4,5 +4,6 @@ export default { "analyze-conversions": "Analyze Conversions", "build-user-flows": "Build User Flows", "track-user-retention": "Track User Retention", - "define-cohorts": "Define Cohorts" + "define-cohorts": "Define Cohorts", + "revenue-analytics": "Revenue Analytics" } diff --git a/pages/docs/features/revenue_analytics.mdx b/pages/guides/launch/revenue-analytics.mdx similarity index 95% rename from pages/docs/features/revenue_analytics.mdx rename to pages/guides/launch/revenue-analytics.mdx index bf2aba3de9..601c8eeedd 100644 --- a/pages/docs/features/revenue_analytics.mdx +++ b/pages/guides/launch/revenue-analytics.mdx @@ -21,7 +21,7 @@ Whether you have a transactions based business model or a subscription based bus ![image](/arpu.webp) 5. CAC aka Customer Acquisition Cost: i.e how much money do we have to spend to acquire a user (do I have to spend 5$ on marketing spend or $20 etc). A good acquisition strategy would mean LTV/ CAC > 1 -The [following FAQ](/docs/features/revenue_analytics#what-should-be-the-shape-of-the-data-to-analyze-these-metrics) explains what the shape of the data should be to build the above revenue metrics. +The [following FAQ](/guides/launch/revenue-analytics#what-should-be-the-shape-of-the-data-to-analyze-these-metrics) explains what the shape of the data should be to build the above revenue metrics. NOTE: You can look at how to build these metrics in Mixpanel by leveraging our [Ecomm template](https://mixpanel.com/project?show-template-selector=true) on either your data or our public demo data set. Here is a [public dashboard](https://mixpanel.com/p/DnjPvUbyke46TtZ9AeCGCs) to give you a view on the metrics you can build @@ -60,7 +60,7 @@ We've got 2 new **computed properties** to help you with subscription revenue me 3. 0 -> 5 = new [zero to positive] 4. 5 -> 20 = upgrade [positive to more positive] 5. 5 -> 5 = flat [no change] -NOTE: all are these are functionalities on [historical profile properties](https://docs.mixpanel.com/docs/data-structure/user-profiles#importing-historical-profile-values) +NOTE: all are these are functionalities on [historical profile properties](/docs/data-structure/user-profiles#importing-historical-profile-values) ![image](/computed_props.png) When creating a revenue metric eg incremental MRR in the last one month, you have two controls to help with it @@ -79,7 +79,7 @@ We also have the ability for you to look at the latest value as of time-period, Please ensure once you setup the Warehouse Connectors, you have Mirror Mode turned on to ensure your data is 100% in sync with the WH even if the WH data is updated - For Transactions based models - Please send purchase value as a event property on every purchase event. Example: `(Event: Purchase completed, {item: clothing, price: $100})` - For Subscription based models - - - Please send a monthly snapshot of the revenue per user/ account as a historical profile property. More details [here](https://docs.mixpanel.com/docs/data-structure/user-profiles#importing-historical-profile-values) + - Please send a monthly snapshot of the revenue per user/ account as a historical profile property. More details [here](/docs/data-structure/user-profiles#importing-historical-profile-values) - If a user/ account is not active, please set the revenue data to zero for the immediate month following so we can tag this as a churned user/ account. #### We have multiple SKUs per account, each with it’s own contract. Can we send this as a revenue object property for an account? Today, we do not support profile history for object type properties