Trustpilot and Chartio: How We Access and Engage With Data

Trustpilot and Chartio: How We Access and Engage With Data

How Trustpilot uses Chartio to combine data from different sources, share data across the organization and embed dashboards within our own product. Trustpilot uses Chartio in a variety of ways, but the end goal is to leverage valuable insights from data to benefit Trustpilot’s internal teams and customers. 

 

Intro

At Trustpilot, we love data. Part of our mission is to create more transparency to empower everyone across the company to have access and the ability to engage with our data. There are a few different platforms we use in our data stack to reach this goal, but the one that allows us to combine data from different sources and visualise our data is Chartio.

We use Chartio in almost all of our departments. Each department has different access to dashboards and data sources, but we all use it to measure our objectives and key results (OKR). In fact, we created our own internal site where Chartio dashboards are embedded so we can display company -wide metrics and performance in different markets. This is a great way to keep everyone on track and motivated by constantly seeing the numbers they need to reach.

However, as a data analyst and one of Trustpilot’s Chartio super users, I’ll dig deeper and give some insight into how our product teams use data visualization in order to facilitate a better understanding of how Trustpilot is used. Additionally, we have created a new product which will empower our customers with data.

Trustpilot’s Data Stack:

Before diving into some of the interesting analyses we use, I want to give a quick overview of our data infrastructure and what it looks like:


Data Sources

Redshift (Our segment tracking data is in Redshift along with our Salesforce data using Segment sources), PostgreSQL, and csv

  • How does it all connect with Chartio? Chartio has changed the way we store/collect data. Whenever we create a data source it is essential that it is accessible using Chartio. This is not only positive since we no longer pull data reports from production databases, but it also increased awareness on the importance of having a singular source of truth.

  • In a growing company it is essential to have data sources that you maintain and trust. This forces us to keep our data clean by collecting it efficiently and properly. Simultaneously, data ownership has been/is promoted by identifying which teams are responsible for specific data sources. .

Sharing Metrics that Matter:

Trustpilot Analytics: Data Products

  • We use Chartio’s embedded feature right in our product. When companies log-in to our business website, they can access a Chartio dashboard immediately on the front page. Trustpilot also has an Analytics product for customers, which is comprised of several Chartio dashboards. It shows companies some basic metrics on their performance. Chartio’s embedding feature has allowed us to add new dashboards to this part of our product as we develop our data sources.
  • Chartio also allows us to create quick MVPs. It gives us the ability to prototype really quickly and easily present a data product to a customer to receive instant feedback. It allows us to show them their data in several different ways and we can upload a sample dataset to see if it could bring them value. We are able to prototype and iterate at crazy speeds. Once we have that commitment, we are able to prove that x number of customers are willing to pay for a product. Receiving this instant feedback allows us to commit to building products with a lot more confidence in their success.

How Chartio helps our product teams:

  • It has changed the way we share data within Product, we are able to give Product Managers their own dashboards and we can help them understand their data and learn about the data that they are collecting.
  • All teams have a tv screen with a dashboard on display, supplying motivation for team members, and providing the first warning sign if there’s an issue, which allows for daily improvements.
  • It has also increased the number of findings since there are several sets of eyes on the data, different people have different findings/find different things interesting.
  • Each quarter the product teams create a dashboard, which displays their teams key results for that quarter (these include live progress, goals, etc.). If one of their key results is to increase usage by x%, the dashboard allows everyone to see their progression and if the usage is actually increasing. Not only does this kind of transparency drive teams to improve, but it also holds teams accountable for their work. If they are unable to achieve their key results it is transparent to everyone, which enables the team to discuss what went wrong and why they weren't able to achieve their goals and the different roadblocks. It’s pointless to set goals which are not measured and it forces teams to create more realistic goals and even reassess their goals at certain points.

Conclusion:

  • Chartio has provided us with one place to combine/aggregate our data, previously it was segmented in different sources and we were only able to manually combine it in a spreadsheet.
  • For my own development it has allowed me to understand data in different ways. It has forced me to improve my SQL skills and think more about data engineering and how to structure data sources.
  • It has cut down on manual reporting and therefore decreased manual errors and eliminated updating reports on a weekly/monthly basis. We previously spent two days a month manually updating spreadsheet reports, it now takes us a few hours to create a custom dashboard, which automatically updates. If data requests come in we can quickly change our internal dashboards to fill the need.
New Call-to-action