<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Peaka - Medium]]></title>
        <description><![CDATA[Peaka helps teams connect, unify, and query all their data sources — without moving or duplicating data. We share insights on data virtualization, analytics, connector performance, and use cases to help you build better data experiences. - Medium]]></description>
        <link>https://medium.com/peaka?source=rss----351a5419f89c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Peaka - Medium</title>
            <link>https://medium.com/peaka?source=rss----351a5419f89c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:23:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/peaka" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Listing Calls Data from Multiple ServiceTitan Accounts]]></title>
            <link>https://medium.com/peaka/listing-calls-data-from-multiple-servicetitan-accounts-4738ad4c9b5f?source=rss----351a5419f89c---4</link>
            <guid isPermaLink="false">https://medium.com/p/4738ad4c9b5f</guid>
            <category><![CDATA[servicetitan]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Mevlüt Can Tuna]]></dc:creator>
            <pubDate>Wed, 03 Sep 2025 13:25:45 GMT</pubDate>
            <atom:updated>2025-10-13T08:27:14.254Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*wzaTuKjhmnHkLiQT3rbiBQ.png" /></figure><p>As a ServiceTitan consultant, you’re constantly juggling calls data across dozens of client accounts. Whether you’re preparing monthly <a href="https://www.peaka.com/blog/consultants-servicetitan-kpi-dashboards">KPI dashboards</a>, analyzing call performance for coaching sessions, or delivering dashboard updates to multiple clients, <a href="https://www.peaka.com/blog/servicetitan-manual-data-export-costs/">manual data exports</a> from each ServiceTitan instance are eating up your billable hours.</p><p>Peaka transforms how consulting firms deliver ServiceTitan analytics. Instead of building custom dashboards for each client or wrestling with spreadsheet exports, you can instantly <a href="https://www.peaka.com/blog/manage-multiple-servicetitan-accounts">unify data from multiple ServiceTitan accounts</a> using natural language queries — no coding required.</p><p>In this guide, we’ll show you how to connect multiple client ServiceTitan accounts to Peaka and use our AI chatbot to instantly retrieve calls data for any client — turning hours of manual work into minutes of automated insights.</p><h3><strong>Setting Up Your ServiceTitan Connections</strong></h3><p>Before you can query calls data for your clients, you’ll need to connect their ServiceTitan accounts to Peaka. The process is straightforward and takes just a few minutes per client.</p><p>First, navigate to the Connections section in your Peaka workspace and select ServiceTitan from the available integrations. You’ll need API credentials from each client’s ServiceTitan admin panel — most clients can generate these quickly with your guidance.</p><p>Once connected, Peaka will automatically sync each client’s ServiceTitan data, including calls records, customer information, and call tracking data. This gives you immediate access to query calls data across your entire client portfolio from a single workspace.</p><p>For detailed step-by-step instructions, check out our comprehensive guide: <a href="https://docs.peaka.com/integrations/service-titan">Connect your ServiceTitan Account to Peaka</a></p><h3><strong>Getting Client Calls Data in 4 Simple Steps</strong></h3><p>Once your clients’ ServiceTitan data is flowing into Peaka, retrieving calls information for any client becomes incredibly straightforward. Here’s how to pull calls data from multiple client accounts:</p><h4><strong>Step 1: Write your query</strong></h4><p>Navigate to your Peaka workspace and create a new query. Select the <strong>AI|GPT</strong> section to access our natural language query interface.</p><p><em>Pro tip: New to Peaka queries? Check out our </em><a href="https://docs.peaka.com/connecting-your-data/peaka-query#what-is-a-peaka-query"><em>comprehensive guide</em></a><em> to get up to speed.</em></p><h4><strong>Step 2: Ask in natural language</strong></h4><p>Simply type your request in natural language. For example:</p><pre>List all calls from all of my ServiceTitan accounts.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_uux-KCqziMg8s-1KRq0Dg.png" /></figure><h4><strong>Step 3: Select your data sources</strong></h4><p>Peaka will automatically suggest the relevant tables. For calls data, you’ll typically need:</p><ul><li><strong>Calls Table</strong>: your_service_titan_connection &gt; telecom &gt; calls</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pS8j1wWus2m3frYoFL2e-A.png" /></figure><h4><strong>Step 4: Execute and analyze</strong></h4><p>Hit run and watch Peaka generate the SQL query behind the scenes. Your results appear instantly, showing all calls from your client’s ServiceTitan account with complete details — ready to drop into your monthly KPI report or coaching session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JZS2cSvd7D2Z8kmYnP3-Qw.png" /></figure><h4><strong>Conclusion: Deliver premium analytics without the overhead</strong></h4><p>As a ServiceTitan consultant, your time should be spent coaching clients and growing your practice — not wrestling with data exports and dashboard builds. With Peaka’s AI chatbot, you can deliver professional calls analytics to any client in minutes, not hours.</p><p>Whether you’re preparing monthly KPI reports, analyzing call performance trends, or building premium dashboard offerings, you now have the tools to scale your consulting practice without hiring developers or learning complex <a href="https://www.peaka.com/blog/how-to-connect-servicetitan-to-looker-studio">BI tools</a>.</p><p>Ready to transform your ServiceTitan consulting delivery? Your next client success story is just one conversation away.</p><p><a href="https://peaka.studio/signup">Sign up to Peaka</a> for free today.</p><p><a href="https://calendly.com/peaka/demo">Book a quick demo</a> and see how Peaka can help simplify ServiceTitan reporting for you and your clients.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4738ad4c9b5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/peaka/listing-calls-data-from-multiple-servicetitan-accounts-4738ad4c9b5f">Listing Calls Data from Multiple ServiceTitan Accounts</a> was originally published in <a href="https://medium.com/peaka">Peaka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Listing Technician Data from Multiple ServiceTitan Accounts]]></title>
            <link>https://medium.com/peaka/listing-technician-data-from-multiple-servicetitan-accounts-331053f56bf8?source=rss----351a5419f89c---4</link>
            <guid isPermaLink="false">https://medium.com/p/331053f56bf8</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[servicetitan]]></category>
            <dc:creator><![CDATA[Mevlüt Can Tuna]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 12:16:21 GMT</pubDate>
            <atom:updated>2025-09-03T12:59:17.836Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*wzaTuKjhmnHkLiQT3rbiBQ.png" /></figure><p>Managing technician data across multiple ServiceTitan accounts is a common challenge for PE firms and multi-location service businesses. Whether you’re consolidating workforce reports, analyzing technician performance across brands, or preparing operational updates, you need an efficient way to pull technician data from all your ServiceTitan instances.</p><p>Peaka offers multiple ways to access and analyze your ServiceTitan data through SQL queries, table views, or our AI chatbot. This flexibility means you can get the consolidated technician data you need from multiple accounts, regardless of your technical background.</p><p>In this guide, we’ll walk you through connecting multiple ServiceTitan accounts to Peaka and use our AI chatbot to instantly retrieve and consolidate technician data across your entire portfolio with no SQL required.</p><h3><strong>Setting Up Your ServiceTitan Connections</strong></h3><p>Before you can query technician data, you’ll need to connect your ServiceTitan account to Peaka. The process is straightforward and takes just a few minutes.</p><p>First, navigate to the Connections section in your Peaka workspace and select ServiceTitan from the available integrations. You’ll need your ServiceTitan API credentials, which you can generate from your ServiceTitan admin panel.</p><p>Once connected, Peaka will automatically sync your ServiceTitan data, including technician records, job assignments, and scheduling information. This gives you immediate access to query technician data across all your connected accounts through our platform.</p><p>For detailed step-by-step instructions, check out our comprehensive guide: <a href="https://docs.peaka.com/integrations/service-titan">Connect your ServiceTitan Account to Peaka</a></p><h3><strong>Getting Invoices Data in 4 Simple Steps</strong></h3><p>Once your ServiceTitan data is flowing into Peaka, retrieving technicians information becomes incredibly straightforward. Here’s how to pull all technicians from multiple ServiceTitan accounts:</p><h4><strong>Step 1: Start a New Query</strong></h4><p>Navigate to your Peaka workspace and create a new query. Select the <strong>AI|GPT</strong> section to access our natural language query interface.</p><p><em>Pro tip: New to Peaka queries? Check out our </em><a href="https://docs.peaka.com/connecting-your-data/peaka-query#what-is-a-peaka-query"><em>comprehensive guide</em></a><em> to get up to speed.</em></p><h4><strong>Step 2: Ask in Plain English</strong></h4><p>Simply type your request in natural language. For example:</p><pre>List all technicians from all of my ServiceTitan accounts.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lx-r8UiNYeb9H40dmrKKtQ.png" /></figure><h4><strong>Step 3: Select Your Data Sources</strong></h4><p>Peaka will automatically suggest the relevant tables. For employee job data, you’ll typically need:</p><ul><li><strong>Technicians Table</strong>: your_service_titan_connection &gt; settings &gt; technicians</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jxxcEfxp9TBkCisJ1Eb4QA.png" /></figure><h4><strong>Step 4: Execute and Analyze</strong></h4><p>Hit run and watch Peaka generate the SQL query behind the scenes. Your results appear instantly, showing all technicians from your connected ServiceTitan accounts with complete details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*46xTIBCC8yvqVKg1-p16xQ.png" /></figure><h4><strong>Conclusion: Convert manual chaos into organized intelligence</strong></h4><p>Managing technician data across multiple ServiceTitan accounts doesn’t have to mean juggling spreadsheets and manual exports. With Peaka’s AI chatbot, you can consolidate workforce data from your entire portfolio using natural language just ask and get instant results.</p><p>Whether you’re tracking performance metrics, planning resource allocation, or preparing executive reports, you now have the tools to make data-driven decisions across all your ServiceTitan instances. No technical expertise required, no time wasted on manual processes.</p><p>Ready to transform how you handle multi-account ServiceTitan data? Your technician insights are just one conversation away.</p><p><a href="https://peaka.studio/signup">Sign up to Peaka</a> for free today.</p><p><a href="https://calendly.com/peaka/demo">Book a quick demo</a> and see how Peaka can help simplify ServiceTitan reporting for you and your clients.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=331053f56bf8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/peaka/listing-technician-data-from-multiple-servicetitan-accounts-331053f56bf8">Listing Technician Data from Multiple ServiceTitan Accounts</a> was originally published in <a href="https://medium.com/peaka">Peaka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Listing All Jobs for an Employee in ServiceTitan Using Peaka]]></title>
            <link>https://medium.com/peaka/listing-all-jobs-for-an-employee-in-servicetitan-using-peaka-04d7501a9968?source=rss----351a5419f89c---4</link>
            <guid isPermaLink="false">https://medium.com/p/04d7501a9968</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[servicetitan]]></category>
            <dc:creator><![CDATA[Mevlüt Can Tuna]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 12:16:18 GMT</pubDate>
            <atom:updated>2025-09-03T12:58:56.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*wzaTuKjhmnHkLiQT3rbiBQ.png" /></figure><p>Managing employee performance in ServiceTitan requires quick access to job data. Whether you’re tracking technician productivity, analyzing job completion rates, or preparing performance reviews, you need an efficient way to pull all jobs assigned to specific employees.</p><p>Peaka offers multiple ways to access and analyze your ServiceTitan data — through SQL queries, table views, or our AI chatbot. This flexibility means you can get the employee job data you need, regardless of your technical background.</p><p>In this guide, we’ll walk you through connecting ServiceTitan to Peaka and use our AI chatbot to instantly retrieve all jobs for any employee in your organization — no SQL required.</p><h3><strong>Setting Up Your ServiceTitan Connection</strong></h3><p>Before you can query employee job data, you’ll need to connect your ServiceTitan account to Peaka. The process is straightforward and takes just a few minutes.</p><p>First, navigate to the Connections section in your Peaka workspace and select ServiceTitan from the available integrations. You’ll need your ServiceTitan API credentials, which you can generate from your ServiceTitan admin panel.</p><p>Once connected, Peaka will automatically sync your ServiceTitan data, including employee records, job assignments, and scheduling information. This gives you immediate access to query any employee’s job history through our platform.</p><p>For detailed step-by-step instructions, check out our comprehensive guide: <a href="https://docs.peaka.com/integrations/service-titan">Connect your ServiceTitan Account to Peaka</a></p><h3><strong>Getting Employee Job Data in 4 Simple Steps</strong></h3><p>Once your ServiceTitan data is flowing into Peaka, retrieving employee job information becomes incredibly straightforward. Here’s how to pull all jobs for any specific employee:</p><h4><strong>Step 1: Start a New Query</strong></h4><p>Navigate to your Peaka workspace and create a new query. Select the <strong>**AI|GPT**</strong> section to access our natural language query interface.</p><p><em>Pro tip: New to Peaka queries? Check out our </em><a href="https://docs.peaka.com/connecting-your-data/peaka-query#what-is-a-peaka-query"><em>comprehensive guide</em></a><em> to get up to speed.</em></p><h4><strong>Step 2: Ask in Plain English</strong></h4><p>Simply type your request in natural language. For example:</p><pre>List all jobs assigned to the employee named Can Tuna, filtered by the user who created them.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jk6SEUoBJnn2Fu4pMTlJtA.png" /></figure><h4><strong>Step 3: Select Your Data Sources</strong></h4><p>Peaka will automatically suggest the relevant tables. For employee job data, you’ll typically need:</p><ul><li><strong>Jobs table</strong>: your_service_titan_connection &gt; job_planning &gt; jobs</li><li><strong>Employees table</strong>: your_service_titan_connection &gt; settings &gt; employees</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ow1Rd2PkQBTyUP5FZoIBXA.png" /></figure><h4><strong>Step 4: Execute and Analyze</strong></h4><p>Hit run and watch Peaka generate the SQL query behind the scenes. Your results appear instantly, showing all jobs assigned to your specified employee with complete details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9425xZk4HvsoLOrugi3iQ.png" /></figure><h4><strong>Conclusion: Fewer manual steps, faster decision-making</strong></h4><p>With Peaka’s AI chatbot, you can instantly pull any employee’s job data from ServiceTitan using simple prompts — no SQL or manual exports needed. Get immediate insights for better workforce management and faster performance reviews.</p><p><a href="https://peaka.studio/signup">Sign up to Peaka</a> for free today.</p><p><a href="https://calendly.com/peaka/demo">Book a quick demo</a> and see how Peaka can help simplify ServiceTitan reporting for you and your clients.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04d7501a9968" width="1" height="1" alt=""><hr><p><a href="https://medium.com/peaka/listing-all-jobs-for-an-employee-in-servicetitan-using-peaka-04d7501a9968">Listing All Jobs for an Employee in ServiceTitan Using Peaka</a> was originally published in <a href="https://medium.com/peaka">Peaka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to List Invoice Data Across Multiple ServiceTitan Accounts]]></title>
            <link>https://medium.com/peaka/how-to-list-invoice-data-across-multiple-servicetitan-accounts-f743f30b573e?source=rss----351a5419f89c---4</link>
            <guid isPermaLink="false">https://medium.com/p/f743f30b573e</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[peaka]]></category>
            <category><![CDATA[servicetitan]]></category>
            <dc:creator><![CDATA[Mevlüt Can Tuna]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 11:59:51 GMT</pubDate>
            <atom:updated>2025-09-03T12:58:13.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*wzaTuKjhmnHkLiQT3rbiBQ.png" /></figure><p>Managing invoice data across multiple ServiceTitan accounts is a common challenge for PE firms and multi-location service businesses. Whether you’re consolidating financial reports, analyzing revenue trends across brands, or preparing investor updates, you need an efficient way to pull invoice data from all your ServiceTitan instances.</p><p>Peaka offers multiple ways to access and analyze your ServiceTitan data — through SQL queries, table views, or our AI chatbot. This flexibility means you can get the consolidated invoice data you need from multiple accounts, regardless of your technical background.</p><p>In this guide, we’ll walk you through connecting multiple ServiceTitan accounts to Peaka and use our AI chatbot to instantly retrieve and consolidate invoice data across your entire portfolio — no SQL required.</p><h3><strong>Setting Up Your ServiceTitan Connections</strong></h3><p>Before you can query employee job data, you’ll need to connect your ServiceTitan account to Peaka. The process is straightforward and takes just a few minutes.</p><p>First, navigate to the Connections section in your Peaka workspace and select ServiceTitan from the available integrations. You’ll need your ServiceTitan API credentials, which you can generate from your ServiceTitan admin panel.</p><p>Once connected, Peaka will automatically sync your ServiceTitan data, including employee records, job assignments, and scheduling information. This gives you immediate access to query any employee’s job history through our platform.</p><p>For detailed step-by-step instructions, check out our comprehensive guide: <a href="https://docs.peaka.com/integrations/service-titan">Connect your ServiceTitan Account to Peaka</a></p><h3><strong>Getting Invoices Data in 4 Simple Steps</strong></h3><p>Once your ServiceTitan data is flowing into Peaka, retrieving invoice information becomes incredibly straightforward. Here’s how to pull all invoices from multiple ServiceTitan accounts:</p><h4><strong>Step 1: Start a New Query</strong></h4><p>Navigate to your Peaka workspace and create a new query. Select the <strong>AI|GPT</strong> section to access our natural language query interface.</p><p><em>Pro tip: New to Peaka queries? Check out our </em><a href="https://docs.peaka.com/connecting-your-data/peaka-query#what-is-a-peaka-query"><em>comprehensive guide</em></a><em> to get up to speed.</em></p><h4><strong>Step 2: Ask in Plain English</strong></h4><p>Simply type your request in natural language. For example:</p><pre>List all invoices from all of my ServiceTitan accounts.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KTrKWNgjm6YK278fRqfbIA.png" /></figure><h4><strong>Step 3: Select Your Data Sources</strong></h4><p>Peaka will automatically suggest the relevant tables. For employee job data, you’ll typically need:</p><ul><li><strong>Invoices Table </strong>: your_service_titan_connection &gt; accounting &gt; invoices</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAVGyAr0sTNMUGcEAHRfuA.png" /></figure><h4><strong>Step 4: Execute and Analyze</strong></h4><p>Hit run and watch Peaka generate the SQL query behind the scenes. Your results appear instantly, showing all jobs assigned to your specified employee with complete details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q69dgzwC9-kabzZDP-Xc8A.png" /></figure><h4><strong>Conclusion: Less data wrestling, more strategic thinking</strong></h4><p>With Peaka’s AI chatbot, you can instantly pull invoice data from multiple ServiceTitan accounts using simple prompts — no SQL or manual exports needed. Get immediate insights for better financial reporting and portfolio-wide invoice analysis.</p><p><a href="https://peaka.studio/signup">Sign up to Peaka</a> for free today.</p><p><a href="https://calendly.com/peaka/demo">Book a quick demo</a> and see how Peaka can help simplify ServiceTitan reporting for you and your clients.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f743f30b573e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/peaka/how-to-list-invoice-data-across-multiple-servicetitan-accounts-f743f30b573e">How to List Invoice Data Across Multiple ServiceTitan Accounts</a> was originally published in <a href="https://medium.com/peaka">Peaka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build a Customer Health Dashboard with SaaS Data]]></title>
            <link>https://medium.com/peaka/how-to-build-a-customer-health-dashboard-with-saas-data-e0b577a54d1c?source=rss----351a5419f89c---4</link>
            <guid isPermaLink="false">https://medium.com/p/e0b577a54d1c</guid>
            <dc:creator><![CDATA[Ozan Batuhan Ceylan]]></dc:creator>
            <pubDate>Tue, 22 Jul 2025 12:38:17 GMT</pubDate>
            <atom:updated>2025-07-22T12:38:17.328Z</atom:updated>
            <content:encoded><![CDATA[<p>Quickly build a customer health dashboard without ETL pipelines. Integrate data from HubSpot, Stripe, and Zendesk to identify risks and boost retention.</p><h3>Project Overview</h3><p>Before customer dissatisfaction snowballs into churn, what if you could spot the early signs from support tickets, health scores, and revenue trends, all in one dashboard?</p><p>In this tutorial, you will build a <strong>customer health dashboard</strong> that integrates data from <strong>Zendesk</strong>, <strong>Hubspot</strong>, and <strong>Stripe</strong> to track key metrics like <strong>support tickets</strong>, <strong>average MRR (Monthly Recurring Revenue)</strong>, <strong>health scores</strong>, and <strong>churn risk</strong>, all in one unified view. The goal is to help <strong>customer success teams</strong>, <strong>product managers</strong>, and <strong>sales leaders</strong> spot early warning signs, improve retention, and reduce churn.</p><p>This dashboard delivers real value for:</p><ul><li><strong>Customer success teams</strong> focused on proactive churn prevention</li><li><strong>Product managers</strong> looking for deeper insights into account health</li><li><strong>Growth and revenue teams</strong> aiming to maximize customer lifetime value and reduce churn costs</li></ul><p>Best of all, instead of spending weeks on complex <strong>data integration</strong> and dashboard development, you will build this entire solution in just a few hours using <strong>Peaka</strong> for seamless data unification and <strong>v0.dev</strong> for fast frontend generation.</p><p>This dashboard serves as a starting point, a foundational solution that you can build upon and customize further as your needs grow. While it covers key customer health metrics, you can easily extend it with more data sources, advanced analytics, or deeper integrations over time.</p><h3>The Tools We Need</h3><p>To build this customer health dashboard, we’ll rely on a streamlined set of tools that simplify data integration and frontend development without the complexity of traditional data engineering.</p><h4>Peaka</h4><p>Peaka acts as the central platform that connects to your existing data sources and lets you join, transform, and model your data in one place using SQL queries. This approach eliminates the need for setting up complex ETL pipelines or managing separate data warehouses, making it faster and easier to create unified views of your customer data while keeping full control over the data logic.</p><h4>v0.dev</h4><p>Once your data models are ready in Peaka, v0.dev enables you to generate a polished, functional dashboard interface using prompt-based UI creation. This allows you to build and iterate on your frontend quickly without writing boilerplate code.</p><h4>Data Sources</h4><p>We’ll connect Peaka to familiar platforms like Zendesk, Hubspot, and Stripe to pull support ticket data, customer health scores, and subscription revenue information. These integrations provide the raw data needed to power the dashboard’s key metrics.</p><h3>What is Peaka?</h3><p>Peaka is a cloud-native data platform that enables teams to connect, transform, and query data from multiple sources in real-time using standard SQL. Unlike traditional data warehouses that require complex ETL pipelines and data duplication, Peaka provides <strong>virtualized data models</strong> that join and aggregate live data without moving it.</p><p>In this project, Peaka acts as the <strong>central data layer</strong>, unifying disparate datasets from Zendesk, Hubspot, and Stripe into clean, queryable virtual tables. This approach allows you to maintain data freshness and consistency while avoiding the overhead of managing separate infrastructure.</p><p>Peaka’s SQL-first design empowers data engineers and analysts to define business logic directly in the platform, accelerating development cycles and improving data governance. Its seamless integration with downstream tools like v0.dev enables rapid frontend development based on these robust data models.</p><p>By using Peaka, you get the best of both worlds: the flexibility and control of SQL with the efficiency and scalability of a modern data platform.</p><h3>Let’s Dive In</h3><h4>Step 1: Setting Up Your Peaka Project</h4><p>Before connecting data sources or writing queries, you’ll need to create a Peaka project and generate an API key for authentication. Follow these steps:</p><ul><li>Go to <a href="https://peaka.studio/">peaka. studio</a> and log in.</li></ul><blockquote>If you don’t have an account yet, sign up. It only takes a couple of minutes.</blockquote><ul><li>From your dashboard, click <strong>Create New Project</strong> and give it a name.</li><li>Open your newly created project and click the gear icon (⚙️) in the bottom-left sidebar to open <strong>Settings</strong>.</li><li>In the <strong>Settings</strong> panel, go to the <strong>API Keys</strong> tab and click <strong>Create API Key</strong>.</li><li>Copy your <strong>Project ID</strong> from the URL in your browser’s address bar. It should look like this:</li></ul><pre>https://peaka.studio/studio/{project_id}/...</pre><blockquote><em>Make sure to save both your API key and Project ID somewhere safe, you’ll need them in the next step when connecting Peaka to your app.</em></blockquote><h4>Step 2: Connect Your Data Sources</h4><p>Let’s start by connecting your first data source, Zendesk.</p><ol><li>Go to your Peaka workspace and click the <strong>+ Data Source</strong> button at the top left.</li><li>In the search bar, type <strong>Zendesk</strong>, then select it from the list.</li><li>Click <strong>Add New Connection</strong>.</li><li>Enter a <strong>Connection Name</strong> and your <strong>Zendesk subdomain</strong>.</li><li>Click <strong>Sign In</strong>, and authorize Peaka to access your Zendesk account.</li></ol><p>Once this process is complete, your Zendesk data will be ready to use inside Peaka.</p><p>Next, follow a similar process to connect <strong>HubSpot</strong>, search, select, and authorize via the OAuth screen. For <strong>Stripe</strong>, you’ll instead use your Stripe API key when creating the connection.</p><p>Need help? You can find step-by-step instructions for each connector in the Peaka documentation:</p><ul><li><a href="https://docs.peaka.com/integrations/zendesk">Zendesk Integration Guide</a></li><li><a href="https://docs.peaka.com/integrations/hubspot">HubSpot Integration Guide</a></li><li><a href="https://docs.peaka.com/integrations/stripe">Stripe Integration Guide</a></li></ul><h4>Step 3: Creating Your Queries</h4><p>To build a dashboard, you’ll first need to define the queries that power your metrics. Here’s how you can create a query on Peaka:</p><ol><li>Navigate to the <strong>Queries</strong> section in the left sidebar.</li><li>Click <strong>➕ New Query</strong> to start creating a new SQL query.</li><li>Choose <strong>Start from Scratch</strong> instead of using a template. (You can explore templates later for common use cases.)</li><li>Write your SQL and click <strong>Run</strong> to preview the results.</li></ol><p>For a more detailed guide on how to create queries in Peaka, check out <a href="https://docs.peaka.com/connecting-your-data/creating-query">this documentation page</a>.</p><p>Let’s go through the core queries you’ll need:</p><h4>1. Active Tickets</h4><p>This query shows how many active support tickets (with statuses “open” or “pending”) each user has created in the past 30 days. It helps identify users who may need more urgent support.</p><pre>SELECT <br>  u.email AS requester_email, -- Requester&#39;s email address<br>  COUNT(*) AS active_ticket_count -- Count of active tickets per user<br>FROM &quot;zendesk&quot;.&quot;public&quot;.&quot;tickets&quot; t<br>JOIN &quot;zendesk&quot;.&quot;public&quot;.&quot;users&quot; u ON t.requester_id = u.id<br>WHERE t.status IN (&#39;open&#39;, &#39;pending&#39;) -- Only tickets that are still open or pending<br>  AND t.created_at &gt;= CURRENT_DATE - INTERVAL &#39;30&#39; DAY -- Tickets created in the last 30 days<br>GROUP BY u.email; -- Group results by user email</pre><h4>2. Monthly Recurring Revenue (MRR)</h4><p>This query calculates the monthly recurring revenue (MRR) per customer by summing up the unit amounts of active or recently incomplete subscriptions. Useful for understanding current revenue flow.</p><pre>SELECT <br>  c.email AS customer_email, -- Customer&#39;s email address<br>  SUM(p.unit_amount / 100) AS mrr_usd -- Sum of subscription amounts (converted from cents to dollars)<br>FROM &quot;stripe&quot;.&quot;payment&quot;.&quot;subscriptions&quot; s<br>JOIN &quot;stripe&quot;.&quot;payment&quot;.&quot;customers&quot; c ON s.customer_id = c.id<br>JOIN &quot;stripe&quot;.&quot;payment&quot;.&quot;prices&quot; p ON s.plan_id = p.id<br>WHERE s.status IN (&#39;active&#39;, &#39;incomplete_expired&#39;, &#39;incomplete&#39;) -- Active or recently incomplete subscriptions<br>GROUP BY c.email; -- Group results by customer email</pre><h4>3. Churn Risk</h4><p>This query identifies customers who have recently submitted a high number of support tickets and cross-references them with their subscription activity to assess churn risk levels.</p><pre>WITH active_tickets AS (<br>  SELECT <br>    u.email AS customer_email, -- Email of the customer who submitted tickets<br>    COUNT(*) AS ticket_count -- Number of tickets created in the last 30 days<br>  FROM &quot;zendesk&quot;.&quot;public&quot;.&quot;tickets&quot; t<br>  JOIN &quot;zendesk&quot;.&quot;public&quot;.&quot;users&quot; u ON t.requester_id = u.id<br>  WHERE t.created_at &gt;= CURRENT_DATE - INTERVAL &#39;30&#39; DAY<br>  GROUP BY u.email<br>),<br>active_subscriptions AS (<br>  SELECT <br>    c.email AS customer_email, -- Customer email from Stripe<br>    MAX(s.ended_at) AS last_payment_date -- Last subscription end date<br>  FROM &quot;stripe&quot;.&quot;payment&quot;.&quot;subscriptions&quot; s<br>  JOIN &quot;stripe&quot;.&quot;payment&quot;.&quot;customers&quot; c ON s.customer_id = c.id<br>  WHERE s.status = &#39;active&#39;<br>  GROUP BY c.email<br>)<br><br>SELECT <br>  at.customer_email, -- Email from active tickets<br>  at.ticket_count, -- Number of tickets submitted<br>  CASE <br>    WHEN at.ticket_count &gt; 5 AND (asub.last_payment_date IS NULL OR asub.last_payment_date &lt; CURRENT_DATE - INTERVAL &#39;30&#39; DAY) THEN &#39;High&#39; -- High risk if many tickets and no recent payment<br>    WHEN at.ticket_count &gt; 3 THEN &#39;Medium&#39; -- Medium risk if moderate ticket count<br>    ELSE &#39;Low&#39; -- Otherwise low risk<br>  END AS churn_risk<br>FROM active_tickets at<br>LEFT JOIN active_subscriptions asub ON at.customer_email = asub.customer_email;</pre><h4>4. Account Health Score</h4><p>This query calculates a composite health score for each customer by combining their active subscription status, recent open tickets, and churn risk level. The score helps prioritize accounts needing attention.</p><pre>WITH ticket_stats AS (<br>  SELECT <br>    u.email AS customer_email, -- Customer email from Zendesk users<br>    COUNT(*) FILTER (WHERE t.status IN (&#39;open&#39;, &#39;pending&#39;) AND t.created_at &gt;= CURRENT_DATE - INTERVAL &#39;30&#39; DAY) AS open_tickets_last_30d, -- Number of open tickets in last 30 days<br>    COUNT(*) AS total_tickets -- Total number of tickets<br>  FROM &quot;zendesk&quot;.&quot;public&quot;.&quot;tickets&quot; t<br>  JOIN &quot;zendesk&quot;.&quot;public&quot;.&quot;users&quot; u ON t.requester_id = u.id<br>  GROUP BY u.email<br>),<br>active_subscriptions AS (<br>  SELECT <br>    c.email AS customer_email, -- Customer email from Stripe<br>    COUNT(*) &gt; 0 AS has_active_subscription -- Boolean flag for active subscription<br>  FROM &quot;stripe&quot;.&quot;payment&quot;.&quot;subscriptions&quot; s<br>  JOIN &quot;stripe&quot;.&quot;payment&quot;.&quot;customers&quot; c ON s.customer_id = c.id<br>  WHERE s.status = &#39;active&#39;<br>  GROUP BY c.email<br>),<br>churn_risk_calc AS (<br>  SELECT <br>    ts.customer_email,<br>    CASE <br>      WHEN ts.open_tickets_last_30d &gt; 5 AND (asub.has_active_subscription = false OR asub.has_active_subscription IS NULL) THEN &#39;High&#39; -- High churn risk if many open tickets and no active subscription<br>      WHEN ts.open_tickets_last_30d &gt; 3 THEN &#39;Medium&#39; -- Medium churn risk for moderate open tickets<br>      ELSE &#39;Low&#39; -- Otherwise low risk<br>    END AS churn_risk<br>  FROM ticket_stats ts<br>  LEFT JOIN active_subscriptions asub ON ts.customer_email = asub.customer_email<br>)<br><br>SELECT<br>  ts.customer_email,<br>  COALESCE(asub.has_active_subscription, false) AS active_subscription, -- Whether customer has active subscription<br>  ts.open_tickets_last_30d, -- Number of open tickets in last 30 days<br>  crc.churn_risk, -- Churn risk level<br>  (<br>    CASE WHEN COALESCE(asub.has_active_subscription, false) THEN 50 ELSE 0 END + -- Add 50 points if active subscription<br>    CASE WHEN ts.open_tickets_last_30d = 0 THEN 20 ELSE 0 END + -- Add 20 points if no open tickets<br>    CASE WHEN ts.open_tickets_last_30d &gt; 5 THEN -20 ELSE 0 END + -- Subtract 20 points if more than 5 open tickets<br>    CASE WHEN crc.churn_risk = &#39;High&#39; THEN -30 ELSE 0 END -- Subtract 30 points if high churn risk<br>  ) AS account_health_score -- Final calculated health score<br>FROM ticket_stats ts<br>LEFT JOIN active_subscriptions asub ON ts.customer_email = asub.customer_email<br>LEFT JOIN churn_risk_calc crc ON ts.customer_email = crc.customer_email;​</pre><h4>Step 4: How to Build the Dashboard on v0.dev</h4><p>Once your queries are ready on Peaka, the next step is turning them into a full-stack dashboard UI. This section explains how to use <a href="https://v0.dev/"><strong>v0.dev</strong></a>, an AI tool that generates production-grade UIs from prompts, to build a fully responsive dashboard with zero boilerplate.</p><p>Here’s how to go from saved queries to a fully functional customer health dashboard:</p><h4><a href="https://docs.peaka.com/blogs/build-health-dashboard-zendesk-hubspot-stripe#write-the-prompt-for-v0-dev">​</a><br>Write the Prompt for v0.dev</h4><p>Begin by preparing a detailed prompt that describes your goal. Here’s an example prompt you can adapt:</p><pre>I have a Peaka account and a Peaka project that contains four saved queries:<br>- active_tickets: Returns number of active support tickets per customer<br>- mrr: Returns monthly recurring revenue (MRR) per customer<br>- account_health_score: Returns a numeric health score between 0 and 100 for each customer<br>- churn_risk: Returns churn risk category (&quot;Low&quot;, &quot;Medium&quot;, or &quot;High&quot;)<br><br>I want to build a full-stack customer health dashboard in Next.js, using React and Tailwind CSS.<br><br>The dashboard layout should include:<br><br>Top section (4 metric cards):<br>- Total active tickets<br>- Average MRR<br>- Average account health score<br>- High churn risk percentage<br><br>Bottom section (charts):<br>- Bar chart showing MRR by customer<br>- Pie chart showing churn risk distribution<br>- Histogram (bar chart) of health score distribution in buckets<br>- Scatter plot of active tickets vs MRR, with churn risk as point color<br><br>All data should be fetched directly from Peaka&#39;s data API using fetch.<br><br>To get data from a Peaka query, I will use the following API pattern:<br><br>POST https://partner.peaka.studio/api/v1/data/projects/{projectId}/queries/execute<br>Authorization: Bearer &lt;token&gt;<br>Content-Type: application/json<br><br>Body:<br>{<br>  &quot;from&quot;: [<br>    {<br>      &quot;catalogName&quot;: &quot;peaka&quot;,<br>      &quot;schemaName&quot;: &quot;query&quot;,<br>      &quot;tableName&quot;: &quot;mrr&quot; // or &quot;active_tickets&quot;, etc.<br>    }<br>  ]<br>}<br><br>Each query will be executed this way from the frontend. You can assume the token is stored in an .env file or injected via a helper function.<br><br>Please generate the full dashboard code as a single `dashboard.tsx` page, using `fetch` to call these APIs from the browser. Use Tailwind CSS for layout. For charts, you can use Recharts or another modern charting library.<br><br>You can check Peaka&#39;s API reference here: https://docs.peaka.com/api-reference/introduction<br><br>Make the code developer-friendly and easy to customize.</pre><p>This prompt provides enough context for v0 to generate a complete dashboard layout with proper data bindings and visualizations.</p><h4>Set Up Environment Variables</h4><p>After generating the UI, v0 will request environment variables for secure access to your Peaka project. Add the following to your .<strong>env</strong> file:</p><pre>PEAKA_API_KEY=your_api_key_here<br>PEAKA_PROJECT_ID=your_project_id_here</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/0*hgNRS3j8ObVN8evs.png" /></figure><p>These values are injected into your app and used when making authenticated <strong>fetch</strong> calls to Peaka’s Data API.</p><h4>Verify API Calls and Response Handling</h4><p>v0 generates initial API logic based on your prompt. To ensure accuracy:</p><ul><li>Review how <strong>fetch</strong> requests are constructed (especially the body structure)</li><li>Compare it with <a href="https://docs.peaka.com/api-reference/data--queries/execute-query"><strong>Peaka’s API documentation</strong></a></li><li>Add sample request and response objects from the docs directly into your prompt (if needed) to improve alignment</li></ul><p>Pay close attention to fields like <strong>catalogName</strong>, <strong>schemaName</strong>, and <strong>tableName</strong>, these need to be exactly as defined in your Peaka query setup.</p><h4><strong>Make Final Adjustments</strong></h4><p>Once the initial dashboard is generated:</p><ul><li>Refine how response data is parsed into metrics and chart series</li><li>Tweak chart components (tooltips, colors, legends, bucket logic)</li><li>Adjust layout and spacing using Tailwind utility classes</li><li>Simplify or restructure component logic for maintainability</li></ul><p>These small improvements will help polish the UI and make the dashboard easier to customize for future use cases.</p><p>Within minutes, you’ll have a live, responsive, developer-friendly customer health dashboard, powered by real-time data from Peaka and built entirely through prompt-driven development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q07r17mivrvL0laJ.png" /></figure><h3>Real-World Use Cases</h3><p>Different roles across a company can benefit from these metrics in meaningful ways. For instance, a <strong>Customer Success Manager</strong> might regularly track Account Health Scores and Active Tickets to prioritize accounts that need immediate attention or proactive engagement. If an account shows a declining health score and an increasing number of unresolved tickets, it’s a clear signal to intervene before churn becomes inevitable.</p><p>On the other hand, a <strong>Revenue Manager</strong> could use MRR data to analyze revenue growth trends and identify which customer segments are driving the most value. By tying this insight with churn risk data, he/she can spot weak points in the customer journey and collaborate with other teams to improve retention.</p><p>Meanwhile, <strong>Product Teams</strong> can look at churn-prone accounts to understand usage patterns, or the lack thereof. If many of the accounts with high churn risk share a common behavior (e.g., not using a key feature), it becomes a product insight that could inform roadmap priorities or onboarding improvements.</p><p>And of course, <strong>Executives</strong> benefit from seeing the bigger picture, how health scores, support loads, and revenue trends correlate across the business. Having these metrics aggregated and visualized in one place enables faster, more informed strategic decisions.</p><h3>Before Peaka and v0.dev: The Legacy Approach</h3><p>Before tools like Peaka, tracking customer metrics across Stripe and other platforms meant stitching together multiple data sources manually.</p><p>To calculate metrics like MRR or active support tickets, teams often relied on:</p><ul><li>Exporting CSVs from Stripe, Intercom, and Jira</li><li>Writing custom SQL scripts in local notebooks or BI tools</li><li>Setting up and maintaining pipelines to sync these exports into a central database</li><li>Using spreadsheet formulas to aggregate or visualize key numbers</li></ul><p>This approach was:</p><ul><li><strong>Time-consuming</strong>: Writing and maintaining queries required technical expertise.</li><li><strong>Error-prone</strong>: Each manual export introduced chances for mismatched data or outdated snapshots.</li><li><strong>Hard to scale</strong>: As the number of metrics or tools increased, keeping everything in sync became a full-time job.</li><li><strong>Poorly democratized</strong>: Business and support teams had to wait for engineers or analysts to fetch the numbers they needed.</li></ul><p>Even with all this effort, the insights often remained fragmented and delayed.</p><h3>Key Takeaways</h3><ul><li>With v0 and Peaka, you can build customer dashboards from natural language prompts, no coding or manual setup required.</li><li>Peaka brings data from multiple platforms into one place, eliminating the need for custom pipelines or integrations.</li><li>Teams like Customer Success, Product, and Account Management can monitor churn risk, MRR, and ticket activity in real time.</li><li>By replacing spreadsheets and scattered tools, Peaka creates a single source of truth for customer health metrics.</li></ul><h3>Conclusion</h3><p>In this example, we combined data from different sources using Peaka’s robust integration layer and SQL-based interface. Then, with just a few steps, we plugged that data into v0 and built a working dashboard UI in no time. The seamless integration between Peaka and v0 made it incredibly easy to go from raw data to visual output, without setting up a backend or writing complex code. It’s a simple yet powerful way to prototype data-driven apps fast.</p><p><em>Originally published at </em><a href="https://docs.peaka.com/blogs/build-health-dashboard-zendesk-hubspot-stripe"><em>https://docs.peaka.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0b577a54d1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/peaka/how-to-build-a-customer-health-dashboard-with-saas-data-e0b577a54d1c">How to Build a Customer Health Dashboard with SaaS Data</a> was originally published in <a href="https://medium.com/peaka">Peaka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build a Churn Analysis Dashboard in 1 Hour Using Peaka and v0.dev — Peaka]]></title>
            <link>https://medium.com/peaka/how-to-build-a-churn-analysis-dashboard-in-1-hour-using-peaka-and-v0-dev-peaka-bbd7e43b8e66?source=rss----351a5419f89c---4</link>
            <guid isPermaLink="false">https://medium.com/p/bbd7e43b8e66</guid>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[churn]]></category>
            <category><![CDATA[v0]]></category>
            <category><![CDATA[peaka]]></category>
            <category><![CDATA[data-integration]]></category>
            <dc:creator><![CDATA[Ozan Batuhan Ceylan]]></dc:creator>
            <pubDate>Tue, 08 Jul 2025 12:32:15 GMT</pubDate>
            <atom:updated>2025-07-08T12:32:15.513Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Build a Churn Analysis Dashboard in 1 Hour Using Peaka and v0.dev — Peaka</h3><h4>Build a dashboard that identifies Pro- and Enterprise-tier subscribers who contacted support shortly before canceling their subscriptions.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KjMfCBJwkzo9GPvl.jpg" /></figure><h3>Project Overview</h3><p>What if your high-paying customers try to tell you something before they churn, and you don’t catch it?</p><p>In this tutorial, you will build a dashboard that identifies <strong>Pro- and Enterprise-tier subscribers who contacted support shortly before canceling</strong> their subscriptions. The goal is to help support and product teams understand churn patterns and take action before it’s too late.</p><p>This dashboard provides real value for:</p><ul><li><strong>Customer support teams</strong> looking to spot at-risk users,</li><li><strong>Product managers</strong> needing context around cancellations,</li><li><strong>Growth and revenue teams</strong> focused on reducing churn.</li></ul><p>Best of all, instead of spending days coding, you will build this entire system in <strong>just 1 hour</strong> using <strong>Peaka</strong> for data integration and <strong>v0.dev</strong> to generate the frontend.</p><h3>The Tools You’ll Need / The Stack</h3><p>Here’s what you’ll use to bring everything together:</p><ul><li><strong>Peaka</strong> — A no-code data integration platform that connects and joins data from Stripe and Zendesk, then turns those queries into APIs you can consume.</li><li><strong>v0.dev</strong> — An AI-powered tool that generates a full-stack dashboard UI based on a simple natural language prompt.</li><li><strong>Stripe + Zendesk</strong> — The core data sources providing subscription details and customer support tickets, respectively.</li></ul><h4>Why Peaka?</h4><p>Peaka is a no-code data operations platform that enables you to:</p><ul><li>Connect to external data sources like APIs, databases, and SaaS applications,</li><li>Model your data as <strong>virtual tables</strong> without moving or duplicating it,</li><li>Create APIs on top of those virtual tables to serve your applications.</li></ul><p>For this dashboard, Peaka provides:</p><ul><li>A seamless way to <strong>connect Zendesk and Stripe data</strong> by matching customer emails,</li><li>A flexible query builder that lets you <strong>join support tickets with subscription data</strong> using SQL,</li><li>Ready to use API endpoints that you can call directly from your app.</li></ul><p>By using Peaka, you avoid building and maintaining a custom backend, saving significant development time and complexity.</p><h4>Why v0.dev?</h4><p>With v0.dev, you can:</p><ul><li>Skip writing any frontend code. Just describe your app in a prompt,</li><li>Get a fully functional, developer-friendly UI generated for you,</li><li>Automatically generate backend integration logic that connects to Peaka’s APIs,</li><li>Easily adapt your app by updating prompts or API specs and regenerating the code.</li></ul><h3>Let’s Start</h3><h4>Step 1: Setting Up Your Peaka Project</h4><p>Before you start building, you need to set up your Peaka workspace and generate an API key for authentication.</p><p>Follow these steps:</p><ul><li>Go to <a href="https://peaka.studio/">peaka.studio</a> and log in.</li></ul><blockquote>If you don’t have an account yet, sign up. It only takes a minute.</blockquote><ul><li>Open your new project, then click the gear icon (⚙️) in the bottom left sidebar to open <strong>Settings</strong>.</li><li>In <strong>Settings</strong>, navigate to the <strong>API Keys</strong> tab and create a new API key.</li><li>Copy your <strong>Project ID</strong> from the URL in your browser’s address bar. It should look like this:</li></ul><pre>https://peaka.studio/studio/{project_id}/..</pre><p>Save both the API key and Project ID safely, you’ll need these when connecting Peaka to v0.dev.</p><h4>Step 2: Connecting Data Sources in Peaka</h4><p>With your project set up, it’s time to bring in your external data.</p><p>In this example, you’ll connect <strong>Stripe</strong> and <strong>Zendesk</strong> to Peaka. These will serve as the foundation for your churn and support analysis.</p><h4>Connecting Stripe</h4><ul><li>In your Peaka project, click the <strong>➕ Add</strong> button on the left sidebar to open the <strong>Connector List</strong>.</li><li>Use the search bar to find <strong>Stripe</strong> among the available connectors.</li><li>Select it, give the connection a name (e.g., stripe_main), and enter your <strong>Stripe API Key</strong>.</li><li>Click <strong>Connect,</strong> and you’re done!</li></ul><p>Your Stripe data will now appear under your connected data sources.</p><figure><img alt="Search Datasource to Connect" src="https://cdn-images-1.medium.com/max/1024/0*othSTG8XQzpnXBIt.png" /></figure><figure><img alt="Connecting Stripe Account" src="https://cdn-images-1.medium.com/max/548/0*-lY315OgIb37OtxT.png" /></figure><h4>Connecting Zendesk</h4><ul><li>Back in the <strong>Connector List</strong>, search for <strong>Zendesk</strong> and select it.</li><li>Since Zendesk supports <strong>OAuth authentication</strong>, setup is quick and easy.</li><li>Provide a <strong>connection name</strong> and your <strong>Zendesk subdomain</strong> (e.g., yourcompany.zendesk.com).</li><li>Peaka will redirect you to Zendesk for login and authorization. Once approved, the connector will be activated.</li><li>You’ll now have access to <strong>Zendesk tickets and user data</strong> within Peaka, no API handling required.</li></ul><figure><img alt="Connecting Zendesk Account" src="https://cdn-images-1.medium.com/max/506/0*KbAEkzq91xxMVCmS.png" /></figure><p>By the end of this step, both <strong>Stripe</strong> and <strong>Zendesk</strong> will be live in your Peaka project fully authenticated and ready to query.</p><h4>Step 3: Writing Queries in Peaka</h4><p>With Stripe and Zendesk connected, it’s time to extract insights by writing queries across both data sources.</p><h4>Creating a New Query in Peaka</h4><ul><li>From the left sidebar, go to the <strong>Queries</strong> section.</li><li>Click <strong>➕ New Query</strong> to create a new SQL query.</li><li>Choose <strong>Start from Scratch</strong> instead of using a template.</li></ul><blockquote>(You can explore Peaka’s templates later for common use cases.)</blockquote><ul><li>Write the following SQL queries and click <strong>Run</strong> to preview the results.</li></ul><figure><img alt="Create a New Query" src="https://cdn-images-1.medium.com/max/799/0*J1JFZ7z_Y5nqDDKL.png" /></figure><figure><img alt="Query Screen" src="https://cdn-images-1.medium.com/proxy/0*DprBSq40-2sje6kZ.png" /></figure><h4>Query 1: Support Tickets Submitted Shortly Before Churn</h4><p>This query finds <strong>Pro or Enterprise users</strong> who submitted a support ticket <strong>within 14 days before canceling</strong> their subscription.</p><p>Use it to identify customers who might have been unhappy or struggling and possibly prevent future churn.</p><pre>SELECT<br>  u.name,<br>  prod.name AS plan_name,<br>  z.subject,<br>  z.description,<br>  u.email AS customer_email<br>FROM<br>  &quot;zd&quot;.&quot;public&quot;.&quot;tickets&quot; z<br>JOIN<br>  &quot;zd&quot;.&quot;public&quot;.&quot;users&quot; u ON z.requester_id = u.id<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;customers&quot; c ON u.email = c.email<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;subscriptions&quot; sub ON c.id = sub.customer_id<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;plans&quot; p ON sub.plan_id = p.id<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;products&quot; prod ON p.product_id = prod.id<br>WHERE<br>  prod.name IN (&#39;Pro Plan&#39;, &#39;Enterprise Plan&#39;)<br>  AND sub.canceled_at IS NOT NULL<br>  AND z.created_at BETWEEN (sub.canceled_at - INTERVAL &#39;14&#39; DAY) AND sub.canceled_at<br>ORDER BY z.created_at DESC<br>LIMIT 100;</pre><h4>Query 2: All Tickets from Premium Users</h4><p>This query retrieves <strong>all support tickets</strong> submitted by <strong>Pro and Enterprise plan</strong> users, whether they churned or not.</p><p>It’s useful for exploring the overall support volume, issue trends, and satisfaction signals from your premium customer base.</p><pre>SELECT<br>  u.name AS customer_name,<br>  prod.name AS plan_name,<br>  z.subject AS ticket_subject,<br>  z.description AS ticket_description,<br>  u.email AS customer_email,<br>  z.priority,<br>  z.status,<br>  z.updated_at<br>FROM<br>  &quot;zd&quot;.&quot;public&quot;.&quot;tickets&quot; z<br>JOIN<br>  &quot;zd&quot;.&quot;public&quot;.&quot;users&quot; u ON z.requester_id = u.id<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;customers&quot; c ON u.email = c.email<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;subscriptions&quot; sub ON c.id = sub.customer_id<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;plans&quot; p ON sub.plan_id = p.id<br>JOIN<br>  &quot;stripe&quot;.&quot;payment&quot;.&quot;products&quot; prod ON p.product_id = prod.id<br>WHERE<br>  prod.name IN (&#39;Pro Plan&#39;, &#39;Enterprise Plan&#39;)<br>ORDER BY z.created_at DESC<br>LIMIT 100;</pre><h4>Step 4: Integrating Peaka Queries into the Frontend with v0.dev</h4><p>With your Peaka queries ready, you can now build a complete frontend dashboard using <a href="https://v0.dev/">v0.dev</a>. This step shows how to integrate live query results into your UI, entirely through prompt-based generation.</p><h4>Start with a Prompt</h4><p>Begin by opening <a href="https://v0.dev/">v0.dev</a> and entering a prompt like this:</p><pre>I have a Peaka account and a Peaka project that contains two queries.<br><br>I want to create a dashboard with the following charts:<br><br>- A table listing users who contacted support shortly before canceling. (You can execute the tickets_by_pro_enterprise_customers query from Peaka)<br>- A list of recent feedback entries from premium subscribers. (You can execute the zendesk_tickets_with_stripe_customer_and_plan_info query from Peaka)<br><br>It should be a full-stack system. The design should be developer-friendly and backend should be integrated with Peaka.<br><br>You can check the API reference here: https://docs.peaka.com/api-reference/introduction</pre><figure><img alt="v0 initial prompt" src="https://cdn-images-1.medium.com/max/1024/0*9AGa2fUXp5Ar5MKN.png" /></figure><h4>Set Environment Variables</h4><p>v0.dev will likely ask you to define the following environment variables to authenticate with Peaka:</p><ul><li>PEAKA_API_KEY</li><li>PEAKA_PROJECT_ID</li></ul><p>Use the values you obtained earlier from your Peaka project’s settings and paste them into v0.dev’s environment configuration.</p><figure><img alt="v0 Api Key Screen" src="https://cdn-images-1.medium.com/max/551/0*gf72jsHPpQRApi7w.png" /></figure><h4>Fix the API Base URL</h4><p>By default, v0.dev may try to connect to https://api.peaka.com/v1, which is not the correct base URL for query execution.</p><p>You can fix this by prompting v0.dev with:</p><pre>API Endpoint base is different than api.peaka.com/v1.<br>It should be https://partner.peaka.studio/api/v1</pre><p>If you’re using the <strong>EU zone</strong>, use:</p><pre>https://partner.eu.peaka.studio/api/v1</pre><figure><img alt="Base URL Fix in v0" src="https://cdn-images-1.medium.com/max/687/0*30rPU2hNkIaFqMux.png" /></figure><h4>Use the Correct Request Format</h4><p>After correcting the base URL, you’ll also need to make sure the request payload matches Peaka’s execute-query API format.</p><p>You can provide v0.dev with this sample request and response structure, based on the <a href="https://docs.peaka.com/api-reference/data-queries/execute-query">official documentation</a>:</p><p><strong>Sample request:</strong></p><pre>const options = {<br>  method: &#39;POST&#39;,<br>  headers: {Authorization: &#39;Bearer &lt;token&gt;&#39;, &#39;Content-Type&#39;: &#39;application/json&#39;},<br>  body: &#39;{&quot;from&quot;:[{&quot;catalogName&quot;:&quot;peaka&quot;,&quot;schemaName&quot;:&quot;query&quot;,&quot;tableName&quot;:&quot;samplequery&quot;}]}&#39;<br>};<br><br>fetch(&#39;https://partner.eu.peaka.studio/api/v1/data/projects/{projectId}/queries/execute&#39;, options)<br>  .then(response =&gt; response.json())<br>  .then(response =&gt; console.log(response))<br>  .catch(err =&gt; console.error(err));</pre><p><strong>Sample response:</strong></p><pre>{<br>  &quot;columns&quot;: [<br>    {<br>      &quot;catalogId&quot;: &quot;2&quot;,<br>      &quot;catalogName&quot;: &quot;peaka&quot;,<br>      &quot;schemaName&quot;: &quot;query&quot;,<br>      &quot;tableName&quot;: &quot;samplequery&quot;,<br>      &quot;columnName&quot;: &quot;amount&quot;<br>    }<br>  ],<br>  &quot;data&quot;: [<br>    [<br>      {<br>        &quot;name&quot;: &quot;amount&quot;,<br>        &quot;displayName&quot;: &quot;amount&quot;,<br>        &quot;dataType&quot;: &quot;bigint&quot;,<br>        &quot;value&quot;: &quot;75&quot;,<br>        &quot;order&quot;: 0<br>      }<br>    ],<br>    [<br>      {<br>        &quot;name&quot;: &quot;amount&quot;,<br>        &quot;displayName&quot;: &quot;amount&quot;,<br>        &quot;dataType&quot;: &quot;bigint&quot;,<br>        &quot;value&quot;: &quot;75&quot;,<br>        &quot;order&quot;: 0<br>      }<br>    ],<br>    [<br>      {<br>        &quot;name&quot;: &quot;amount&quot;,<br>        &quot;displayName&quot;: &quot;amount&quot;,<br>        &quot;dataType&quot;: &quot;bigint&quot;,<br>        &quot;value&quot;: &quot;75&quot;,<br>        &quot;order&quot;: 0<br>      }<br>    ]<br>  ]<br>}</pre><figure><img alt="Example Payload and Response prompt" src="https://cdn-images-1.medium.com/max/743/0*jNFuR5_aQ11Nk3do.png" /></figure><h4>Final Touches via Prompt Iteration</h4><p>Once your frontend is connected to Peaka and fetching live data, you can polish the UI using plain prompts.</p><p>For example:</p><pre>Map the &quot;date&quot; field to the &quot;updated_at&quot; column in the recent feedback table, and remove the &quot;rate&quot; field.</pre><p>v0.dev will apply your changes automatically, no need to manually edit code.</p><blockquote><em>✅ At the end of this step, you’ll have a dynamic frontend powered by Peaka’s live query data fully operational in under an hour.</em></blockquote><h4>Step 5: The Final Dashboard</h4><p>After hooking up Peaka as the data layer in a <a href="https://v0.dev/">v0.dev</a> dashboard, you’ll have a clean, fully functional, and developer-friendly interface, powered entirely by live data from Stripe and Zendesk.</p><p>The dashboard consists of two key components:</p><h4>1. Users Who Contacted Support Shortly Before Churning</h4><p>This table lists:</p><ul><li>Customer name</li><li>Email address</li><li>Plan type (Pro or Enterprise)</li><li>Ticket subject &amp; description</li><li>Ticket creation date (within 14 days before cancellation)</li></ul><p>This component highlights <strong>last-minute support activity</strong> from users who churned, providing early-warning signals of dissatisfaction or friction. It’s an invaluable tool for customer support and product teams to spot trends behind cancellations.</p><figure><img alt="Support Before Cancellation screen" src="https://cdn-images-1.medium.com/max/1024/0*EPtIeFdvn9wImkvt.png" /></figure><h4>2. Recent Feedback from Premium Subscribers</h4><p>This section displays all tickets submitted by <strong>current</strong> Pro and Enterprise users, regardless of churn status. It includes:</p><ul><li>Customer name</li><li>Plan name</li><li>Ticket subject &amp; description</li><li>Ticket priority, status, and last updated date</li></ul><p>This real-time view helps teams <strong>monitor ongoing support needs</strong> and stay ahead of potential churn risks before they escalate.</p><figure><img alt="Premium Subscribers’ Ticket Screen" src="https://cdn-images-1.medium.com/max/1024/0*hYx84HLAste2htA6.png" /></figure><h4>Why This Dashboard Delivers Value</h4><p>This dashboard isn’t just a data visualization, it enables action. Here’s how different teams benefit:</p><ul><li><strong>Product teams</strong> can identify recurring friction points.</li><li><strong>Support teams</strong> can evaluate whether unresolved tickets correlate with churn.</li><li><strong>Revenue &amp; growth teams</strong> can track churn trends across plan tiers.</li><li><strong>CSMs</strong> can proactively reach out to users showing warning signs.</li></ul><h4>Time and Effort Saved</h4><p>Traditionally, building this system would require:</p><ul><li>Manual API integrations</li><li>Authentication handling</li><li>SQL joins and data modeling</li><li>Backend service development</li><li>Frontend component coding</li></ul><p>…resulting in <strong>days or even a week</strong> of effort.</p><p>By using <strong>Peaka + v0.dev</strong>, the same outcome can be achieved in <strong>under an hour</strong>, with:</p><ul><li>No custom backend development</li><li>No manual UI coding</li><li>Just clear prompts and a few API keys</li></ul><blockquote><em>💡 This is a fast, scalable way to ship internal tools or MVPs using live SaaS data without compromising on developer experience.</em></blockquote><h3>Real-World Use Cases</h3><p>This exact approach can be adapted for various needs:</p><ul><li><strong>Support teams</strong>: Proactively identify at-risk customers.</li><li><strong>Product teams</strong>: Spot recurring feedback from premium users.</li><li><strong>Growth teams</strong>: Understand why high-value customers churn.</li></ul><p>All without hiring a data team or building internal tools from scratch.</p><h3>The Conventional Way</h3><p>The traditional approach would have looked like this:</p><ul><li>ETL pipeline to pull data from Stripe and Zendesk,</li><li>A data warehouse to store and query the results,</li><li>A backend service to expose APIs,</li><li>A frontend team to build a dashboard.</li></ul><p>Estimated time: <strong>2–3 days, at minimum</strong>.</p><p>Peaka + v0? <strong>1 hour.</strong></p><h3>Key Takeaways</h3><ul><li><strong>Churn signals often hide in support data:</strong> Users who reach out to support shortly before canceling are waving red flags. Surfacing these interactions helps teams take proactive action before it’s too late.</li><li><strong>Peaka makes integrations painless:</strong> Connect to platforms like Stripe and Zendesk without writing any code, model the data with SQL, and instantly turn queries into APIs.</li><li><strong>v0.dev eliminates frontend overhead:</strong> With natural language prompts, you can generate fully functional dashboards that connect to live data, no UI or backend coding required.</li><li><strong>1 hour = days of saved effort:</strong> What would normally take days, building data pipelines, backend services, and frontend components, can now be achieved in under an hour.</li><li><strong>Accessible for non-technical teams:</strong> PMs, support leads, and growth managers can gain insights without needing to write a single line of code.</li><li><strong>Flexible and reusable:</strong> The same structure can be repurposed for different queries, data sources, or dashboard layouts with minimal changes.</li></ul><blockquote><em>🎯 Bottom line: Skip the complexity, accelerate insight.</em></blockquote><blockquote><em>Peaka + v0.dev is a turbocharged way to build MVPs and internal tools.</em></blockquote><h3>Conclusion</h3><p>By simply:</p><ul><li>Connecting Zendesk and Stripe to Peaka,</li><li>Writing two SQL queries,</li><li>Prompting v0.dev to generate the frontend,</li></ul><p>I built a fully functional, data-powered churn insight dashboard in just <strong>1 hour</strong>.</p><p>If you’re a developer or even a PM who wants results without the overhead of building everything from scratch, give this combo a try.</p><p><em>Originally published at </em><a href="https://docs.peaka.com/blogs/how-to-build-churn-dashboard"><em>https://docs.peaka.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbd7e43b8e66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/peaka/how-to-build-a-churn-analysis-dashboard-in-1-hour-using-peaka-and-v0-dev-peaka-bbd7e43b8e66">How to Build a Churn Analysis Dashboard in 1 Hour Using Peaka and v0.dev — Peaka</a> was originally published in <a href="https://medium.com/peaka">Peaka</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>