Census changelog www.getcensus.com

New

As part of our warehouse-centric observability suite that helps every user Sync with Confidence, we've released Sync Dry Runs for Salesforce, our most popular destination.

You can run a test sync without changing your destination data and receive a detailed summary report of how your data downstream will change.

The report shows the expected sync time, source record errors, and destination changes (number of records created, updated, and deleted). A dry run serves as a sanity check so both data and ops teams are aware of the scope of their updates and can make final approvals.

👉 Read the full announcement or see the product docs

New

Create custom behavioral events to track events from your data warehouse, like webinar registration, conference attendance, and onboarding completion, in your HubSpot activity timeline.

First define the event in HubSpot, including any custom event properties, then use the name in the Event Name property during the Census sync.

Check out the product docs for more set up details ✌️

Improvement

Zendesk: Update-only Ticket

Mailchimp: Support Tags Object and Add/update list members by hash

Shopify: User metadata fields

S3 Auth Alternatives: Role-based authentication, custom keys

Braze: Nested custom attribute support and Push Token structured field

New

Customers already use our integration with Postgres as a source to sync data to downstream business tools. Now you can connect to Postgres as a destination!

✨ Census + Postgres opens up internal use cases like pushing data warehouse insights to personalize app interactions. Enable data teams to influence products faster by empowering them to sync modeled and transformed data straight into their apps.

Get started with the docs, or read more in the blog!

New

• Added pagination by default to all non-single object endpoints (e.g. /syncs vs. /syncs/[ID])

• Expanded support for Models (/sources/[ID]/models). You can now get a list of all models for a single source, as well as create/update/delete models.

  • Models are now referred to by their Model ID instead of their Source ID, meaning that IDs should be consistent across the entire app (and with what we display in the UI). The old Source ID is now displayed as source_object_id.
  • description and approved status are now included in the API.

• Expanded support for Sources (/sources). You can now create, update, and delete sources.

  • Every reference of data_source (referring to /sources/[ID]/objects) is now referenced as object. This is particularly relevant to syncs, which now reference source_attributes.object instead of source_attributes.data_source.
  • type is now included inside sources.

• Expanded support for Destinations (/destinations). You can now create, update, and delete sources.

  • You can now refresh the list of destination objects for a destination by hitting /destinations/[ID]/refresh_objects and /destinations/[ID]/refresh_objects_status

• You can now GET a list of destination objects (/destinations/[ID]/objects), not just get a specific destination object

  • You can now refresh the list of fields for a given destination object by hitting /destinations/[ID]/objects/[OBJECT_FULL_NAME]/refresh_fields and /destinations/[ID]/objects/[OBJECT_FULL_NAME]/refresh_fields_status

• Expanded support for Syncs /syncs. You can now update and delete syncs.

  • from objects within column to field mappings in syncs are now objects. You must specify type as column or constant_value and put the actual value in data. As an example:

    {
        "from": "EMAIL", // References a column named 'EMAIL'
        // Becomes...
        "from": {
            "type": "column", // Manually specify it's a column
            "data": "EMAIL" // The column name
        }
    }
    

    {
        "from": {
            "value": "Jason", // References 'Jason' as a constant value
            "basic_type": "text" // And type 'text'
        },
        // Becomes...
        "from": {
            "type": "constant_value", // Specify it's a constant value
            "data": { // Include the actual data here
                "value": "Jason",
                "basic_type": "text"
            }
        }
    }
    

  • Added mirror_strategy as an option.

• Updated errors and error messages to be more friendly to users.

👉 For more info on the Census API: API Product Documentation

New

🚀 To infinity and beyond with Sync Logs: Census can write detailed logs of each data point you’ve synced so you can audit, troubleshoot, and create alerts using the most granular information – all in your warehouse!

Read the full announcement

For folks on Business plans and above, opt-in for Sync Logs here 🎉

New

Improvement

Notion

LinkedIn Ads

Google Analytics

Campaign Monitor

Orbit

Kustomer

Totango

Freshsales

Delighted

Enhancements:

Heap.io: Event Append

Pipedrive: Deal Participants

Pardot: List Support

Segment: Track Events

Customer.io: Update only and Collection Support

Facebook: Conversions API Custom Properties

New

✨ With Census and Notion, you can be truly self-serve with data in the warehouse and power operational workflows such as:

• Syncing product, billing, and customer data to Notion tables for pipeline reporting, financial forecasting, or campaign analysis
• Creating dynamic tables for weekly update reports powered by the freshest data
• Enriching product research and engineering roadmaps with customer data from the CRM or Google Sheets

Watch the video tutorial:

👉 More details in the blog or get started with the doc now.

New

✨ We recently added a self-service billing portal so all you need is a credit card to upgrade! Before, you'd have to chat with the Census sales team to upgrade your plan to the next tier.

You can upgrade to a higher tier plan (Growth or Business), access current or past invoices, and manage payment information – whenever it’s convenient for you.

No human interaction needed, unless you want it!

👉 More info in the blog or log in to Census to upgrade now.

New

Fresh data from the source helps you send the most relevant email to the right person every time, all the time.

💡 Operational Analytics use case: Use the 360º customer data you already have to build hyper-targeted segments to send personalized emails, reengage inactive users, and promote new products based on browsing or purchase history.

👉 See example use cases on the integration page or get started with the docs.