To visualize your Ploomes CRM data in Looker Studio, connect your Ploomes account to Kondado and select Looker Studio as your destination. Kondado replicates your deals, client information, and sales activities on a configurable schedule, keeping your dashboards current without manual exports or complex spreadsheet maintenance. You can build comprehensive reports showing funnel progression, client segmentation, and sales performance using the automatically updated data, enabling your team to identify trends and respond to market changes quickly. Business users gain immediate visibility into pipeline health and client relationships without waiting for technical teams to prepare data extracts, while sales managers track team performance through intuitive visualizations.
Kondado connects Ploomes to Looker Studio through a direct “Via Kondado” connection that requires no intermediate databases or technical setup, allowing business teams to visualize CRM data with automated updates every 5 minutes, 15 minutes, hourly, or daily.
Each item below is automatically replicated by Kondado from Ploomes into Looker Studio — no schema setup, no manual mapping.
36
available pipelines
275
extractable fields
∞
Auto-refresh
Available integrations
Positions
Table contains information about positions, including id, name, and associated user profile.
Cities
Table presents data about cities, including id, name, and associated state.
Cities: states
Table provides information about states related to cities, including id and state name.
Cities: countries
Table contains data about countries associated with cities, including id and country name.
Clients (companies and individuals)
Table presents information about clients, including id, name, email, and status.
Clients: ratings
Table provides data about client ratings, including id and rating name.
Clients: sources
Table contains information about client sources, including id and source name.
Clients: relationships
Table presents data about relationships between clients, including id and relationship type.
Clients: segments
Table provides information about client segments, including id and segment name.
Clients: status
Table contains data about client status, including id and status description.
Client Types
Includes fields such as id and name, allowing categorization of clients into different types for better management.
Departments
Contains fields such as id and name, facilitating the organization and structuring of departments within the company.
Documents
Presents fields such as id and filename, allowing management of documents associated with clients and sales.
Currencies
Includes fields such as id and currency, essential for financial management and conversion of values in different currencies.
Deals
Has fields such as id, ordernumber, and amount, allowing tracking and analysis of completed sales.
Deal Stages
Includes fields such as id, name, and ordination, which help define the progression of deals through different stages.
Deal Funnels
Presents fields that allow visualization and management of different sales funnels and their stages.
Deal Loss Reasons
Includes fields such as id and name, helping to identify and analyze the reasons why deals were not closed.
Deal Status
Presents fields that indicate the current status of deals, allowing better tracking of progress.
Products
Contains fields such as id and name, essential for managing and categorizing the products offered.
Product Groups
Includes fields such as id, name, and description, allowing for the categorization of products into specific groups for better organization and analysis.
Product Families
Contains fields such as id, name, and group_id, facilitating the organization of products into related families for more efficient management.
Proposals
Presents fields such as id, filename, and approval status, allowing for the management and tracking of proposals sent to clients.
Proposal Products
Includes fields such as proposal_id, product_id, and quantity, detailing the products included in each proposal for accurate tracking.
Proposal Approval Status
Contains fields such as id and name, allowing for the categorization of different approval statuses for submitted proposals.
Interaction Records
Includes fields such as id, type, and date, recording interactions made with clients for relationship analysis.
Tasks
Presents fields such as id, name, and status, allowing for effective management of tasks assigned to users within the platform.
Task Recurrence Intervals
Contains fields such as id and frequency, defining the periodicity of tasks for better work organization.
Task Types
Includes fields such as id and name, categorizing tasks into different types for easier management.
Email Reminder Types
Presents fields such as id and description, allowing the configuration of different types of email reminders for users.
Users
Table contains information about users, including fields such as id, name, and email, as well as role id and profile id.
User Suspension Reasons
Table lists the reasons for user suspension, with fields such as id and name, along with comments on the suspension.
User Profiles
Table presents user profiles, including fields such as id, name, and avatar url, along with phone and user language.
Sales
Table contains data on sales, including fields such as id, order number, date, customer id, and total sale amount.
Sales Stages
Table lists sales stages, with fields such as id, name, icon, and ordination of stages within a funnel.
Sales Products
Table contains information on sold products, including fields such as order id, product id, and quantity, along with unit price and discount.
With your Ploomes data available in Looker Studio, you can combine information from the Deals, Clients, and Deal Stages pipelines to create dynamic sales funnel visualizations. Track how prospects move through each stage, analyze win rates by client segment, and monitor proposal approval status alongside actual sales figures from the Sales pipeline. This combination gives sales managers immediate visibility into pipeline health and helps identify which client sources and product groups are driving the most revenue, enabling faster strategic decision-making without switching between platforms or waiting for manual report generation.
Try out all the features for free for 14 days
How to create Ploomes dashboards in Looker Studio
Visualize your data automatically — no spreadsheet exports or custom scripts.
1
Connect Ploomes to Kondado
Authenticate your Ploomes account in Kondado to establish your data source. Select which pipelines you need, such as Deals, Clients, or Sales data, and set your preferred update frequency.
2
Select Looker Studio destination
Choose Looker Studio as your destination and configure the connection using the "Via Kondado" option. This creates a direct link between your CRM data and visualization platform without intermediate storage.
3
Build dashboards and schedule updates
Create charts and reports in Looker Studio using your replicated Ploomes data, then configure automatic refresh schedules to keep insights current. Set different update frequencies for different datasets based on how frequently you need to see new information.
Try out all the features for free for 14 days
Access Ploomes data in Looker Studio and combine it with dozens of other data sources
If the source you want is not listed, drop us a chat message. We love to add new sources!
Answers about visualizing Ploomes data in Looker Studio automatically
How do I connect Ploomes to Looker Studio using Kondado?▼
Start by selecting Ploomes as your data source in the Kondado platform and authenticate your account credentials. Then choose Looker Studio as your destination and select which data endpoints you want to replicate, such as Deals, Clients, or Sales data. Kondado handles the connection automatically through the "Via Kondado" option, so your data flows directly into Looker Studio without requiring database configuration or coding.
What sales KPIs can I track with Ploomes data in Looker Studio?▼
You can monitor conversion rates between deal stages, average deal size by product group, and sales velocity from proposal to closed won. Track client acquisition by source and segment, measure proposal approval rates, and analyze win/loss ratios using the Deal Loss Reasons data. These metrics help identify bottlenecks in your sales process and highlight which client relationships generate the most revenue.
How often does Ploomes data update in Looker Studio?▼
Kondado updates your data on a configurable schedule that you control, with options ranging from every 5 minutes to daily refresh. You can set different frequencies for different datasets, updating high-priority sales figures every 15 minutes while refreshing client reference data daily. This ensures your dashboards reflect current business conditions without overwhelming your systems with unnecessary updates.
Can I share Ploomes dashboards with my sales team?▼
Yes, once you build reports in Looker Studio, you can share them with unlimited viewers inside or outside your organization. Set viewing permissions for specific team members or make dashboards available to entire departments, allowing sales reps to see their individual performance while managers view consolidated team metrics. Recipients can view interactive charts and apply filters without needing a Kondado account.
Do I need technical skills to build Ploomes reports in Looker Studio?▼
No coding or database knowledge is required to create visualizations using your replicated Ploomes data. Looker Studio's drag-and-drop interface lets you build charts from your Deals, Clients, and Sales data using familiar business terms. Kondado presents the data in ready-to-use formats, so you can focus on designing insightful reports rather than handling technical configurations.
Can I combine Ploomes data with other sources in Looker Studio?▼
Absolutely, Looker Studio allows you to blend your Ploomes CRM data with information from Google Sheets, BigQuery, or other platforms to create comprehensive business views. Combine sales figures from Ploomes with marketing spend data to calculate acquisition costs, or merge client data with support tickets for complete relationship visibility. This cross-platform analysis reveals insights that single-source reporting cannot provide.
'%3E%3Cpath d='M51,41a9.978,9.978,0,0,0-7.857,3.835L22.648,34.588a9.69,9.69,0,0,0,0-5.176l20.5-10.247a10.1,10.1,0,1,0-1.791-3.577L20.857,25.835a10,10,0,1,0,0,12.33L41.352,48.412A9.994,9.994,0,1,0,51,41Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)
'%3E%3Cpath d='M33,47.645V60.71c.024-.014.05-.018.073-.033l11-7A2,2,0,0,0,45,51.992V40.012Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M31,47.645,19,40.011V51.992a2,2,0,0,0,.927,1.688l11,7c.023.015.049.019.073.033Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M32,21.693l12-7.634L33.076,7.086a2,2,0,0,0-2.152,0L20,14.059Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M12,35.556,0,27.922V39.9A2,2,0,0,0,.927,41.59l11,7c.023.014.049.019.073.033Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M52,35.556l12-7.634V39.9a2,2,0,0,1-.927,1.687l-11,7c-.023.014-.049.019-.073.033Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M47,38.914a2,2,0,0,0-.924-1.686L38,32.074V27.922l12,7.634V48.621c-.024-.014-.05-.019-.073-.033L47,46.726Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M13,33.821l12-7.634L14.076,19.214a2,2,0,0,0-2.152,0L1,26.187Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M17,38.914a2,2,0,0,1,.924-1.686L26,32.074V27.922L14,35.556V48.621c.024-.014.05-.019.073-.033L17,46.726Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M32,45.91l12-7.634L33.076,31.3a2,2,0,0,0-2.152,0L20,38.276Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M14.076,19.214a2,2,0,0,0-2.152,0L1,26.187l12,7.634,12-7.634Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M49.924,19.214a2,2,0,0,1,2.152,0L63,26.187,51,33.821,39,26.187Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M26,27.922,14,35.556V48.621c.024-.014.05-.019.073-.033L17,46.726V38.914a2,2,0,0,1,.924-1.686L26,32.074Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M27.076,25.138A2,2,0,0,1,28,26.824V30.8l1.848-1.179A4,4,0,0,1,31,29.123V23.428L19,15.794v4.19Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M36.924,25.138A2,2,0,0,0,36,26.824V30.8l-1.848-1.179A4,4,0,0,0,33,29.123V23.428l12-7.634v4.19Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M33.076,31.3a2,2,0,0,0-2.152,0L20,38.276,32,45.91l12-7.634Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)
'%3E%3Cpath d='M50.348,42.573c0-9.411-8.691-12.336-16.348-14.416v-16.1a32.837,32.837,0,0,1,9.363,1.656l2.778,1.11,2.228-5.57L45.584,8.134A38.043,38.043,0,0,0,34,6.046V1H30V6.081c-8.213.594-16.348,4.86-16.348,13.471,0,9.036,8.841,11.732,16.348,13.744V50.074a33.591,33.591,0,0,1-12.006-2.511l-2.683-1.341-2.684,5.367,2.684,1.342c.243.121,5.7,2.792,14.689,3.152V63h4V56.065C44,55.462,50.348,50.3,50.348,42.573Zm-30.7-23.021c0-5.133,5.96-7.016,10.348-7.446V27.071C23.512,25.243,19.652,23.535,19.652,19.552ZM34,50.043V34.393c6.5,1.882,10.348,3.761,10.348,8.18C44.348,48.377,37.873,49.744,34,50.043Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)