Raah.dev

Product Introduction

1. Definition: Raah.dev is a comprehensive, privacy-first analytics and real-user monitoring (RUM) platform designed for modern product teams. It technically integrates revenue analytics, user journey tracking, and network observability into a single dashboard.
2. Core Value Proposition: It exists to bridge the critical data gap between business metrics and technical performance. Raah.dev connects payments and conversions directly with page speed, API latency, errors, and ISP performance, enabling teams to understand not just what users are doing, but why they convert or churn based on their real-world experience.

Main Features

1. Revenue Attribution & Analytics: This feature directly ties Stripe payments or confirmed backend events to specific user visits. How it works: It uses a cookie-free browser beacon to track visits and, when a payment is confirmed (via Stripe sync or server-side event), matches the payment to the originating visit using browser ID or hashed identity linking. This provides net revenue, refund tracking, and attribution by channel, campaign, and landing page.
2. Funnel & Journey Analysis with Performance Context: This goes beyond traditional funnel analysis by displaying technical performance metrics alongside conversion steps. How it works: The platform visualizes user paths (journeys) and defined funnels (e.g., Pricing -> Checkout -> Purchase). At each step, it can surface correlated data like the p95 latency of a checkout API for visits that dropped off, or Core Web Vitals scores for key pages, providing context for abandonment.
3. Real-User Observability (RUM): This feature provides detailed performance monitoring from the end-user's perspective. How it works: The JavaScript beacon collects detailed timing data for page loads, API calls, and third-party scripts. This data is broken down by geography, Internet Service Provider (ISP), browser, and device, allowing teams to pinpoint performance issues affecting specific user segments in real-time.

Problems Solved

1. Pain Point: Product and engineering teams often operate in silos, using separate tools for business analytics (e.g., Google Analytics, Mixpanel) and performance monitoring (e.g., New Relic, Datadog RUM). This disconnect makes it difficult to prove the business impact of slow pages or API errors.
2. Target Audience: The primary personas are Product Managers, Growth Marketers, and Frontend/Full-Stack Engineers in SaaS and e-commerce companies who need to correlate user behavior, revenue, and technical performance to make informed prioritization decisions.
3. Use Cases: Essential scenarios include: diagnosing checkout abandonment by revealing slow payment gateway APIs for specific ISPs; justifying performance optimization work by showing "revenue at risk" from users experiencing poor Core Web Vitals; and evaluating marketing channel ROI not just by traffic, but by the quality of user experience and conversion rate per channel.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):

   • Pros: Unifies three critical data domains (business, behavioral, performance) into a single workflow, eliminating context switching. Privacy-first by design with cookie-free tracking and user-controlled identity. Provides actionable "revenue at risk" estimates to prioritize fixes. Direct Stripe integration simplifies revenue tracking.
   • Cons: As a newer, integrated platform, it may lack the deep, specialized depth of best-in-class standalone tools (e.g., the query flexibility of a pure BI tool or the deep trace-level diagnostics of an APM). The value is maximized for teams willing to adopt its unified view.

2. Key Alternatives & Differentiation:

   • vs. Plausible/Umami: Raah.dev differentiates by moving beyond simple, privacy-friendly pageview analytics. While Plausible and Umami excel at lightweight traffic stats, Raah adds revenue tracking, detailed journey mapping, and full real-user performance observability, targeting product teams needing deeper insights.
   • vs. Vercel Analytics/Netlify Analytics: These are provider-specific and primarily focused on frontend performance metrics for sites hosted on their platforms. Raah.dev is platform-agnostic, connects to any backend (especially via its API observability), and integrates direct revenue data, making it suitable for complex, full-stack applications with their own payment processing.
   • vs. Traditional RUM (New Relic, Datadog): While these tools offer powerful performance diagnostics, they are often complex and siloed from business metrics. Raah.dev offers a more streamlined, product-focused interface that directly juxtaposes performance data with conversion funnels and revenue, lowering the barrier to analysis for cross-functional teams.

Frequently Asked Questions (FAQ)

1. How does Raah.dev track revenue without compromising privacy? Raah.dev uses a cookie-free beacon to generate random browser IDs. Revenue is tracked by matching confirmed payment events (from Stripe or your backend) to these anonymous IDs. For logged-in users, you can optionally send a hashed user ID you control, maintaining privacy while enabling user-level analysis.
2. Can Raah.dev replace my existing analytics and APM tools? Raah.dev is designed as a unified dashboard for product-focused insights. It can replace simpler analytics tools (like Google Analytics for basic traffic) and provide RUM capabilities. For deep application performance management (APM) with code-level profiling or infrastructure monitoring, you may still need a specialized APM or infra tool alongside it.
3. What is "revenue at risk" and how is it calculated? "Revenue at risk" is an estimate of potential conversion value lost due to subpar user experience. It is calculated by analyzing the conversion rate gap between users who experienced good performance (e.g., fast API response, good Core Web Vitals) versus those who experienced poor performance, and extrapolating that gap to the total traffic and average order value.
4. Does Raah.dev support tracking for single-page applications (SPAs)? Yes, the Raah.dev JavaScript SDK is built to handle modern SPAs. It automatically tracks pageview changes via the History API, captures client-side performance metrics, and allows for manual event tracking within dynamic application states.
5. How does the ISP and carrier performance breakdown help? This feature identifies if users from specific internet providers (e.g., Comcast, Verizon, Vodafone) or mobile carriers experience significantly slower API latency or higher error rates. This is crucial for diagnosing issues that are not global but affect key customer segments based on their network, which traditional geo-based monitoring often misses.