Import Custom Actions
Custom Actions are actions taken by a user or company, that you've tracked
Schema:
These columns are required for this import type. At least one of your columns is expected to map to these columns, or match the name exactly.
action_name
✅
The name of the action. If none is provided, this will be deduced from your table / dataset name
identity
✅
This can be an email or company domain (acme.com)
date
✅
The date of the action
company_domain
✖️
Can be it's own individual column if identity is an email
user_id
✖️
if you have a user_id for a user that you use elsewhere, you can specify this here
Optional Schema (non-required columns):
Having these extra defined columns help better connect and enrich your data for better use within HockeyStack (column names are expected to match, for import to work properly)
Action Properties and other properties:
This is extra information to describe an action. Other columns within your table will be included as action properties the import.
You can also specify object-specific data by prefixing it with the CRM object type:
company_to specify a company property
How it works:
Here's an example Newsletter Engagement custom action
action_name
Newsletter Engagement
date
2025-01-01
company_domain
company.com
user_id
123456789
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
call_scheduled
True
This will be saved as an action property
name
Someone Everyone
This will be saved as an action property
Last updated