Customer Stories

How Handshake tracks their full customer journey | Census

Sean Lynch
Sean Lynch April 26, 2021

Sean is co-founder and Chief Product Officer (CPO) at Census. He loves enabling data-driven organizations, so he's energized by introducing the world to Data Activation. San Francisco, California, United States

Today, we’ve got a Census customer guest post from Phillip at Handshake. If you're not familiar, Handshake is the number one site for students to find a job, connecting 8 million active students across 1,100 schools with 500,000 employers—including all 500 of the Fortune 500—on their platform. Phillip manages business systems for the Employer (or B2B side) sales team at Handshake and has been leading the charge on improving sales processes and tracking sales data at Handshake, Samsara and SurveyMonkey for 6 years. Today Phillip’s sharing his powerful technique for building complex Salesforce objects with SQL to streamline analytics.

Like most Salesforce customers, Handshake monitors Opportunities closely as they move from creation to closing. But we found that Opportunities only captured a slice of the complete customer journey through our sales funnel. We wanted to track the full journey, starting from the first interaction with the sales team, well before the opportunity gets created. These insights help guide our go-to-market teams on channels that are effective and areas in the journey that need improvement.

At Handshake, the journey begins when a prospect first interacts with our sales team or takes an action to qualify as an MQL. Sometimes, this is a webinar sign-up or demo request, but other times an SDR might proactively reach out to the prospect to discuss ways they could better leverage the Handshake platform. The Customer Journey ends when the prospect is either disqualified, goes cold, or is associated with an opportunity that moves to either closed won or closed lost.

We decided to build a new Customer Journey custom object to track this lifecycle. Our Customer Journey object is a single record that logs important milestones a prospect reaches while in the sales funnel (our prospects are all contacts because managing leads are a nightmare, but that’s a different post!) We’d use the Customer Journey custom object to log the journey start, journey end, start campaign, end campaign, and the date/time of important milestones between. It looks like this:

Initially, we planned to do this in Salesforce using native platform tools. We would create an Apex trigger on Tasks, Contacts, and Opportunities to build a system of automation and custom relationships. Then we would generate a new Customer Journey when appropriate and update an existing customer journey when an active journey already existed. This would work for generating and maintaining customer journeys going forward, but we would need to write a complex Apex script to reconstruct historical customer journeys. In addition, the Salesforce task and contact history tables we would need to query were several million rows each, and Salesforce's SOQL does not play nicely with large datasets.

I realized that an easier approach would be to use Census to construct the Customer Journey records nightly with a SQL query to our data warehouse. SQL is great for constructing tables, and it was much easier to use for this purpose than an Apex script.

Using a Census model, I wrote a query that uses our daily snapshot of Salesforce data to construct a table of journey events, and we can extend that to include other data sources in the future.

After that, it was simple to map this table to the Customer Journey object and set up a nightly sync in Census to upsert all Customer Journeys. In addition to getting all historical customer journeys into our Salesforce instance in one go, there was no custom code to maintain or governor limits to worry about going forward, since the nightly Census sync would keep everything up to date.

We've been using Customer Journeys now for several months, and it's given us insight into how prospects interact with our sales team and use marketing collateral. This data will continue playing a role in predicting close rates based on specific customer interactions, analyzing stage by stage conversion rates to improve our processes, and monitoring pipeline health indicators as we grow our sales and marketing teams.

Interested in how Census can help your company reach new heights? Book a demo to get the deets from a product specialist then start your free trial to see how Census can empower your data teams. 💪

Related articles

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps:

Best Practices
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue

Remember when the days of "Dear [First Name]" emails felt like cutting-edge personalization?

Product News
Why Census Embedded?
Why Census Embedded?

Last November, we shipped a new product: Census Embedded. It's a massive expansion of our footprint in the world of data. As I'll lay out here, it's a natural evolution of our platform in service of our mission and it's poised to help a lot of people get access to more great quality data.