Census — Data, ETL product updates and releases, tracked on megachangelog.
HTTP Request object syncs now support per-sync custom headers on the HTTP Request destination and within NetSuite and HubSpot integrations, allowing more flexible request customization.
DELETE syncs in the HTTP Request destination now support JSON and URL-encoded request bodies, expanding the types of integrations and APIs that can be called during deletion operations.
The Users and Invitation organization endpoints in the Fivetran Activations API have been deprecated in favor of Fivetran's core Users endpoints, which offer expanded functionality including invitation generation and account-level role management. Developers should plan to use both API keys in parallel during the transition to the standard Fivetran auth mechanisms.
The Microsoft Dynamics connector now supports Service Principal (client credentials) authentication as an alternative to OAuth, giving users more flexibility in how they authenticate their connections.
Workspace Owners in Fivetran Activations can now assign custom roles to workspace members, previously limited to account administrators. This improves access control management within Fivetran Activations workspaces.
The Zendesk connector now supports lookup fields on v2 custom objects, allowing fields that reference other Zendesk objects like Users or Organizations to be mapped through a "Lookup by" option in the UI.
The LinkedIn Ads connector now supports syncing multiple customer identifiers (emails, ad IDs) at once, enabling better matching when contacts have multiple IDs on file.
The HTTP Request destination now supports the Client Credentials OAuth grant type, enabling server-to-server authentication flows without user login for machine-to-machine API integrations.
Activation syncs can now be triggered automatically when upstream Fivetran connections and transformations change. Configure these dependencies directly in your sync's trigger settings under the Fivetran tab with no additional setup required.
The Salesforce connector now supports the FinancialAccount object for Salesforce Financial Services Cloud customers, enabling FSC users to sync financial account data.
The Userflow connector now supports EU region selection via a new Region dropdown in the connection setup UI. Existing connections default to US with no changes required.
The Ortto connector now supports regional API endpoints (US, AU, EU) that can be selected during connection setup. Existing connections default to US.
The Amazon Athena connector now supports Liquid template expressions in sync mappings, allowing you to transform and combine source fields using Liquid syntax (e.g., {{ record['first_name'] }} {{ record['last_name'] }}) when syncing to your destination.
The Freshsales connector now supports dynamic rate limiting that adapts to your account's API limits, improving reliability and sync performance.
Fivetran Activations now supports Spotify Ads as a destination, enabling businesses to sync customer data to build targeted audiences and track conversions across audio, video, and display ads.
The X Ads connector now supports ip_address and user_agent as optional fields for web conversions, enabling richer data collection and targeting capabilities.
The Zendesk connector now supports v2 custom objects. Zendesk will remove legacy custom objects on July 27, 2026, so users should migrate to ensure their syncs continue running.
Census is deprecating Census Store and related features (CSV Datasets, Mesh Datasets, and Iceberg catalog access) as it unifies with Fivetran's data platform. Existing accounts will have read-only access from July 2026, and the service will shut down completely on August 1, 2026.
Transactional emails from Census are now sent from activation-support@fivetran.com instead of support@getcensus.com. Users with email filters or rules based on the sender address should update them to include both addresses.
Census has disabled per-workspace weekly summary emails in preparation for integration into Fivetran, with an improved version planned for the future. If you have automated processes depending on the current email format, contact support to request re-enablement.