You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/docs/boards/templates.mdx
+26-5Lines changed: 26 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,17 @@ The Feature Launch template uses four inputs, two of which are events: “Featur
24
24
- New Feature: Pick an event that captures the adoption of your new feature. For adding reviews to a streaming service, the event could be publishing a review. For e-commerce, it might be creating a “save for later” collection.
25
25
-[Feature Value Moment](https://developer.mixpanel.com/docs/plan-your-implementation#value-moment-event): Select an event that indicates that a user is experiencing value in your feature. For a social media platform, it could be liking a new type of content; for a streaming service, it could be sharing a playlist; for e-commerce, it might be purchasing from the “save for later” collection.
26
26
27
+
The AI Company KPI template uses several events and properties:
28
+
29
+
- Sign Up: An event triggered the first time a user is identified in your system, typically upon account creation or registration.
30
+
- Launch AI: An event triggered when a user first begins interacting with an AI feature, such as opening a chatbot interface or engaging a virtual assistant.
31
+
- AI Prompt Sent: An event recorded each time a user submits a prompt or query to an AI system. Include the prompt content as a property.
32
+
- AI Response Sent: An event triggered when the AI system sends a response back to the user. Include properties such as api token usage (API Tokens Used), estimated cost (API Cost), and latency (API Response Time).
33
+
- API Error: An event that logs runtime errors encountered by the AI feature or its underlying APIs during user interaction. This should capture relevant error metadata for diagnostics.
34
+
- User Feedback Submitted: An event triggered when a user provides feedback on an AI-generated response. Include properties for the Feedback Text and Sentiment, which could be structured (e.g., thumbs up/down) or unstructured (e.g., free-text).
35
+
- AI Dismissed: An event triggered when a user ends their interaction with an AI feature, such as closing a chatbot or exiting an assistant interface.
36
+
-[Conversion Event](https://developer.mixpanel.com/docs/plan-your-implementation#value-moment-event): Select an event that indicates that a user is experiencing value in your feature. For a social media platform, it could be liking a new type of content; for a streaming service, it could be sharing a playlist; for e-commerce, it might be purchasing from the “save for later” collection.
37
+
27
38
For projects that have already been implemented and have data, you will select your events, which will enable the `Create` CTA, and your Board will be generated.
28
39
29
40
For projects that do not have data, please refer to our [dev docs](https://developer.mixpanel.com/docs/plan-your-implementation) and [implementation](https://help.mixpanel.com/hc/en-us/categories/115001197206-Data-and-Implementation) resources.
@@ -84,7 +95,6 @@ The Lifecycle Cohort Analysis Template breaks down your user base into the parts
84
95
85
96
In this section, you will find other example Boards built out in our demo data sets to highlight examples of how our most successful and data-mature customers monitor their implementation and drive adoption of Mixpanel across their organizations. The examples in this section are meant to be used as inspiration for additional Boards you can create to make sure your team is effectively monitoring your implementation as well as enabling end users to feel confident implementing and using Mixpanel.
86
97
87
-
88
98
### Implementation Monitoring & Data Governance
89
99
90
100
This template is meant to be used largely by teams that implemented Mixpanel instrumentation and will be monitoring the data governance of the implementation on an on going basis. The two sections in the Board cover best practices for:
@@ -94,7 +104,11 @@ This template is meant to be used largely by teams that implemented Mixpanel ins
94
104
95
105
[Implementation Monitoring & Data Governance Example Board Here](https://mixpanel.com/project/3018488/view/3536632/app/boards/#id=6664368)
96
106
97
-
<imgwidth="923"alt="Implementation Monitoring and Data Governance"src="https://github.com/mixpanel/docs/assets/136498120/6c21d6a2-bb33-4043-b762-6c4b64ccda1d" />
107
+
<img
108
+
width="923"
109
+
alt="Implementation Monitoring and Data Governance"
### Training Board for Champions to use to Educate Users
100
114
@@ -106,8 +120,11 @@ This template is meant to be used by Mixpanel Champions looking to train their t
106
120
107
121
[Training Board for Champions Example Here](https://mixpanel.com/project/3018488/view/3536632/app/boards#id=7198653)
108
122
109
-
<imgwidth="923"alt="Training Board for Champions to use to Educate Users"src="https://github.com/mixpanel/docs/assets/136498120/1bf32c1d-1bc8-43e8-8efc-01c2ae56aea1" />
110
-
123
+
<img
124
+
width="923"
125
+
alt="Training Board for Champions to use to Educate Users"
@@ -125,4 +142,8 @@ Below are various examples of some common questions or issues that Mixpanel end
125
142
126
143
[Data Troubleshooting Guide Example Here](https://mixpanel.com/project/3018488/view/3536632/app/boards#id=6664372)
127
144
128
-
<imgwidth="921"alt="Data Troubleshooting Guide for End Users"src="https://github.com/mixpanel/docs/assets/136498120/ed65ef6a-b080-4aa8-a54b-598d8ac2f982" />
0 commit comments