🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
Enhance NoData component and documentation for troubleshooting
Bill Yangc981b52a91c7
diff --git a/client/src/app/[site]/components/Header/NoData.tsx b/client/src/app/[site]/components/Header/NoData.tsxindex cd60372b0..cc73e9f3b 100644--- a/client/src/app/[site]/components/Header/NoData.tsx+++ b/client/src/app/[site]/components/Header/NoData.tsx@@ -94,7 +94,11 @@ export function NoData() {<a href="https://rybbit.com/docs/script" className="text-blue-500 hover:underline">docs</a>{" "}- for more information.+ for more information, or{" "}+ <a href="https://rybbit.com/docs/script-troubleshooting" className="text-blue-500 hover:underline">+ troubleshoot+ </a>{" "}+ if your script isn't sending traffic.</span>{/* Framework Guide Cards */}<div className="">diff --git a/docs/content/docs/behavior-analytics/errors.mdx b/docs/content/docs/behavior-analytics/errors.mdxindex 07d015d00..d7f0970ee 100644--- a/docs/content/docs/behavior-analytics/errors.mdx+++ b/docs/content/docs/behavior-analytics/errors.mdx@@ -1,286 +1,30 @@----title: Errors Tab-description: A comprehensive guide to tracking and resolving errors in Rybbit's Behavior Analytics+title: Errors+description: Track JavaScript errors on your website----# A Guide to Rybbit's Errors Tab+The Errors tab shows JavaScript errors occurring on your website, helping you identify and fix bugs that affect user experience.-The Errors tab in Rybbit's Behavior Analytics section provides visibility into JavaScript errors and exceptions occurring on your website. While users often silently suffer through broken features and technical issues, the Errors tab brings these problems into the light, allowing you to quickly identify and resolve the bugs that degrade user experience and cost you conversions.+## Enabling Error Tracking-## What is Error Tracking?+Enable error tracking in your [site settings](/docs/site-settings).-Error tracking monitors JavaScript errors that occur in the browser as users interact with your website. These might include syntax errors, network failures, unhandled exceptions, or any other JavaScript issues that break functionality or degrade the user experience.+## Error Information-By automatically capturing errors and the context in which they occur, Rybbit helps you transition from reactive debugging (users report problems) to proactive quality assurance (you identify and fix issues before they hurt your business).+For each error, you'll see:-## Why Error Tracking Matters+- **Error Type** - ReferenceError, TypeError, SyntaxError, NetworkError, etc.+- **Error Message** - The specific error message+- **Stack Trace** - The chain of function calls that led to the error+- **Affected Users** - Number of unique users who encountered this error+- **Occurrence Count** - How many times the error was triggered+- **First/Last Seen** - When the error first appeared and most recently occurred+- **Affected Pages** - Which pages generated this error+- **Browser & Device** - Which environments experience this error-JavaScript errors on your website directly impact your business:+## Using Error Data-**Lost Conversions**: A broken checkout button might prevent customers from completing purchases. Error tracking reveals these critical issues immediately.--**Poor User Experience**: Errors often cascade, breaking features and confusing users. Early detection prevents negative user experiences.--**Hidden Problems**: Many users silently abandon your site when they encounter errors. Without error tracking, you'd never know there was a problem.--**Development Efficiency**: Instead of developers chasing vague user reports ("your site is broken"), error tracking provides exact error messages and stack traces.--**Quality Assurance**: Errors that slip through testing in production are caught and fixed much faster with visibility into real user errors.--## Accessing the Errors Tab--To view and analyze errors on your website:--1. Log into your Rybbit dashboard-2. Navigate to the **Behavior** section in the left sidebar-3. Click on the **Errors** tab--You'll see a list of all JavaScript errors occurring on your website, grouped by error type and severity.--## Key Error Metrics--When examining the Errors tab, you'll encounter important metrics about your website's health:--### Error Type-The classification of the error (ReferenceError, TypeError, SyntaxError, NetworkError, etc.). This helps you categorize and prioritize fixes.--### Error Message-The specific error message returned by JavaScript. This often clearly describes what went wrong.--### Stack Trace-The chain of function calls that led to the error. This shows you exactly where in your code the error occurred.--### Affected Users-The number of unique users who encountered this error. A single user seeing an error is less critical than hundreds of users affected.--### Occurrence Count-How many times this specific error has been triggered. Frequent errors indicate high-priority issues.--### First Seen-When the error first appeared. New errors might indicate recently introduced bugs.--### Last Seen-When the error most recently occurred. Errors that went away might have been fixed. Errors that persist need attention.--### Affected Pages-Which pages on your website generated this error. This reveals if the issue is site-wide or isolated to specific areas.--### Severity Level-The impact level of the error (critical, major, minor). Critical errors often prevent core functionality.--### Browser & Device-Which browsers and devices experience this error. Some errors only occur in specific environments.--## Error Types and Causes--Understanding different error types helps you prioritize fixes:--### Reference Errors-Caused by attempting to use undefined variables. Often indicates missing dependencies or incorrect variable names.--### Type Errors-Occur when code tries to perform an operation on the wrong data type (e.g., calling a method on undefined). Common in code that doesn't validate input.--### Syntax Errors-Issues in code structure. Usually caught during development but can occur in dynamically generated code.--### Network Errors-Failed API calls or failed resource loading. Might indicate server issues, CDN problems, or user connectivity issues.--### Permission Errors-Attempt to access restricted resources. Often indicates incorrect authentication or authorization.--### Range Errors-Operations outside valid ranges (e.g., array access out of bounds).--### Custom Errors-Errors thrown intentionally by your code for validation or business logic purposes.--## Analyzing Error Patterns--The Errors tab becomes most valuable when you identify patterns:--### Error Frequency-Monitor if errors are increasing, staying stable, or decreasing. Sudden spikes indicate new problems. Gradual increases suggest systematic issues.--### Error Clustering-Multiple errors from the same user might indicate they're triggering a specific error condition. Look for patterns in which actions cause errors.--### Device-Specific Errors-Some errors occur only on mobile or only on specific browsers. This helps you test in the right environment.--### Timing Patterns-Do errors spike at specific times? This might correlate with deployments, heavy traffic periods, or external service outages.--### Conversion Impact-Which errors are preventing users from completing important actions? Prioritize fixing errors on critical pages.--## Common Use Cases--### Identifying Critical Issues-When errors are preventing users from converting or accessing core features, fix them immediately.--### Post-Deployment Monitoring-After deploying new code, monitor the Errors tab for sudden spikes indicating bugs introduced by the deployment.--### Debugging User Reports-When users report problems, the Errors tab often provides the exact technical issue and stack trace.--### Improving Stability-Regularly reviewing and fixing errors improves your overall application stability and user satisfaction.--### A/B Testing Validation-After launching A/B tests or feature experiments, monitor errors to ensure new variants don't introduce bugs.--### Performance Debugging-Some errors are caused by memory leaks or performance issues. Tracking errors helps identify performance problems.--### Third-Party Integration Issues-Errors often indicate that third-party integrations (analytics, payment processors, chat tools) are malfunctioning.--## Error Tracking Configuration--To use the Errors tab effectively:--1. **Enable Error Tracking**: Ensure error tracking is enabled in your Rybbit configuration-2. **Proper Installation**: Verify the Rybbit script is installed before other scripts that might throw errors-3. **Source Maps**: If you use minified code, upload source maps for readable stack traces-4. **Environment Tagging**: Tag errors by environment (production, staging, development) to ignore non-production errors-5. **Filtering**: Configure the system to ignore known, harmless errors in your stack--## Understanding Stack Traces--Stack traces show you the exact execution path that led to an error:--```-ReferenceError: cart is not defined- at checkout() (app.js:245)- at handlePaymentClick() (app.js:180)- at HTMLElement.onclick (checkout.html:50)-```--This tells you:-- **Error**: Variable `cart` is undefined-- **Root Location**: Line 245 in app.js, in the `checkout()` function-- **Call Chain**: `checkout()` was called from `handlePaymentClick()` which was called from a click handler--With this information, you can quickly find and fix the bug.--## Prioritizing Error Fixes--Not all errors are equally important. Use these criteria to prioritize:--**By Impact**: How many users are affected? Critical = hundreds of users, Major = dozens, Minor = few--**By Severity**: Does it completely break functionality (critical) or just degrade it (major/minor)?--**By Visibility**: Does the error occur on frequently visited pages or obscure pages?--**By Business Impact**: Does the error prevent conversions or affect core features?--**By Frequency**: Is the error happening constantly (high priority) or rarely (lower priority)?--## Best Practices for Error Management--**Fix Frequently Occurring Errors First**: Errors affecting many users should be fixed before edge-case errors.--**Use Source Maps**: Keep source maps handy so you can read stack traces in minified code.--**Test Fixes**: When fixing an error, verify the fix works before deploying to production.--**Monitor After Fixes**: After fixing an error, monitor the Errors tab to verify it's actually gone.--**Set Up Alerts**: Configure alerts for critical error spikes to catch new issues immediately.--**Document Errors**: Keep notes on errors you've fixed to avoid repeating mistakes.--**Version Tracking**: If possible, track which code version each error is associated with to isolate when bugs were introduced.--## Advanced Error Debugging--### Correlating Errors with Sessions-Find users who encountered errors and examine their sessions to understand what they were doing when the error occurred.--### Analyzing Error Sequences-Sometimes multiple errors occur in sequence. Understanding the sequence helps identify root causes.--### Monitoring Third-Party Errors-Track errors from third-party scripts (ads, analytics, chat widgets). Some can be ignored, others indicate integration failures.--### Performance-Related Errors-Memory errors and timeout errors often indicate performance issues. Address these alongside traditional error fixes.--### Error Recovery Success-Monitor whether errors automatically recover or if they break functionality. Unrecoverable errors are more critical.--## Privacy Considerations--Rybbit's error tracking respects privacy:--- Error messages and stack traces don't automatically include PII-- You should review error data to ensure no sensitive information is leaking-- Users can opt out of error tracking-- Error data follows the same retention and security policies as other analytics--Be careful not to log sensitive information (passwords, API keys, personal data) in error messages.--## Common Error Scenarios--### Redux/State Management Errors-Often indicate components trying to access undefined state properties. Fix by ensuring proper state initialization.--### Third-Party Library Errors-When errors come from libraries you didn't write, check for compatibility issues or incorrect usage.--### Network Timeout Errors-Indicate slow API responses or failed requests. Consider implementing retry logic.--### CORS Errors-Indicate requests blocked by browser security policies. Review your CORS configuration.--### Memory Leak Errors-When browser memory consumption grows continuously, track down code creating unreferenced objects.--### Timing-Related Errors-Errors that occur intermittently might be timing-related (race conditions, asynchronous issues).--## Troubleshooting Error Tracking--### No errors appearing-Check that error tracking is enabled and that you have JavaScript errors occurring on your site (they might be being caught elsewhere).--### Errors seem inaccurate-Verify source maps are properly configured. Without source maps, minified code shows unhelpful stack traces.--### Too many trivial errors-Configure the system to ignore errors that don't affect users, or filter them in your dashboard.--### Missing error context-Ensure the Rybbit script loads early and before other scripts that might throw errors.--## Connecting Errors with Other Analytics--### Errors and Sessions-See in which sessions errors occurred to understand user impact.--### Errors and Users-Identify which users are affected by specific errors, allowing for targeted support.--### Errors and Events-Some errors might be preceded by specific events. Track these sequences to understand error causes.--## Conclusion--The Errors tab in Rybbit's Behavior Analytics transforms your website monitoring from reactive (waiting for user complaints) to proactive (automatically detecting and fixing issues). By systematically reviewing and addressing errors, you dramatically improve user experience, increase conversions, and build a more stable product.--Make it a habit to check the Errors tab regularly, prioritize fixes based on user impact, and monitor after deployments for any unexpected issues. Combined with other Behavior Analytics features, error tracking gives you complete visibility into your website's health and your users' experience.--**Additional Resources:**-- [Sessions Tab Guide](/docs/behavior-analytics/sessions)-- [Events Tab Guide](/docs/behavior-analytics/events)-- [Users Tab Guide](/docs/behavior-analytics/users)-- [Track Custom Events](/docs/track-events)-- [Debugging Performance Issues](/docs/troubleshooting)-- [Product Analytics - Funnels Guide](/docs/product-analytics/funnels_guide)-- [API - Sending Events](/docs/api/sending-events)-- [Blog: Website Traffic Drop](/blog/website-traffic-drop)+- **Prioritize by impact** - Fix errors affecting the most users first+- **Monitor after deployments** - Watch for new errors after releasing code+- **Debug user reports** - Find the exact technical issue when users report problems+- **Track third-party issues** - Identify when external integrations are malfunctioningdiff --git a/docs/content/docs/behavior-analytics/events.mdx b/docs/content/docs/behavior-analytics/events.mdxindex e89ab88d9..c5a735a56 100644--- a/docs/content/docs/behavior-analytics/events.mdx+++ b/docs/content/docs/behavior-analytics/events.mdx@@ -1,271 +1,34 @@----title: Events Tab-description: A comprehensive guide to tracking and analyzing custom events in Rybbit's Behavior Analytics+title: Events+description: Track custom events on your website----# A Guide to Rybbit's Events Tab+The Events tab shows custom events tracked on your website.-The Events tab in Rybbit's Behavior Analytics section lets you track and analyze custom events that happen on your website. While standard analytics tracks page views and basic interactions, the Events tab gives you control over what actions matter most to your business—whether that's button clicks, form submissions, purchases, sign-ups, feature usage, or any other meaningful user interaction.+## Setting Up Events-## What is a Custom Event?+See the [Track Events guide](/docs/track-events) for implementation details.-A custom event is any action you define as important for your business. Unlike page views which happen automatically, custom events require you to implement tracking code. This intentional approach means you only track what matters to you, keeping your analytics focused and your data collection minimal.+## Events Page-Custom events are the bridge between your business goals and user behavior. By tracking events, you transform raw user actions into meaningful signals that show you what users are doing and whether they're achieving your desired outcomes.+The events page includes:+- **Events Chart** - Visualize event trends over time+- **Custom Events List** - All tracked events with counts+- **Event Log** - Recent individual event occurrences-## Types of Events You Can Track+## Event Metrics-Rybbit allows you to track virtually any user action as a custom event:+For each event:+- **Event Name** - The name you assigned to the event+- **Count** - Total times triggered in the selected period+- **Percentage** - Share of total events-### Engagement Events-- Button clicks (CTA, "Learn More," "Get Started")-- Link clicks-- Video plays and completions-- Form submissions-- Content shares-- Feature interactions+## Event Properties-### Conversion Events-- Product purchases-- Sign-ups and registrations-- Newsletter subscriptions-- Account upgrades-- Demo requests-- Contact form submissions+Click the expand arrow on any event to view its properties. Properties show the key-value pairs attached to events, helping you understand event context (e.g., which product was purchased, what button was clicked).-### Feature Usage Events-- Feature activations-- Tool usage-- Feature completions-- API calls-- File uploads/downloads+## Filtering-### User Journey Events-- Onboarding completion-- Tutorial progression-- Milestone achievements-- Status changes-- User level-ups--## Accessing the Events Tab--To view and analyze your events:--1. Log into your Rybbit dashboard-2. Navigate to the **Behavior** section in the left sidebar-3. Click on the **Events** tab--You'll see a comprehensive list of all tracked events on your website, along with frequency, user information, and other metrics.--## Key Event Metrics--When examining the Events tab, you'll encounter important metrics about your custom events:--### Event Name-The name you assigned to the custom event. Clear, consistent naming makes it easier to track and analyze events.--### Event Count-The total number of times this event has been triggered across all users and sessions. High counts indicate frequent user actions around this feature or functionality.--### Unique Users-The number of distinct users who have triggered this event. This shows how many of your users interact with this specific feature or functionality.--### Conversion Rate-For key events (especially purchases), this shows what percentage of your total users or sessions resulted in this event. High conversion rates on important events indicate strong product-market fit.--### Average Value-If you track monetary value with your events (common for purchases), this shows the average transaction value.--### Event Properties-Custom data attached to each event. For example, a "Purchase" event might include properties like product_id, price, quantity, and category.--### First Triggered-When the first instance of this event occurred, showing how long you've been tracking this action.--### Last Triggered-The most recent time this event was triggered, indicating current user engagement with this feature.--## Filtering and Analyzing Events--Rybbit provides powerful filtering to help you understand specific events:--### Filter by Event Name-Focus on specific events you care about most. For example, analyze only "Purchase" events or "Feature A Activation" events.--### Filter by User-See which specific users triggered events, useful for understanding power users or investigating individual user journeys.--### Filter by Session-Analyze events within specific sessions to understand the context and sequence of user actions.--### Filter by Event Properties-Drill down into specific event details. For example, filter "Purchase" events by product category or price range.--### Filter by Time Range-Compare event trends across different time periods to measure growth, impact of changes, or seasonal patterns.--### Filter by Source-If tracking events from multiple sources (website, app, etc.), filter by source to analyze platform-specific behavior.--## Common Use Cases--### Measuring Conversion Funnel-Track events across your user journey (sign-up → feature activation → purchase) to measure conversion rates at each stage and identify where users drop off.--### Feature Adoption Tracking-Monitor how many users discover and use new features you've released. Low adoption might indicate the feature needs better onboarding or visibility.--### Understanding Feature Engagement-Track which features users interact with most frequently. This data guides your product roadmap and feature prioritization.--### Validating Product Changes-After making changes to your product, monitor event metrics to measure impact. Did the change increase desired actions or decrease undesired ones?--### Identifying Power Users-Find users who trigger many important events. These engaged users are valuable for retention and can provide product feedback.--### Analyzing User Workflow-Track the sequence of events users follow when accomplishing a goal. Optimization opportunities often appear when users take unexpected or inefficient paths.--### Debugging Issues-Monitor error events to identify when users encounter problems on your site. Spikes in error events might indicate a bug or performance issue.--### Measuring Marketing Campaign Impact-Track campaign-specific events to measure whether users from specific campaigns take desired actions at higher rates.--## Setting Up Event Tracking--Before you can analyze events, you need to track them. This typically involves:--1. **Identify Key Events**: Determine which user actions matter most to your business-2. **Implement Tracking**: Add event tracking code to your website using Rybbit's SDK or API-3. **Name Consistently**: Use clear, consistent names for your events (e.g., "purchase_completed" not "sale" or "checkout")-4. **Add Context**: Include relevant properties with events to provide additional context-5. **Test**: Verify events are firing correctly before relying on the data-6. **Monitor**: Regularly review event data to ensure tracking is working as expected--## Event Property Best Practices--When tracking custom events, include relevant properties to add context:--### For E-commerce Events-Include product_id, price, category, quantity, discount, currency, etc.--### For Sign-up Events-Include plan_type, source, location, device_type, etc.--### For Engagement Events-Include feature_name, action_type, duration, success, etc.--### For Error Events-Include error_type, error_message, page_path, severity, etc.--Include only relevant properties—more isn't always better. Cleaner events are easier to analyze and require less data storage.--## Analyzing Event Patterns--Look for patterns across your event data:--### Event Sequences-Do users typically trigger events in a specific sequence? Understanding natural workflows helps you optimize your user experience.--### Time Patterns-Do certain events spike at specific times of day or days of the week? This might indicate optimal times for marketing or feature releases.--### Cohort Differences-Do different user segments (by device, location, referrer) have different event patterns? This reveals optimization opportunities for specific groups.--### Conversion Funnel Efficiency-Track how users move through your conversion funnel. Where do most users drop off? What's the typical path for converters?--### Feature Engagement Trends-Do usage patterns for specific features increase or decrease over time? This guides feature maintenance and development priorities.--## Advanced Event Analysis Techniques--### Funnel Analysis-Manually analyze the sequence of events users trigger. For example: "view_product" → "add_to_cart" → "view_checkout" → "purchase_completed"--### Cohort Comparison-Compare event behavior between user cohorts (acquired at different times, from different sources, using different devices) to identify factors that drive engagement.--### Retention Analysis-For users who trigger important events (like "premium_upgrade"), track how their retention differs from other users over time.--### Lifetime Value Calculation-For monetization events, sum the total value generated by each user across all their events to calculate user lifetime value.--### Event Attribution-When users trigger important conversion events, trace back which previous events or sessions contributed to that conversion.--## Troubleshooting Event Tracking--### Events not appearing-Verify that tracking code is properly installed and that you're using the correct event names. Check browser console for JavaScript errors.--### Inconsistent event names-If the same action is tracked with different names (e.g., "signup" and "sign_up"), consolidate to a single name for cleaner analysis.--### Missing event properties-Ensure your tracking code includes relevant properties. Without properties, it's harder to analyze event context.--### Event counts seem low-Compare event counts to your overall traffic. If conversion events are below 1%, you may have product issues or incorrect tracking.--### Properties showing unexpected values-Validate that your code is passing the correct values to event properties. Test thoroughly before relying on the data.--## Privacy and Event Data--Rybbit's event tracking respects user privacy:--- Events don't require cookies-- PII (passwords, emails, credit cards) should never be included in events-- You control what data is collected through your event definitions-- Users can opt out of event tracking-- Event data follows the same retention policies as other analytics data--Configure PII masking to automatically redact sensitive information from event properties.--## Best Practices for Event Tracking--**Start Simple**: Begin with your most important events. Add more later as you understand your data needs.--**Use Consistent Naming**: Adopt a naming convention (e.g., verb_noun like "button_clicked," "form_submitted") and stick with it.--**Include Context**: Events are more useful when you understand the context. Include relevant properties.--**Test Thoroughly**: Before deploying tracking to production, verify events fire correctly in development.--**Document Your Events**: Keep a document listing all events you track, their names, and what properties they include.--**Monitor for Changes**: Periodically review event counts to spot unusual spikes or drops that might indicate tracking issues.--**Connect to Business Goals**: Ensure you're tracking events that actually relate to your business objectives.--## Connecting Events with Other Analytics--### Events and Users-Analyzing which users trigger which events helps you identify user segments and power users.--### Events and Sessions-Understanding events within the context of sessions shows how events relate to the overall user journey.--### Events and Errors-Correlation between user actions and errors can help you identify which features are causing issues.--## Conclusion--The Events tab in Rybbit's Behavior Analytics transforms your website into a feedback machine that shows you exactly what users are doing and whether they're achieving your business goals. By thoughtfully selecting what to track and analyzing the resulting data, you gain actionable insights that drive product improvement and business growth.--Start by identifying your most important user actions, implement tracking, and then regularly review the data to understand user behavior patterns. Over time, event data becomes an invaluable tool for measuring product success and guiding optimization efforts.--**Additional Resources:**-- [Track Custom Events Guide](/docs/track-events)-- [Users Tab Guide](/docs/behavior-analytics/users)-- [Sessions Tab Guide](/docs/behavior-analytics/sessions)-- [Errors Tab Guide](/docs/behavior-analytics/errors)-- [Product Analytics - Funnels Guide](/docs/product-analytics/funnels_guide)-- [Event Tracking Best Practices](/docs/track-events)-- [API - Sending Events](/docs/api/sending-events)-- [Blog: Churn Rate vs Retention Rate](/blog/churn-rate-vs-retention-rate)+- Click any event name to filter the dashboard to sessions containing that event+- Use the filter panel to combine event filters with other dimensions+- Filter by time range to analyze event trendsdiff --git a/docs/content/docs/behavior-analytics/sessions.mdx b/docs/content/docs/behavior-analytics/sessions.mdxindex 75945a713..a3e6e64fe 100644--- a/docs/content/docs/behavior-analytics/sessions.mdx+++ b/docs/content/docs/behavior-analytics/sessions.mdx@@ -1,188 +1,31 @@----title: Sessions Tab-description: A comprehensive guide to understanding and analyzing user sessions in Rybbit's Behavior Analytics+title: Sessions+description: Analyze individual user sessions----# A Guide to Rybbit's Sessions Tab+The Sessions tab shows individual user visits to your website, including all page views, interactions, and events during each session.-The Sessions tab in Rybbit's Behavior Analytics section provides deep insights into how users interact with your website during individual visits. Unlike traditional analytics that show aggregated metrics, the Sessions tab reveals the complete picture of individual user journeys, allowing you to understand exactly how your visitors navigate, engage, and convert on your site.+## Session Metrics-## What is a Session?+Each session displays:-A session represents a continuous period of user activity on your website. It includes all page views, interactions, events, and behavioral data from the moment a user arrives until they leave or become inactive. Sessions are fundamental to understanding user behavior because they capture the context and sequence of user actions rather than isolated data points.+- **Duration** - Time spent on site+- **Pages Visited** - Number of pages viewed+- **Events Triggered** - Custom events fired during the session+- **Device & Browser** - Technical environment+- **Location** - Geographic location based on IP+- **Entry/Exit Page** - Where the session started and ended+- **Bounce Status** - Whether the user left after one page-In Rybbit, sessions are tracked without cookies while still maintaining the privacy-first approach that defines our platform. Each session is identified through an anonymous identifier that allows you to replay and analyze user journeys without compromising privacy.+## Filtering Sessions-## Accessing the Sessions Tab+Filter by:-To view your site's sessions data:+- Duration, pages visited, or events triggered+- Device type, browser, or location+- Referrer or traffic source+- Date range-1. Log into your Rybbit dashboard-2. Navigate to the **Behavior** section in the left sidebar-3. Click on the **Sessions** tab+## Session Replay-You'll be presented with a comprehensive list of all sessions on your website, along with key metrics and filtering options to help you find the sessions most relevant to your analysis.--## Key Session Metrics--When examining the Sessions tab, you'll encounter several important metrics:--### Session Duration-The total length of time a user spends on your website during a single visit. Longer sessions generally indicate higher engagement, though this varies by website type. For example, a news site might have longer sessions than an e-commerce checkout flow.--### Pages Visited-The number of pages a user views during their session. This metric helps identify how much of your site visitors explore and can indicate whether your navigation and content discovery are effective.--### Events Triggered-The count of custom events that occurred during the session. Events might include button clicks, form submissions, video plays, or any other tracked interactions you've configured in Rybbit.--### Device & Browser-Information about the device and browser used during the session. This helps you understand your audience's technical environment and identify any device-specific issues.--### Location-The geographic location of the user based on IP address. This provides valuable insights into your geographic audience distribution and can help with localization efforts.--### Entry Page-The first page the user visited in the session. Understanding entry pages reveals which content attracts visitors and can guide your SEO and marketing strategies.--### Exit Page-The last page before the user left your site. Exit pages are critical for identifying where users abandon their journey, which can indicate problem areas that need optimization.--### Bounce Status-Whether the user bounced (left the site after viewing only one page). High bounce rates on specific pages often indicate issues with content relevance, page load speed, or user experience.--## Filtering and Searching Sessions--Rybbit provides powerful filtering capabilities to help you find the sessions most relevant to your analysis:--### Filter by Duration-Find sessions within a specific time range. For example, you might focus on users who spent more than 5 minutes on your site, indicating high engagement.--### Filter by Page-Analyze sessions that include specific pages. This is useful for understanding user behavior around particular content or features.--### Filter by Events-Search for sessions that contain specific events. For instance, find all sessions where users triggered a "Purchase" event to understand successful customer journeys.--### Filter by Device-Isolate sessions from specific devices (desktop, mobile, tablet) to identify device-specific user behavior patterns.--### Filter by Browser-Examine sessions from specific browsers to diagnose browser-specific issues or understand browser preferences in your audience.--### Filter by Location-Segment sessions by geographic location to understand regional user behaviors and preferences.--### Filter by Referrer-Find sessions from specific traffic sources. This helps you understand which marketing channels and referral sources drive quality traffic.--### Filter by Date Range-Use custom date ranges to compare user behavior across different time periods, seasonal trends, or after implementing changes to your site.--## Analyzing Session Patterns--The Sessions tab becomes most powerful when you look for patterns across multiple sessions:--### High-Engagement Sessions-Identify users who spend significant time on your site, visit many pages, and trigger important events. These sessions often represent your most engaged users and can reveal what's working well on your site.--### Problem Sessions-Look for patterns in sessions with high bounce rates or quick exits. Sessions where users visited critical pages but then left immediately might indicate usability issues or missing information.--### Conversion Paths-Track the typical sequence of pages and events that lead to conversions. Understanding the conversion path helps you optimize the user journey and remove friction.--### Feature Discovery-Monitor sessions to see which features users discover and interact with. Low usage of certain features might indicate poor discoverability or unclear value proposition.--## Common Use Cases--### Debugging User Experience Issues-When users report problems on your site, the Sessions tab allows you to replay their exact experience and understand what went wrong.--### Identifying Bottlenecks-Look for sessions where users get stuck or abandon the process. Common bottlenecks include complex forms, slow-loading pages, or confusing navigation.--### Validating Feature Changes-After implementing new features or redesigning sections of your site, compare session patterns before and after the change to measure impact.--### Understanding Traffic Quality-Sessions from high-quality traffic sources typically show longer duration, more pages visited, and higher conversion rates. Use this to optimize your marketing spend.--### Improving Onboarding-Analyze sessions from first-time visitors to see where they get confused or drop off. Improving onboarding reduces churn among new users.--### Optimizing for Mobile-Compare sessions on mobile devices versus desktop to identify mobile-specific issues. Many sites see dramatic differences in session quality between devices.--## Session Privacy Considerations--Rybbit's Sessions tab maintains privacy-first principles:--- Sessions are identified anonymously without requiring cookies-- Personal information like passwords, credit card numbers, and sensitive form data can be masked using Rybbit's PII protection features-- Users can opt out of session tracking without affecting other analytics-- Session data is retained according to your configured data retention policy--You can customize PII masking rules to ensure sensitive information is never recorded, even in sessions.--## Tips for Effective Session Analysis--**Look Beyond Averages**: A high average session duration might hide the fact that some users bounce immediately while others stay for hours. Segment your data to understand the distribution.--**Compare Cohorts**: Compare session patterns between different user segments (by device, location, traffic source) to identify where improvements are needed.--**Correlate with Events**: Cross-reference sessions with important events to understand which behaviors lead to conversions or desired outcomes.--**Monitor Over Time**: Track how session metrics change over time. Improvements in engagement metrics often precede changes in conversion rates.--**Use with Session Replay**: While the Sessions tab shows aggregate metrics, pair it with individual session replays (if enabled) to see exactly what users are doing.--**Test and Iterate**: Use session insights to identify problems, implement fixes, then monitor whether new session metrics improve.--## Troubleshooting Common Issues--### No session data appearing-Ensure the Rybbit tracking script is properly installed on your website and that you've waited for some user traffic to accumulate.--### Session durations seem incorrect-Session timeout is typically 30 minutes of inactivity. If a user closes their browser, that session ends even if they return the next day.--### Missing sessions from certain browsers-Check browser console for JavaScript errors that might prevent tracking. Some browser extensions block tracking scripts.--### Unexpected location data-IP-based geolocation has inherent limitations and occasional inaccuracies. Location data should be used as an approximation rather than an exact science.--## Advanced Analysis Techniques--### Funnel Analysis through Sessions-Identify the sequence of pages users visit before converting. Create a mental model of your conversion funnel by observing which page sequences are most common in converting sessions.--### Session Segmentation-Create mental segments of users based on session characteristics:-- **Browsers**: Users who quickly scan content-- **Explorers**: Users who visit many pages-- **Converters**: Users who complete desired actions-- **Bouncers**: Users who leave after one page--Each segment may require different optimization strategies.--### Behavioral Cohorts-Compare sessions from different time periods or traffic sources to identify behavioral differences that might explain performance variations.--## Conclusion--The Sessions tab in Rybbit's Behavior Analytics is a powerful tool for understanding your users. By examining session patterns, metrics, and behaviors, you can identify opportunities for optimization, diagnose problems, and ultimately build a better experience for your users.--Start by exploring your most recent sessions, look for patterns among high-engagement and low-engagement users, and use those insights to guide your optimization efforts. Paired with other analytics features like event tracking and behavior flow analysis, the Sessions tab gives you a complete understanding of how users interact with your website.--**Additional Resources:**-- [Getting Started with Rybbit Analytics](/docs)-- [Users Tab Guide](/docs/behavior-analytics/users)-- [Events Tab Guide](/docs/behavior-analytics/events)-- [Errors Tab Guide](/docs/behavior-analytics/errors)-- [Track Custom Events](/docs/track-events)-- [Product Analytics - Retention Guide](/docs/product-analytics/retention_guide)-- [Session Replay Guide](/docs/product-analytics/replay-session)-- [API - Sending Events](/docs/api/sending-events)+If [session replay](/docs/product-analytics/replay-session) is enabled, you can watch a recording of any session to see exactly what the user did.diff --git a/docs/content/docs/behavior-analytics/users.mdx b/docs/content/docs/behavior-analytics/users.mdxindex 92c533c16..c4969be2c 100644--- a/docs/content/docs/behavior-analytics/users.mdx+++ b/docs/content/docs/behavior-analytics/users.mdx@@ -1,225 +1,31 @@----title: Users Tab-description: A comprehensive guide to understanding and analyzing individual users in Rybbit's Behavior Analytics+title: Users+description: Analyze individual users across sessions----# A Guide to Rybbit's Users Tab+The Users tab shows unique visitors and their behavior across multiple sessions.-The Users tab in Rybbit's Behavior Analytics section provides detailed insights into the individual people visiting your website. While traditional analytics often focuses on aggregated metrics and traffic patterns, the Users tab shifts the perspective to show you who your visitors are, their behaviors, engagement patterns, and how they interact with your site over time.+## User Metrics-## What is a User?+For each user, you'll see:-A user in Rybbit represents a unique visitor to your website. Unlike cookie-based analytics, Rybbit identifies users through privacy-first mechanisms that don't compromise visitor privacy. Each user is assigned a unique identifier that allows you to track their behavior across multiple sessions without using cookies.+- **User ID** - Anonymized identifier+- **First/Last Visit** - When they first and most recently visited+- **Total Sessions** - Number of separate visits+- **Pages Viewed** - Total pages across all sessions+- **Events Triggered** - Total custom events+- **Device Type** - Desktop, mobile, or tablet+- **Location** - Geographic location-Understanding users is fundamental to modern analytics because it allows you to move beyond "how many people visited" to answer more meaningful questions like "who are my users," "what do they do," and "how can I better serve them."+## Filtering Users-## Accessing the Users Tab+Filter by:-To view your site's user data:+- Number of sessions or page views+- Specific events triggered+- Device type or location+- First visit or last activity date-1. Log into your Rybbit dashboard-2. Navigate to the **Behavior** section in the left sidebar-3. Click on the **Users** tab+## Identified Users-You'll be presented with a comprehensive list of unique visitors along with key information about each user, their activity, and engagement metrics.--## Key User Metrics--When examining the Users tab, you'll find several important metrics about each user:--### User ID-A unique, anonymized identifier for each visitor. This ID allows you to track a user across multiple sessions and devices (if they use the same browser).--### First Visit-The date and time when the user first visited your website. This helps you understand user acquisition patterns and identify your oldest engaged users.--### Last Visit-The most recent date and time the user visited your site. This metric indicates user retention and helps identify dormant or churned users.--### Total Sessions-The number of separate visits the user has made to your website. Users with more sessions are generally more engaged and loyal.--### Pages Viewed-The total number of pages visited across all sessions by this user. High page view counts often indicate strong engagement with your content.--### Events Triggered-The total number of custom events (like button clicks, form submissions, or purchases) triggered by this user across all their sessions.--### Device Type-The type of device(s) the user has accessed your site from (desktop, mobile, tablet). Some users may appear multiple times if they visit from different devices.--### Location-The geographic location where the user accessed your site, based on IP address geolocation.--### Referrer-How the user initially arrived at your site (organic search, paid ads, social media, direct, etc.).--### Last Activity-The type of action the user took during their most recent visit (page view, event triggered, scroll, etc.).--## Filtering and Searching Users--Rybbit provides powerful filtering options to help you segment and analyze specific user groups:--### Filter by Total Sessions-Find users who have visited your site a specific number of times. For example, identify one-time visitors versus loyal users who return frequently.--### Filter by Page Views-Isolate users based on how many pages they've viewed. This helps identify power users who deeply engage with your content versus casual browsers.--### Filter by Events-Search for users who have triggered specific events. For instance, find all users who have completed a purchase or signed up for a newsletter.--### Filter by Device-Segment users by their device type (desktop, mobile, tablet) to understand usage patterns across different platforms.--### Filter by Location-Analyze users from specific geographic regions or countries to understand your global audience and identify regions for growth.--### Filter by Referrer-Find users who arrived from specific traffic sources to understand which channels bring high-quality visitors.--### Filter by Activity Date-Isolate users who visited within a specific time period. This helps identify recently active users versus historical users.--### Filter by First Visit Date-Find users who discovered your site within a specific timeframe. This is useful for measuring the impact of marketing campaigns or product launches.--## Analyzing User Behavior Patterns--The Users tab becomes most powerful when you identify and analyze patterns across user groups:--### High-Value Users-Identify users who visit frequently, view many pages, and trigger important events. These power users often provide the most value and should be prioritized in retention efforts.--### One-Time Visitors-Find users who visited only once and didn't return. Understanding why these visitors churn can help you improve your onboarding and value proposition.--### Device-Specific Users-Look for patterns in how different user groups use different devices. Some users may primarily access your site on mobile while others prefer desktop.--### Geographic Patterns-Analyze user behavior by location to identify regional differences in engagement, preferences, and conversion patterns.--### Traffic Source Quality-Compare users from different referrers to determine which marketing channels and traffic sources bring the most engaged and valuable users.--## Common Use Cases--### Understanding User Retention-Track how many users return to your site over time. Compare new users versus returning users to measure customer loyalty and identify churn risks.--### Identifying High-Value Customers-Find users who have completed valuable actions (purchases, sign-ups, upgrades) and analyze what they have in common. Use these patterns to identify similar users for targeted outreach.--### Improving New User Onboarding-Analyze the behavior of first-time visitors to see where they struggle or drop off. Use these insights to streamline your onboarding experience.--### Measuring Marketing Campaign Effectiveness-Compare users acquired through different marketing channels to determine which campaigns bring the most engaged and valuable users.--### Optimizing for Key User Segments-Identify your most valuable user segments (by geography, device, behavior) and optimize your product and marketing specifically for them.--### Detecting Bot or Spam Activity-Look for unusual user behavior patterns that might indicate bots or malicious activity, such as users triggering hundreds of events in seconds.--## User Privacy and Data Protection--Rybbit's Users tab maintains strict privacy standards:--- User identification is anonymous and doesn't rely on cookies-- No personally identifiable information (PII) is collected without explicit consent-- Users can opt out of tracking at any time-- All user data is encrypted and stored securely-- User data retention follows GDPR and CCPA compliance standards--You maintain full control over your user data with options for self-hosting and complete data ownership.--## Tips for Effective User Analysis--**Segment by Behavior, Not Just Demographics**: While location and device data is useful, segmenting by behavior (pages viewed, events triggered) often reveals more actionable insights.--**Look for First-Time User Patterns**: Understanding how new users interact differently from returning users can dramatically improve your onboarding and activation rates.--**Track User Lifecycle**: Monitor how individual users progress through different stages (awareness, engagement, conversion, retention). Use this to identify drop-off points and opportunities.--**Correlate with Business Metrics**: Connect user data with your business outcomes. Which user segments generate the most revenue, sign-ups, or other valuable actions?--**Monitor Emerging Segments**: Regularly check the Users tab for new patterns. Emerging user segments sometimes represent new market opportunities.--**Compare Before and After Changes**: When you make changes to your site or product, monitor how user behavior patterns change to measure impact.--## Troubleshooting Common Issues--### Missing user data-Ensure the Rybbit tracking script is installed and that your privacy settings allow user identification. Some strict privacy settings may disable user-level tracking.--### Users appearing multiple times-This typically happens when users visit from different browsers or devices. This is expected behavior in Rybbit's privacy-first approach.--### Unexpected user counts-If user numbers seem low, check that your traffic is actually being tracked. Verify the script is loading correctly and no content blockers are interfering.--### Location data seems inaccurate-IP-based geolocation has inherent limitations. Location should be used as an approximation, particularly for mobile users.--## Advanced User Analytics--### User Cohort Analysis-Group users by when they first visited (weekly, monthly cohorts) and track how retention and engagement differ. This helps you understand if recent traffic quality differs from historical users.--### User Lifetime Value (LTV)-For users who complete valuable actions (purchases), calculate their lifetime value by tracking their total contribution over all sessions. This helps prioritize high-value user retention.--### Activation Analysis-Track the path new users take to reach their first meaningful action (first page view, event, conversion). Users who activate quickly are more likely to become long-term users.--### Churn Prediction-Monitor users who haven't visited recently. Users with long gaps between visits are at higher risk of permanent churn. Consider re-engagement campaigns for these users.--### User Segmentation Strategies-Create mental models of different user types:-- **Casual Browsers**: Few sessions, low engagement-- **Regular Users**: Consistent visits, moderate engagement-- **Power Users**: Frequent visits, high engagement, multiple events-- **Converters**: Users who complete valuable actions--Each segment may require different optimization strategies.--## Connecting Users with Other Analytics--### Users and Sessions-Each user typically has multiple sessions. Use the Sessions tab to understand the specific behavior within individual user sessions.--### Users and Events-Custom events provide context for user behavior. Correlate user segments with the events they trigger to understand motivation and satisfaction.--### Users and Errors-If enabled, error tracking shows which users are experiencing issues. Investigate error patterns to improve product quality.--## Best Practices--**Privacy-First Approach**: Always remember that behind every user ID is a real person. Respect their privacy and use data responsibly.--**Focus on Actionable Segments**: Don't just identify segments—use insights to make concrete changes to improve their experience.--**Regular Monitoring**: Check the Users tab regularly to spot emerging trends, new user segments, or changing behavior patterns.--**Balance Quantitative and Qualitative**: Pair user metrics with qualitative feedback (surveys, support tickets) for a complete understanding.--## Conclusion--The Users tab in Rybbit's Behavior Analytics transforms raw traffic data into human-centered insights. By understanding who your users are, how they behave, and what drives their engagement, you can build a better product and marketing strategy.--Start by exploring your recent users, identify your most engaged and valuable users, and use those patterns to guide your optimization efforts. Combined with session analysis and event tracking, user data gives you a complete picture of how people interact with your website.--**Additional Resources:**-- [Sessions Tab Guide](/docs/behavior-analytics/sessions)-- [Events Tab Guide](/docs/behavior-analytics/events)-- [Errors Tab Guide](/docs/behavior-analytics/errors)-- [Track Custom Events](/docs/track-events)-- [Product Analytics - Retention Guide](/docs/product-analytics/retention_guide)-- [User Cohort Analysis](/docs/product-analytics/journeys_dashboard)-- [Getting Started with Rybbit Analytics](/docs)-- [Blog: Churn Rate vs Retention Rate](/blog/churn-rate-vs-retention-rate)+If you use the [identify API](/docs/identify-users), you can see your own user IDs alongside the anonymous identifiers.diff --git a/docs/content/docs/guides/google-tag-manager.mdx b/docs/content/docs/guides/google-tag-manager.mdxindex c7c02b03c..d871e7454 100644--- a/docs/content/docs/guides/google-tag-manager.mdx+++ b/docs/content/docs/guides/google-tag-manager.mdx@@ -33,7 +33,6 @@ However, GTM sanitizes script tags by removing non-standard HTML attributes like(function() {var el = document.createElement("script");el.src = "https://app.rybbit.io/api/script.js";- el.async = true;el.defer = true;el.setAttribute("data-site-id", "YOUR_SITE_ID");document.head.appendChild(el);diff --git a/docs/content/docs/meta.json b/docs/content/docs/meta.jsonindex 24f563233..80c8faf6e 100644--- a/docs/content/docs/meta.json+++ b/docs/content/docs/meta.json@@ -7,6 +7,7 @@"self-host-vs-cloud","---Usage---","script",+ "script-troubleshooting","track-events","identify-users","guides",diff --git a/docs/content/docs/product-analytics/funnels_guide.mdx b/docs/content/docs/product-analytics/funnels_guide.mdxindex 97a81bb3a..ca8d2d081 100644--- a/docs/content/docs/product-analytics/funnels_guide.mdx+++ b/docs/content/docs/product-analytics/funnels_guide.mdx@@ -1,412 +1,48 @@----title: Funnels-description: Understanding Rybbit's funnels tab+title: Funnels+description: Track conversion through multi-step processes----# Understanding Funnel Analysis in Rybbit+-This guide will help you understand how to measure conversion rates, identify where users drop off, and optimize the paths that lead to your most important business outcomes.+Funnels track users as they move through a series of steps toward a goal, showing where users convert and where they drop off.-<img src="/blog/rybbit_funnels_dashboard.png" alt="Rybbit's Funnel dashboard" />+## Creating a Funnel+Click "Create Funnel" and define your steps. Each step can be:+- **Path** - A URL path (e.g., `/pricing`, `/checkout`)+- **Event** - A custom event name (e.g., `signup_clicked`, `purchase_completed`)-## What is Funnel Analysis?+### Step Configuration-Funnel analysis is the process of tracking users as they move through a series of steps toward a specific goal. Whether that goal is completing a purchase, signing up for an account, finishing onboarding, or any other important action, funnel analysis shows you exactly where users succeed and where they abandon the process.+For each step, you can configure:+- **Type** - Path or Event+- **Value** - The path pattern or event name+- **Label** (optional) - A friendly name for the step+- **Hostname** (optional) - Filter to a specific domain+- **Property Filters** (optional) - Match specific URL parameters or event properties-Think of it like watching water flow through a physical funnel. You pour water in at the top, but some leaks out at various points along the way. By the time the water reaches the bottom, you're left with less than you started with. The same thing happens with users on your website or app. Many start a process, but fewer complete it. Funnel analysis helps you identify those "leaks" so you can plug them.+### Wildcards-## Why Funnel Analysis Matters+Use wildcards in path patterns:+- `*` matches a single path segment (e.g., `/blog/*` matches `/blog/post-1`)+- `**` matches multiple segments (e.g., `/docs/**/intro` matches `/docs/api/v2/intro`)-Funnel analysis is one of the most powerful tools in your analytics toolkit because it directly impacts your bottom line. Here's why it matters:+## Funnel Metrics-**Measure what actually drives revenue.** Unlike general traffic metrics, funnel analysis focuses on the specific actions that lead to business outcomes. You're not just counting visitors; you're measuring how many people actually do the things that matter.+For each step:+- **Sessions** - How many sessions reached this point+- **Conversion Rate** - Percentage of the first step that reached this step+- **Dropped** - How many sessions dropped off before this step-**Find your biggest opportunities.** When you can see exactly where users drop off, you know precisely where to focus your optimization efforts. Why guess at what needs fixing when the data can tell you?+The visualization shows two bars:+- **Solid bar** - Overall conversion from the first step+- **Striped bar** - Conversion from the previous step-**Quantify the impact of changes.** After you make improvements, funnel analysis shows you whether those changes actually worked. Did that new checkout flow increase conversions? The funnel will tell you.+## Viewing Sessions-**Understand the full picture.** Individual page metrics only show part of the story. Funnel analysis reveals how the entire sequence of steps works together, helping you optimize the complete experience rather than just isolated touchpoints.+Click any step to expand it and view:+- **Reached** - Sessions that completed this step+- **Dropped Off** - Sessions that completed the previous step but not this one-## Anatomy of a Funnel--Every funnel in Rybbit consists of a series of steps that users must complete in sequence to reach your goal. Let's break down what you'll see:--### Steps--Each step in your funnel represents a specific action or page view. For an e-commerce checkout funnel, your steps might be:-1. View product page-2. Add item to cart-3. Begin checkout-4. Enter shipping information-5. Complete payment--For a SaaS signup funnel, it might look like:-1. Visit pricing page-2. Click signup button-3. Fill out registration form-4. Verify email-5. Complete onboarding--You define these steps based on what matters for your specific conversion goal.--### Users at Each Step--For each step, Rybbit shows you how many users reached that point. This number will typically decrease as you move down the funnel because not everyone who starts will complete every step.--### Conversion Rate--This critical metric shows you what percentage of users successfully moved from one step to the next. If 1,000 users viewed a product page and 300 added it to cart, your conversion rate from step 1 to step 2 is 30%.--### Drop-off Rate--The flip side of conversion rate, drop-off rate shows what percentage of users left without completing the next step. In the example above, the drop-off rate would be 70%. This metric highlights where you're losing the most users.--### Overall Conversion Rate--This shows the percentage of users who completed the entire funnel from start to finish. If 1,000 users started and 50 completed the final step, your overall conversion rate is 5%. This is your key performance indicator for the funnel as a whole.--## Reading Your Funnel Visualization--Rybbit presents funnel data in an intuitive visual format that makes patterns immediately obvious:--### The Funnel Shape--The classic funnel visualization narrows as you move from top to bottom, with each step visually representing the number of remaining users. The width of each section corresponds to the volume of users, making drop-offs instantly visible.--### Color Coding--Many funnel visualizations use color to highlight performance. Green might indicate healthy conversion rates, while yellow or red highlight problem areas where drop-offs are unusually high.--### Numbers and Percentages--At each step, you'll see both absolute numbers (how many users) and percentages (what proportion of the previous step). Both metrics are important for understanding your funnel's performance.--## Identifying Problems in Your Funnel--Once you have your funnel set up, the real work begins: finding and fixing issues. Here's what to look for:--### Steep Drop-offs--The most obvious red flag is a step where a large percentage of users abandon the process. If 80% of users drop off at a particular step, that's screaming for your attention. Something at that step is creating significant friction.--Common causes of steep drop-offs include:-- Confusing or unclear instructions-- Technical errors or bugs-- Requests for too much information too soon-- Slow page load times-- Unexpected costs or requirements-- Poor mobile experience-- Lack of trust signals (security badges, testimonials, etc.)--### Gradual Erosion--Sometimes the problem isn't one dramatic drop-off but rather consistent erosion throughout the funnel. If every step loses 30-40% of users, your overall conversion rate suffers even though no single step looks terrible. This pattern suggests a broader issue with user motivation, the value proposition, or the overall user experience.--### Comparison to Benchmarks--What constitutes a "good" conversion rate varies by industry, funnel type, and step position. Generally:-- Early steps should have higher conversion rates (70-90%)-- Middle steps might range from 40-70%-- Final steps (like payment) often see 60-80% conversion--However, these are just rough guidelines. The most important benchmark is your own performance over time. Are your conversion rates improving or declining?--### Time-based Patterns--Look at how your funnel performs across different time periods. Do conversion rates drop on weekends? Are mobile users dropping off more than desktop users? Does the funnel perform differently by traffic source? These patterns reveal opportunities for targeted improvements.--## Strategies for Improving Your Funnel--Once you've identified problems, it's time to fix them. Here are proven strategies for improving conversion rates:--### Reduce Friction--Friction is anything that makes it harder for users to complete a step. To reduce friction:-- Minimize the number of form fields-- Remove unnecessary steps entirely-- Enable autofill for forms-- Provide clear, simple instructions-- Fix technical issues and errors-- Improve page load speed-- Simplify navigation--The golden rule: every additional field, click, or second of loading time reduces conversions. Be ruthless about eliminating anything that doesn't absolutely need to be there.--### Build Trust and Credibility--Users hesitate when they don't trust you. To build trust:-- Display security badges and certifications-- Show customer testimonials and reviews-- Include clear privacy policies-- Be transparent about pricing and terms-- Provide contact information-- Use professional design and copy-- Show real photos and authentic content--Trust is especially critical at steps involving personal information or payment.--### Clarify Value and Reduce Uncertainty--Users abandon when they're unsure about what they're getting or what happens next. To clarify:-- Clearly state what users will receive-- Show progress indicators so they know how many steps remain-- Preview what comes next before asking for commitment-- Provide examples or samples-- Answer common questions proactively-- Set clear expectations about timing, pricing, and process--### Optimize for Mobile--If your funnel shows significantly worse performance on mobile devices, prioritize mobile optimization:-- Use large, tappable buttons-- Simplify forms for small screens-- Ensure fast mobile load times-- Test the entire flow on actual mobile devices-- Consider mobile-specific features like Apple Pay or Google Pay--### Address Specific Objections--For each drop-off point, think about what specific concerns or objections users might have:-- Is the price higher than expected? Consider showing value or offering payment plans.-- Is the commitment too large? Offer a trial or money-back guarantee.-- Is the process taking too long? Show progress and reduce steps.-- Do users need more information? Provide FAQs or chat support.--### Test Everything--The only way to know if your improvements actually work is to test them. Use A/B testing to compare different versions of problematic steps:-- Test different copy and headlines-- Try various form layouts-- Experiment with button colors, sizes, and placement-- Test different value propositions-- Try adding or removing elements--Let the data tell you what works rather than relying on assumptions.--## Advanced Funnel Analysis Techniques--Once you're comfortable with basic funnel analysis, these advanced techniques can provide deeper insights:--### Segmentation--Don't just look at your funnel in aggregate. Segment it by:-- Traffic source (organic, paid, referral, direct)-- Device type (mobile, tablet, desktop)-- User type (new vs. returning)-- Geographic location-- Time of day or day of week--Different segments often behave very differently. Understanding these differences helps you create targeted improvements.--### Cohort Analysis--Track how funnel performance changes over time by analyzing cohorts of users who entered the funnel during specific time periods. This helps you:-- Measure the impact of specific changes-- Identify seasonal patterns-- Spot gradual improvements or degradation-- Understand if recent users behave differently than historical users--### Micro-conversions--In addition to your main funnel, track smaller actions that indicate engagement and interest:-- Time spent on page-- Interactions with key elements-- Video views-- Content downloads-- Feature usage--These micro-conversions help you understand user intent and identify engaged users who might just need a little extra push to convert.--### Multi-path Funnels--Sometimes users don't follow your intended path. They might skip steps, complete them in different orders, or take alternative routes. Setting up multiple funnel variations helps you understand these alternative journeys and optimize them too.--## Common Funnel Types and Their Benchmarks--Different types of funnels have different characteristics. Here's what to expect:--### E-commerce Checkout Funnel--Typical steps: Product page → Add to cart → Checkout → Payment → Confirmation--Average overall conversion: 2-5%--Common drop-off points:-- Adding to cart (users browsing vs. buying)-- Entering shipping information (friction point)-- Payment (final hesitation before commitment)--### SaaS Signup Funnel--Typical steps: Landing page → Signup form → Email verification → Onboarding → First use--Average overall conversion: 10-30% (highly variable)--Common drop-off points:-- Signup form (too many fields)-- Email verification (friction, users lose momentum)-- Onboarding (complexity, unclear value)--### Lead Generation Funnel--Typical steps: Landing page → Form submission → Confirmation → Follow-up engagement--Average overall conversion: 10-40% (depends heavily on offer quality)--Common drop-off points:-- Form submission (asking for too much information)-- Follow-up engagement (poor nurturing, timing issues)--### Content Engagement Funnel--Typical steps: Homepage → Article view → Newsletter signup → Content download--Average overall conversion: 5-15%--Common drop-off points:-- Newsletter signup (value proposition unclear)-- Content download (too much friction for the perceived value)--## Time Dimensions in Funnel Analysis--Understanding the time aspect of your funnels is crucial. Rybbit lets you analyze funnels across different time dimensions:--### Session-based Funnels--These track users completing all steps within a single session (typically defined as continuous activity without a 30-minute gap). Session-based funnels are ideal for:-- Quick processes like checkout flows-- Single-visit conversion goals-- Measuring immediate conversion intent--### Time-window Funnels--These allow users to complete steps across multiple sessions within a defined time period (hours, days, or weeks). Time-window funnels are better for:-- Complex decisions with research phases-- Multi-day consideration processes-- B2B conversions with longer sales cycles--Choose the right time dimension for your specific use case. An impulse purchase funnel should be session-based, while a SaaS trial conversion might need a 14-day window.--## Setting Up Effective Funnels--To get the most value from funnel analysis, set up your funnels thoughtfully:--### Start with Your Goal--Work backward from your most important business outcome. What is the critical action you want users to take? That's your final step.--### Identify Key Milestones--Between your starting point and goal, what are the essential steps users must complete? Don't include every single page view; focus on the meaningful milestones that represent progress toward your goal.--### Keep it Simple--Start with 3-5 steps. You can always create more detailed funnels later, but begin with the core journey. Too many steps make analysis overwhelming and dilute your focus.--### Define Steps Clearly--Make sure each step represents a distinct, measurable action. Vague definitions lead to confusing data.--### Consider Multiple Funnels--You probably have several important conversion goals. Create separate funnels for each:-- Purchase funnel-- Signup funnel-- Onboarding funnel-- Feature adoption funnel-- Renewal or upgrade funnel--Each funnel tells a different story about your user experience.--## Connecting Funnels to Business Outcomes--The ultimate goal of funnel analysis isn't just to improve conversion rates. It's to drive business results. Here's how to connect your funnel insights to outcomes:--### Calculate Revenue Impact--When you improve a conversion rate, calculate the revenue impact. If increasing your checkout completion rate from 60% to 65% means 50 more purchases per month at an average order value of $100, that's $5,000 in additional monthly revenue. This helps you prioritize improvements and demonstrate ROI.--### Understand Customer Acquisition Cost (CAC)--Funnel analysis helps you understand the true cost of acquiring customers. If you're spending $10,000 on ads that bring 5,000 visitors to your signup funnel, and only 100 complete signup, your CAC is $100. Improving your funnel conversion rate directly reduces your CAC.--### Improve Lifetime Value (LTV)--Users who successfully complete onboarding funnels typically have higher lifetime value. By optimizing these early experiences, you're not just increasing immediate conversions but also improving long-term customer value.--### Reduce Support Costs--Confusing funnels generate support tickets. When you smooth out the rough patches in your conversion process, you reduce the burden on your support team and improve the customer experience.--## Common Mistakes to Avoid--Even experienced teams make these funnel analysis mistakes:--### Optimizing the Wrong Steps--Focus on the steps with the biggest drop-offs AND the most users. Improving a step that only 10 users reach doesn't matter much. Prioritize improvements where you have volume.--### Ignoring Mobile vs. Desktop Differences--Your funnel might look fine on desktop and terrible on mobile (or vice versa). Always analyze device-specific performance.--### Making Too Many Changes at Once--If you change five things simultaneously and conversions improve, you won't know which change worked. Test iteratively so you can learn from each improvement.--### Not Considering User Intent--Not everyone who enters your funnel intends to convert. Some users are just browsing, researching, or comparing. A 3% conversion rate might actually be excellent if 95% of users are just looking. Context matters.--### Forgetting About User Experience--You can optimize a funnel to death by removing every possible barrier, but if the result is a terrible user experience that damages trust or brand perception, you've made a mistake. Balance conversion optimization with user satisfaction.--### Analyzing Too Infrequently--Funnels need regular monitoring. Check your key funnels at least weekly. Set up alerts for significant changes in conversion rates so you can respond quickly to problems.--## Taking Action on Your Insights--Data without action is just trivia. Here's how to move from analysis to improvement:--**Prioritize based on impact.** Which improvements will generate the most additional conversions? Start there.--**Create hypotheses.** Don't just identify problems; form specific theories about why users drop off and what might fix it.--**Test systematically.** Implement changes one at a time (or use proper A/B testing) so you can measure their impact.--**Document your learnings.** Keep track of what you've tested, what worked, and what didn't. This institutional knowledge is valuable.--**Share insights across teams.** Funnel insights aren't just for analysts. Share them with designers, developers, marketers, and product managers so everyone understands where improvements are needed.--**Celebrate wins.** When you successfully improve a funnel, make sure the team knows. Positive reinforcement encourages continued optimization efforts.--## Conclusion--Funnel analysis is both science and art. The science is in the data: the conversion rates, drop-off percentages, and user counts. The art is in interpretation: understanding why users behave certain ways and what changes will make a difference.--As you work with your funnels in Rybbit, remember that every funnel tells a story about your users' experience. Some stories are success stories about smooth, frictionless paths to conversion. Others are cautionary tales about confusion, frustration, and abandonment. Your job is to listen to what the data is telling you and rewrite those stories to have happier endings.--If you have questions about setting up funnels, interpreting your data, or need help troubleshooting a particularly stubborn conversion problem, our support team is here to help. We've seen thousands of funnels and can often spot patterns and opportunities that might not be immediately obvious.--Start with one important conversion goal, set up a funnel to measure it, identify your biggest drop-off point, and make one improvement. Then measure the results and iterate. That simple cycle, repeated consistently, is how great products get built and successful businesses grow.-------**Related Reading:**-- [Product Analytics - Retention Guide](/docs/product-analytics/retention_guide)-- [Product Analytics - Journeys Dashboard](/docs/product-analytics/journeys_dashboard)-- [Behavior Analytics - Events Tab](/docs/behavior-analytics/events)-- [Behavior Analytics - Sessions Tab](/docs/behavior-analytics/sessions)-- [Track Custom Events](/docs/track-events)-- [Blog: Churn Rate vs Retention Rate](/blog/churn-rate-vs-retention-rate)-- [Blog: E-commerce Analytics](/blog/ecommerce-analytics)--## Questions about any feature?--- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)\ No newline at end of file+This helps you investigate why users drop off at specific points.diff --git a/docs/content/docs/product-analytics/journeys_dashboard.mdx b/docs/content/docs/product-analytics/journeys_dashboard.mdxindex fd91a867c..4ac494bba 100644--- a/docs/content/docs/product-analytics/journeys_dashboard.mdx+++ b/docs/content/docs/product-analytics/journeys_dashboard.mdx@@ -1,251 +1,39 @@---title: User Journeys-description: Understanding Rybbit's user journey tab+description: Visualize how users navigate your site----# Understanding User Journeys in Rybbit+-This guide will help you understand how users navigate through your website or app, identify where they get stuck, and discover the paths that lead to your most important outcomes.+User journeys show the actual paths people take as they move through your website, revealing how they flow from page to page.-<img src="/blog/rybbit_journey_dashboard.png" alt="Rybbit's dashboard" />--## What Are User Journeys?--User journeys represent the actual paths people take as they move through your website or application. Instead of looking at isolated pageviews or events, journey analysis shows you the sequence of actions users take, revealing how they flow from one page or feature to another.--Think of it like watching footprints in the sand. You can see where people started, which direction they went, where they paused, and ultimately where they ended up. This complete view helps you understand not just what users do, but how they navigate and why they might be getting stuck.--## Why Journey Analysis Matters--Understanding user journeys gives you insights that simple traffic metrics can't provide:--**Discover unexpected behavior.** Users rarely follow the exact path you designed. Journey analysis reveals the routes people actually take, which might surprise you. Maybe users are navigating to your pricing page from an unexpected source, or perhaps they're taking a circuitous route to find information that should be easier to access.--**Identify friction points.** When you see where users commonly drop off or backtrack, you've found friction in your experience. These are the moments where your design, content, or functionality isn't meeting user needs.--**Optimize conversion paths.** By understanding which sequences of actions lead to conversions and which don't, you can remove barriers and encourage users down more successful paths.--**Validate your design assumptions.** You might assume users will navigate your site in a certain way, but journey analysis shows you the reality. This evidence can inform design decisions and help prioritize improvements.--## How to Read the Journey Visualization--Rybbit's journey visualization presents user flows as a connected diagram, showing how users move between different pages or events on your site.+## Reading the Visualization### Nodes--Each circle or box in the visualization represents a page, screen, or event. This could be your homepage, a product page, a signup form, or any tracked action. The node shows the name of the page or event and typically includes a count of how many users reached this point.+Each circle represents a page or event. The size indicates how many users reached that point.### Connections--The lines or arrows between nodes show the flow of users from one step to another. The thickness or prominence of these connections usually indicates how many users took that particular path. Thicker connections mean more users followed that route, while thinner connections represent less common paths.+Lines between nodes show user flow. Thicker connections mean more users took that path.### Flow Direction--The visualization typically flows from left to right or top to bottom, showing progression through time. Users start on the left (or top) and move toward the right (or bottom) as they navigate through your site.--### Multiple Paths--You'll often see nodes with multiple incoming and outgoing connections. This is completely normal. It shows that users reached this page from different sources and continued to different destinations. This branching reveals the reality of user behavior: there's rarely just one path through your experience.+The visualization flows left to right, showing progression through time.## Key Patterns to Look For-### The Happy Path--Look for the most common route from your starting point to your goal (like a signup or purchase). This is your "happy path," the journey that most successfully converts users. Understanding this path helps you optimize it further and encourage more users down this route.--### Drop-off Points--When you see a node where many users enter but few continue, you've found a drop-off point. This could indicate:-- Confusing content or design-- Missing information users need to proceed-- Technical issues preventing progression-- A natural endpoint where users found what they needed--Context matters here. Not all drop-offs are problems. If users reached a help article and then left, they might have found their answer. But if users are abandoning your checkout flow, that's definitely worth investigating.--### Backtracking and Loops--When you see users moving backward or returning to the same pages repeatedly, it often indicates confusion or difficulty finding information. Users might be:-- Unable to locate what they're looking for-- Comparing options back and forth-- Encountering unclear navigation-- Looking for information that's missing--### Alternative Routes--Sometimes you'll discover that users reach important pages through unexpected paths. Perhaps most conversions come from your blog rather than your marketing pages, or users frequently access your pricing page from your documentation instead of your homepage.--These discoveries are gold. They reveal what actually works, not just what you intended to work.--## Interpreting Different Journey Types--### Entry Point Analysis--When you start your journey visualization from an entry point (like your homepage or a landing page), you're asking: "Where do people go from here?" This helps you understand how effective different pages are at guiding users forward and whether your navigation and calls-to-action are working.--### Goal-Based Analysis--When you work backward from a goal (like a purchase or signup), you're asking: "How did successful users get here?" This reveals the paths that lead to conversion, helping you identify which content and touchpoints are most valuable in driving desired outcomes.--### Full Journey Mapping--Looking at complete journeys from entry to exit shows the big picture of user behavior. You'll see common patterns, unusual detours, and the overall flow of traffic through your site. This holistic view helps with information architecture and navigation design.--## Using Journey Insights to Take Action--### Simplify Complex Paths--If users are taking many steps to reach important pages, consider creating shortcuts. Add direct navigation links, implement better search functionality, or restructure your information architecture to reduce friction.--### Fix Drop-off Points--For pages where users commonly exit, investigate what might be causing the problem:-- Review the content for clarity and completeness-- Check for technical issues or slow load times-- Ensure calls-to-action are clear and compelling-- Test whether important information is missing--### Amplify Successful Paths--When you identify paths that lead to high conversion rates, make them easier to follow:-- Create more entry points to these successful routes-- Add prominent navigation to pages that perform well-- Use these journeys as templates for improving other paths--### Reduce Backtracking--If users frequently return to previous pages, improve your navigation and information design:-- Make key information more visible-- Add breadcrumbs or progress indicators-- Provide better page-level navigation-- Consider whether related information should be combined--## Tips for Effective Journey Analysis--### Start with a Question--Don't just open the journey visualization and stare at it. Start with a specific question:-- How do users reach our pricing page?-- What do users do after reading our blog posts?-- Where do people go when they abandon checkout?-- Which paths lead to the highest conversion rates?--Having a clear question helps you focus on relevant insights.--### Segment Your Analysis+- **Happy Path** - The most common route to conversion+- **Drop-off Points** - Where many users enter but few continue+- **Backtracking** - Users moving backward, often indicating confusion+- **Alternative Routes** - Unexpected paths to important pages-Different types of users often take different journeys. Consider analyzing journeys separately for:-- New vs. returning visitors-- Different traffic sources (organic, paid, referral)-- Mobile vs. desktop users-- Different user demographics or behaviors--This segmentation reveals nuances that might be hidden in aggregate data.--### Focus on Volume--While it's interesting to see every possible path users take, focus your attention on the most common routes. The paths followed by the majority of users will have the biggest impact if you improve them. Don't spend time optimizing journeys that only a handful of users experience.--### Look for Changes Over Time--Journey patterns can shift when you make site changes, launch campaigns, or experience seasonal variations. Regularly checking your journey visualization helps you spot these changes and understand their impact.--### Combine with Other Data--Journey visualization is powerful, but it's even better when combined with other analytics:-- Use heatmaps to understand behavior on specific pages-- Check session recordings to see why users behave certain ways-- Review form analytics to understand drop-offs in conversion flows-- Compare journey data with user feedback and surveys--## Common Use Cases--### Onboarding Optimization--For products with signup flows or onboarding sequences, journey analysis helps you see where new users get stuck and how successfully they reach activation milestones.--### Content Performance--Understanding how users navigate through your content reveals which articles drive further engagement, which are dead ends, and how your content ecosystem connects.--### E-commerce Checkout--Mapping the journey from product browsing to purchase shows you exactly where shoppers abandon and which product discovery paths lead to the highest conversion rates.--### Feature Adoption--In applications, journey analysis helps you understand how users discover and adopt features, revealing whether your in-app guidance is effective.--## Technical Considerations--### Event Tracking--The quality of your journey visualization depends on your event tracking. Make sure you're tracking the pages and actions that matter to your analysis. If key steps in the user journey aren't being tracked, you'll have blind spots in your visualization.--### Session Definition--Journey analysis typically groups actions within user sessions. Understanding how Rybbit defines sessions (usually based on a period of inactivity) helps you interpret the data correctly. Very long sessions might actually represent multiple distinct journeys.--### Privacy and Data Sampling--Keep in mind that privacy settings and data sampling can affect journey visualization. If you have Enhanced Privacy mode enabled, journey tracking may be limited. Also, for sites with very high traffic, Rybbit might sample data to maintain performance, which means you're seeing representative patterns rather than every single journey.--## Getting Started with Your Journey Analysis--Ready to dive into your user journeys? Here's how to begin:--1. **Identify your key pages or events.** What actions matter most to your business? Start by analyzing journeys related to these critical touchpoints.--2. **Choose a starting point.** Pick either an entry point (to see where users go) or a goal (to see how users get there). Don't try to analyze everything at once.--3. **Look for the obvious patterns.** Start with the most common paths. What do most users do? This gives you a baseline understanding.--4. **Investigate anomalies.** Once you understand the norm, look for unusual patterns. High drop-off rates, unexpected routes, and excessive backtracking all warrant investigation.--5. **Form hypotheses.** Based on what you see, develop theories about why users behave certain ways. Why might they be taking this path? What might be causing this drop-off?--6. **Validate and act.** Use other data sources to validate your hypotheses, then make improvements. After implementing changes, return to the journey visualization to see if behavior shifts as expected.--7. **Iterate continuously.** Journey analysis isn't a one-time activity. Make it part of your regular analytics routine, checking in weekly or monthly to spot new patterns and measure the impact of your changes.--## Making Journey Analysis Part of Your Workflow--The most successful teams use journey analysis regularly, not just occasionally. Consider:--**Setting up alerts** for significant changes in common journey patterns. If your main conversion path suddenly sees a drop-off increase, you want to know immediately.--**Reviewing journeys in planning meetings** when discussing new features or site changes. Understanding current behavior helps you design better solutions.--**Sharing journey insights across teams** so designers, developers, marketers, and product managers all understand how users navigate your experience.--**Documenting your findings** so you can track how journey patterns evolve and measure the impact of improvements over time.--## Remember: Users Don't Follow Scripts--One of the most important lessons from journey analysis is that users are unpredictable. They don't follow the neat paths we design. They explore, backtrack, take shortcuts, and find creative ways to reach their goals.--This isn't a failure of your design. It's the reality of human behavior. Journey analysis helps you embrace this reality and design experiences that work with how people actually navigate, not how we wish they would.--## Conclusion--Journey analysis can reveal profound insights about your user experience, but it can also raise more questions than it answers. If you're seeing patterns you don't understand or want help interpreting your journey data, reach out to our support team. We're happy to help you make sense of your users' paths.--Every journey tells a story. Your job is to listen to what your users' journeys are telling you and use those insights to create better experiences. Happy exploring!-----+## Using Journey Insights-**Related Reading:**-- [Product Analytics - Retention Guide](/docs/product-analytics/retention_guide)-- [Product Analytics - Funnels Guide](/docs/product-analytics/funnels_guide)-- [Behavior Analytics - Users Tab](/docs/behavior-analytics/users)-- [Behavior Analytics - Sessions Tab](/docs/behavior-analytics/sessions)-- [Behavior Analytics - Events Tab](/docs/behavior-analytics/events)-- [Track Custom Events](/docs/track-events)-- [Blog: Churn Rate vs Retention Rate](/blog/churn-rate-vs-retention-rate)+- **Simplify complex paths** - Create shortcuts to important pages+- **Fix drop-off points** - Investigate why users leave at certain pages+- **Amplify successful paths** - Make high-converting routes easier to follow+- **Reduce backtracking** - Improve navigation where users get lost-## Questions about any feature?+## Analysis Types-- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)\ No newline at end of file+- **Entry point analysis** - Where do users go from a specific page?+- **Goal-based analysis** - How did converting users get there?+- **Full journey mapping** - Overall flow from entry to exitdiff --git a/docs/content/docs/product-analytics/replay-session.mdx b/docs/content/docs/product-analytics/replay-session.mdxindex cc0441168..ceb2b0bec 100644--- a/docs/content/docs/product-analytics/replay-session.mdx+++ b/docs/content/docs/product-analytics/replay-session.mdx@@ -1,34 +1,40 @@---title: Session Replay-description: A guide to how to use Rybbit's Session Replay Tab+description: Watch recordings of user sessions----# A Guide to Rybbit’s Session Replay Tab-Have you ever wondered what your users are actually doing on your website when they are using it? One of Rybbit’s most useful features allows you to take a peek into what individual users are doing on your site; you can literally view an anonymized replay of all their interactions on your website.--This is obviously very useful for any owner interested in understanding how their website is performing, if you’ve ever pondered what your users are really doing on your site beyond just numbers and charts then this feature is an absolute must have. We’ll walk you through how to use it, why it’s incredibly useful, and some creative ways you can apply it to supercharge your online presence.-# What exactly is Session Replay?-Session replay is a feature that allows you to watch anonymized recordings of real sessions on your website, it’s like being able to replay a memory of all the interactions on your website for a particular session. You can see mouse movements, clicks, scrolls, traffic flows, and even a set of user details such as the country, region, device and other details of each user. Unlike services like Google Analytics that just give you numbers and aggregations, session replays provide actual visual playback to help you see the user story behind the stats. And true to Rybbit’s core pillar, this is all done without cookies to ensure user privacy while also delivering powerful insights.-<img src="/blog/replay_sessions.png" alt="Rybbit's performance dashboard" />-# How to set up Session Replay- 1. Set Up Rybbit on your website: Add the Rybbit tracking script to your website, you only need to add the snippet after you paste into your HTML head tag, you can grab this from your Rybbit dashboard after you sign up.- 2. Enable the Session Replay feature: You can either toggle it on your site settings in the Dashboard or add the attribute **data-session-replay=”true”**. It will look something like this:- `<script async defer src="https://your-rybbit-instance.com/tracker.js" data-site="YOUR_SITE_ID" data-session-replay="true"></script>`-3. Protect PII (Personally Identifiable Information): This feature is optional, but it is highly recommended-4. Access the Session Replays in your Dashboard: After Session Replays are enabled, you can go to the “Session Replays” tab on the left hand side of your Rybbit Dashboard, you can filter sessions by criteria like duration, errors or user region. You just need to click on a session to start viewing the playback, you can then use the timeline to look through the events, zoom in on clicks and analyze these interactions in real time.-# Why is the Session Replay tab useful?-Session replay allows you to simply cut through all the noise and see what your users are actually doing, providing you with actionable insights. Here are some use cases that you can consider:-- UX Optimization: You can identify where users are getting stuck, perhaps there are some confusing layouts or slow pages, you can use Replays along with A/B testing to determine where you can make improvements.-- Beyond the metrics: Metrics like pageviews and bounce rates are good to know, but they don’t tell you when the users are struggling with a form or leaving the page because it’s too slow. Session replays will reveal these pain points visually.-- Understand what your users are doing on your site: Seeing actual users and their actual sessions can help you build a much better comprehension of your audience.-- Share with your team: You can share replays with your team for collaboration or for reporting reasons.--From just being a solo developer, or being a high-powered marketing team, or a technical oriented developer team, session replays allow you to have a truly granular view on how your users are actually interacting with your website.-# Final Remarks-At Rybbit, we built Session Replay to harmonize data and real-world user stories. If you’re tired of opaque analytics tools, then give it a try. Setup takes literally minutes and does not impact your site's performance whatsoever thanks to our cookie less approach.--**Additional Resources:**-- [Getting Started with Rybbit Analytics](https://rybbit.com/docs)-- [Self-Hosting Guide](https://rybbit.com/docs/self-hosting)-- [Tracking Custom Events](https://rybbit.com/docs/track-events)-- [Framework Integration Guides](https://rybbit.com/docs) (React, Next.js, Vue, plus 20+ frameworks)+++Session replay lets you watch anonymized recordings of real user sessions, showing mouse movements, clicks, scrolls, and page navigation.++## Enabling Session Replay++Enable session replay in your [site settings](/docs/site-settings), or add the attribute to your tracking script:++```html+<script+ src="https://your-rybbit-instance.com/api/script.js"+ data-site-id="YOUR_SITE_ID"+ data-session-replay="true"+ defer+></script>+```++## What You'll See++- Mouse movements and clicks+- Scrolling behavior+- Page navigation+- Form interactions (with PII masked)+- User details: country, device, browser++## Using Session Replay++- **UX optimization** - Identify where users get stuck or confused+- **Debug issues** - See exactly what happened when users report problems+- **Understand behavior** - Go beyond metrics to see the full user story+- **Share with your team** - Collaborate on findings++## Privacy++Session replay automatically masks sensitive information. Enable PII protection in your settings for additional masking of form inputs and text content.diff --git a/docs/content/docs/product-analytics/retention_guide.mdx b/docs/content/docs/product-analytics/retention_guide.mdxindex 1f0a6e114..7551e5b4c 100644--- a/docs/content/docs/product-analytics/retention_guide.mdx+++ b/docs/content/docs/product-analytics/retention_guide.mdx@@ -1,160 +1,44 @@----title: Retention Analytics-description: Understanding Rybbit's retention tab+title: Retention+description: Measure how many users return over time----# Understanding Retention Analysis in Rybbit+-This guide will help you understand how to use retention analysis in Rybbit to measure user engagement and identify opportunities to improve your product or website.--<img src="/blog/rybbit_retention_dashboard.png" alt="Rybbit's dashboard" />--## What is Retention Analysis?--Retention analysis helps you answer one of the most important questions in product analytics: **Are people coming back to use your product?**--Unlike simple metrics like total visitors or pageviews, retention analysis shows you how many users return to your site or app over time. This gives you insight into whether users find lasting value in what you offer.+Retention analysis shows how many users come back to your site over time, revealing whether users find lasting value.## Understanding Cohorts-At the heart of retention analysis are cohorts. A cohort is simply a group of users who share something in common, typically when they first visited your site or performed a specific action.--For example:-- All users who first visited your site on January 15th form one cohort-- All users who first visited during the week of January 15-21st form a weekly cohort-- All users who signed up for an account in February form a monthly cohort+A cohort is a group of users who share a common start date. For example, all users who first visited on January 15th form one cohort.-By grouping users this way, you can track how their behavior changes over time and compare different groups to see if certain periods brought in more engaged users.+## Reading the Retention Table-## How to Read the Retention Table+### Rows+Each row is a different cohort, grouped by first visit date.-The retention table in Rybbit shows you how many users from each cohort returned after a certain period. Here's what you'll see:+### Columns+- **Day/Week 0** - Starting point (always 100%)+- **Day/Week 1, 2, 3...** - Users who returned after that period-### The Rows-Each row represents a different cohort, typically grouped by the date or week when users first arrived. The leftmost column shows when that cohort started.--### The Columns-The columns represent time periods after the cohort's start date:-- **Day 0 / Week 0**: The starting point (always 100%)-- **Day 1 / Week 1**: Users who returned after 1 day/week-- **Day 2 / Week 2**: Users who returned after 2 days/weeks-- And so on...--### The Numbers-The percentages show what portion of the original cohort returned in each time period. For example, if 40% appears in the "Day 7" column, it means 40% of users who started in that cohort came back after a week.+### Numbers+Percentages show what portion of the original cohort returned. 40% in the "Day 7" column means 40% of users came back after a week.### Color Coding-Rybbit uses color intensity to help you quickly spot patterns:-- Lighter colors indicate higher retention rates-- Darker colors indicate more drop-off-- This makes it easy to spot trends at a glance--## Key Insights to Look For--### 1. The Retention Curve Pattern-Look at how retention changes as you move across the columns. Most products show a pattern like this:-- Sharp drop-off in the first few days (Day 0 to Day 3)-- Gradual decline over the following weeks-- Eventually plateauing at a "baseline" retention rate--The shape of this curve tells you a lot. A steep drop suggests users aren't finding value quickly. A flatter curve indicates better long-term engagement.--### 2. Comparing Cohorts-Look down the columns to compare different cohorts at the same point in their lifecycle. Ask yourself:-- Are newer cohorts retaining better or worse than older ones?-- Did retention improve after you launched a new feature?-- Which time periods brought in the stickiest users?--This comparison helps you understand if your product improvements are working and which acquisition efforts bring quality users.--### 3. Critical Time Windows-Pay special attention to these periods:-- **Day 1 retention**: Did users find enough value to come back the next day?-- **Day 7 retention**: Did users integrate your product into their routine?-- **Day 30 retention**: Have users formed a habit and found lasting value?--These milestones help you identify where users drop off and what experiences might need improvement.--## Common Patterns and What They Mean--### The Cliff Drop-If you see retention falling from 100% to 20-30% within the first few days, it often means:-- Your onboarding experience isn't effectively communicating value-- Users don't understand how to use key features-- There's a mismatch between what users expected and what they found--### The Steady Decline-A gradual, consistent drop over time is normal, but if it's too steep, consider:-- Are users getting ongoing value or is the novelty wearing off?-- Do you have features that encourage repeat usage?-- Are you staying top-of-mind with notifications or emails?+- Lighter colors = higher retention+- Darker colors = more drop-off-### The Plateau-When retention levels off (stops declining significantly), you've found your core users. This baseline retention represents users who have found genuine, lasting value. Understanding who these users are and what they do differently is key to improving overall retention.+## Key Insights-### Improving Trends-If newer cohorts show better retention than older ones at the same lifecycle stage, congratulations! Your product improvements are working. Document what changed so you can replicate success.--## Tips for Taking Action--### Start with Day 1-Focus on getting users to return the day after their first visit. This is your first chance to prove value and sets the tone for long-term retention.--### Identify Drop-off Points-Look for the steepest declines in your retention curve. These represent critical moments where users decide your product isn't valuable enough. Investigate what happens at those points.--### Segment Your Analysis-Don't just look at all users together. Filter by:-- Traffic source (organic, paid, referral)-- User type (new vs returning)-- Specific behaviors or features used--This helps you understand which types of users retain best and why.--### Track Over Time-Retention analysis is most powerful when viewed as a trend. Check your retention dashboard regularly to see if your efforts are moving the needle. Set benchmarks and celebrate improvements.--## Understanding Enhanced Privacy Mode--If you have Enhanced Privacy mode enabled in Rybbit, keep in mind that it affects retention tracking. In this mode, Rybbit forgets user identifiers daily, which means:-- Retention beyond 24 hours becomes less accurate-- Unique user counts over longer periods may be inflated-- The retention dashboard becomes less useful overall--This trade-off prioritizes user privacy at the cost of long-term behavior tracking. If retention insights are critical for your business, you may want to disable Enhanced Privacy mode.--## Getting Started--To make the most of retention analysis in Rybbit:--1. **Set a baseline**: Look at your current retention rates to understand where you stand-2. **Choose your intervals**: Decide whether daily, weekly, or monthly cohorts make most sense for your product-3. **Watch for patterns**: Monitor your retention table regularly to spot trends-4. **Form hypotheses**: When you see concerning patterns, develop theories about why they're happening-5. **Test improvements**: Make changes to your product and track whether newer cohorts retain better-6. **Iterate**: Use what you learn to continuously improve the user experience--## Conclusion--Retention analysis is one of the most powerful tools in your analytics toolkit. It reveals the truth about whether your product creates lasting value for users. If you have questions about interpreting your retention data or want to discuss what you're seeing, don't hesitate to reach out to our support team.--Remember: good retention doesn't happen by accident. It's the result of deeply understanding your users, continuously improving your product, and making sure every interaction delivers value. Your retention dashboard is your guide on that journey.-----+- **Day 1 retention** - Did users find enough value to return the next day?+- **Day 7 retention** - Did users integrate your product into their routine?+- **Day 30 retention** - Have users formed a habit?-**Related Reading:**-- [Behavior Analytics - Users Tab](/docs/behavior-analytics/users)-- [Behavior Analytics - Sessions Tab](/docs/behavior-analytics/sessions)-- [Behavior Analytics - Events Tab](/docs/behavior-analytics/events)-- [Product Analytics - Journeys Dashboard](/docs/product-analytics/journeys_dashboard)-- [Product Analytics - Funnels Guide](/docs/product-analytics/funnels_guide)-- [Track Custom Events](/docs/track-events)-- [Blog: Churn Rate vs Retention Rate](/blog/churn-rate-vs-retention-rate)+## Common Patterns-## Questions about any feature?+- **Cliff drop** - Sharp decline in first few days indicates onboarding issues+- **Steady decline** - Gradual drop suggests novelty wearing off+- **Plateau** - When retention levels off, you've found your core users+## Note on User ID Salting-- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)\ No newline at end of file+If [User ID Salting](/docs/site-settings) is enabled, retention beyond 24 hours becomes less accurate since user identifiers reset daily.diff --git a/docs/content/docs/script-troubleshooting.mdx b/docs/content/docs/script-troubleshooting.mdxnew file mode 100644index 000000000..4dab4a0a4--- /dev/null+++ b/docs/content/docs/script-troubleshooting.mdx@@ -0,0 +1,161 @@+---+title: Troubleshooting+description: Common issues and solutions when the Rybbit tracking script isn't sending traffic+---++import { Callout } from 'fumadocs-ui/components/callout';+import { Steps, Step } from 'fumadocs-ui/components/steps';++If you've installed the Rybbit tracking script but aren't seeing any traffic in your dashboard, this guide will help you diagnose and fix common issues.++## Check if the Script is Loaded++The first step is to verify that the Rybbit script is properly loaded on your page.++<Steps>+<Step>+### Open Your Browser's Developer Console++Right-click anywhere on your webpage and select **Inspect** (or **Inspect Element**). Then click on the **Console** tab at the top of the panel that opens.++Alternatively, you can use keyboard shortcuts:+- **Windows/Linux**: Press `Ctrl + Shift + J` or `F12`+- **Mac**: Press `Cmd + Option + J`+</Step>++<Step>+### Type "rybbit" and Press Enter++In the console, type `rybbit` and press Enter.++**If the script is loaded correctly**, you'll see an object with functions like this:+```javascript+{event: ƒ, pageview: ƒ, identify: ƒ, setTraits: ƒ, clearUserId: ƒ, …}+```++**If the script is NOT loaded**, you'll see an error like:+```+Uncaught ReferenceError: rybbit is not defined+```++If you see the error, the script is not loading properly. Continue reading for common causes.+</Step>+</Steps>++## Common Issues++### Data Attributes Being Stripped++Some platforms, content management systems, and tag managers automatically remove or sanitize `data-*` attributes (or all non-standard attributes) from script tags. This means the `data-site-id` attribute required by Rybbit gets removed, causing the script to fail silently.++**Platforms known to strip attributes:**+- Google Tag Manager+- Some WordPress page builders+- Certain website builders (Webflow, Wix, Squarespace in some configurations)+- Some CDN or caching plugins++**Solution:** Instead of using the standard script tag, inject the script dynamically using JavaScript:++```javascript+<script>+ (function() {+ var el = document.createElement("script");+ el.src = "https://app.rybbit.io/api/script.js";+ el.defer = true;+ el.setAttribute("data-site-id", "YOUR_SITE_ID");+ document.head.appendChild(el);+ })();+</script>+```++This approach creates the script element programmatically and sets the `data-site-id` attribute via JavaScript, which bypasses any HTML sanitization.++<Callout type="info">+For detailed Google Tag Manager setup instructions, see our [Google Tag Manager Guide](/docs/guides/google-tag-manager).+</Callout>++### Ad Blockers++In rare cases, ad blockers may block the Rybbit tracking script. While Rybbit is privacy-focused and doesn't use cookies for tracking, some aggressive ad blockers may still flag analytics scripts.++**How to check if an ad blocker is the issue:**+1. Temporarily disable your ad blocker+2. Refresh the page+3. Check the console again for the `rybbit` object++**Solutions:**+- **For your own testing**: Disable your ad blocker or add your site to the allowlist+- **For your visitors**: Consider setting up a [proxy](/docs/proxy-guide) to serve the script from your own domain, which significantly reduces the chance of being blocked++### Script Not in the Right Location++The Rybbit script should be placed in the `<head>` section of your HTML. If it's placed in the wrong location or loaded after the page has already finished loading, it may not work correctly.++**Verify the script placement:**+1. View your page source (right-click → **View Page Source**)+2. Search for `rybbit` or `script.js`+3. Confirm it appears within the `<head>...</head>` tags++### Incorrect Site ID++Double-check that your `data-site-id` matches the site ID shown in your Rybbit dashboard.++1. Go to your Rybbit dashboard+2. Navigate to your site's settings+3. Copy the site ID and compare it with what's in your script tag++### Content Security Policy (CSP) Blocking++If your site has a strict Content Security Policy, it may block the Rybbit script from loading or executing.++**Check for CSP errors:**+1. Open the browser console+2. Look for errors mentioning "Content Security Policy" or "CSP"++**Solution:** Add the Rybbit script domain to your CSP headers:++```+script-src 'self' https://app.rybbit.io;+connect-src 'self' https://app.rybbit.io;+```++If you're self-hosting Rybbit, replace `app.rybbit.io` with your Rybbit instance domain.++### Script Loading Too Late in SPAs++In single-page applications (React, Vue, Next.js, etc.), if the script loads after the initial page render, the automatic pageview might not fire.++**Solution:** Ensure the script is in your root HTML template (like `index.html` or `_document.js` in Next.js), not dynamically imported in a component.++For Next.js specifically, see our [Next.js Guide](/docs/guides/nextjs).++## Testing Your Installation++Once you've made changes, verify that tracking is working:++1. **Check the console**: Type `rybbit` to confirm the object exists+2. **Trigger a test event**: In the console, run:+ ```javascript+ rybbit.event("test_event")+ ```+3. **Check your dashboard**: Navigate to the Events tab in your Rybbit dashboard and look for "test_event" (it may take a few seconds to appear)+4. **Check the Network tab**: In browser dev tools, go to the Network tab, filter by "track" or "rybbit", and verify requests are being sent with 200 status codes++## Still Having Issues?++If you've tried all the above and are still not seeing traffic:++1. **Check the browser Network tab** for any failed requests to your Rybbit instance+2. **Verify your site ID** is correct in the dashboard+3. **Check if traffic is being filtered** - review your [IP exclusions](/docs/hiding-own-traffic) and [country exclusions](/docs/filter-traffic) to ensure your traffic isn't being blocked+4. **For self-hosted instances** - ensure your Rybbit server is running and accessible++---++**Related Documentation:**+- [Tracking Script Installation](/docs/script)+- [Track Events](/docs/track-events)+- [Proxy Guide](/docs/proxy-guide)+- [Google Tag Manager Guide](/docs/guides/google-tag-manager)+- [Hide Your Own Traffic](/docs/hiding-own-traffic)+- [Filter Traffic](/docs/filter-traffic)diff --git a/docs/content/docs/web-analytics/globe-tab.mdx b/docs/content/docs/web-analytics/globe-tab.mdxindex b44bdb59d..376b52850 100644--- a/docs/content/docs/web-analytics/globe-tab.mdx+++ b/docs/content/docs/web-analytics/globe-tab.mdx@@ -1,85 +1,30 @@----title: Globe dashboard-description: How to use the globe dashboard in Rybbit Analytics+title: Globe+description: Visualize geographic traffic distribution----# Understanding the Globe dashboard in Rybbit Analytics+The Globe tab shows where your visitors connect from on an interactive map.-### What You'll See+## View Modes-When you open the Globe tab, you're greeted with an interactive map showing where your visitors connect from. The interface offers two visualization modes: 2D and 3D.+### 2D Map+- **Timeline** - View sessions by timeframe, click individual sessions for details+- **Coordinates** - Sessions as dots with color intensity showing traffic volume+- **Countries** - Countries highlighted by traffic volume+- **Subdivisions** - Granular view by national subdivisions-#### 2D Map View--<img src="/blog/rybbit_2d_view.png" alt="Rybbit's dashboard" />--The 2D map has four options, timeline, coordinates, countries and subdivisions.--- Timeline: Timeline allows you to view all of your sessions by a specific timeframe geographically on the map, you can select different timeframes (1h, 1m, etc..) and also click on each session individually to view the session details.-- Coordinates: Coordinates view allows you to view sessions as dots on the map, with varying color intensities and dot sizes meaning different numbers of visitors, you can click a dot and see all the sessions associated with that dot.-- Countries: Countries with more traffic appear highlighted, with color intensity showing traffic volume. Darker colors mean more visitors.-- Subdivisions: Subdivisions is a more granualar version of the countries view, you can view sessions by each partiuclar national subdivision.--### Time Controls--Like the Main tab, the Globe tab includes full time controls. Pick your date range and watch the map adjust to show traffic for that period.--Compare this week to last week. See how geographic distribution changes over time. Spot growing markets or declining regions.--### Filtering on the Globe Tab--You can also use the filter tab near the top left of the panel to filter just like in the main dashboard.--Apply filters to see geographic distribution for specific segments. Want to see where your mobile users come from? Apply a device filter and watch the map update.--Combine filters for detailed analysis:-- Mobile users from social media-- Desktop users who converted-- First-time visitors versus returning-- Users who triggered specific events--The Globe tab respects all your filters, making it a powerful segmentation tool.---#### 3D Globe View (Optional)--You can also get access to a 3D globe. This transforms your traffic data into a stunning visual experience.--<img src="/blog/rybbit_3d_view.png" alt="Rybbit's dashboard" />---The 3D map has the same four options as the 2D map has, timeline, coordinates, countries and subdivisions.--- Timeline: Timeline allows you to view all of your sessions by a specific timeframe geographically on the map, you can select different timeframes (1h, 1m, etc..) and also click on each session individually to view the session details.-- Coordinates: Coordinates view allows you to view sessions as dots on the map, with varying color intensities and dot sizes meaning different numbers of visitors, you can click a dot and see all the sessions associated with that dot.-- Countries: Countries with more traffic appear highlighted, with color intensity showing traffic volume. Darker colors mean more visitors.-- Subdivisions: Subdivisions is a more granualar version of the countries view, you can view sessions by each partiuclar national subdivision.--The 3D globe lets you:+### 3D Globe+Same four views as 2D, plus:- Rotate by dragging- Zoom in and out-- See traffic hotspots glow+- Traffic hotspots glow-Perfect for monitoring launches, campaigns, or just watching your site's reach in action.+The 3D view requires a Mapbox API token. Self-hosted installations need `MAPBOX_TOKEN` in environment variables. Cloud includes this automatically.-Note: The 3D view requires a Mapbox API token. For self-hosted installations, add `MAPBOX_TOKEN` to your environment variables. The cloud version includes this automatically.+## Time Controls-### Using the Globe Tab Effectively--Here's how to get the most from this feature:--**Monitor Launches**: Keep the Globe tab open during product launches or content releases. Watch traffic arrive from different regions in real-time.--**Identify Growth Markets**: Check the Globe tab weekly to spot emerging markets. If traffic from a new region increases, that's your signal to consider localization or regional targeting.--**Impress Stakeholders**: The 3D globe makes a fantastic visual for presentations. Show executives where your users actually are.------## Getting Support+Pick date ranges to see how geographic distribution changes over time.-Questions about these tabs or any Rybbit features?+## Filtering-- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)\ No newline at end of file+Apply the same filters as the main dashboard to see geographic distribution for specific segments.diff --git a/docs/content/docs/web-analytics/goals-tab.mdx b/docs/content/docs/web-analytics/goals-tab.mdxindex 8fc34c348..a9553c728 100644--- a/docs/content/docs/web-analytics/goals-tab.mdx+++ b/docs/content/docs/web-analytics/goals-tab.mdx@@ -1,189 +1,50 @@----title: Goals dashboard-description: How to use the Goals dashboard in Rybbit Analytics+title: Goals+description: Track conversions and outcomes----## The Goals Tab+-+Goals let you track specific outcomes like signups, purchases, or key page views.-Goals let you track specific outcomes you care about. Did users sign up? Did they complete checkout? Did they view key pages? The Goals tab helps you measure success.+## Creating a Goal-### Creating Your First Goal+Click "Create Goal" and provide:+- **Goal Name** (optional) - Descriptive name like "Newsletter Signup"+- **Goal Type** - Page Goal or Event Goal-Click "Create Goal" to open the goal setup interface.+### Page Goals-You'll need to provide:+Trigger when users visit specific URLs.-**Goal Name**: Something descriptive like "Newsletter Signup" or "Purchase Complete"+- **Path Pattern** - The URL to match (e.g., `/checkout/complete`)+- **URL Parameters** (optional) - Match specific query parameters-**Goal Type**: Choose between:-- Page path goals (user visits a specific URL)-- Event goals (user triggers a custom event)--**Target**: The page path or event name to track--**Value** (optional): Assign a monetary value to conversions--### Page Path Goals--Page path goals trigger when users visit specific URLs. Common examples:--- Thank you pages after form submission-- Order confirmation pages after checkout-- Onboarding completion pages-- Download confirmation pages--Enter the URL path exactly as it appears in your analytics. Use wildcards for dynamic URLs:-- `/thank-you` matches exactly `/thank-you`-- `/thank-you*` matches `/thank-you`, `/thank-you?ref=email`, etc.-- `/order/*/confirmation` matches `/order/12345/confirmation`+Use wildcards in path patterns:+- `*` matches a single path segment+- `**` matches multiple segments### Event Goals-Event goals trigger when custom events fire. You need to have custom event tracking implemented first.--Common event goals:-- Button clicks ("signup_clicked")-- Video completions ("video_complete")-- Form submissions ("contact_form_submitted")-- Feature usage ("premium_feature_used")--Events offer more flexibility than page goals. You can track actions that don't result in page loads.--### Viewing Goal Performance--After creating goals, the Goals tab displays your conversion metrics.--For each goal, you'll see:-- **Conversion Count**: How many times this goal converted-- **Conversion Rate**: Percentage of sessions that converted-- **Total Value**: Sum of all conversion values (if set)-- **Trend**: Up or down compared to previous period--### Conversion Funnel Analysis--Click any goal to see detailed funnel analysis. This shows the path users take before converting.--The funnel reveals:-- Top entry pages for converting sessions-- Most common paths to conversion-- Where drop-offs happen-- Average time to conversion--This analysis helps you:-- Optimize high-converting entry points-- Fix pages where users drop off-- Understand the customer journey-- Reduce time to conversion--### Goals by Traffic Source--See which channels drive the most conversions. The Goals tab breaks down conversions by source.--Compare conversion rates across:-- Organic search-- Social media-- Direct traffic-- Referrals-- Paid campaigns--Maybe organic search converts at 5% while social converts at 1%. This tells you where to focus acquisition efforts.--### Goals by Device--Device type affects conversion rates. Mobile users often convert less than desktop users, but that varies by industry.--If mobile conversion rates lag significantly, you need mobile optimization. Focus on:-- Simplifying mobile checkout flows-- Reducing form fields-- Improving mobile page speed-- Testing tap targets and button sizes--### Setting Conversion Value--Assigning values to goals lets you track revenue or value generated through your site.--Set values based on:-- Average order value (for purchases)-- Estimated lead value (for B2B sites)-- Lifetime value estimates (for signups)-- Advertising value (for pageviews)--With values set, the Goals tab shows total value generated, making ROI calculations straightforward.--### Multiple Goals--Most sites should track several goals. Create goals for:--**Top of Funnel**:-- Newsletter signups-- Free trial starts-- Resource downloads--**Middle of Funnel**:-- Product page views-- Demo requests-- Add to cart actions--**Bottom of Funnel**:-- Purchase completions-- Account creation-- Premium upgrades--Tracking multiple goals shows you the complete picture. Maybe signups are up but purchases are down. Or downloads increase but signups decline. These patterns inform strategy.--### Time to Conversion--For each goal, see how long it takes users to convert after their first visit.--Most conversions happen:-- Immediately (same session)-- Within 24 hours-- Within a week-- Or longer--Understanding conversion timing helps you:-- Set appropriate retargeting windows-- Adjust email follow-up schedules-- Measure campaign effectiveness over correct timeframes-- Identify quick wins versus nurture needs--### Goals vs Funnels--Goals track single conversion events. Funnels (covered elsewhere) track multi-step processes. Use both together:--- **Goals**: Track end results (signup completed, purchase made)-- **Funnels**: Analyze the steps leading to those results (viewed product → added to cart → proceeded to checkout → completed purchase)--### Using Goals Effectively--Get the most from goals by:--**Start with Core Conversions**: Track your most important business outcomes first. Don't create dozens of goals immediately.--**Add Context with Segments**: Don't just track overall conversion rates. Segment by source, device, and location to understand what drives success.--**Set Benchmarks**: Record current conversion rates, then track improvements. Did your optimization increase conversions by 10%? You'll know.+Trigger when custom events fire. Requires [event tracking](/docs/track-events) to be implemented.-**Monitor Trends**: Weekly checks catch problems early. If conversion rates suddenly drop, investigate immediately.+- **Event Name** - The event to track (e.g., `sign_up_completed`)+- **Event Properties** (optional) - Match specific property key-value pairs-**Test and Learn**: Try changes, measure impact on goals, keep what works. Goals make experimentation measurable.+## Goal Metrics-**Assign Ownership**: Someone should own each goal and work to improve it. Goals without owners don't improve.+For each goal:+- **Conversions** - Total number of times this goal was triggered+- **Conversion Rate** - Percentage of sessions that converted-### Goal Alerts (Coming Soon)+A progress bar shows the conversion rate visually.-Future Rybbit versions will include goal alerts. Get notified when:-- Conversion rates drop below thresholds-- A goal hits target numbers-- Conversion patterns change significantly+## Viewing Conversions-For now, check goals regularly to catch changes early.+Click any goal to expand it and view the sessions that converted. This helps you understand who is converting and what they did.-Questions about any feature?+## Managing Goals-- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: Join 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)+- **Edit** - Modify goal configuration (type cannot be changed)+- **Clone** - Create a copy of an existing goal+- **Delete** - Remove a goal permanentlydiff --git a/docs/content/docs/web-analytics/main-tab.mdx b/docs/content/docs/web-analytics/main-tab.mdxindex 6091296ab..6fd4e1aa0 100644--- a/docs/content/docs/web-analytics/main-tab.mdx+++ b/docs/content/docs/web-analytics/main-tab.mdx@@ -1,355 +1,56 @@----title: Main Dashboard-description: How to interpret and use the Main Dashboard in Rybbit+title: Main Dashboard+description: Overview of the main analytics dashboard----# Understanding the Main Tab in Rybbit Analytics+-The main dashboard serves as your home base in Rybbit Analytics. This is where you land after logging in, and honestly, it's designed so you might never need to leave. Everything you need for daily analytics monitoring lives here. This guide breaks down every section, metric, and feature you'll find on the Main tab.+The main dashboard is your home base in Rybbit Analytics, showing all key metrics at a glance.-## Your Analytics Command Center+## Top Metrics-Think of the Main tab as your website's dashboard. Within seconds of opening Rybbit, you get a complete picture of how your site performed. No drilling through menus, no hunting for data. It's all right there.+- **Unique Users** - Different people who visited your site+- **Total Sessions** - Number of visits (30-minute inactivity starts a new session)+- **Total Pageviews** - Every page load from every visitor+- **Bounce Rate** - Percentage of single-page sessions+- **Pages Per Session** - Average pages viewed per visit+- **Session Duration** - Average time spent per visit-<img src="/blog/rybbit_main_dashboard.png" alt="Rybbit's dashboard" />+## Time Controls-## Top Metrics Bar+Select date ranges: Today, Yesterday, Last 7/30/90 days, or custom range.-The top of your Main tab displays your core numbers. These metrics update in real-time, so you can refresh and watch the changes happen.+## Filters-### Unique Users--This shows how many different people visited your site during your selected time period. Rybbit identifies unique users without cookies—it uses a combination of IP address hashing and user agent information. The number stays accurate while respecting privacy.--### Total Sessions--A session represents one visit to your site. If someone visits, leaves, and comes back 30 minutes later, that counts as two sessions. This metric tells you how many visits your site received.--### Total Pageviews--Raw pageview count—every page load from every visitor. If one person views five pages, that's five pageviews. Simple.--### Bounce Rate--The percentage of sessions where visitors viewed only one page and left. We covered this metric extensively in our bounce rate guide, but you'll reference it constantly from the Main tab.--### Pages Per Session--Average number of pages viewed per visit. Higher numbers usually indicate better engagement, though context matters. A blog reader might view one long article and leave satisfied.--### Session Duration--Average time spent on your site per visit. Like pages per session, this varies by site type. News sites might see quick visits, while documentation sites often see longer sessions.--## Time Controls and Filtering--Above your metrics bar sits the date range selector. This determines what data you're seeing everywhere on the Main tab.--### Date Range Selector--Click the date display to pick your time range, for example you can choose:-- Today-- Yesterday-- Last 7 days-- Last 30 days-- Last 90 days-- Custom range-- Other options as seen in the screenshot--The custom option lets you choose between any two dates.--## Filters Panel--The filters panel (accessible from the top bar) lets you combine multiple filters for granular analysis.--### Adding Filters--Click "Filter" and then "Add Filter" and choose from 15+ dimensions:-- Device type-- Browser-- OS-- Country-- City-- Referrer-- UTM parameters+Combine filters for granular analysis:+- Device type, browser, OS+- Country, city+- Referrer, UTM parameters- Custom event properties-- And more--### Combining Filters--Stack multiple filters to create specific segments. Want to see mobile users from the United States who arrived via organic search? Add three filters:-1. Device = Mobile-2. Country = United States-3. Referrer contains "google"--Your entire Main tab now shows only sessions matching all three conditions.--## Hostname Filter--For sites that track multiple domains (maybe you run several sites or subdomains), the hostname filter helps separate them.--### Selecting Domains--Click the hostname selector to choose which domains to display. Track blog.yoursite.com separately from app.yoursite.com, or combine them for a complete picture.--To clear the filter, click the X on the filter tag near the top.--## The Main Chart--Your primary visualization sits front and center. This chart shows your selected metric over time.--### Switching Metrics-Click the stat selector to change what the chart displays:-- Users-- Sessions-- Pageviews-- Bounce Rate-- Pages Per Session-- Session Duration+## Main Chart-The chart updates instantly to show your chosen metric's trend.+Shows your selected metric over time. Click the metric selector to switch between Users, Sessions, Pageviews, Bounce Rate, Pages Per Session, or Session Duration.-### Reading the Graph+## Traffic Sources-Hover over any point to see exact numbers for that time bucket.+See where your traffic comes from:+- **Direct** - Typed URL or bookmarks+- **Search** - Google, Bing, DuckDuckGo, etc.+- **Social** - Twitter, Facebook, LinkedIn, Reddit+- **Referral** - Other websites-Patterns jump out visually. Traffic spikes? You'll spot them. Steady decline? That shows up too. The chart makes trends obvious.--## Traffic Sources Breakdown--Scroll further and you'll hit the referrer section. This shows where your traffic comes from.--### Source Categories--Rybbit automatically categorizes traffic:-- **Direct**: Typed URL or bookmarks-- **Search**: Google, Bing, DuckDuckGo, etc.-- **Social**: Twitter, Facebook, LinkedIn, Reddit-- **Referral**: Other websites linking to you--Each category shows session count and percentage of total traffic.--### Detailed Referrer List--Click any individual referrer to filter your entire view to just that traffic source. Now all your metrics show only visitors from that source. Check bounce rate for Reddit traffic specifically, or see if Twitter visitors view more pages than average.--Click any category in the channels tab to expand and see specific sources. Under "Social," for example, you'll see exactly how many sessions came from Twitter versus LinkedIn.+Click any source to filter the entire dashboard to that traffic.## UTM Parameters-If you use UTM tags for campaign tracking, this section becomes incredibly valuable.--### Campaign Data--See all your campaigns with metrics for each:-- Campaign name (utm_campaign)-- Source (utm_source)-- Medium (utm_medium)-- Term (utm_term)-- Content (utm_content)--Each parameter shows session counts and allows filtering.--Click any campaign to filter the Main tab to just that campaign's traffic. Compare bounce rates across campaigns, or see which campaign drives the longest sessions.--### Pages--You can use this section to find the exact pages (their URL's, the page titles, entry and exit pages, and hostnames) that your users are visitng.--## Top Pages--The pages section shows which URLs received the most traffic.--### Page List--Pages rank by view count. Each entry displays:-- Page path-- Pageview count-- Unique visitors to that page-- Average time on page-- Bounce rate for that page--### Page Performance--Notice how each page shows its own bounce rate and time on page. This helps identify high-performers and problem pages. A landing page with 80% bounce rate and 10-second average time? That needs work.--Click any page to filter the entire Main tab to just sessions that viewed that page. Suddenly you're analyzing only visitors who hit your pricing page, for example.--## Entry and Exit Pages--These sections break down where visits begin and end.--### Entry Pages--Your entry pages show which URLs serve as landing points. For each entry page, you see:-- Session count starting there-- Bounce rate for sessions starting there-- Average pages per session from that entry--Entry page data matters for SEO and marketing. Which pages bring traffic? Which ones convert visitors into engaged users?--### Exit Pages--Exit pages show where people leave. High exit rates on checkout pages signal problems. High exits on thank-you pages? That's expected and fine.--## Device and Browser Breakdown--Keep scrolling to find device, browser, and operating system data.--### Device Type+View campaign data: utm_campaign, utm_source, utm_medium, utm_term, utm_content.-See the split between:-- Desktop-- Mobile-- Tablet--Each shows session count and percentage. Mobile-first sites will see mobile dominate; B2B tools often show desktop leads.--### Browser, Device and OS--Detailed browser information appears below devices:-- Browser name (Chrome, Safari, Firefox, Edge)-- Browser version-- Device Type (Desktop/Mobile)-- Operating system-- OS version--This helps debug issues. Seeing weird behavior reports? Check if they correlate with a specific browser version.--Click any device type, browser, or OS to filter your view to just those sessions.--## Screen Resolution Data--Screen sizes matter for responsive design. The resolutions section shows what sizes your visitors use.--### Resolution List--Common resolutions appear with session counts:-- 1920x1080 (Full HD)-- 1366x768 (Laptop standard)-- 414x896 (iPhone sizes)-- And many more--This data informs design decisions. If 60% of your traffic uses mobile resolutions, mobile-first design becomes critical.--## Geographic Data--The countries section shows where your visitors connect from.--### Country List--Countries appear ranked by session count. Each entry shows:-- Country flag and name-- Session count-- Percentage of total traffic (hover over the specific country to see)--## Custom Events Section--Below your main chart, you'll see your custom events (if you've set any up). These show how often specific actions happen on your site.--### Filtering by Events--Each event gets its own card displaying:-- Event name-- Total count for the period-- Trend indicator (up or down from previous period)--Click any event card to filter the entire Main tab to show only sessions where that event occurred.--After clicking an event, notice how all your metrics update to reflect only sessions containing that event. Want to see bounce rate for users who played a video? Click the video_play event. Curious about average session duration for users who added items to cart? Click add_to_cart.--This turns events from simple counters into powerful segmentation tools.--## Weekly Trends--At the bottom of the Main tab, you'll find a weekly comparison widget.--### Week-over-Week Comparison--This section shows key metrics over the week:-- Unique Visitors-- Sessions-- Pageviews-- Bounce Rate-- Pages per session-- Session Duration--## Making the Most of the Main Tab--Here's how to use the Main tab effectively:--### Start with the Big Picture--Open Rybbit, glance at your top metrics. Are numbers where you expect? Any surprises? This 10-second check gives you daily pulse.--### Investigate Anomalies--Notice an unexpected spike or drop? Click into that time period on the chart. Check which pages drove the change. Look at traffic sources. Follow the data trail.--### Compare Time Periods--Use the date picker to compare similar periods. How does this Monday compare to last Monday? This campaign to the previous one? These comparisons reveal what's working.--### Combine Filters for Deep Dives--Don't just look at overall stats. Layer filters to understand specific user segments. Mobile users from paid campaigns behave differently than desktop users from organic search. See how.--### Track Improvements Over Time--Made site changes? Watch the metrics over days and weeks. Did improving mobile performance reduce mobile bounce rate? Did adding videos increase session duration? The Main tab shows results.--### Use Event Filtering--This feature transforms the Main tab. Instead of asking "how did my site perform overall," you ask "how did users who took action X perform?" Much more actionable.--### Check Geographic Patterns--International traffic growing? Time to think about localization. One country dominating? Consider timezone-specific content scheduling or support hours.--### Monitor Entry Pages--Your entry pages determine first impressions. High bounce rates on entry pages mean visitors aren't finding what they expected. Fix those pages first.--## Tips and Tricks--### Bookmark Filtered Views--Found a particularly useful filtered view? Bookmark that URL. Rybbit's filters appear in the URL, so bookmarking saves your exact configuration.--### Use Mobile for Quick Checks--The Main tab works great on mobile browsers. Stuck in a meeting but need to check a number? Pull up Rybbit on your phone—everything's there.--### Set Up Multiple Projects--Managing several sites? Create separate projects for each. The project selector at the top lets you switch between them instantly.--## Common Questions--**Q: Why don't my numbers match Google Analytics exactly?**--Rybbit uses different counting methods, bot detection works better, and there's no sampling. Small discrepancies are normal. Over time, you'll find Rybbit's numbers more reliable.--Not noticeably. Rybbit's handles filtered queries incredibly fast, even with millions of events.--**Q: Can multiple team members view the Main tab simultaneously?**--Yes. Rybbit supports organizations and multiple users. Each person can have their own filters and views without affecting others.--## Getting Support--Questions about any feature?--- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: Join 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)-----+## Additional Breakdowns-**Related Guides:**-- [Calculating Bounce Rate with Rybbit](/blog/bounce-rate)-- [Getting Started with Rybbit Analytics](/docs)-- [Tracking Custom Events](/docs/track-events)-- [Using Session Replay Effectively](/docs/product-analytics/replay-session)\ No newline at end of file+- **Top Pages** - Most visited URLs with pageviews, visitors, time on page, and bounce rate+- **Entry/Exit Pages** - Where visits begin and end+- **Devices & Browsers** - Desktop/mobile/tablet split, browser and OS breakdown+- **Screen Resolutions** - What sizes your visitors use+- **Geographic Data** - Countries and regions+- **Custom Events** - Click any event to filter to sessions containing itdiff --git a/docs/content/docs/web-analytics/pages-tab.mdx b/docs/content/docs/web-analytics/pages-tab.mdxindex 3244c779c..ec6e4d5a6 100644--- a/docs/content/docs/web-analytics/pages-tab.mdx+++ b/docs/content/docs/web-analytics/pages-tab.mdx@@ -1,54 +1,28 @@----title: Pages dashboard-description: How to use the pages dashboard in Rybbit Analytics+title: Pages+description: Analyze page performance----## The Pages Tab+-The Pages tab provides detailed analysis of every URL on your site. While the Main tab shows top pages, the Pages tab gives you the full picture with advanced filtering and sorting.+The Pages tab shows detailed analytics for every URL on your site.-### Pages Table+## Page Metrics-The main feature here is a comprehensive table listing every page tracked on your site.+Each page displays:+- **Page URL** - The full path+- **Sessions** - Number of sessions that viewed this page+- **Average Time on Page** - How long visitors spend there-<img src="/blog/rybbit_pages_dashboard.png" alt="Rybbit's dashboard" />+## Filtering-Each row shows:-- **Page URL**: Full path or truncated display-- **Average Time on Page**: How long visitors spend there-- **Sessions**: Number of sessions for each page--### Filtering on the Pages Tab--You can also use the filter tab near the top left of the panel to filter just like in the main dashboard.--Combine filters for detailed analysis:+Use the same filters as the main dashboard to analyze specific segments:- Mobile users from social media- Desktop users who converted-- First-time visitors versus returning- Users who triggered specific events-### Identifying Problem Pages--The Pages tab makes it easy to spot underperforming content:--1. See the pages with the lowest average time on page-2. Look for pages with least sessions--### Using Pages Tab Insights--Here's what to do with the data:--**Content Audit**: Sort by pageviews to find your most popular content. These pages deserve regular updates and optimization.--**SEO Opportunities**: Check entry pages with high traffic but low average time on page. These rank well but don't deliver what searchers expect. Adjust content or meta descriptions.------## Getting Support--Questions about these tabs or any Rybbit features?+## Identifying Issues-- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)\ No newline at end of file+- Sort by lowest time on page to find content that isn't engaging+- Sort by fewest sessions to find underperforming pages+- Compare entry pages to see which content attracts trafficdiff --git a/docs/content/docs/web-analytics/performance-tab.mdx b/docs/content/docs/web-analytics/performance-tab.mdxindex 765060697..c0398126f 100644--- a/docs/content/docs/web-analytics/performance-tab.mdx+++ b/docs/content/docs/web-analytics/performance-tab.mdx@@ -1,172 +1,59 @@----title: Performance Dashboard-description: How to use the performance dashboard in Rybbit Analytics+title: Performance+description: Track Core Web Vitals and site speed----## The Performance Tab+-The Performance tab tracks Core Web Vitals and other speed metrics. Site performance directly affects user experience, conversions, and SEO rankings. This tab shows you exactly how your site performs for real users.+The Performance tab tracks Core Web Vitals from real user data.-<img src="/blog/rybbit_performance_dashboard.png" alt="Rybbit's dashboard" />+## Enabling Performance Tracking-### Web Vitals Dashboard--The top of the Performance tab displays your three Core Web Vitals scores with color-coded indicators.--#### Largest Contentful Paint (LCP)--LCP measures how long the main content takes to load. Users see blank screens while LCP is happening, so faster is better.+Enable Web Vitals in your [site settings](/docs/site-settings).+## Web Vitals+### Largest Contentful Paint (LCP)+How long the main content takes to load.- **Good**: Under 2.5 seconds-- **Needs Improvement**: 2.5-4 seconds.+- **Needs Improvement**: 2.5-4 seconds- **Poor**: Over 4 seconds-Rybbit shows you:-- Your median LCP-- Distribution of LCP scores-- LCP by page-- LCP by device type-- LCP trends over time--#### Interaction to Next Paint (INP)--INP measures how quickly your site responds to user interactions like clicks, taps, and keypresses. Lower numbers mean more responsive interfaces.--- **Good**: Under 200 milliseconds-- **Needs Improvement**: 200-500 milliseconds-- **Poor**: Over 500 milliseconds--Check INP to identify:-- Slow-responding buttons-- Laggy form inputs-- Delayed navigation-- Overall interactivity issues--#### Cumulative Layout Shift (CLS)--CLS measures visual stability. How much does content jump around while loading? Low scores mean stable pages where elements don't shift unexpectedly.-+### Cumulative Layout Shift (CLS)+How much content jumps around while loading.- **Good**: Under 0.1- **Needs Improvement**: 0.1-0.25- **Poor**: Over 0.25-High CLS often comes from:-- Images without dimensions-- Ads or embeds loading late-- Fonts swapping in-- Dynamically injected content--### Performance by Page--Scroll down to see performance metrics broken down by page. Some pages might perform great while others drag down your averages.--The table shows each page with:-- Average LCP-- Average INP-- Average CLS-- Number of samples--Sort by any metric to find your slowest pages. These pages should be your optimization priorities.--### Performance by Device--Device type significantly affects performance. Mobile devices often show worse metrics than desktop.--Compare performance across:-- Desktop-- Mobile-- Tablet--If mobile performance lags far behind desktop, prioritize mobile optimization. Most traffic comes from mobile devices now, so mobile performance matters more than ever.--### Performance by Browser--Different browsers handle performance differently. Check if certain browsers struggle with your site.--Sometimes you'll find browser-specific issues. Maybe Safari loads slowly while Chrome performs well. This points to specific optimization opportunities.--### Performance Trends+### Interaction to Next Paint (INP)+How quickly your site responds to user interactions.+- **Good**: Under 200ms+- **Needs Improvement**: 200-500ms+- **Poor**: Over 500ms-The Performance tab includes trend charts showing how your metrics change over time.+### First Contentful Paint (FCP)+How long until the first content appears.+- **Good**: Under 1.8 seconds+- **Needs Improvement**: 1.8-3 seconds+- **Poor**: Over 3 seconds-Watch these trends after making changes:-- Did your optimization improve LCP?-- Did adding new features hurt INP?-- Has CLS gotten worse over time?+### Time to First Byte (TTFB)+How long until the server responds.+- **Good**: Under 800ms+- **Needs Improvement**: 800-1800ms+- **Poor**: Over 1800ms-Trends reveal whether you're moving in the right direction.+## Percentile Selector-### Real User vs Lab Data+Choose which percentile to view (p50, p75, p90, p95, p99). The p75 is commonly used for Core Web Vitals assessment.-Rybbit collects real user performance data—what actual visitors experience on actual devices over actual connections. This differs from lab testing tools that simulate performance.+## Comparison-Real user data shows:-- Actual device performance (old phones, new laptops)-- Real network conditions (slow mobile, cable)-- Geographic variations-- Browser diversity--Lab tests are useful for debugging, but real user data tells you what actually happens.--### Using Performance Data--Here's how to act on performance metrics:--**Find Problem Pages**: Sort by worst LCP/INP/CLS and fix those pages first. High-traffic pages with poor performance hurt the most.--**Prioritize Mobile**: If mobile metrics lag, focus optimization efforts there. Most users browse on mobile now.--**Set Performance Budgets**: Track your median metrics and set goals. Aim to improve by specific amounts each quarter.--**Monitor After Changes**: Deploy changes, then watch the Performance tab. Do metrics improve or worsen?--**Fix the Worst First**: A few terrible pages drag down your averages more than many slightly slow pages. Fix the worst performers for maximum impact.--### Common Performance Fixes--Based on what you see in the Performance tab:--**For High LCP**:-- Optimize images (compress, use modern formats)-- Reduce server response time-- Remove render-blocking resources-- Use CDN for static assets-- Implement lazy loading--**For High INP**:-- Reduce JavaScript execution time-- Split long tasks into smaller chunks-- Defer non-critical scripts-- Optimize event handlers-- Remove unused JavaScript--**For High CLS**:-- Add width/height to images and videos-- Reserve space for ads and embeds-- Avoid injecting content above existing content-- Use font-display: optional-- Size containers before loading content--### Performance Impact on Business--Why performance matters:--**Conversions**: Amazon found every 100ms of latency costs them 1% in sales. Faster sites convert better.--**SEO**: Google uses Core Web Vitals as ranking signals. Better performance means better rankings.--**User Satisfaction**: Users abandon slow sites. 53% of mobile users leave pages that take over 3 seconds to load.--**Revenue**: For e-commerce, performance directly affects the bottom line. Faster checkouts mean more completed purchases.--The Performance tab gives you the data to prove performance investments pay off.-----+Each metric shows the change from the previous period, with green indicating improvement and red indicating degradation.-Questions about any feature?+## Breakdowns-- **Documentation**: [rybbit.com/docs](https://rybbit.com/docs)-- **Discord Community**: Join 385+ members at [discord.gg/DEhGb4hYBj](https://discord.gg/DEhGb4hYBj)-- **Twitter/X**: [@yang_frog](https://x.com/yang_frog)-- **GitHub**: [github.com/rybbit-io/rybbit](https://github.com/rybbit-io/rybbit)+- **By Page** - Find your slowest pages+- **By Device** - Compare mobile vs desktop performance+- **By Browser** - Identify browser-specific issues+- **By Country** - See geographic performance differencesdiff --git a/docs/src/components/CustomHeader.tsx b/docs/src/components/CustomHeader.tsxindex e9ab3f18a..82d7a014d 100644--- a/docs/src/components/CustomHeader.tsx+++ b/docs/src/components/CustomHeader.tsx@@ -50,12 +50,12 @@ export function CustomHeader() {>Docs</Link>- <Link+ {/* <Linkhref="/blog"className="text-sm font-base text-neutral-600 dark:text-neutral-400 hover:text-neutral-900 dark:hover:text-white transition-colors">Blog- </Link>+ </Link> */}<Linkhref="/sponsors"className="text-sm font-base text-neutral-600 dark:text-neutral-400 hover:text-neutral-900 dark:hover:text-white transition-colors"