Destination fields are the total number of fields in downstream SaaS destinations (e.g., Intercom) which Census syncs data into for a workspace. These are measured across all syncs, not individual syncs.
For example, let’s say you have a Salesforce contacts sync and a Hubspot contacts sync. For 10 fields you could sync 1 field to Salesforce and nine to Hubspot, or five to each, or anything in between. If you sync the same five fields to both Hubspot and Salesforce, that would total to 10 fields because it’s relative to the downstream destination.
In the Census UI, destination fields can be found within a sync as the mapped fields and identifiers.
Each month a workspace can sync up to the number of destination fields specified by the plan. This includes destination fields updated by Census via scheduled, triggered and/or manual syncs.
Destination fields are unique per destination, so a field (e.g., active_users_last_30d) synced into two different destinations will be counted twice towards the monthly allocation, however if two different syncs send data to that same field within one destination, it will only count once.
You can sync data to an unlimited number of destination with Census. The Enterprise connections which are only available on the Platform plan are Oracle, Anaplan, Workday, NetSuite, and Shopify.
We add new source and destination integrations every week. If you don't see an integration in our catalog, contact us and we can prioritize it. If you want to build an integration yourself, check out our Custom API.
We offer a no-commitment trial, with access to all destinations and features, for 14 days. After that, your account will convert into a Free plan.
Early stage companies who are part of the Census Startup Program will receive a discount in year one.