Got questions? This way.
FAQs, quick fixes, and official info on every feature.
Can't find your question here, try our support forums.
Accounts:
Questions and answers related specifically to your account.
Currently, VisitorIntel doesn't support changing the email address linked to your account. To use a new email address, you'll need to add it as a new user to your company account.
At VisitorIntel, each account must be associated with a unique email address, which serves as the primary identifier for the account. Currently, our system does not support the functionality for a single email address to manage or switch between multiple accounts. This means if you require separate accounts for different purposes, you will need to use a different email address for each account you create. This approach ensures secure and distinct access to each account.
If you want to use VisitorIntel on another website you'll need to set up a second account as we only allow one active domain per account.
At VisitorIntel, each account must be associated with a unique email address, which serves as the primary identifier for the account. Currently, our system does not support the functionality for a single email address to manage or switch between multiple accounts. This means if you require separate accounts for different purposes, you will need to use a different email address for each account you create. This approach ensures secure and distinct access to each account.
Recoding profiles from additional domains can be accomplished by setting up an additional account specifically for that domain. The process is straightforward and cost-free. The only requirement is that each account must be associated with a distinct email address, which serves as your unique login credential. This ensures that each domain is managed individually, providing clear and organized tracking.
If you and your colleague have each created separate accounts for your business and are looking to merge them, we're here to assist. Currently, we don't offer an automated process for merging accounts directly through our platform. However, our support team is readily available to facilitate this process for you.
To initiate the account merger, please send an email to our support team at [email protected]. In your email, kindly include the following information:
The business name associated with each account.
The email addresses used to create both accounts (yours and your colleague's).
Your preference for which account you wish to retain. Typically, this would be the account with the active script that is currently collecting data.
Our team will guide you through the steps required to merge the accounts efficiently. We aim to make this process as smooth as possible for you.
Data Collection and Accuracy Insights:
Explore the intricacies of our data collection processes and gain insights into the precision and reliability of the data we provide.
We're excited to share how VisitorIntel works to bring clarity and value to your experience with us. Our technology is designed with a unique capability to recognize anonymous web traffic by aligning it with profiles from our extensive partner network. This process enables us to identify users and provide you with insightful data directly relevant to your interests.
In cases where a user's device has not been previously cookied by our publisher network, the capability of VisitorIntel to accurately identify the user is significantly reduced. This limitation stems from the lack of essential tracking data that cookies typically provide. Without these cookies, VisitorIntel does not have sufficient information to confidently ascertain the user's identity. As a result, our system is designed not to collect or record data from such devices.
This approach aligns with our commitment to data accuracy and user privacy. By ensuring that we only collect data when we have reliable identification, we maintain the integrity of our data collection process. It's important to understand that this cookie-based identification is a fundamental part of how VisitorIntel operates. It allows us to provide precise and valuable data to our clients while respecting the privacy boundaries of users. Therefore, the effectiveness of VisitorIntel in gathering and recording user data is closely tied to the presence of our network's cookies on the user's device.
VisitorIntel is designed to identify contacts exclusively within the United States. We use geofencing technology in conjunction with the user's browser to enable this feature. Our services become active only after confirming that the user's IP address originates from the United States. This ensures our operations are strictly limited to the U.S. region.
As of January 2024, preliminary data indicates that VisitorIntel achieves a 90% accuracy rate. With each new iteration of VisitorIntel, we are committed to refining and improving this accuracy.
VisitorIntel possesses the capability to discern and categorize approximately 20-30% of your traffic originating from the United States, achieving this at a detailed contact level resolution. This means that for around a quarter of the visitors coming to your website from the U.S., R!B2B can successfully identify and provide specific contact information. This feature is particularly useful for businesses aiming to understand and engage with their audience more effectively. By utilizing this capability, you gain valuable insights into a significant segment of your user base, enabling targeted communication and more personalized user experiences. Our system continuously strives to optimize and enhance the accuracy of this identification process, aiming to expand the percentage of traffic that can be resolved with such detail.
The nature of this question suggests a misconception that our person-level identification is based on a user's IP address. It's important to clarify that we do not use IP addresses for visitor identification. Especially in a corporate environment where VPNs (Virtual Private Networks) or company WiFi are used, relying on IP addresses for individual identification becomes nearly impossible. This is because VPNs and company networks typically mask or share IP addresses among multiple users, making it challenging to distinguish individuals based solely on this data. Our approach to user identification focuses on different methodologies that are more reliable, ensuring accurate data collection.
Our cookies are classified as first-party cookies by major web browsers, including Google Chrome. This categorization is significant as it places them outside the scope of the stringent tracking prevention measures that these browsers are planning to implement. First-party cookies are set directly by our website, as opposed to third-party cookies which are created by domains other than the one the user is visiting. This distinction is crucial in the context of evolving web privacy standards and browser policies.
Due to their first-party status, our cookies are designed to offer a more seamless and integrated user experience on our website. They play a key role in personalizing and optimizing the user experience, by remembering user preferences, settings, and login information. Furthermore, as browsers like Chrome move towards more aggressive tracking prevention strategies, primarily targeting third-party cookies, our first-party cookies ensure continued functionality and user experience enhancement without falling afoul of these new measures.
It's important to note that while our cookies are not the focus of the upcoming tracking prevention initiatives, we remain committed to user privacy and data protection. We adhere to all relevant regulations and best practices in data handling, ensuring that our users' privacy is respected and their data is securely managed.
Viewing email addresses, whether through our dashboard or via Slack notifications, is a feature exclusive to our paid service tiers. If email addresses are not currently visible to you and this is a feature you're interested in, please consider upgrading to VisitorIntel Pro to access this capability.
Coincidence, really.
The other person was undoubtedly on your website at the same time as you and their profile was collected and transmitted to you.
VisitorIntel possesses the capability to discern and categorize approximately 20-30% of your traffic originating from the United States, achieving this at a detailed contact level resolution. This means that for around a quarter of the visitors coming to your website from the Global, VisitorIntel can successfully identify and provide specific contact information. This feature is particularly useful for businesses aiming to understand and engage with their audience more effectively. By utilizing this capability, you gain valuable insights into a significant segment of your user base, enabling targeted communication and more personalized user experiences. Our system continuously strives to optimize and enhance the accuracy of this identification process, aiming to expand the percentage of traffic that can be resolved with such detail.
Script Installation:
Your go-to guide for seamless installation, setup tips, and troubleshooting our script to ensure optimal functionality on your website.
Using Google Tag Manager, you can add URL restrictions that will prevent Google Tag Manager, and therefore our tracking script from running on specified URLs.
Access your GTM account
Open your GTM dashboard.
Create or Edit a Trigger
If you're creating a new trigger, click 'New'. To modify an existing one, select it from the list.
If your desire is for our tracking script to run on multiple pages,
Configure Trigger Type
Choose the trigger type that suits your needs, typically a Page View trigger for URL-based restrictions.
Set Trigger Conditions
In the trigger configuration, go to 'Some Page Views' and set up conditions that define the URLs where GTM should run. For example, you can specify 'Page URL equals [your desired URL]' or use regular expressions for more complex URL patterns.
Attach the Trigger to Tags
Link this trigger to the tags you want to be limited by these URL conditions.
Preview and Publish
Use the Preview mode to test the setup and ensure it works as expected on the specified URLs. Once confirmed, publish the changes.
This approach lets GTM fire tags only on the pages you specify, providing greater control over your tracking and data collection.
Our tracking script is designed with a built-in security feature that strictly limits its functionality to the domains that have been explicitly authorized in your account settings. This means that the script will only activate and track user interactions on the websites that you have specified. Here's how it works:
Domain Verification
When the tracking script is loaded on a webpage, it first verifies the domain against a list of approved domains associated with your account.
Activation Criteria
If the current domain matches one of the authorized domains, the script activates and functions normally, tracking user interactions and gathering data as configured.
Security Check
This security measure prevents unauthorized use of the tracking script on domains outside of your control, enhancing the integrity and reliability of your data.
Configuration
To add or modify the list of authorized domains, you can easily update your account settings through our user dashboard.
At present, our tracking script is designed to support a single active Top-Level Domain (TLD) per account for enhanced security and optimized performance. However, by registering a naked domain, all associated subdomains are automatically included, ensuring comprehensive coverage within your primary domain. While we understand the desire for multiple domain tracking, this limitation is in place to maintain the highest standards of security and efficiency in our service.
No.
VisiorIntel's script is designed to load asynchronously, ensuring it has minimal to no impact on your website's load times and overall performance. This approach allows the script to operate in the background without interfering with the user's experience or the site's functionality.
The built-in script verification tool serves primarily as a convenience to assist with the installation process. Importantly, the script will automatically verify itself the moment it transmits the first byte of data, making manual verification a helpful but not mandatory step.