HockeyStack Implementation Scope: Data Warehouse Connection

Some customers choose to connect their data warehouse with HockeyStack. To ensure a seamless integration, we follow the process outlined below.

Prerequisites

Before we start the technical part of the integration, we need some initial information from you:

1. Contact to a person responsible for the data in your organization

2. Data sample (50 rows of complete data)

3. A column that stores a unique identifier for the row

4. Permissions (the details per provider are available in this doc)

The Process

1. Customer to provide the CSM with all the prerequisites

2. HockeyStack to validate the sample dataset

3. Customer to validate whether the sample dataset's reporting capabilities meet expectations (e.g., access to all the needed columns)

4. Customer to provide HockeyStack with the full dataset

5. HockeyStack to build the connection

6. HockeyStack to validate the full dataset

7. HockeyStack to provide a method to validate the data within the tool (i.e. build a specific report to compare numbers)

8. Customer to validate the full dataset

   1. Correctness (are the numbers matching)

   2. Completeness (are all of the records there)

   3. Freshness (is the data up to date)

9. Customer to tune the data, if there are any imperfections

Congratulations, you're all set to use your warehouse data in HockeyStack!

Requirements

Data warehouse integration requires the data set to include:

• 'company_domain' field for any company-based data (e.g., 'hockeystack.com' for HockeyStack company)

• 'email' field for user-based data (e.g. '[e-mail]' for John Smith)

• A column that stores a unique identifier for the row

• A column that stores the last update date

We will only pull the records that have values in those fields.

Data Completeness

Please ensure that identifiers are included within the original dataset. HockeyStack does not support joins to other datasets at this time.

Non-Sales-Led Revenue

If you want HockeyStack to pull revenue that is not sales-led (e.g., usage-based revenue or marketplace transactions), the data must be provided in an aggregated form. This means that instead of sending HockeyStack one row per revenue portion, you should transform the data into one row per company or person. The dataset should include the following two fields:

1. Start of the contract: Date field for when the contract starts

2. Preliminary deal value: Depending on your reporting method, this represents the value of the deal you want to report on while signing—typically a sum of amount of transactions within the first 30 or 90 days of the contract. This value is static and does not change over time.

3. Cumulative deal value: A field that you update regularly, reflecting the total revenue generated by the deal over time.

The standard requirements outlined above must also be met.