Integrate Kustomer Data with BigQuery for Useful Analytics and Activation

A Step-by-Step Guide

Kustomer logo
BigQuery logo

Make the Most of Your Kustomer Data in BigQuery

Kustomer and BigQuery are a natural fit for data modeling, business intelligence and data activation – especially for retail brands interested in optimizing their overall business performance, acquisition and retention marketing programs, and merchandising and fulfillment operations decisions.

Kustomer is a customer service CRM platform that centralizes customer interactions and data for businesses. It offers a unified view of customer information, automates support processes, and enables personalized and efficient customer communication. Kustomer is designed to enhance customer service by providing a seamless and collaborative platform for support teams. BigQuery is a serverless and cost-effective enterprise data warehouse that works across clouds and scales with your data. Use built-in ML/AI and BI for insights at scale. Together, the software application and cloud data tooling provide business and data practitioners with an opportunity to analyze and optimize shopper engagement, clienteling and personalization to drive profitable growth.

Connect to Kustomer

The first step toward useful, modeled Kustomer data in BigQuery is to connect the source and destination systems. There are many legacy tools available in market that handle the ETL or ELT transfer of Kustomer data to BigQuery, and there are emerging tools that accomplish this transfer while providing value-added services like local data logging, and semantic data labeling and mapping along the way – making Kustomer data modeling, analytics and activation easier once the data is landed in BigQuery.

To connect to Kustomer, follow these easy steps

  • Open SoundCommerce in any browser. Open the “Intelligent Pipeline” application from the top right navigation menu. Select “Sources” from the left navigation menu. Choose “Add New Source” from within the Sources pane to open the data source library.

  • Search or browse to find “Kustomer” within the data source library.

  • Complete the “Connection Setup” form with your credentials and token to securely connect to Kustomer and begin collecting source data.

Log Kustomer Data for Flexible Modeling in BigQuery

There are a few more considerations to address along the way. First, what happens if Kustomer is unavailable for some reason, or the data you’re expecting has been purged by Kustomer? What happens when Kustomer changes their API schemas and data scope? What happens if you need to reinterpret your Kustomer data for a new use case in the future?

You’ll want your Kustomer data immutably logged locally, just upstream of BigQuery to ensure you have the data and data flow flexibility you need to future-proof your Kustomer data and models. SoundCommerce provides permanent logging of Kustomer data upstream of BigQuery to ensure failover and future-proofing. Regardless of how you connect your Kustomer and BigQuery data, you’ll want a data lake or event log in the middle to ensure data integrity and modeling flexibility.

Define and Label Kustomer Data for BigQuery

As new technologies arise and best practices evolve, traditional integration tools like ETL and ELT data pipelines are giving way to intelligent pipelines that help prep data for BigQuery starting at ingest. Simply moving JSON from Kustomer to BigQuery leaves all the work for your data team in BigQuery.

As you onboard your Kustomer data into BigQuery, you’ll want to create semantic labels and metadata that describe the Kustomer data for easier unification and modeling across other systems and data in BigQuery.

There are third-party solutions that will catalog your Kustomer data and generate semantic labels and mappings after you’ve landed it in BigQuery. With SoundCommerce, the Kustomer data is defined and labeled on its way into BigQuery instead, to avoid this costly rework later. You’ll end up with business-ready entities like orders, customers, products and campaigns, making it much easier to model your Kustomer data in BigQuery.

Map Kustomer Entities to BigQuery

Once the raw Kustomer data has been organized into useful entities, it’s time to map the Kustomer data into useful tables in BigQuery.

Why do defined and labeled entities from Kustomer matter so much? The main reason is that Kustomer data needs to be combined with data from other SaaS and on-premise software systems in useful ways. Landing raw Kustomer data in BigQuery without this semantic understanding means data engineering and analyst teams must do all of the heavy lifting regarding the meaning of the Kustomer data and the standardization of the meaning of that Kustomer data from scratch in BigQuery.

Defining, labeling and mapping the Kustomer data on the way in means much less effort once the data is landed in BigQuery.

Materialize Kustomer Data in BigQuery

Next, you’ll establish a secure connection to BigQuery:

  • Select “Destinations” from the left navigation menu. Choose “Add New Destination” from within the Destinations pane to open the data destination library.

  • Complete the “Connection Setup” form to securely connect to BigQuery to establish a secure destination for your labeled, mapped and modeled data.

That’s it! You now have logged, labeled and mapped data from Kustomer flowing securely to BigQuery.

Model Kustomer Data in BigQuery

Once you have well-formed entities from Kustomer onboarded to BigQuery, it’s time to build useful analytical and behavioral models on the Kustomer data – and combine the Kustomer data with data sets from other systems in BigQuery for more advanced, cross-dimensional analysis.

You can build your own analytical models on the Kustomer data in BigQuery using languages like SQL and Python, organized into model libraries in tools like DBT or Coalesce. With SoundCommerce, you get prebuilt analytical models for Kustomer running in BigQuery, with ready access to the model source code in DBT.

Host the Modeled Kustomer Data in BigQuery for Analytics

BigQuery supports reporting and visualization through a wide variety of analytics tools including Sigma, Tableau, Looker, Power BI and Microstrategy to name a few. You can build your own dashboards, tabular views and graphs in any of these tools to reveal insights about Kustomer in your BigQuery models. SoundCommerce provides pre-built embedded reports in Sigma to reduce the time, cost and risk of BI reporting of Kustomer data out of BigQuery – so you can start making better decisions and taking better action as soon as you’ve connected Kustomer to BigQuery.

Host the Modeled Kustomer Data in BigQuery for Campaign and Customer Activation

Whether your marketing team uses Kustomer for activation – or uses other tools and channels or both to take action on the data – you’ll want to be able to easily move your modeled Kustomer data in BigQuery to your most important marketing applications.

If you’ve followed the steps above to properly onboard and model your Kustomer data in BigQuery, it’s easy to use reverse ETL (rETL) tools like Census or Hightouch to orchestrate the data from there, or use SoundCommerce native orchestrations to push data into common channels and applications like Facebook, Instagram, TikTok, Braze, Klaviyo, Insider or Dynamic Yield to put the Kustomer data in BigQuery to use!

Getting Your Kustomer Data Defined, Labeled, Mapped and Modeled in BigQuery is Easy!

SoundCommerce can automate the steps necessary to bring Kustomer data into BigQuery, addressing the key functions of raw Kustomer data logging, Kustomer semantic definitions and mappings, and pre-built Kustomer data models that are analytics- and activation ready in BigQuery.

Contact us today to get started with Kustomer in BigQuery!

Technical Resources for Integrating
Kustomer Data with BigQuery

More information and technical specifications for data collection from Kustomer is available at:

Kustomer API Documentation

More information and technical specifications for data ingest into BigQuery is available at:

BigQuery API Documentation

Integrate and Model Kustomer Data in BigQuery