Treasure Data helps you grow your service.
March 15, 2021

Treasure Data helps you grow your service.

나영 김 | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Treasure Data

We use Treasure Data across the entire organization. Mainly for data warehouse use, CDP was used for marketing optimization, and data regularly loaded by workflow was used for monitoring the status by linking with communication channels (Slack). In addition, the kit provided by Treasure Box was used (NBA ..).
By utilizing the functions provided by Treasure Data, various loaded data were analyzed or trends were checked to make quick decisions, and they were also used to prioritize.
  • CDP provides a unified view of data from all touchpoints in the customer journey until a single customer uses the service. This feature is very helpful in making service decisions and direction.
  • It provides a variety of extensions to bring your data together in one place and helps you do this easily.
  • Kits provided by Treasure Box provide basic but helpful methods for further development of services.
  • Since Treasure Data is used throughout the company, a dictionary was needed to know for what purpose it was created in order to manage the details created such as database, table, workflow, and master segment.
  • For this, I personally created and used it manually in Excel. I would like to have a dashboard that is automatically extracted or accessible only with admin privileges to manage it separately.
  • If there is a page where you can check the ERD, or if there is a function to create a relationship between tables by linking the ERD with the table link of Treasure Data, it is more efficient from an Ed Hook perspective if non-developers can check the relationship of the entire table.
  • The official document is good, but if there is a document translated into Korean, it will be easier to access Treasure Data for those who are new to it. Because of the entry barrier of English, it seems that it is difficult for some employees to learn, so I translated the document into Korean and spread it.
  • Being able to do optimized marketing has resulted in higher ROI than ever before.
  • Although there was a consensus across the company that decisions should be made based on data, there were insufficient resources to build a data infrastructure. At this point, the CTO made a proposal to the organization and started using Treasure Data.
Menu categorizing seems to be in the right order when viewed by the developer. In the first menu, there is a function to load third-party data and to manage the workflow so that the data can be updated regularly, and in the second menu, there is a function to manage and control the loaded data. Thirdly, there is a menu where you can perform marketing actions using the loaded data, and check trends after activation. This overall flow seems to have been well made based on the flow from loading data to action.

However, from the perspective of developers, the flow felt natural, but from the perspective of non-developers, it seems that the third menu is considered higher when viewed as a priority. Therefore, rather than showing the default page displayed when entering the first time as a job, it seems to be more familiar to show the dashboard of the master segment they are using. In other words, if you can customize the first screen for each role, you will be able to use the Treasure Data more for each role, and this will help you focus more on important donations for each role.