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: apps/docs/content/docs/dashboard.mdx
+67-1Lines changed: 67 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -272,6 +272,10 @@ Discover your global audience and optimize for different regions:
272
272
**Privacy Note**: Location data is derived from IP addresses and anonymized. No precise location tracking is performed.
273
273
</Callout>
274
274
275
+
<Callouttype="tip"title="Powering the Map View">
276
+
The geographic data displayed on maps and in regional breakdowns is typically derived from the user's IP address at the beginning of a session. This functionality is an integral part of session tracking. Ensure `trackSessions={true}` (which is enabled by default) in your [SDK configuration](/docs/sdk#-configuration-options) to collect this data.
277
+
</Callout>
278
+
275
279
## 💻 Technology Stack Analysis
276
280
277
281
Understand your audience's technical environment:
@@ -323,6 +327,10 @@ Understand your audience's technical environment:
323
327
324
328
Track and analyze your business-specific events with detailed property breakdowns:
325
329
330
+
<Callouttype="info"title="Populating This Section">
331
+
The analytics, breakdowns, and examples shown here are populated by the custom events you actively send from your application using the `db.track('your_event_name', {your_properties})` method. The more relevant and well-structured custom events you track, the more insightful this section will become. For detailed guidance on how to implement custom event tracking, please refer to the [SDK Methods Reference](/docs/sdk#-sdk-methods-reference) and strategies in the [Custom Event Tracking](/docs/sdk#-custom-event-tracking) section of the SDK documentation.
The performance metrics, including Core Web Vitals, are populated when you enable `trackPerformance={true}` (enabled by default) and `trackWebVitals={true}` (disabled by default, but recommended) in your [SDK configuration](/docs/sdk#-optional-tracking-features). Enabling these options allows the SDK to collect detailed timing and performance data from the user's browser.
@@ -575,6 +587,10 @@ Monitor your website's technical health and user experience:
575
587
576
588
Monitor and resolve issues affecting your users:
577
589
590
+
<Callouttype="tip"title="Enabling Error Data Collection">
591
+
To populate the error tracking sections of the dashboard, ensure you have `trackErrors={true}` enabled in your [SDK configuration](/docs/sdk#-optional-tracking-features). This will automatically capture unhandled JavaScript errors and promise rejections. For more detailed context on specific handled errors, you can manually send error events using `db.track('error', { /* custom properties */ })` as described in the [SDK Methods Reference](/docs/sdk#-sdk-methods-reference).
592
+
</Callout>
593
+
578
594
### 🐛 JavaScript Error Analytics
579
595
580
596
<Accordions>
@@ -759,4 +775,54 @@ Get your data where you need it:
759
775
760
776
<Callouttype="info">
761
777
**Need Help?** Join our [Discord community](https://discord.gg/JTk7a38tCZ) or [contact support](mailto:support@databuddy.cc) for dashboard assistance.
762
-
</Callout>
778
+
</Callout>
779
+
780
+
---
781
+
782
+
## 📊 Funnel Analysis
783
+
784
+
Funnel analysis helps you understand how users progress through specific sequences of actions on your site, such as a signup process or a checkout flow. Defining and tracking these steps is crucial for identifying drop-off points and optimizing conversion rates.
785
+
786
+
<Callouttype="tip"title="Populating Funnel Data">
787
+
To populate funnel data, you need to:
788
+
1. Define the steps of your funnel within the Databuddy dashboard settings.
789
+
2. Ensure each step corresponds to a custom event (or page view) that you are tracking with the SDK. For example, a signup funnel might be defined by a sequence of events like `viewed_signup_page` (a screen view), `started_signup_form` (custom event), and `completed_signup` (custom event).
790
+
791
+
The sequence of these events for users will then build the funnel visualization. For more details on sending custom events, see the [SDK Methods Reference](/docs/sdk#-sdk-methods-reference) in the SDK documentation.
792
+
</Callout>
793
+
794
+
*(Detailed instructions on how to define funnels within the dashboard interface and interpret the funnel visualization will be available here. This feature helps pinpoint where users drop off in key workflows.)*
795
+
796
+
---
797
+
798
+
## 🗺️ User Journey Visualization
799
+
800
+
User journey visualization allows you to see the paths users take through your website on a session-by-session basis. This includes the sequence of page views and custom events they trigger, offering insights into user behavior and navigation patterns.
801
+
802
+
<Callouttype="tip"title="Data for User Journeys">
803
+
This feature relies on the comprehensive event data tracked by the SDK. The richness of the user journeys depends on:
804
+
- Thorough `screen_view` tracking (often automatic via `trackScreenViews={true}` in the [SDK configuration](/docs/sdk#-configuration-options)).
805
+
- Detailed custom event tracking (`db.track()`) for significant interactions as described in the [SDK Methods Reference](/docs/sdk#-sdk-methods-reference).
806
+
807
+
Each event is tied to a user's session, allowing the dashboard to reconstruct their path.
808
+
</Callout>
809
+
810
+
*(Information on how to access and interpret user journey maps in the dashboard, including filtering by user segments or starting/ending events, will be detailed here. This helps understand common paths to conversion or points of confusion.)*
811
+
812
+
---
813
+
814
+
## 👤 User Profiles
815
+
816
+
The dashboard can compile user profiles that show a history of activity for individual visitors, even if they are anonymous. These profiles are built by aggregating all events linked to the same unique user ID, which the SDK manages automatically as part of session tracking (`trackSessions={true}`).
817
+
818
+
<Callouttype="tip"title="Building Rich User Profiles">
819
+
Richer user profiles are developed when you consistently track custom events that provide context about user actions and milestones. While the SDK handles user identification, the depth of each profile is determined by the quality and breadth of your event tracking strategy.
820
+
821
+
Refer to these SDK documentation sections for more:
822
+
-[Custom Event Tracking](/docs/sdk#-custom-event-tracking) for strategy.
823
+
-[Standard Event Reference](/docs/sdk#-standard-event-reference) for common event types.
824
+
-[SDK Methods Reference](/docs/sdk#-sdk-methods-reference) for `db.track()` and `db.setGlobalProperties()`.
825
+
- The `db.setGlobalProperties()` method can be particularly useful for adding persistent attributes to a user's profile.
826
+
</Callout>
827
+
828
+
*(Details on where to find user profiles in the dashboard, what information they contain (e.g., event history, first seen, last seen, device info, location), and how to use them for segmentation or understanding individual user behavior will be provided here.)*
0 commit comments