# Vector

#### Overview

Some HockeyStack customers want **enhanced fingerprinting and enrichment capabilities** that can identify site visitors even when they’re browsing with **VPNs, privacy mode, or cookie restrictions.**

The **Vector.co integration** helps extend HockeyStack by providing **real-time contact and intent data** from Vector’s network. This includes visitor information, custom intent topics, and signals that can be used inside HockeyStack to trigger workflows, enhance segmentation, and improve attribution models.

#### What is Vector.co?

**Vector.co** is a **contact-based, real-time B2B intent and advertising platform** that:

* Surfaces **custom intent topics** and behavioral signals
* Builds **hyper-targeted ad audiences**
* Enriches contact data across web, CRM, and advertising destinations

Customers add Vector’s pixel to their website, where Vector captures and enriches visitor information. It then consolidates these enriched contacts into a **segment funnel**, ready to be sent to destinations such as CRMs, ad platforms, Slack, or HockeyStack.

#### How the HockeyStack + Vector Integration Works

You can integrate using Vector’s **webhook** feature.

**How to set it up**

1. In Vector, open the **left sidebar** and go to **Integrations → Webhook Settings**.
2. Add a new webhook endpoint:\
   `https://app.hockeystack.com/api/integrations/vector/webhook`
3. In the **Events** section, enable the events you want to the send to your HockeyStack instance
4. Open the **Advanced** tab and add the following header:
   * `x-api-key: {{apiKey}}`\
     \&#xNAN;*(You can find your API key in the HockeyStack Settings page)*
5. Save the configuration.

Next, go to **Segments** in the left sidebar, edit the segment you want, and add a new **Webhook action** pointing to this endpoint.

Once configured, Vector will send detected intent events directly to HockeyStack, where they’ll appear as custom actions that you can use across your analytics, filters, and automations.

#### What You Can Do with Vector Data in HockeyStack

Once ingested, Vector data becomes part of the HockeyStack event model - meaning it can be used anywhere that standard actions can.

**Use cases include:**

* **Segmentation and filtering:** e.g., “Companies who have `vector data received` in the last 7 days.”
* **Workflow triggers:** e.g., “When Vector sends new contact data → alert in Slack or enrich CRM record.”
* **Journey analysis:** Combine Vector’s contact data with HockeyStack’s behavioral events for deeper journey insights.
* **Attribution:** Use Vector’s intent data as a top-of-funnel signal within Journey Score.

#### Custom Intent Topics

Yes - **custom intent topics** can be imported from Vector. These appear as metadata on the `vector data received` action, enabling filtering and scoring based on Vector’s inferred topics or interests.  You can then create filters or reports around these topics for tighter segmentation or prioritization.

#### Setup, Timing, and Cost

* **Setup time:** Minimal - configuring the webhook in Vector and validating receipt in HockeyStack typically takes minutes.
* **Odin compatibility:** Odin reads and queries Vector data the same way it reads Salesforce or native event data - no limitations.
* **Cost impact:** There’s **no additional charge** for ingesting Vector data; it counts as standard event activity.
* **Volume guidance:** For Account Intelligence customers with \~100–150K MTU, the **base package** should comfortably handle expected Vector event volume.

The Vector.co integration enhances HockeyStack and Odin capabilities by bringing in **real-time, contact-level, and intent-rich data** directly from Vector’s enrichment engine.

| Capability           | Supported      | Description                                                                  |
| -------------------- | -------------- | ---------------------------------------------------------------------------- |
| Enrichment           | ✅ (via Vector) | Vector identifies and enriches visitor data before sending it to HockeyStack |
| Custom intent topics | ✅              | Import from Vector and use for segmentation or scoring                       |
| Workflow triggers    | ✅              | “Vector data received” can launch automations                                |
| Integration setup    | ⚡ Quick        | Webhook connection, no custom development needed                             |

**Next Steps:**

1. Add your **Vector pixel** to your website.
2. In Vector, create a **workflow** that sends enriched contact data to HockeyStack’s webhook destination.
3. Confirm that “vector data received” appears in HockeyStack timelines.
4. Build **filters, workflows, or reports** using Vector data as triggers or parameters.

**Note:** HockeyStack does **not** perform de-anonymization down to the individual person.  Any identified contact data visible in your workspace originates from [Vector.co](http://vector.co/) (if enabled), other third-party enrichment sources configured by you, or volunteered by the visitor.  Anonymous visitors tracked by HockeyStack remain anonymous **until they take an identifying action, such as a form fill - at which point all prior anonymous touches are automatically linked to their identified profile.**


---

# 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/other/vector.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.