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, 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)	Deanonymization: identifies the person visiting your site before they introduce themselves	On page visit or chat engagement
Bombora (Deanonymization)	Deanonymization: resolves the visitor's company and firmographics (industry, size, revenue)	On every page visit (All Site Traffic mode)
Explorium (Lead Enrichment)	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.

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.

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. 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, for example enrolling visitors from target accounts
• CRM syncing through your CRM Integrations field mappings

For a walkthrough of how fields map to your CRM objects, see Developer: Spara Objects & Fields.