> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/advanced-data-connections/account-list-import.md).

# Account List Import

### **New Activations of this feature will be Disabled as of December 25, 2025.**  <a href="#block-0e3d8efb0ddc4c15b7b25127f60a100d" id="block-0e3d8efb0ddc4c15b7b25127f60a100d"></a>

HockeyStack allows you to import a CSV of companies into the system to use in your reporting. To import an account list, navigate to [Settings > Reporting & Tracking](https://hockeystack.com/dashboard/settings?tab=1).

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2Fma8deKvoNNThDsHJfDjs%2Fimage.png?alt=media&amp;token=ece9f35a-9a42-457e-a54b-ba44a52c0e1f" alt=""><figcaption></figcaption></figure>

Requirements for the uploaded CSV:

* Can have a maximum of 100k rows
* The first row should include headers. The headers to include are:
  * company\_domain
    * Example: hockeystack.com. No https or any additional characters.
  * date
    * This field is optional.
    * Formatted as YYYY-MM-DD
* There should be no empty rows in the data, or no invalid pieces of data

When the list is imported, HockeyStack will create an action in each company’s journey with the below structure:

* **Action Name:** Account List Uploaded
* **Date:** Either the supplied date column in the account’s row in the CSV, or the date of the upload if there is no date supplied.
* **Action Properties:**
  * **hockeystack\_\_account\_list\_name\_\_custom:** *\<Account List Name>*
* **Company Properties:**
  * **hockeystack\_\_account\_list\_\_*****\<Account List Name>*****:** true

Then, you can either use the company property in your filters like below:

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2Fu1Qv1TWjd7F2Dw9Ir4Z2%2Fimage.png?alt=media&amp;token=6f5a4273-0e15-4e37-b2fe-9821b75671a3" alt=""><figcaption></figcaption></figure>

Or, you can create a goal with it:

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2Fo2L6XcY7mDWDK51TFkQx%2Fimage.png?alt=media&amp;token=fc734c1f-4a7d-4b84-85e1-68ef1757367c" alt=""><figcaption></figcaption></figure>

You can also create a defined property with it to use as a dashboard filter:<br>

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2FGaO13gpu8Cn9RpXxeEQF%2Fimage.png?alt=media&amp;token=adf22692-6a12-4b9e-855c-8cfc0d139ba3" alt=""><figcaption></figcaption></figure>

## Use Cases <a href="#block-64eb60d82d064ed5b5a0f5d16542b5b9" id="block-64eb60d82d064ed5b5a0f5d16542b5b9"></a>

* ABM Lists
* Tracking actions that are not date-stamped in CRM (E.g. event attendance in HubSpot)
* Tracking actions that don’t exist in a connected system (E.g. PLG Signups)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.hockeystack.com/marketing-intelligence/advanced-data-connections/account-list-import.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
