For B2B marketers, identifying anonymous website visitors and integrating their insights into robust data systems can be the key to uncovering hidden opportunities and optimizing attribution models. RevSure platform can help de-anonymize visitors to the company website. RevSure works with various data vendors to achieve this capability. It integrates these solutions to turn unknown visitors into leads, uncover early interactions, improve attribution, and enhance account intelligence, giving B2B marketers a clear view of the entire buyer journey and filling the gaps left by the traditional attribution models.
Below are some of the commonly asked questions about visitor de-anonymization:
Data & Accesibility:
What is Visitor De-anonymization?
Visitor De-anonymization is the process of identifying the visitors to your website at Personal level (name, email, company, etc.) in real time so that your GTM team knows who is visiting your website and act on the information.
How does RevSure support de-anonymization?
RevSure partners with data providers like RB2B and 5x5Coop to provide visitor de-anonymization service.
How does visitor de-anonymization technology work?
Our data partners look for cookies and other signals from their partner networks available in the visitor’s browser session to identify visitors.
What happens when a de-anonymized visitor is already a Lead in CRM?
In this case, RevSure creates a Page Visit activity for that Lead in RevSure and associates the activity to the existing Lead.
What happens when a de-anonymized Visitor belongs to an Account that exists in CRM?
RevSure automatically creates a Lead record in RevSure platform and links it to the existing Account in CRM.
The Page Visit activity will show up in the Timeline Journey of the Account.
What happens when the de-anonymized Visitor (person and company) data does not exist in CRM?
RevSure creates a Lead record and an Account record in RevSure platform along with the Page Visit activity record.
How can I see the de-anonymized visitors?
Apply a filter for Visitor RevSure De-anonymized = True in the Visitors tab under the “Lead Prioritization” module. Not all RB2B visitors are RevSure De-anonymized because some of them might already be in their CRM.
Can I de-duplicate visitors between FIRST_PARTY_SDK and RB2B?
This is possible when a form fill happens through FIRST_PARTY_SDK which helps us merge the visitors based on email/name. Until then, this is not possible because we do not get IP/Browser/Device level information from RB2B.
How can I see the de-anonymized visitors who are still visitors?
By applying the filters Visitor Lead Conversion = False and Visitor RevSure De-anonymized = True, we can identify de-anonymized visitors that have still not converted to a Lead in the customer’s CRM.
How can I see de-anonymized visitors that have converted into leads?
By applying the filter Visitor Lead Conversion = True and Visitor RevSure De-anonymized = True, we can identify de-anonymized visitors that have converted to a Lead in the customer’s CRM.
How can I see all the accounts that RevSure de-anonymized?
In the ‘Account Prioritization’ module, apply the filter Account RevSure De-anonymised = True.
How can I see de-anonymized accounts that are still visitors and have no known contacts?
In the ‘Account Prioritization’ module, apply the filters Account RevSure De-anonymised = True and Number of Contacts = 0.
How can I see accounts that have been de-anonymized and that are not in my CRM?
By definition, Account RevSure De-anonymized = True means that the account is not in the CRM. If an account that we identify through our data providers is found to be already in the CRM, we do not tag it as a RevSure de-anonymized account.
How can I see new visitor contacts that were identified from de-anonymization but are neither in my CRM or MAP?
By definition, Visitor RevSure De-anonymized = True means that the person is not in the CRM or MAP. If a visitor that we identify through our data providers is found to be already in the CRM, we do not tag it as a RevSure de-anonymized visitor.
How can I see new leads that were identified via de-anonymization but are not in my CRM or MAP?
Refer to the question “How can I see the de-anonymized visitors who are still visitors?”
What does it mean if a de-anonymized visitor is tagged to an SFDC Account?
For de-anonymized visitors from RB2B, we first try to map them to a CRM/MAP account based on the Person’s email domain or the Company name. If a match is found, we map the visitor to the CRM/MAP account; otherwise, we create a new “de-anonymized” account entry in RevSure and map the visitor to that account.
Security & Compliance:
Do the scripts track visitors without consent?
No, the scripts will be installed by the customer and tied to the Cookie-consent manager on the website. So, the scripts won’t fire until the visitor has accepted tracking cookies.
Are the scripts secure?
The scripts are securely served over HTTPS from a dedicated [Amazon] CloudFront CDN (Content Delivery Network). This ensures fast, reliable delivery with built-in protections like TLS encryption, DDoS mitigation, and global edge caching for enhanced security and performance.
What is the recommended privacy policy message that should be displayed on the website when installing the de-anonymization scripts?
When you visit or log in to our website, cookies and similar technologies may be used by our online data partners or vendors to associate these activities with other personal information they or others have about you, including by association with your email. We (or service providers on our behalf) may then send communications and marketing to these emails. You may opt out of receiving this advertising by visiting https://app.retention.com/optout and https://5x5data.com/opt-out-preferences.