Setting up your Data for import

Data imports & exports require a Data Warehouse add-on. Please contact your CSM with any questions about how to get started with Data Syncs

Overall Data Requirements:

Actions and Object based data require an identifier associated with each row of data. For user-based data this is an email and for company-based data this is a company domain.

• To ensure that a record is imported, this identifier needs to be present, or else there is no way to connect this record to other data within the platform.

• The only exception to an email or company domain is another unique identifier for a record provided by a CRM (e.g. Salesforce ID)

• Records that lack this requirement can not be imported and will be missing from the import.

Choose an import type:

HockeyStack has four primary types of data. When importing data to HockeyStack from your data warehouse, aligning your source data to our internal data models helps us properly connect what you're importing to data that already exists in HockeyStack.

HockeyStack DataSync Import data types:

Type	Description
Website Actions	Each row represents a website action taken by a user or company
Metadata	General metrics that can't be connected to a single person or a company. Most prominent example is Campaign / Ad data, but this can also include other marketing activity. Each row is a timestamp and the combination of campaign, ad group, ad, and UTM information. There are three metrics that can be tracked for the timestamp: spend, clicks, and impressions.
Properties	Object properties, usually relating to companies or specific users. Each row is an object type, object value, and corresponding property. For example: object type: Company ID object value: that company's Salesforce Account ID property name: Company Name property value: 'Acme.inc'
Custom Actions	Each row represents an action taken by a user or company

How to best configure your data for import on HockeyStack

Each import has a schema and required fields to ensure that the data you import can be properly connected to a user or company if necessary. After choosing an import type, please ensure that the schema within your data warehouse matches the schema outlined in one of the import types listed below:

Import Custom Actions

Import Website Actions

Import Metadata

Import Properties

Indexing your Data

Recurring imports require a date based column (such as added_at ) that makes it clear what rows are newly added to your data source.

Further, table-based Data Warehouses (Snowflake or BigQuery) require this column to help with optimal indexing. (aka: How do we go over your data in the most cost-efficient fashion?)