Merge branch 'main' into jg-sr-docs

mixpanel · May 9, 2024 · 35c70fb · 35c70fb
2 parents a04d2b3 + 9e7f51d
commit 35c70fb
Show file tree

Hide file tree

Showing 49 changed files with 1,629 additions and 184 deletions.
diff --git a/components/ExtendedButton/ExtendedButton.tsx b/components/ExtendedButton/ExtendedButton.tsx
@@ -0,0 +1,27 @@
+export default function ExtendedButton({ title, link }) {
+    const handleClick = () => {
+      window.location.href = link; // Redirects to the specified link
+    }
+
+    return (
+      <button onClick={handleClick} className="text-white 
+      
+      // Background
+      bg-gradient-to-b from-purple50 to-purple100 hover:from-purple50 hover:to-purple100 active:from-purple50 active:to-purple140
+  
+      // Shadow
+      shadow-sm hover:shadow-md
+  
+      // Shadow
+      rounded-full hover:rounded-lg 
+      
+      // Font 
+      font-medium  text-md 
+      
+      // Padding
+      px-7 py-2.5">
+        {title}
+      </button>
+    )
+  }
+
diff --git a/components/Search/Search.module.scss b/components/Search/Search.module.scss
@@ -11,4 +11,14 @@
 .inputContainer {
     display: flex;
     flex-direction: row;
+}
+
+@media (max-width: 768px) {
+    .searchBar {
+        display: none;
+    }
+
+    .icon {
+        width: 20px;
+    }
 }
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -31,18 +31,18 @@
     "nextra-theme-docs": "latest",
     "react": "^18.2.0",
     "react-dom": "^18.2.0",
-    "sass": "^1.74.1",
+    "sass": "^1.77.0",
     "sharp": "^0.32.6"
   },
   "devDependencies": {
     "@redocly/openapi-cli": "1.0.0-beta.16",
     "@types/mixpanel": "^2.14.8",
-    "@types/node": "20.12.5",
+    "@types/node": "20.12.8",
     "autoprefixer": "^10.4.19",
     "postcss": "^8.4.38",
     "rdme": "8.6.6",
     "tailwindcss": "^3.4.3",
-    "typescript": "^5.4.4",
+    "typescript": "^5.4.5",
     "yaml": "2.4.1"
   }
 }
diff --git a/pages/_document.js b/pages/_document.js
diff --git a/pages/changelogs/2024-05-09-home.mdx b/pages/changelogs/2024-05-09-home.mdx
@@ -0,0 +1,20 @@
+---
+title: "Home"
+slug: "changelog-2024-05-09-home.mdx"
+hidden: false
+createdAt: "2024-05-09T16:50:45.397Z"
+updatedAt: "2024-05-09T16:50:45.397Z"
+date: "2024-05-09"
+---
+
+Home is the new landing experience in Mixpanel. It’s for you to jump back into your workflows and get a glimpse into what’s happening across your product and your project in Mixpanel.
+
+The main sections of Home includes:
+
+- **Your Recents**: most recently viewed reports and boards by you
+- **Your Product**: this section is default populated with the top insights reports in your project, you can customize and change which insight report you’d like to display on Home
+- **Top Boards**: the most popular boards in your project
+- **Suggested Creators**: people in Mixpanel who are building boards and reports that we recommend checking out
+- **Recent Users**: a list of recently seen users on your product
+- **New Events**: a list of newly tracked events in your project
+- **Resources**: a list of resources that are also available in the top navigation
diff --git a/pages/docs/_meta.json b/pages/docs/_meta.json
@@ -4,6 +4,7 @@
 		"title": "INTRO"
 	},
 	"what-is-mixpanel": "What is Mixpanel?",
