Kylas Marketplace Apps
Features \ Integration and Marketplace \ Kylas Marketplace Apps \ Bi & Analytics integration
Bi & Analytics app helps users to connect their Kylas database with any BI and Analytics tool e.g. Power BI, Adobe analytics, or Zoho analytics. Google analytics and looker studio etc.
Users can connect their Kylas database with a BI or Analytics tool and can generate complex cross-entity reports that involve data from multiple entities such as - Deal revenue by Contact City, Number of Leads owned by Teams, Revenue generated by Teams, Funnel reports, etc.
We will publish a database connection detail in the app through which you can connect the database with BI and Analytics tools to get the data.
Follow the below steps, in order to sync the data with BI and Analytics.
View the Kylas field name vs the table in the BI and Analytics database.
When you save the sync settings, we will start listening to Kylas Webhooks and sync the database for records created, updated, or deleted within BI and Analytics. On top of that, if you wish to sync your existing data, please follow the below steps.
Please follow the below steps to connect Kylas database for reporting.
Relationships between two or more tables are very important to fetching correct reports, especially for cross-entity reports. Some of the BI tools available in the market will be able to detect the relationships between the Kylas database tables automatically however if they are not able to, then you can go ahead and create relationships manually.
Relationship type | Meaning | Example from Kylas |
One to Many | When one record of the first table can be associated to many records from the second table. | Company – Contact since a Company can be associated with multiple Contacts, but a contact can have only one Company associated with it. |
Many to One | When many records of the first table can be associated with one. | Lead – Pipeline since many Leads can have the same pipeline. |
Many to Many | When one record of the first table can be associated with multiple records and vice versa. | Deal – Contacts since a Deal can have multiple contacts and a Contact can also have multiple Deals associated with it. |
One to One | When one record of first table can be associated with only one record of the second table and vice versa. | Currently no two entities in Kylas are associated with this type of relation. |
Meeting
Read AllSearchList
ReadLead
Read, ReadAll, Task, SMS, Call, Note, MeetingDeal
Read, ReadAll, Task, SMS, Call, Note, Meeting, QuotationTask
Read, ReadAll, NotePipeline
Read, ReadAllCall
Read, ReadAllProducts-Services
Read, ReadAllContact
Read, ReadAll, Task, SMS, Call, Note, Meeting, QuotationQuotation
Read, ReadAllUser
Read, ReadAllTeam
Read, ReadAllProfile
Read, ReadAllNote
Read, ReadAllEmail_Template
Read, ReadAllCompany
Read, ReadAll, Task, Note, Meeting, Quotation