megachangelog
Feature

Trigger Activation Syncs from Fivetran Connections and Transformations

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.

 

New

  

Activation syncs can now be triggered automatically when upstream Fivetran connections and transformations. You can configure these dependencies directly in your sync's trigger settings under a the Fivetran tab — no additional setup required. This replaces the previous Fivetran activation trigger based on API keys and is now enabled automatically for every account.

Stay tuned! We'll be building on this foundation to support more advanced scheduling and orchestration workflows over time.

Learn more in our docs →

fivetranactivationsyncstriggersorchestration

Source: original entry ↗

More from Census

Follow Census to get its new changes in your feed and email digest.

Improvement

Braze: Email and User Alias as Identifiers

The Braze connector now supports email and user_alias as user identifiers for Event and PurchaseEvent syncs, alongside the existing external_id option, providing more flexibility in data synchronization.

brazeconnectorsidentifiersevents
Improvement

LinkedIn Conversions: lead as an Optional Field

LinkedIn Conversions now supports an optional lead field to map Lead Gen Form Response IDs and attribute conversion events to specific lead forms.

linkedinconversionsintegrationslead-forms
Announcement

API V2 Beta Endpoints Now Available

Census introduces the first V2 API endpoints with a new Sources API that supports region and storage backend selection, Group ID management for access controls, and Personal Access Token authentication. Workspaces have been removed from the API and Workspace API Keys are no longer supported.

apibetasourcesauthenticationmigration
See all Census changes →