Import Custom Actions

Everything that falls outside of website actions should be imported using the Custom Actions import type.

Most common examples are trial data for PLG customers or product analytics data that HockeyStack does not currently integrate with.

Example Schema

All column names should be in underscores.

Column Name	Example Value	Requirement	Description
action_name	Newsletter Engagement	required	The name of the action. If none is provided, this will be deduced from your table / dataset name
identity	[email protected]	required	Identifier column. email address or company domain
date	2025-03-18T12:58:01.000Z	required	The timestamp of the custom action
user_id	684748833	recommended	Contact or company id from CRM or other sources. provides additional identifier information
company_domain	company.com		This will be saved as a company property
company_name	Awesome Company		This will be saved as a company property
engagement_type	Direct		This will be saved as an action property
is_returning_user	False		This will be saved as an action property
email_opened_at	1735689600000		This will be saved as an action property
email_scheduled	True		This will be saved as an action property
contact_name	Someone Everyone		This will be saved as an action property

Optional Schema (non-required columns):

Having extra columns help better connect and enrich your data within HockeyStack. Column names are expected to align with our formatting guidelines for import to work properly.

Action Properties and Other Properties:

You can specify object-specific data by prefixing it with the hardcoded object type:

• company_ to specify a company property

Other columns within your table that do not fit the example schema provided will be included as action properties in the import.