The more complicated your needs, the harder it is to use Birst.
Overall Satisfaction with Birst
Birst is used across my organization, but particularly by the sales and marketing departments. It is used to track pipeline flow from impressions to revenue.
Pros
- Birst's SQL-like language is conveniently familiar for experienced developers
- Birst integrates well with Salesforce and external CSV data sources.
- Birst's support staff is reasonably responsive, if not always able to provide a satisfactory result.
Cons
- Birst contains several sub-systems with similar, but signifcantly incompatible, syntax and functionalities. This leads to confusion and difficulty.
- Birst provides insufficient control over how charts are rendered and how dashboard prompts are displayed and used. This has lead to significant dissatisfaction on the part of those for whom I've developed dashboards.
- Significant parts of Birst resemble a relational database, but cannot be made to function like one. This results in jumping through complicated hoops to construct the fact tables for a multiple-relation data system.
- Alooma and Periscope Data
Birst's ETL is better suited to our purposes than Alooma's stream-based processing.
Birst's designer is more mature and meets or needs better than Periscope's reporting functionality, at the time I investigated it.
Birst's designer is more mature and meets or needs better than Periscope's reporting functionality, at the time I investigated it.
Comments
Please log in to join the conversation