Skip to content

🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.

adding new article

Joey Meng9dd47bf05c3c
diff --git a/docs/content/blog/_meta.js b/docs/content/blog/_meta.js
index 940707ae7..5474bc738 100644
--- a/docs/content/blog/_meta.js
+++ b/docs/content/blog/_meta.js
@@ -3,6 +3,8 @@ export default {
"How my open source SaaS got 5,000 Github stars in 9 days with zero marketing effort",
"website-traffic-drop":
"Why did my website traffic drop?",
+ "ecommerce-analytics":
+ "Rybbit Analytics for E-commerce Websites",
"onyx-ai-knowledge-platform":
"How We Use Onyx to Power Knowledge Management at Rybbit",
};
\ No newline at end of file
diff --git a/docs/content/docs/product-analytics/bounce-rate.mdx b/docs/content/blog/bounce-rate.mdx
similarity index 98%
rename from docs/content/docs/product-analytics/bounce-rate.mdx
rename to docs/content/blog/bounce-rate.mdx
index bb0950081..92cba785e 100644
--- a/docs/content/docs/product-analytics/bounce-rate.mdx
+++ b/docs/content/blog/bounce-rate.mdx
@@ -1,6 +1,9 @@
---
title: How to Calculate Bounce Rate with Rybbit Analytics
description: How to Calculate Bounce Rate with Rybbit Analytics
+date: 2025-11-21
+tags: ['analytics', 'metrics']
+author: Bill Yang
---
# How to Calculate Bounce Rate with Rybbit Analytics
diff --git a/docs/content/blog/ecommerce-analytics.mdx b/docs/content/blog/ecommerce-analytics.mdx
new file mode 100644
index 000000000..7d3a4d0cd
--- /dev/null
+++ b/docs/content/blog/ecommerce-analytics.mdx
@@ -0,0 +1,358 @@
+---
+title: Rybbit Analytics for E-commerce Websites
+date: 2025-11-22
+description: A comprehensive guide to using Rybbit Analytics for your e-commerce website to track sales, conversions, and customer behavior
+tags: ["analytics", "ecommerce", "conversion"]
+author: Bill Yang
+---
+
+If you run an e-commerce website, understanding your customer behavior and sales funnel is crucial for growth. Whether you're running a small online store or a large marketplace, having the right analytics in place can mean the difference between scaling successfully and struggling to understand why your sales are declining.
+
+This is where Rybbit Analytics comes in. Unlike traditional analytics platforms that overwhelm you with data you don't need, Rybbit gives you actionable insights into your e-commerce metrics while respecting your customers' privacy and keeping your data under your control.
+
+## Why E-commerce Sites Need Better Analytics
+
+Most e-commerce platforms come with basic built-in analytics, but they're often limited in scope. You might see how many people visited your product pages, but can you easily answer these critical questions:
+
+- Which marketing channels are actually driving purchases, not just traffic?
+- What's the conversion rate for mobile vs desktop users?
+- Are customers from certain countries more likely to complete a purchase?
+- Which product pages have high traffic but low conversion rates?
+- How is your site's performance affecting your sales?
+- What's the customer journey from landing to checkout?
+
+Traditional analytics tools like Google Analytics can answer some of these questions, but they come with significant downsides: complex setup, privacy concerns, cookie consent banners, data ownership issues, and an overwhelming interface that requires training to navigate effectively.
+
+## What Makes Rybbit Different for E-commerce
+
+Rybbit is built from the ground up to be simple, privacy-focused, and actionable. Here's what that means for your e-commerce business:
+
+**No Cookie Consent Banners Required** - Rybbit doesn't use cookies, which means you don't need those annoying cookie banners that hurt your conversion rates. Your checkout flow stays clean and simple.
+
+**Lightning Fast** - The Rybbit script is incredibly lightweight (under 1KB), so it won't slow down your product pages or checkout process. Every millisecond of load time matters for e-commerce conversions.
+
+**You Own Your Data** - With the self-hosted option, all your customer data stays on your servers. No third-party access, no data sharing, complete control.
+
+**Simple, Actionable Metrics** - Rybbit focuses on the metrics that actually matter for e-commerce, without drowning you in vanity metrics.
+
+## Setting Up Rybbit for Your E-commerce Site
+
+Getting started with Rybbit is straightforward. You can either use the hosted version or self-host it (which many e-commerce businesses prefer for data sovereignty).
+
+### Installation
+
+Add the Rybbit tracking script to your site's header. For most e-commerce platforms, this goes in your theme's template file:
+
+```html
+<script defer src="https://your-rybbit-instance.com/script.js" data-project-id="your-project-id"></script>
+```
+
+That's it. No complex configuration, no tag managers required, no cookies to configure.
+
+### Tracking E-commerce Events
+
+While Rybbit automatically tracks page views, you'll want to track key e-commerce events like:
+
+- Product views
+- Add to cart
+- Checkout initiated
+- Purchase completed
+
+Here's how you track a purchase:
+
+```javascript
+rybbit.event("Purchase", {
+ value: orderTotal,
+ currency: "USD",
+ transaction_id: orderId,
+});
+```
+
+## Key Metrics for E-commerce Success
+
+### 1. Traffic Sources and Quality
+
+Understanding where your traffic comes from is table stakes, but Rybbit makes it easy to see which sources actually convert.
+
+<img src="/blog/channelfilter.png" alt="Rybbit's Channel Filter feature" />
+
+Using Rybbit's channel filter, you can quickly see traffic from:
+
+- Organic search
+- Paid advertising
+- Social media
+- Email campaigns
+- Direct traffic
+- Referrals
+
+But more importantly, you can combine this with your purchase events to see which channels drive actual revenue, not just visits. This helps you allocate your marketing budget more effectively.
+
+### 2. Geographic Performance
+
+If you're selling internationally, geographic data is crucial. Rybbit makes it easy to analyze performance by country.
+
+<img src="/blog/countryfilter.png" alt="Rybbit's country filter" />
+
+You can use geographic filtering to:
+
+- Identify high-converting markets worth investing in
+- Spot countries with high traffic but low conversion (maybe you need better shipping options or payment methods)
+- Optimize your ad spend by focusing on profitable regions
+- Plan inventory and shipping logistics based on where your customers are
+
+### 3. Device and Platform Analysis
+
+E-commerce conversion rates often vary significantly between desktop and mobile. Rybbit lets you filter by device type to understand these differences.
+
+<img src="/blog/devicefilter.png" alt="Rybbit's device filter" />
+
+Common insights you might discover:
+
+- Mobile traffic is high but conversion is low β†’ your mobile checkout might need work
+- Tablet users have higher average order values β†’ consider tablet-specific promotions
+- Desktop users browse more pages before purchasing β†’ optimize your navigation for desktop
+
+### 4. Page Performance Analysis
+
+Page speed directly impacts e-commerce conversions. Studies show that even a 100ms delay can reduce conversion rates by 7%.
+
+<img src="/blog/performancedashboard.png" alt="Rybbit's performance dashboard" />
+
+Rybbit's performance tab shows you the Largest Contentful Paint (LCP) for each page. If your product pages or checkout pages have high LCP times, you're losing money. The performance dashboard makes it easy to identify which pages need optimization.
+
+**What to look for:**
+
+- Product pages with high traffic but slow load times β†’ optimize images, reduce scripts
+- Checkout pages with performance issues β†’ this is costing you direct sales
+- Category pages that load slowly β†’ customers will bounce before seeing your products
+
+### 5. Conversion Funnel Insights
+
+One of the most powerful uses of Rybbit for e-commerce is tracking your conversion funnel. Using the pages tab, you can see the customer journey:
+
+<img src="/blog/pages.png" alt="Rybbit's page tab" />
+
+The embedded graphs make it easy to spot where customers are dropping off:
+
+- High traffic to product pages but low "add to cart" pages β†’ product pages need better CTAs
+- Many add to cart events but few checkout initiations β†’ shipping costs revealed too late?
+- Checkout started but not completed β†’ payment issues or complicated forms?
+
+### 6. Time-Based Patterns
+
+Understanding when your customers shop helps you optimize promotions and advertising.
+
+<img src="/blog/customdaterange.png" alt="Rybbit's custom date range filter" />
+
+Using Rybbit's date range filters, you can:
+
+- Compare this month vs last month to track growth
+- Identify seasonal patterns in your business
+- See if your recent marketing campaigns are working
+- Spot unusual drops or spikes that need investigation
+
+### 7. Referrer Analysis
+
+Beyond broad traffic sources, Rybbit lets you drill down into specific referrers to see exactly which sites, influencers, or affiliate partners are driving traffic.
+
+<img src="/blog/referrerfilter.png" alt="Rybbit's referrer filter" />
+
+This is especially valuable for:
+
+- Affiliate programs - see which affiliates drive the most valuable traffic
+- Influencer marketing - track which influencers actually drive sales
+- Content marketing - identify which guest posts or mentions are worth pursuing
+- Partner relationships - measure the value of co-marketing efforts
+
+## Real-World E-commerce Scenarios
+
+### Scenario 1: Optimizing Marketing Spend
+
+Sarah runs a sustainable fashion e-commerce store. She was spending $5,000/month on Facebook ads and $3,000/month on Google Ads. Using Rybbit's channel filtering combined with purchase events, she discovered:
+
+- Facebook ads drove more traffic but had a 0.8% conversion rate
+- Google Shopping ads had less traffic but a 3.2% conversion rate
+- Organic search had the highest conversion rate at 4.1%
+
+**Action taken:** She shifted budget from Facebook to Google Shopping and invested in SEO. Three months later, her overall conversion rate increased by 47% while her ad spend decreased by 25%.
+
+### Scenario 2: Fixing Mobile Conversion Issues
+
+Mike's electronics store had 65% mobile traffic but only 20% of purchases came from mobile devices. Using Rybbit's device filter and page analysis, he discovered:
+
+- Mobile users were dropping off at the checkout page
+- The checkout page had an LCP of 4.2 seconds on mobile (anything over 2.5 seconds is poor)
+- Mobile users were bouncing at a 72% rate from the payment page
+
+**Action taken:** Mike optimized his mobile checkout, reduced the number of form fields, improved page speed, and added mobile payment options like Apple Pay. Mobile conversion rate increased from 1.1% to 2.8%.
+
+### Scenario 3: International Expansion
+
+Jessica's beauty products store was primarily US-focused but noticed growing international traffic. Using Rybbit's geographic filtering, she found:
+
+- UK traffic had high engagement and good conversion rates
+- German traffic was significant but had a 0.3% conversion rate
+- Australian visitors had the highest average order value
+
+**Action taken:** She added localized payment options for Germany (SEPA), improved international shipping information, and added UK and Australian pricing. International sales increased by 134% in the next quarter.
+
+### Scenario 4: Product Page Optimization
+
+Tom's sporting goods store had great traffic but declining conversion rates. Using Rybbit's pages tab, he analyzed individual product pages and found:
+
+- High-traffic product pages often had the worst conversion rates
+- Pages with detailed descriptions and multiple images converted better
+- Video demonstrations on product pages showed significantly higher conversion
+
+**Action taken:** He prioritized improving the top-traffic, low-conversion product pages first, adding better images, detailed specifications, and customer reviews. Overall conversion rate improved by 22%.
+
+## Privacy and E-commerce: Why It Matters
+
+E-commerce businesses collect sensitive customer data - names, addresses, payment information. Using privacy-respecting analytics like Rybbit sends a positive signal to customers:
+
+**No Data Sharing** - Customer behavior data stays with you, never sold to advertisers
+
+**GDPR and Privacy Compliant** - Rybbit is built to respect privacy laws by default
+
+**No Cookie Banners** - Better user experience means better conversion rates
+
+**Build Trust** - Privacy-conscious customers appreciate businesses that respect their data
+
+In an era where data breaches make headlines regularly, being able to tell your customers that you use privacy-first analytics is a competitive advantage.
+
+## Comparing Rybbit to Other E-commerce Analytics
+
+### vs. Google Analytics
+
+**Google Analytics:**
+
+- Requires complex e-commerce tracking setup
+- Needs cookie consent banners
+- Data belongs to Google
+- Overwhelming interface with hundreds of metrics
+- Slower script impacts page speed
+
+**Rybbit:**
+
+- Simple event tracking
+- No cookie banners needed
+- You own all data
+- Focused on actionable metrics
+- Minimal performance impact
+
+### vs. Platform Built-in Analytics (Shopify, WooCommerce, etc.)
+
+**Built-in Analytics:**
+
+- Limited to basic metrics
+- Can't easily track custom events
+- Limited filtering and segmentation
+- No performance metrics
+- No data portability
+
+**Rybbit:**
+
+- Comprehensive yet simple analytics
+- Custom event tracking
+- Powerful filtering and segmentation
+- Built-in performance monitoring
+- Self-hostable with full data control
+
+## Advanced E-commerce Tracking with Rybbit
+
+### Customer Lifetime Value (CLV) Tracking
+
+Track repeat purchases to understand customer lifetime value:
+
+```javascript
+// Track first purchase
+rybbit.event("First Purchase", {
+ value: orderTotal,
+ customer_id: customerId,
+});
+
+// Track repeat purchases
+rybbit.event("Repeat Purchase", {
+ value: orderTotal,
+ customer_id: customerId,
+ purchase_count: totalPurchases,
+});
+```
+
+### Cart Abandonment Analysis
+
+Track when users add items to cart but don't complete checkout:
+
+```javascript
+// Add to cart
+rybbit.event("Add to Cart", {
+ product_id: productId,
+ value: productPrice,
+});
+
+// Checkout started
+rybbit.event("Checkout Started", {
+ cart_value: totalValue,
+});
+
+// Purchase completed (or not)
+rybbit.event("Purchase", {
+ value: orderTotal,
+});
+```
+
+By tracking these events, you can calculate your cart abandonment rate and work to reduce it.
+
+### Product Category Performance
+
+Track which product categories perform best:
+
+```javascript
+rybbit.event("Product View", {
+ category: "Electronics",
+ subcategory: "Headphones",
+ product_id: productId,
+});
+```
+
+This helps you understand which categories drive the most engagement and sales, informing your inventory and marketing decisions.
+
+## Getting Started with Rybbit for Your E-commerce Store
+
+1. **Sign up or self-host** - Choose between the hosted version for convenience or self-hosting for complete data control
+
+2. **Add the script** - Install the Rybbit tracking script on your e-commerce site (works with any platform)
+
+3. **Set up event tracking** - Add events for your key conversion points (add to cart, checkout, purchase)
+
+4. **Define your metrics** - Decide what success looks like for your business and set up your Rybbit dashboard accordingly
+
+5. **Start analyzing** - Use the filtering and segmentation features to understand your customer behavior
+
+6. **Optimize and iterate** - Use insights from Rybbit to make data-driven decisions about your store
+
+## Best Practices for E-commerce Analytics with Rybbit
+
+**Track What Matters** - Don't track everything, focus on metrics that drive business decisions
+
+**Segment Your Analysis** - Use filters to understand different customer segments, devices, and channels
+
+**Compare Time Periods** - Always look at trends over time, not just individual snapshots
+
+**Combine with Other Data** - Rybbit analytics work best when combined with your e-commerce platform's sales data
+
+**Act on Insights** - Analytics are only valuable if you use them to make changes
+
+**Monitor Performance** - Keep an eye on page performance metrics - they directly impact conversion
+
+**Review Regularly** - Set aside time weekly or monthly to review your analytics and spot trends
+
+## Conclusion
+
+Running a successful e-commerce business requires understanding your customers, your traffic, and your conversion funnel. Rybbit Analytics provides all the tools you need to make data-driven decisions without the complexity, privacy concerns, or performance impact of traditional analytics platforms.
+
+Whether you're just starting out with a small online store or scaling a multi-million dollar e-commerce business, Rybbit gives you the insights you need to grow - in a simple, privacy-respecting package that your customers will appreciate.
+
+The combination of Rybbit's clean interface, powerful filtering capabilities, performance monitoring, and privacy-first approach makes it the ideal analytics solution for modern e-commerce businesses. And with both hosted and self-hosted options, you can choose the setup that best fits your needs.
+
+Ready to get better insights into your e-commerce business? Give Rybbit a try and see how much clearer your data becomes when you focus on what actually matters.
\ No newline at end of file
diff --git a/docs/content/docs/product-analytics/funnels_guide.mdx b/docs/content/docs/product-analytics/funnels_guide.mdx
new file mode 100644
index 000000000..c6f29c36a
--- /dev/null
+++ b/docs/content/docs/product-analytics/funnels_guide.mdx
@@ -0,0 +1,401 @@
+---
+title: Funnels
+description: Understanding Rybbit's funnels tab
+---
+
+# 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.
+
+<img src="/blog/rybbit_funnels_dashboard.png" alt="Rybbit's Funnel dashboard" />
+
+
+## What is Funnel Analysis?
+
+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.
+
+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.
+
+## Why Funnel Analysis Matters
+
+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:
+
+**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.
+
+**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?
+
+**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.
+
+**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.
+
+## 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.
+
+## 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
diff --git a/docs/content/docs/product-analytics/journeys_dashboard.mdx b/docs/content/docs/product-analytics/journeys_dashboard.mdx
new file mode 100644
index 000000000..5c9c9ebe7
--- /dev/null
+++ b/docs/content/docs/product-analytics/journeys_dashboard.mdx
@@ -0,0 +1,240 @@
+---
+title: User Journeys
+description: Understanding Rybbit's user journey tab
+---
+
+# 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.
+
+<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.
+
+### 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.
+
+### 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.
+
+### 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.
+
+## 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
+
+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!
+
+## 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
diff --git a/docs/content/docs/product-analytics/meta.json b/docs/content/docs/product-analytics/meta.json
index 43e6f43d4..6035e72a1 100644
--- a/docs/content/docs/product-analytics/meta.json
+++ b/docs/content/docs/product-analytics/meta.json
@@ -1,4 +1,4 @@
{
"title": "Product Analytics",
- "pages": ["bounce-rate", "replay-session"]
-}
+ "pages": ["retention_guide", "journeys_dashboard", "replay-session", "funnels_guide"]
+}
\ No newline at end of file
diff --git a/docs/content/docs/product-analytics/replay-session.mdx b/docs/content/docs/product-analytics/replay-session.mdx
index d07ea935d..cc0441168 100644
--- a/docs/content/docs/product-analytics/replay-session.mdx
+++ b/docs/content/docs/product-analytics/replay-session.mdx
@@ -1,5 +1,5 @@
---
-title: Session Replay Dashboard
+title: Session Replay
description: A guide to how to use Rybbit's Session Replay Tab
---
diff --git a/docs/content/docs/product-analytics/retention_guide.mdx b/docs/content/docs/product-analytics/retention_guide.mdx
new file mode 100644
index 000000000..25bca9481
--- /dev/null
+++ b/docs/content/docs/product-analytics/retention_guide.mdx
@@ -0,0 +1,149 @@
+---
+title: Retention Analytics
+description: Understanding Rybbit's retention tab
+---
+
+# 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.
+
+## 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
+
+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.
+
+## How to Read the Retention Table
+
+The retention table in Rybbit shows you how many users from each cohort returned after a certain period. Here's what you'll see:
+
+### 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.
+
+### 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?
+
+### 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.
+
+### 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.
+
+## 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
diff --git a/docs/content/docs/web-analytics/goals-tab.mdx b/docs/content/docs/web-analytics/goals-tab.mdx
index 79ddb51d9..8fc34c348 100644
--- a/docs/content/docs/web-analytics/goals-tab.mdx
+++ b/docs/content/docs/web-analytics/goals-tab.mdx
@@ -5,18 +5,14 @@ description: How to use the Goals dashboard in Rybbit Analytics
## The Goals Tab
-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.
+![Rybbit Goals Dashboard](/blog/rybbit_goals_dashboard.png)
-![Screenshot of Goals tab overview]
-*Image: Goals tab interface*
+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 Your First Goal
Click "Create Goal" to open the goal setup interface.
-![Screenshot of goal creation form]
-*Image: New goal setup screen*
-
You'll need to provide:
**Goal Name**: Something descriptive like "Newsletter Signup" or "Purchase Complete"
@@ -29,9 +25,6 @@ You'll need to provide:
**Value** (optional): Assign a monetary value to conversions
-![Screenshot showing goal type selection]
-*Image: Choosing goal type*
-
### Page Path Goals
Page path goals trigger when users visit specific URLs. Common examples:
@@ -41,9 +34,6 @@ Page path goals trigger when users visit specific URLs. Common examples:
- Onboarding completion pages
- Download confirmation pages
-![Screenshot of page path goal configuration]
-*Image: Setting up a page path goal*
-
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.
@@ -53,9 +43,6 @@ Enter the URL path exactly as it appears in your analytics. Use wildcards for dy
Event goals trigger when custom events fire. You need to have custom event tracking implemented first.
-![Screenshot of event goal configuration]
-*Image: Setting up an event-based goal*
-
Common event goals:
- Button clicks ("signup_clicked")
- Video completions ("video_complete")
@@ -68,9 +55,6 @@ Events offer more flexibility than page goals. You can track actions that don't
After creating goals, the Goals tab displays your conversion metrics.
-![Screenshot of goals dashboard with multiple goals]
-*Image: Overview of all active goals*
-
For each goal, you'll see:
- **Conversion Count**: How many times this goal converted
- **Conversion Rate**: Percentage of sessions that converted
@@ -81,9 +65,6 @@ For each goal, you'll see:
Click any goal to see detailed funnel analysis. This shows the path users take before converting.
-![Screenshot of funnel analysis for a goal]
-*Image: Conversion funnel visualization*
-
The funnel reveals:
- Top entry pages for converting sessions
- Most common paths to conversion
@@ -100,9 +81,6 @@ This analysis helps you:
See which channels drive the most conversions. The Goals tab breaks down conversions by source.
-![Screenshot of goal conversions by source]
-*Image: Conversion rates by traffic channel*
-
Compare conversion rates across:
- Organic search
- Social media
@@ -116,9 +94,6 @@ Maybe organic search converts at 5% while social converts at 1%. This tells you
Device type affects conversion rates. Mobile users often convert less than desktop users, but that varies by industry.
-![Screenshot of goals by device type]
-*Image: Conversion rates across devices*
-
If mobile conversion rates lag significantly, you need mobile optimization. Focus on:
- Simplifying mobile checkout flows
- Reducing form fields
@@ -129,9 +104,6 @@ If mobile conversion rates lag significantly, you need mobile optimization. Focu
Assigning values to goals lets you track revenue or value generated through your site.
-![Screenshot of goal value configuration]
-*Image: Adding monetary value to a goal*
-
Set values based on:
- Average order value (for purchases)
- Estimated lead value (for B2B sites)
@@ -159,18 +131,12 @@ Most sites should track several goals. Create goals for:
- Account creation
- Premium upgrades
-![Screenshot showing multiple active goals]
-*Image: Dashboard with various goal types*
-
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.
-![Screenshot of time to conversion chart]
-*Image: Conversion timing distribution*
-
Most conversions happen:
- Immediately (same session)
- Within 24 hours
diff --git a/docs/package-lock.json b/docs/package-lock.json
index 2ef0ab2fc..62bfd69d5 100644
--- a/docs/package-lock.json
+++ b/docs/package-lock.json
@@ -109,6 +109,7 @@
"integrity": "sha512-e7jT4DxYvIDLk1ZHmU/m/mB19rex9sv0c2ftBtjSBv+kVM/902eh0fINUzD7UwLLNR+jU585GxUJ8/EBfAM5fw==",
"dev": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"@babel/code-frame": "^7.27.1",
"@babel/generator": "^7.28.5",
@@ -1856,17 +1857,6 @@
"node": ">=12.4.0"
}
},
- "node_modules/@opentelemetry/api": {
- "version": "1.9.0",
- "resolved": "https://registry.npmjs.org/@opentelemetry/api/-/api-1.9.0.tgz",
- "integrity": "sha512-3giAOQvZiH5F9bMlMiv8+GSPMeqg0dbaeo58/0SlA9sxSqZhnUtxzX9/2FzyhS9sWQf5S0GJE0AKBrFqjpeYcg==",
- "license": "Apache-2.0",
- "optional": true,
- "peer": true,
- "engines": {
- "node": ">=8.0.0"
- }
- },
"node_modules/@orama/orama": {
"version": "3.1.16",
"resolved": "https://registry.npmjs.org/@orama/orama/-/orama-3.1.16.tgz",
@@ -3386,6 +3376,7 @@
"integrity": "sha512-6mDvHUFSjyT2B2yeNx2nUgMxh9LtOWvkhIU3uePn2I2oyNymUAX1NIsdgviM4CH+JSrp2D2hsMvJOkxY+0wNRA==",
"devOptional": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"csstype": "^3.0.2"
}
@@ -3396,6 +3387,7 @@
"integrity": "sha512-9KQPoO6mZCi7jcIStSnlOWn2nEF3mNmyr3rIAsGnAbQKYbRLyqmeSc39EVgtxXVia+LMT8j3knZLAZAh+xLmrw==",
"devOptional": true,
"license": "MIT",
+ "peer": true,
"peerDependencies": {
"@types/react": "^19.2.0"
}
@@ -3459,6 +3451,7 @@
"integrity": "sha512-BnOroVl1SgrPLywqxyqdJ4l3S2MsKVLDVxZvjI1Eoe8ev2r3kGDo+PcMihNmDE+6/KjkTubSJnmqGZZjQSBq/g==",
"dev": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"@typescript-eslint/scope-manager": "8.46.2",
"@typescript-eslint/types": "8.46.2",
@@ -3994,6 +3987,7 @@
"resolved": "https://registry.npmjs.org/acorn/-/acorn-8.15.0.tgz",
"integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==",
"license": "MIT",
+ "peer": true,
"bin": {
"acorn": "bin/acorn"
},
@@ -4374,6 +4368,7 @@
}
],
"license": "MIT",
+ "peer": true,
"dependencies": {
"baseline-browser-mapping": "^2.8.19",
"caniuse-lite": "^1.0.30001751",
@@ -4540,6 +4535,7 @@
"resolved": "https://registry.npmjs.org/chevrotain/-/chevrotain-11.0.3.tgz",
"integrity": "sha512-ci2iJH6LeIkvP9eJW6gpueU8cnZhv85ELY8w8WiFtNjMHA5ad6pQLaJo9mEly/9qUyCpvqX8/POVUTf18/HFdw==",
"license": "Apache-2.0",
+ "peer": true,
"dependencies": {
"@chevrotain/cst-dts-gen": "11.0.3",
"@chevrotain/gast": "11.0.3",
@@ -4732,6 +4728,7 @@
"resolved": "https://registry.npmjs.org/cytoscape/-/cytoscape-3.33.1.tgz",
"integrity": "sha512-iJc4TwyANnOGR1OmWhsS9ayRS3s+XQ185FmuHObThD+5AeJCakAAbWv8KimMTt08xCCLNgneQwFp+JRJOr9qGQ==",
"license": "MIT",
+ "peer": true,
"engines": {
"node": ">=0.10"
}
@@ -5132,6 +5129,7 @@
"resolved": "https://registry.npmjs.org/d3-selection/-/d3-selection-3.0.0.tgz",
"integrity": "sha512-fmTRWbNMmsmWq6xJV8D19U/gw/bwrHfNXxrIN+HfZgnzqTHp9jOmKMhsTUjXOJnZOdZY9Q28y4yebKzqDKlxlQ==",
"license": "ISC",
+ "peer": true,
"engines": {
"node": ">=12"
}
@@ -5757,6 +5755,7 @@
"integrity": "sha512-t5aPOpmtJcZcz5UJyY2GbvpDlsK5E8JqRqoKtfiKE3cNh437KIqfJr3A3AKf5k64NPx6d0G3dno6XDY05PqPtw==",
"dev": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"@eslint-community/eslint-utils": "^4.8.0",
"@eslint-community/regexpp": "^4.12.1",
@@ -5942,6 +5941,7 @@
"integrity": "sha512-whOE1HFo/qJDyX4SnXzP4N6zOWn79WhnCUY/iDR0mPfQZO8wcYE4JClzI2oZrhBnnMUCBCHZhO6VQyoBU95mZA==",
"dev": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"@rtsao/scc": "^1.1.0",
"array-includes": "^3.1.9",
@@ -6453,6 +6453,7 @@
"resolved": "https://registry.npmjs.org/fumadocs-core/-/fumadocs-core-16.0.3.tgz",
"integrity": "sha512-3kr1u0V0iHgIcQek+iRQKvJdbHp+Th8PAO4t74ZzgMpTbHOH6mI1zEpMEask/fTZHKOxDLSJ+q16s+1sAvC5yg==",
"license": "MIT",
+ "peer": true,
"dependencies": {
"@formatjs/intl-localematcher": "^0.6.2",
"@orama/orama": "^3.1.16",
@@ -8202,6 +8203,7 @@
"resolved": "https://registry.npmjs.org/lucide-react/-/lucide-react-0.548.0.tgz",
"integrity": "sha512-63b16z63jM9yc1MwxajHeuu0FRZFsDtljtDjYm26Kd86UQ5HQzu9ksEtoUUw4RBuewodw/tGFmvipePvRsKeDA==",
"license": "ISC",
+ "peer": true,
"peerDependencies": {
"react": "^16.5.1 || ^17.0.0 || ^18.0.0 || ^19.0.0"
}
@@ -9454,6 +9456,7 @@
"resolved": "https://registry.npmjs.org/next/-/next-16.0.0.tgz",
"integrity": "sha512-nYohiNdxGu4OmBzggxy9rczmjIGI+TpR5vbKTsE1HqYwNm1B+YSiugSrFguX6omMOKnDHAmBPY4+8TNJk0Idyg==",
"license": "MIT",
+ "peer": true,
"dependencies": {
"@next/env": "16.0.0",
"@swc/helpers": "0.5.15",
@@ -10040,6 +10043,7 @@
"resolved": "https://registry.npmjs.org/react/-/react-19.2.0.tgz",
"integrity": "sha512-tmbWg6W31tQLeB5cdIBOicJDJRR2KzXsV7uSK9iNfLWQ5bIZfxuPEHp7M8wiHyHnn0DD1i7w3Zmin0FtkrwoCQ==",
"license": "MIT",
+ "peer": true,
"engines": {
"node": ">=0.10.0"
}
@@ -10049,6 +10053,7 @@
"resolved": "https://registry.npmjs.org/react-dom/-/react-dom-19.2.0.tgz",
"integrity": "sha512-UlbRu4cAiGaIewkPyiRGJk0imDN2T3JjieT6spoL2UeSf5od4n5LB/mQ4ejmxhCFT1tYe8IvaFulzynWovsEFQ==",
"license": "MIT",
+ "peer": true,
"dependencies": {
"scheduler": "^0.27.0"
},
@@ -11128,7 +11133,8 @@
"resolved": "https://registry.npmjs.org/tailwindcss/-/tailwindcss-4.1.16.tgz",
"integrity": "sha512-pONL5awpaQX4LN5eiv7moSiSPd/DLDzKVRJz8Q9PgzmAdd1R4307GQS2ZpfiN7ZmekdQrfhZZiSE5jkLR4WNaA==",
"devOptional": true,
- "license": "MIT"
+ "license": "MIT",
+ "peer": true
},
"node_modules/tapable": {
"version": "2.3.0",
@@ -11350,6 +11356,7 @@
"integrity": "sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==",
"dev": true,
"license": "Apache-2.0",
+ "peer": true,
"bin": {
"tsc": "bin/tsc",
"tsserver": "bin/tsserver"
@@ -11892,6 +11899,7 @@
"resolved": "https://registry.npmjs.org/zod/-/zod-4.1.12.tgz",
"integrity": "sha512-JInaHOamG8pt5+Ey8kGmdcAcg3OL9reK8ltczgHTAwNhMys/6ThXHityHxVV2p3fkw/c+MAvBHFVYHFZDmjMCQ==",
"license": "MIT",
+ "peer": true,
"funding": {
"url": "https://github.com/sponsors/colinhacks"
}
diff --git a/docs/public/blog/rybbit_funnels_dashboard.png b/docs/public/blog/rybbit_funnels_dashboard.png
new file mode 100644
index 000000000..1ff75b444
Binary files /dev/null and b/docs/public/blog/rybbit_funnels_dashboard.png differ
diff --git a/docs/public/blog/rybbit_goals_dashboard.png b/docs/public/blog/rybbit_goals_dashboard.png
new file mode 100644
index 000000000..df6aa88f4
Binary files /dev/null and b/docs/public/blog/rybbit_goals_dashboard.png differ
diff --git a/docs/public/blog/rybbit_journey_dashboard.png b/docs/public/blog/rybbit_journey_dashboard.png
new file mode 100644
index 000000000..a14f7caeb
Binary files /dev/null and b/docs/public/blog/rybbit_journey_dashboard.png differ
diff --git a/docs/public/blog/rybbit_retention_dashboard.png b/docs/public/blog/rybbit_retention_dashboard.png
new file mode 100644
index 000000000..b5d145757
Binary files /dev/null and b/docs/public/blog/rybbit_retention_dashboard.png differ
diff --git a/docs/src/app/blog/[...slug]/page.tsx b/docs/src/app/blog/[...slug]/page.tsx
index 5b6b57f8e..a45c9e904 100644
--- a/docs/src/app/blog/[...slug]/page.tsx
+++ b/docs/src/app/blog/[...slug]/page.tsx
@@ -168,7 +168,7 @@ export default async function BlogPostPage(props: { params: Promise<{ slug: stri
components={{
...defaultMdxComponents,
pre: (props: React.ComponentPropsWithoutRef<"pre">) => (
- <Pre {...props} className="bg-neutral-900 border border-neutral-800 rounded-lg" />
+ <Pre {...props} className="bg-neutral-50 dark:bg-neutral-900 border border-neutral-200 dark:border-neutral-800 rounded-lg" />
),
code: ({ className, ...props }: React.ComponentPropsWithoutRef<"code">) => {
// Check if this code is inside a pre tag (code block)
@@ -177,7 +177,7 @@ export default async function BlogPostPage(props: { params: Promise<{ slug: stri
return <code className={className} {...props} />;
}
// Inline code
- return <code className="bg-neutral-900 px-1.5 py-0.5 rounded text-sm" {...props} />;
+ return <code className="bg-neutral-50 dark:bg-neutral-900 px-1.5 py-0.5 rounded text-sm" {...props} />;
},
}}
/>