+	"what-to-track": "What to Track",
 	"quickstart": "Quickstart",
 	"data-in": {
 		"type": "separator",

diff --git a/pages/docs/boards/templates.mdx b/pages/docs/boards/templates.mdx
@@ -92,7 +92,7 @@ This template is meant to be used largely by teams that implemented Mixpanel ins
 - Monitoring the health of your implementation and nuances to look out for that could be a sign of poor implementation health.
 - Driving consistency in naming convention best practices and a better general understanding of how to manage data governance of your Mixpanel implementation
 
-[Implementation Monitoring & Data Governance Example Board Here](https://mixpanel.com/s/15N8Dg)
+[Implementation Monitoring & Data Governance Example Board Here](https://mixpanel.com/project/3018488/view/3536632/app/boards/#id=6664368)
 
 <img width="923" alt="Implementation Monitoring and Data Governance" src="https://github.com/mixpanel/docs/assets/136498120/6c21d6a2-bb33-4043-b762-6c4b64ccda1d" />
 
@@ -104,7 +104,7 @@ This template is meant to be used by Mixpanel Champions looking to train their t
 - Summaries of each core Mixpanel report (Insights, Funnels, Flows, & Retention) and clear examples articulating which Mixpanel reports/features users can leverage given the type of metric on which they’re wanting to report.
 - Links to support articles so users can self-serve education on nuances of Mixpanel’s functionality
 
-[Training Board for Champions Example Here](https://mixpanel.com/s/3niUys)
+[Training Board for Champions Example Here](https://mixpanel.com/project/3018488/view/3536632/app/boards#id=7198653)
 
 <img width="923" alt="Training Board for Champions to use to Educate Users" src="https://github.com/mixpanel/docs/assets/136498120/1bf32c1d-1bc8-43e8-8efc-01c2ae56aea1" />
 
@@ -123,6 +123,6 @@ Below are various examples of some common questions or issues that Mixpanel end
 - Who should I talk to about reporting questions and Mixpanel UI misunderstandings?
 - Who should I report a data issue or bug to?
 
-[Data Troubleshooting Guide Example Here](https://mixpanel.com/s/35CUaL)
+[Data Troubleshooting Guide Example Here](https://mixpanel.com/project/3018488/view/3536632/app/boards#id=6664372)
 
 <img width="921" alt="Data Troubleshooting Guide for End Users" src="https://github.com/mixpanel/docs/assets/136498120/ed65ef6a-b080-4aa8-a54b-598d8ac2f982" />
diff --git a/pages/docs/data-governance/data-clean-up.mdx b/pages/docs/data-governance/data-clean-up.mdx
@@ -86,7 +86,7 @@ We limit access to Data Deletion in these scenarios:
 - Your Mixpanel role is not Owner or Admin
 - Your data extends beyond the past 90 days
 - Your event volumes are > 5 billion events per month, any month over the trailing 3 months
-- You have made 10 deletes over the past calendar month
+- Your project has not had more than 10 deletes over the past calendar month 
 
 ### How to use
 

diff --git a/pages/docs/data-structure/advanced/group-analytics.mdx b/pages/docs/data-structure/advanced/group-analytics.mdx
@@ -181,6 +181,10 @@ curl --request POST \
   --data data_group_id=<data_group_id_here>
 ```
 
-The `data_group_id` can be found in the URL of the group profile page:
+The `<data_group_id>` can be found in the URL of the [Group Profile](/docs/data-structure/advanced/group-analytics#group-profiles) page:
 
-`https://mixpanel.com/project/2888952/view/3418364/app/profile#distinct_id=<distinct_id>&data_group_id=-<data_group_id>`
+`https://mixpanel.com/project/<project_id>/view/<workspace_id>/app/profile#distinct_id=<distinct_id>&data_group_id=<data_group_id>`
+
+Here's an actual example with `data_group_id` = `1405123841946871899`: 
+
+https://mixpanel.com/project/3187769/view/3699049/app/profile#distinct_id=company_id_8889&data_group_id=-1405123841946871899
diff --git a/pages/docs/data-structure/property-reference.md b/pages/docs/data-structure/property-reference.md
@@ -159,7 +159,7 @@ Mixpanel supports five data types for properties: String, Numeric, Boolean, Date
 
 ## Object and List of Objects Data Types
 
-Mixpanel also supports object and [list of objects](https://docs-git-kurbycchua-update-property-reference-mixpanel.vercel.app/docs/features/advanced#list-of-objects-property-support) data types in a limited capacity. These are typically for very specific use cases such as in e-commerce (eg Cart Items, Search Filters). It is highly encouraged that you use the five primary data types as they are fully supported in the Mixpanel UI.
+Mixpanel also supports object and [list of objects](/docs/features/advanced#list-of-objects-property-support) data types in a limited capacity. These are typically for very specific use cases such as in e-commerce (eg Cart Items, Search Filters). It is highly encouraged that you use the five primary data types as they are fully supported in the Mixpanel UI.
 
 ### Object
 

diff --git a/pages/docs/features/_meta.json b/pages/docs/features/_meta.json
@@ -5,7 +5,8 @@
     "custom-events": "Custom Events",
     "custom-properties": "Custom Properties",
     "saved-behaviors": "Saved Behaviors",
-    "sessions": "Sessions",
+    "session-replay": "Session Replay",    
+    "sessions": "Sessions",    
     "spark": "Spark",
     "advanced": "Advanced"
 }
diff --git a/pages/docs/features/session-replay.md b/pages/docs/features/session-replay.md
@@ -0,0 +1,81 @@
+# Session Replay
+
+## **Overview**
+
+Mixpanel Session Replay is the fastest way to understand the whole picture about your customers and make better product decisions, by combining quantitative and qualitative user insights. 
+
+When digging into customer journeys in Mixpanel’s analytics, you can understand “where do customers drop-off?” And now, Mixpanel Session Replay enables you to quickly follow-up with, “why do customers drop off?”
+
+## Availability
+
+Currently, Session Replay is currently in invite-only beta access for:
+
+- customers on our [Enterprise plan](https://www.notion.so/Session-Replay-Docs-v1-c32c9817ec1b49798d1ca7d1ccc5880c?pvs=21)
+- projects without [EU Data Residency](https://docs.mixpanel.com/docs/privacy/eu-residency) enabled
+
+You can join the waitlist for beta access [here](https://mixpanel.com/m/session-replay-beta/).
+
+For any questions about Session Replay or beta access, please reach out to your Account Manager.
+
+## **Using Session Replay**
+
+Session Replay can be accessed in two places:
+
+1. From User Profile page
+2. From Mixpanel reports
+
+**From User Profile page**
+
+In any user’s profile page, Click the ‘View Replays’ button to watch replays from that user. From here, you will be taken to our Replay Player.
+
+![replayProfileEntry](/replayProfileEntryPoint.png)
+
+**From Mixpanel reports**
+
+Click any point on a chart for Event and Funnel metrics, and select ‘View Replays’ to view replays that show that event being fired. From here, you will be taken to our Replay Player. 
+
+![replayReportEntry](/replayReportEntryPoint.png)
+
+*Note: reports entry point is currently supported for Event and Funnel metrics only.*
+
+## **Replay Player**
+
+![replayHeroImage](/replayHeroImage.png)
+
+The Replay Player allows you to watch replays, as well as:
+
+- Expand the player to full-screen
+- Copy a URL to share with your teammates
+- Change the playback speed
+- Automatically skip periods of the replay where user is inactive
+
+The Replay Feed on the left of the player also allows you to:
+
+- sort replays by recency
+- search for replays by user's name / email, replay date, or user ID
+
+## **Privacy**
+
+Our Session Replay Beta Service Addendum can be found [here](https://mixpanel.com/legal/session-replay-beta-service-addendum/).
+
+## **FAQ**
+
+### **Is Session Replay available for mobile?**
+
+To start, Session Replay is available only for web-based applications (including mobile web). We hope to offer mobile support in the near future. 
+
+### Can I prevent Session Replay from recording sensitive content?
+
+By default, all on-screen text elements are masked in replays. Additionally, you can customize how you initialize our SDK to fully control (1) where to record and (2) whom to record. For more details, please see our [implementation docs](https://docs-k17v3wqal-mixpanel.vercel.app/docs/tracking-methods/sdks/javascript#session-replay-beta).
+
+### How long are replays stored?
+
+30 days.
+
+### Does Session Replay work on projects with EU Data Residency enabled?
+
+Not currently, but we plan to add support soon.
+
+### How soon are Replays available for viewing after a session begins?
+
+There is about a ~1 minute delay between when recordings are captured and when they appear in Mixpanel.
diff --git a/pages/docs/migration/amplitude.md b/pages/docs/migration/amplitude.md
@@ -38,7 +38,36 @@ We also support additional data for extending your use cases with Mixpanel:
 - [Lookup tables](https://developer.mixpanel.com/reference/lookup-tables): For event data which was already sent, you can use these to extend the data already sent into Mixpanel. A common use case is taking an identifier like a transaction ID, item ID, etc. and using lookup tables to enrich the data with additional information like the amount, category, etc. from your data warehouse.
 
 ## Loading historical data
-If you have access to your Amplitude data in your data warehouse, the simplest way to bring this historical data into Mixpanel is by using our warehouse connector. At a high-level, the migration consists of 3 steps:
+
+### Mixpanel's Migration Service
+If you have under 15M events in Amplitude, you can migrate your historical Amplitude data using Mixpanel's free migration service. 
+
+Here's an example request to the migration service which you can customize:
+
+```bash
+curl --request POST \
+  --url http://migrate.api.mixpanel.com/amplitude \
+  --data '{
+	"AMPLITUDE_API_KEY": "YOUR_AMP_KEY",
+	"AMPLITUDE_API_SECRET": "YOUR_AMP_SECRET",
+	"MIXPANEL_TOKEN": "YOUR_MP_TOKEN",
+	"START_DATE": "YYYY-MM-DD",
+	"END_DATE": "YYYY-MM-DD"
+  }'
+```
+
+This service will use your provided credentials to export Amplitude data, transform the data, and load event + user profiles into your Mixpanel project. If no dates are provided, the service defaults to a 30 day duration relative to the present.
+
+[Watch the demo tutorial](https://www.loom.com/share/f947d42db01541a0b74953461e3c6cc0?sid=43c1ef52-d008-4b6d-9015-afa14b05901c) for more in-depth instructions on how to use the migration service.
+
+Notes:
+* Any events ingested via this method in the current month will count toward your plan. We recommend testing this while on a Free plan first. You may also pass a `"DRY_RUN" : true` param in the JSON which will show you how many events will be migrated.
+* If you are using Mixpanel or Amplitude's EU data residency, pass `"REGION": "EU"` with your request.
+* This migration service is in beta -- if you have questions or run into issues, please reach out to us [here](mailto:[email protected]).
+
+
+### Data Warehouse Connectors 
+If you have access to your Amplitude data in your data warehouse, the most scalable way to bring this historical data into Mixpanel is by using our warehouse connector. At a high-level, the migration consists of 3 steps:
 1. Set up a new Mixpanel project which is on [Simplified ID Merge system](/docs/tracking-methods/id-management/identifying-users#simplified-vs-original-id-merge). 
 2. Transform Amplitude data in your data warehouse (sample SQL transformation included below).   
 3. Set up [Mixpanel Warehouse Connector](/docs/tracking-methods/data-warehouse/overview) to initiate data sync from your data warehouse to Mixpanel.