# Configure a Data Syncs Import

The purpose of an import is to seamlessly unify your data that already exist in HockeyStack (like CRM, marketing automation etc. data that we automatically pull) with custom datapoints that exist outside of your common GTM stack.

Frequent examples of the kind of data our customers import into HockeyStack include trial subscription data, additional CRM-related datapoints, and non-digital marketing spend etc. Although the kind of data we can ingest is flexible, we need it to fit into a certain requirement set for it to be useful throughout the platform.

It is critical to first define what kind of data you want to import into HockeyStack. We currently allow four main import types: 

* **Website Actions**: web traffic data in time-series format coming separate from our web tracker
* **Custom Actions**: custom time-series data from other tools (like trials, product analytics etc.)
* **Properties**: custom object records (like subscriptions, line items etc.) along with their properties
* **Custom Spend:** specialized metadata import for ingesting offline or non-tracked campaign spend
* **Metadata**: aggregate metrics that isn't attributable to a specific person/account

{% content-ref url="/pages/OzwA1C6wf8pz8gBD9Nhj" %}
[Setting Up Your Data Import](/integrations/datasyncs/configure-a-datasync-import/setting-up-your-data-for-import.md)
{% endcontent-ref %}

After determining your import type, connect your data warehouse:

{% content-ref url="/spaces/edLASfWbQxGa0eYkwALS/pages/Rc0GacoPda50jUhbtNEG" %}
[Connecting your Warehouse](/integrations/datasyncs/connecting-your-warehouse.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hockeystack.com/integrations/datasyncs/configure-a-datasync-import.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.