Heap vs Looker: Which is a better fit?

I love how easy it is to set up and use. I didn't expect it to be so intuitive and user friendly considering all that it does.

Unless you have a background as a developer, using this software can be really confusing.

I love Heap's collaboration tools, which allow me to involve team members in data path and chart preparation to get the best results. Reports, dashboards, and data mining are easy too.

It need basic html tagging knowledge. Sometimes it's confusing for business users.

I really like the idea of having the chance of gathering metrics about the usage of your platform, tracking users interactions and more useful data, and providing complete metric graphics.

Paulo P

CTO

Even though heap has put in place warnings when events stop triggering, it is still hard to maintain if you don't bring your developers on board to avoid making structural or class changes.

Muzamil M

Sales and Marketing Specialist

It is great for creating custom reports and dashboards (Offers the ability to track almost everything). Setting up flows is very easy.

Paulo P

CTO

The amount of configurations and customizations in the dashboards and reports is limited.

I love the ability to visualize all of the data in one space. Dashboard creation is easy and so useful.

Can get a bit confusing and confining with more complex queries/analysis. Machine written sql can be annoying.

We use ours with Redshift and Aurora and they take most advantage of both systems. Their super awesome customer support - always available chat who are really good at what they are doing.

To be fair, if you have a terrible underlying data warehouse, then all Looker will do is expose that.

It’s a good option if you want to do dashboards connected to google sheets. Also a good alternative to PowerBi.

Unfortunately, their documentation could use some improving as often I find myself confused and unsure what to do with their docs.

Looker has been a great and useful tool for out business. Where we've found challenges is in the specific data dictionary and set-up, which internally was not well prepared prior to implementation.

I dislike how long it can take certain reports in Looker to load.