RevSure transforms anonymous website engagements into actionable, high-priority leads through robust de-anonymization capabilities. This page details how it works, supported integrations, and how you can view and manage de-anonymized visitors and accounts.

RevSure’s Approach to De-Anonymization

RevSure transforms anonymous website engagements into actionable, high-priority leads through robust de-anonymization capabilities. Here's how:

‍Integration with Leading Data Enrichment Tools: RevSure integrates with third-party data enrichment tools such as RB2B, People Data Labs, 5x5 Coop, and more to reveal the identities of anonymous visitors. These tools leverage vast datasets tracking visitor behavior across the web, cross-referencing IP addresses and other identifiers to uncover details like:
- Company information (name, industry, size).
- Individual roles and interests tied to the visitor.
‍IP Address Mapping: The de-anonymization process begins with IP-to-company mapping:
- Specialized services identify the likely organization associated with the IP address.
- Baseline firmographic data, such as company name, industry, and size, is established.
‍Data Enrichment and Quality Management: Data from enrichment sources like RB2B and People Data Labs is normalized and deduplicated to ensure quality and consistency.‍
CRM Integration and Hygiene
- Account Association: RevSure automatically associates de-anonymized visitors with existing CRM accounts using company names and email addresses.
- Write-Back Support: For new accounts or leads, RevSure offers a configurable option to write de-anonymized data back into the CRM or MAP, ensuring comprehensive tracking.
Add-On Feature: De-anonymization is available as an add-on package, providing flexibility for businesses to choose the features that align with their needs.

Viewing De-anonymized Visitors

Apply the filter Visitor RevSure De-anonymized = True in the Visitors tab under the "Lead Prioritization" module to see de-anonymized visitors. Note that some RB2B visitors might already exist in the CRM and will not be tagged as RevSure de-anonymized.

De-duplicating Visitors Between FIRST_PARTY_SDK and RB2B

De-duplication is possible when a form fill occurs via FIRST_PARTY_SDK, allowing visitors to merge based on email or name. Without a form fill, this is not feasible as RB2B does not provide IP, browser, or device-level information.

Identifying De-anonymized Visitors Still Classified as Visitors

Use the filters Visitor Lead Conversion = False and Visitor RevSure De-anonymized = True to find de-anonymized visitors who have not yet converted into leads in the CRM.

Viewing De-anonymized Visitors Converted into Leads

To identify de-anonymized visitors who have converted into leads, apply the filters Visitor Lead Conversion = True and Visitor RevSure De-anonymized = True.

Accessing All De-anonymized Accounts

In the "Account Prioritization" module, use the filter Account RevSure De-anonymized = True to view all de-anonymized accounts.

Viewing De-anonymized Accounts Without Known Contacts

Apply the filters Account RevSure De-anonymized = True and Number of Contacts = 0 in the "Account Prioritization" module to see de-anonymized accounts without known contacts.

Identifying Accounts De-anonymized but Not in CRM

Accounts tagged as Account RevSure De-anonymized = True are not present in the CRM. If data providers find an account already in the CRM, it will not be labelled as de-anonymized.

Finding New Visitor Contacts Not in CRM or MAP

Visitors tagged as Visitor RevSure De-anonymized = True are not in the CRM or MAP. Those already present in the CRM are not tagged as de-anonymized.

Mapping De-anonymized Visitors to Salesforce Accounts

RevSure maps de-anonymized visitors to CRM/MAP accounts using email domains or company names. If no match is found, a new "de-anonymized" account is created in RevSure and the visitor is linked to that account, including those without known contacts or CRM records.