Interviews

How Screencastify syncs data with ActiveCampaign to better personalize emails | Census

Roslyn Coutinho
Roslyn Coutinho January 05, 2023

Roz doubles as a product marketing manager and brand marketing manager at Census. She's a designer turned product manager, driven by curiosity and a constant desire to learn. San Francisco, California, United States

This interview is part of our Select Stars series, highlighting use cases of data and ops practitioners driving more impact by activating data in their business.

Zack Blois is the VP of Strategy and Operations at Screencastify, which provides an easy and simple way to create, share, and consume asynchronous videos. In this interview, Zack shares how and why he pivoted from marketing to operations, how he began working in data, and how his team improved email marketing by syncing data with ActiveCampaign.

What is your role at Screencastify? 

I joined Screencastify about two years ago as the Director of Marketing. Screencastify was growing rapidly, and part of that growth was building out the marketing function. I was the second marketing hire and helped build our team from two members to seven.

As things progressed and marketing got more established, it became clear that I could help the company in operations as I have a revenue operations background and a marketing background. I was given the chance and the honor to move over into my current role, which is VP of Strategy and Operations. My goal is to build out this function, which includes revenue, operations, data, and strategy for the go-to-market group.

Your background isn’t in data engineering, yet you clearly have data and analytics skills. How did you get here?

I always joke that I've made a career out of doing things people didn't want to do or didn't have the time to do.  Often, data analytics or CRM efforts get overlooked or teams assume the issues will be worked out on their own. But I’ve been interested in this area and am willing to dive in.

I started my career as a teacher, which is a great tie to what we do here at Screencastify because so many of our awesome users are educators. Joining was a way for me to get back to my roots a little bit, which was awesome. 

After teaching, I made my way into marketing through a small EdTech company. I gravitated to operational components, including how to use relational databases within revenue organizations. I was very interested in building the architecture and the automation needed to get the data needed for our customers. I was also interested in ensuring we had the right information in our reports to know what was going on in the business.

Throughout my career, I’ve gravitated back toward operations and data. I've gotten a chance to work at growing companies and more established enterprises. I’ve built out data operations for different departments and occasionally for entire companies.

How is your data team organized?

We recently built a centralized data team that reports to me. Historically, data has been owned by different departments, and we often collaborated directly to handle those needs. Now, it’s finally become centralized.

Can you describe your data stack today?

At a high level, everything revolves around a data warehouse. We use BigQuery as our primary warehousing tool, then we operate off of a hub-and-spoke model where we set up our upstream data architecture in BigQuery. 

We think a lot about the “keys” between our tools. We sync BigQuery and dbt with ActiveCampaign, for example, for our user communication and engagement efforts, and we sync BigQuery with Salesforce for a lot of our aggregated data. 

We also use Pendo for product engagement and we're bringing a lot of product-level data that isn't already captured by Pendo into the tool through a number of different keys. This helps us improve personalization.

Generally, we rely heavily on a central source of truth, then go directly to the endpoints that allow us to engage and help our customers in the best way possible.

What challenges have you encountered when it comes to managing data?

I’m part of a marketing operations Slack community, and a fellow member brought up how they were using Census to migrate data out of their data warehouse into their different endpoints. A light bulb went off in my head as I realized that was a challenge at Screencastify.

Basically, our data warehouse was our record of truth and we trusted it. The challenge for us was migrating that data into our tools in a way that made sense. Census was attractive to us because I could set it up on my own. Although I can get my hands dirty with some SQL, I’m certainly not a full-time data professional. 

The fact that I really could build this portion of the data pipeline in literally 15 minutes was a huge selling point. And it works really well. It scales really well, and it allowed us to do some sophisticated things that literally at other companies had taken me months to work with a data team to build when you think about data pipelines in one day, essentially.

Show & Tell: Syncing Data to ActiveCampaign

We use ActiveCampaign for engaging users outside of our product (i.e. our marketing and product emails are housed and sent in the tool). One of our goals was to get product data and usage data for individual users into our ActiveCampaign destination so we could better personalize our messaging.

For example, we like to send status updates and reporting metrics to our users to let them know how many videos they’ve made within the product. The information helps us, as well, because we can start to understand where usage is high or low over given time periods, and then start to provide additional enrichment or potentially some help if we see that users aren’t engaged. 

We have a free version of Screencastify, as well, and part of our strategy is to identify when users are good candidates for upgrading. Although users can get a lot of value from our free version, there are some limitations. We can start to see when a user might be running into those limitations based on their usage, and then send messages to help them understand the benefits of upgrading.

Historically, we had relied on a custom API to push data to Active Campaign to personalize and automate our emails. This custom API worked okay, but product and engineering had to maintain it. As fields were added, we would have to update the API. Census allowed us to make updates and builds quickly, ultimately pushing product usage data directly into ActiveCampaign.

What advice would you give to those with a similar use case that want to use a reverse ETL tool?

Think about your business objectives before anything else. You have to consider what’s good for your customer and what’s good for the business. Census is an incredibly flexible tool that allows you to use the tools you’re already using in the way that you want. I recommend that folks start with their business requirements that Census can help support. Once you’ve nailed down your objectives, you can start to expand and evolve from there.

👉 Learn more about how Screencastify uses Census here.

✨ Want to be featured in our next Select Stars profile? Apply here and we’ll be in touch soon!

Related articles

Customer Stories
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native

Every business’s best source of truth is in their cloud data warehouse. If you’re a SaaS provider, your customer’s best data is in their cloud data warehouse, too.

Best Practices
Keeping Data Private with the Composable CDP
Keeping Data Private with the Composable CDP

One of the benefits of composing your Customer Data Platform on your data warehouse is enforcing and maintaining strong controls over how, where, and to whom your data is exposed.

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: