SaaS Datasets
Census allows you to create datasets directly from your CRM systems like HubSpot and Salesforce, making it easy to work with your business data alongside your warehouse data. This guide explains how SaaS Datasets work and how to get started.
Overview
SaaS Datasets allow you to:
Import any object from supported CRMs (including custom objects)
Control which fields are imported for each object
Automatically refresh data on your schedule (hourly, daily, or never)
Use all Census features with your CRM data (AI columns, enrichments, deduplication)
Create segments and syncs using your CRM data
Query the data from your existing data warehouse using Census's Iceberg catalog
Getting Started
To create your first SaaS Dataset:
Navigate to the
Datasets
tab in CensusClick
+ New Dataset
in the top-right cornerSelect
Import Dataset from App
Choose your CRM system (HubSpot or Salesforce)
Select the objects and fields you want to import
Configure your refresh schedule
Save your dataset
How It Works
Data Storage and Access
Your data is imported using your CRM's API credentials
The data is stored in Apache Iceberg format in Census Store
Census provides an Iceberg catalog that makes this data queryable from your data warehouse
Data is automatically refreshed based on your specified schedule
Querying Your Data
Because SaaS Datasets are stored in Apache Iceberg format, you can query them directly from your data warehouse using federated queries - meaning you don't need to copy the data into your warehouse first. This is sometimes called "Zero-Copy" or "Zero-ETL" access.
For example, if you're using Snowflake, you can query your SaaS Dataset tables just like any other table:
Data Lifecycle
Data is automatically refreshed based on your configured schedule
When you delete a dataset, all associated data is permanently removed from storage
You maintain full control over which objects and fields are imported
Features and Capabilities
SaaS Datasets can be used with all Census features:
Data Access Methods
Your SaaS Dataset data is accessible through:
Census UI - Browse and manage your datasets directly
Your Data Warehouse - Query the data using federated queries via the Census Iceberg catalog
Best Practices
Start with a subset of fields to optimize initial load times
Set refresh schedules based on your data update frequency
Monitor your API usage to stay within CRM limits
Regularly review and clean up unused datasets
Security and Compliance
All data is encrypted at rest and in transit
Access controls are managed through Census permissions
Data storage follows Census's security and compliance standards
Option to use your own storage infrastructure for additional control
Last updated
Was this helpful?