Bombora (Deanonymization)
Resolve anonymous website visitors to their company with Bombora's firmographic data.
Bombora is an alternative Deanonymization provider to Vector (Deanonymization). Where Vector attempts to identify the specific person visiting your site, Bombora resolves the visitor's company and describes it with firmographic labels: industry, company size, and revenue, plus the visitor's professional group and seniority band.
Each account uses one deanonymization provider, chosen with your Spara point of contact. Bombora is a good fit when your team acts on account-level signals (which companies are visiting) rather than individual identities.
Enabling Bombora
Your current provider and trigger mode are visible under Settings > Signals in the Spara platform. The settings are managed by Spara: your Spara point of contact enables Bombora for your account.
Fields captured
When Bombora resolves a visitor's company, Spara writes the match to dedicated deanonymization fields on the lead record:
Deanonymized Company name
Matched company
Deanonymized Company domain
Matched company's website domain
Deanonymized Industry
Company's industry (e.g., Finance, Software)
Deanonymized Company size
Employee-count band (e.g., "XXLarge (10,000+ Employees)")
Deanonymized Revenue
Annual revenue band (e.g., "XXLarge ($1B+)")
Deanonymized Professional group
Visitor's professional function (e.g., "Finance Professional")
Deanonymized Seniority
Visitor's seniority band (e.g., "C-suite")
These labels come from Bombora's fixed taxonomy, which is the same vocabulary Spara's condition builders offer as dropdown options. That means Bombora-resolved fields plug directly into workflow conditions and preview targeting without any value mapping on your side.
All fields follow the structure described in Data Model.
Bombora resolves companies, not people. It does not return the visitor's name, email, or LinkedIn profile. Professional group and seniority describe the visitor in aggregate terms, not their identity. If person-level identification matters more to your team, discuss Vector (Deanonymization) with your Spara point of contact.
Match rates
Bombora identifies at the company level, which resolves at a higher rate than person-level identification: corporate networks and IPs frequently map to a company even when the individual can't be identified. Actual rates depend on your visitor mix; traffic from home networks, mobile carriers, and VPNs is less likely to resolve. Your Spara point of contact can share expected coverage for your audience.
Using the data
Workflow enrollment: reference Bombora fields in Workflows conditions, for example "Deanonymized Company size is XXLarge (10,000+ Employees)", to act on visits from your target segment.
CRM syncing: map deanonymized fields to CRM properties in your CRM Integrations settings.
Lead review: deanonymized visitors appear on the Leads page, where the Identification filter separates them from self-identified leads.
FAQ
How is Bombora different from Vector?
Vector attempts person-level identity resolution: names, emails, LinkedIn profiles. Bombora resolves the visitor's company and describes it with firmographic bands. Vector answers "who is this?"; Bombora answers "what kind of company is visiting, and what kind of role is this person in?"
Can I use both Bombora and Vector?
Each account runs one deanonymization provider at a time. Your Spara point of contact can help you choose the right one for your use case.
Do I need to change my website?
No code changes are needed beyond the standard Spara snippet, which loads Bombora's tag for enabled accounts. As with any third-party data partner, confirm your Privacy Policy and Consent Management Platform (CMP) disclosures with your Spara point of contact.
Last updated