Census uses your Vitally API key to send data. Before we can connect Census to Vitally, we need to first copy that key out of Vitally's settings page.
1.
Click the ⚙️ icon at the bottom of the left sidebar, select Integrations, and then Vitally Analytics API. Or navigate directly to https://[your-domain].vitally.io/integrations/api
Optionally name your new connection and then click Save
🗄 Supported Objects
Object Name
Supported?
Matching Keys
Create Fields
Users
✅
User ID only
✅
Accounts
✅
Account ID only
✅
"Track" Event
✅
Event ID
✅
NPS
🔜
Vitally defines User ID and Account ID as the unique ID for these objects in your system. You are free to use whatever ID you like, but it needs to be unique.
User Behavior Notes
Users must have at least one Account in Vitally so Accounts is a required field when syncing to users. It's also an Array field so it you'll need to provide it an array value or JSON formatted Array.
Any Account ID values used when mapping to that don't already exist in Vitally will be automatically created.
🔄 Supported Sync Behaviors
Learn more about all of our sync behaviors on our Core Concept page.
Behaviors
Supported?
Objects
Update or Create
✅
All
Update Only
🔜
All
Contact us if you want Census to support more Sync Behaviors for Vitally
🔍 Additional Service Quirks
Vitally's internal database has a delay between Census completing its upload and having those results reflected in the UI. This delay can be a couple seconds to a couple minutes in extreme cases.
As with all Census syncs, when you unmap a field in Census, we will stop updating those fields. We do not delete them.