Supported integrations & how to create the hierarchy
You can currently create both levels of the hierarchy (Organizations and Accounts) in Hubspot. Doing so is actually quite straightforward - you simply need to map a Hubspot object into Vitally as the Organization object. Follow our normal Hubspot instructions for Accounts, as the steps are basically identical for Organizations.
You can select the column that references the Organization ID the Account belongs to (only applicable in the Account setup flow when Organizations is enabled).
Once you have configured these settings we will pull in the fields as traits. No additional field mapping is required.
You can currently create both levels of the hierarchy (Organizations and Accounts) in Segment. To do so, there are two requirements:
- 2.You must send a
groupfor each level of the hierarchy. Each
groupneeds a trait that identifies the level in some way. For example, pass in a
leveltrait with values for
Account. You can name your traits and values anything - they just need to exist so that our system can parse a
groupcall and understand if it is for the
From here, our team must configure some things on our end to support your Segment
groups and ensure they get routed to the right level. Please contact your Vitally CSM to learn more.
To associate an Account created by a Segment
groupto an Organization in Vitally, your
groupcalls should have a trait in them that contains the external ID of the Organization the Account should be associated to. For example, let's say you have an Organization in Vitally with an external ID of
org-1, and Account with external ID
account-1should be associated to that Organization in Vitally . Your
groupfor the account might look something like this:
Once you have this trait in place, contact your Vitally CSM and they can configure your integration to link Accounts to Organizations using this trait.
Users are associated to Organizations via Segment by simply using
groupcalls support a
userId, we'll simply auto-associate the User specified in the
userIdfield to the Organization referenced by the
group's ID (i.e. the first argument to the
You can currently create both levels of the hierarchy (Organizations and Accounts) in Salesforce. Doing so is actually quite straightforward - you simply need to map a Salesforce object into Vitally as the Organization object. Follow our normal Salesforce instructions for Accounts, as the steps are basically identical for Organizations.
When configuring how Accounts map in to Vitally in the Salesforce integration page, there's a question in the Accounts configuration that asks the below:
Here, you'll want to select the Salesforce field on your Account object that contains a 'pointer' (i.e. reference) to the parent object (i.e. the Organization) the Account should be associated to in Vitally. This will ensure the Account is correctly linked to the Organization in Vitally. If the referenced parent object does not already exist in Vitally as an Organization, it will be created.
Similarly to the above, when configuring the User/Contact sync with Salesforce, you'll see this question:
Here, you'll need to select the Salesforce field that contains a pointer/reference to the parent object (i.e. the Organization) the User should be associated to in Vitally.
You can create both levels of the hierarchy (Accounts and Organizations) with all our data warehouse integrations. Please see the docs for these integrations to understand how this works here.
You can also manually create every level of the hierarchy directly within the Vitally UI. To do so, either use the Quick Jump window or the global create button in the top left of the UI.
Once your Organizations are created, you'll be able to associate both Accounts and Users to their Organizations when creating/editing an Account/User.
You can create the hierarchy when creating or updating accounts and supplying the organizationId in the "Accounts" or "Users" payload.