> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/integrations/signals.md).

# Signals Integrations

Third-party data providers that identify and enrich the leads engaging with your Spara agents.

Signals integrations connect Spara to third-party data providers that resolve who is visiting your site and fill in what you know about them. The data flows directly into your [Leads](/pipeline/leads.md), where it powers agent personalization, workflow conditions, and CRM syncing.

Spara currently supports three Signals providers:

| Provider                                                          | What it does                                                                                | When it runs                                |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------- |
| [Vector (Deanonymization)](/integrations/signals/vector.md)       | Deanonymization: identifies the person visiting your site before they introduce themselves  | On page visit or chat engagement            |
| [Bombora (Deanonymization)](/integrations/signals/bombora.md)     | Deanonymization: resolves the visitor's company and firmographics (industry, size, revenue) | On every page visit (All Site Traffic mode) |
| [Explorium (Lead Enrichment)](/integrations/signals/explorium.md) | Lead enrichment: adds contact and company data to leads with a known work email             | When a lead's work email is captured        |

Vector and Bombora are alternative deanonymization providers; each account runs one, chosen with your Spara point of contact. Vector aims at person-level identity, Bombora at company-level firmographics.

{% hint style="info" %}
You can view your Signals configuration — and what each provider has returned for your Leads — under **Settings > Signals** in the Spara platform. Signals are managed by Spara: contact your CSM to enable a provider or change your configuration. Once enabled, the data flows automatically with no configuration required on your side.
{% endhint %}

## How the two providers work together

Deanonymization and enrichment are complementary stages of the same funnel:

1. **Vector** or **Bombora** makes the first guess at who an anonymous visitor is, using IP and identity-resolution signals. No email required.
2. **Explorium** fills in the full picture once a lead's work email is known, layering on verified contact and company data.

A single lead can benefit from both stages: deanonymization identifies them on their first visit, and Explorium enriches them the moment they share their email.

## Where the data lands

All Signals data is written to fields on the lead record, following the structure described in [Data Model](/build/data-model.md). That means it can be used anywhere lead fields are used:

* **Agent context** so agents can reference the lead's company, role, and background in conversation
* **Workflow conditions** in [Workflows](/build/workflows.md), for example enrolling visitors from target accounts
* **CRM syncing** through your [CRM Integrations](/integrations/crm-integrations.md) field mappings

For a walkthrough of how fields map to your CRM objects, see [Developer: Spara Objects & Fields](https://docs.spara.com/developers/data-model).


---

# 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.spara.com/integrations/signals.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.