> 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/report-examples-and-insights/data-model-and-tracking/how-does-hockeystack-deduplicate-accounts.md).

# How HockeyStack deduplicates accounts?

By default, HockeyStack deduplicates accounts based on the company domain.

If multiple records share the same domain, they will be automatically merged into one company.

However, if accounts don’t have a domain (or have different domains), they won’t be auto-merged. In this case, you can manually merge them in the Journey view by selecting the companies with the same name and clicking Merge Companies.

> *Note:* Merging companies is **irreversible**, so we recommend reviewing carefully before completing the merge.
>
> Merging companies works across all HockeyStack products.


---

# 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/report-examples-and-insights/data-model-and-tracking/how-does-hockeystack-deduplicate-accounts.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.