Google Cloud Platform Blog
CoolaData digs into the “why” of online consumer behavior with help from Google Compute Engine
Sunday, December 1, 2013
Today’s guest blogger is Nick Terner, backend team leader at
CoolaData
, based in Tel Aviv, Israel. CoolaData provides fully actionable, unified behavioral analytics solutions for online companies. The company recently raised
$7.5 million in Series A funding
.
CoolaData delivers something different to the world of big data analytics. Many companies in the space offer solutions designed to answer the “what” and the “when” of consumer online behavior. We uncover the “why.” Why did a customer cancel an account? Who is likely to uninstall my app? Why did a customer abandon an online shopping cart?
To uncover the why, we need to examine the sequence of events that occurred before a customer made a certain decision. For example, did they go to an online retailer’s customer service site and not receive the help they need? And to better understand the why, we need to look for patterns in online behavior, often times using historical data.
All of the above requires that we analyze a great deal of data – current and historical – using innovative methods like cohorts, paths and funnels. And to produce actionable big data analysis in real-time, we use
Google Compute Engine
for the data enrichment process. Compute Engine allows us to take the information, analyze and learn from it in order to determine actionable insights for our customers quickly.
CoolaData is building a unified behavioral analytics solution that is infinitely scalable, powerful and dynamic, with
Google Cloud Platform
as the foundation. Hadoop and Storm run on Compute Engine, and
Google App Engine
serves our Semantic Layer web API.
Google BigQuery
enables analysis of the huge datasets we collect from a variety of sources via
Google Cloud Storage
. So far, gaming, e-commerce and FinTech companies are the initial adopters. We also participate in the trusted tester program for Google Compute Engine, which has allowed us to use new features, while at the same time providing recommendations for others.
Our development team decided to use Compute Engine when we built our platform over a year ago. Google’s predictable workload performance was key, but unified authentication across the cloud platform and encryption were also major factors. With Compute Engine, we know exactly what we’ll get when we provision an instance. The Compute Engine team offered great support and allowed us to plan out our future capabilities. In addition, Compute Engine now has transparent maintenance, which allows us to perform regular proactive maintenance without impacting running VMs. We expect this will make Google a reliable, high-performance environment, and regular host patches will also ensure better security than other providers.
Compute Engine’s predictable performance is a huge benefit because it allows us to plan for growth. As we move out of beta testing and prepare for the general availability of our solution in early 2014, we know we can onboard new customers smoothly – even if they bring us huge amounts of historical data. We also know that we can easily add connections to more third-party data sources. The more information we can analyze, the better we’ll be at helping them not only understand the reasons behind a customer’s decision, but also predict and influence the choices that customer and other similar customers will make in the future.
-Contributed by Nick Terner, Backend Team Lead, Cooladata
No comments :
Post a Comment
Don't Miss Next '17
Use promo code NEXT1720 to save $300 off general admission
REGISTER NOW
Free Trial
GCP Blogs
Big Data & Machine Learning
Kubernetes
GCP Japan Blog
Labels
Announcements
56
Big Data & Machine Learning
91
Compute
156
Containers & Kubernetes
36
CRE
7
Customers
90
Developer Tools & Insights
80
Events
34
Infrastructure
24
Management Tools
39
Networking
18
Open Source
105
Partners
63
Pricing
24
Security & Identity
23
Solutions
16
Stackdriver
19
Storage & Databases
111
Weekly Roundups
16
Archive
2017
Feb
Jan
2016
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2015
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Feed
Subscribe by email
Technical questions? Check us out on
Stack Overflow
.
Subscribe to
our monthly newsletter
.
Google
on
Follow @googlecloud
Follow
Follow
Follow
No comments :
Post a Comment