Import Properties

This is probably the more convoluted import type to understand. But don't worry, below explanations should help clear the air on when a Properties import is necessary and how to set it up.

This import is used to ingest properties of objects (can be additional properties of default CRM objects or new custom objects that you currently do not have access to in HockeyStack).

Most common examples include subscription data that cannot be tracked through the CRM or product line items that are updated through the data warehouse directly. This data type also supports importing additional properties for objects we already track - like importing additional properties for accounts in your CRM.

Choosing an Object Type

HockeyStack's standard objects map from CRM objects (primarily Salesforce and HubSpot). If your object type maps to a standard object type from your CRM, you can select it and import as such. Examples are not limited to:

HockeyStack Object	Salesforce Object	HubSpot Object
Company	Account	Company
User	Contact	Contact
Deal	Opportunity	Deal

Default object types are useful when you have additional datapoints about your companies and contacts etc. that your CRM does not have access to. HockeyStack can be used to unify all these datapoints.

Custom Objects:

You can also import custom objects into HockeyStack, which you would configure under "Other" type in the Data Syncs configuration page. A custom object can represent any type of structured information that can be associated with a company or user, such as Outreach Call logs, subscription details of your trial users, or other custom datasets.

The only extra information we need to be able to configure a Custom Object Properties import is an object key - which is a unique underscore key to define what the object is to be called and a _id suffix (i.e. subscription_id, outreach_call_id etc.)

Example Schema

All column names should be in underscores.

Each row in the table signifies one record of the given object type. The term “record” describes a particular occurrence of an object (i.e. a single Company in your CRM).

Column Name	Example Value	Requirement	Description
identity	acme.com	required	Identifier column. This can be an email address or company domain.
unique_id	492143	required	A unique id for the record/row. This guide on data grain helps determine how to come up with the value for this column.
company_domain	acme.com	recommended	This will allow us to connect this data to the corresponding Company record in HockeyStack.
user_id	399	recommended	This will allow us to connect this data to the corresponding User record in HockeyStack.
call_length	45		This will be saved as a property of the record.
call_start_date	2025-03-20T23:30:21.000Z		This will be saved as a property of the record.

Connecting your Custom Object to a Company or User:

• If you specify a company_domain column, this will allow us to connect this data to the corresponding Company record in HockeyStack.

• If you specify a user_id column, this will allow us to connect this data to the corresponding User record in HockeyStack.

Determining the Properties of the Record

Any column name that doesn't map to a specified column in the given schema example will be ingested as a property of the given record.