IP-Based Identification

Website deanonymization (also called visitor identification or IP-to-company matching) allows you to identify which companies are visiting your pages, even if they don't fill out a form.

These tools work by matching visitor IP addresses to company databases, giving your sales team insight into which accounts are showing buying intent.

Common use cases:

• •Identify high-value accounts browsing your pricing page
• •Trigger sales outreach when target accounts visit your site
• •Enrich your CRM with website visit data
• •Build account-based marketing audiences

Deanonymization tools typically follow this pattern:

1. 1.A JavaScript snippet loads on your page
2. 2.The script captures the visitor's IP address and page data
3. 3.The provider matches the IP to their company database
4. 4.Company information is sent to your dashboard or CRM

What you can identify:

• •Company name and domain
• •Industry and company size
• •Pages visited and time on site
• •Geographic location

What you cannot identify:

• •Individual names or emails (unless they fill out a form)
• •Personal browsing from home IP addresses
• •Visitors using VPNs or mobile networks

To add a visitor identification tool to your Flint site:

1. 1.Click the Settings button in the top left of the editor
2. 2.Click the Site Settings tab
3. 3.Click the Custom Code accordion
4. 4.Paste your provider's script into the Head Scripts field
5. 5.Save your changes

The script will automatically load on all your published pages.

Important: Replace any placeholder API keys in the example below with your actual credentials from your provider's dashboard.

The video below demonstrates setting up an RB2B implementation using the custom code configuration:

Most deanonymization providers use a similar script pattern. Here's a generic template you can adapt:

(function() {
  if (window.yourProvider) return;
  window.yourProvider = { loaded: true };
  var script = document.createElement('script');
  script.async = true;
  script.src = 'https://your-provider-cdn.com/tracker.js?key=YOUR_API_KEY';
  document.head.appendChild(script);
})();

Key elements:

• •Loading guard (if (window.yourProvider) return) prevents the script from loading twice on single-page navigation
• •Async loading ensures the script doesn't block page rendering
• •API key identifies your account with the provider

Here are some popular B2B visitor identification tools that work with Flint:

Each provider has their own dashboard where you can view identified companies, set up alerts, and configure CRM integrations.

To confirm your deanonymization script is working:

1. 1.Publish a page with your script configured
2. 2.Visit the published page from a corporate network (not home Wi-Fi)
3. 3.Open your browser's Developer Tools (F12) and check the Network tab
4. 4.Look for requests to your provider's domain
5. 5.Check your provider's dashboard for the visit

Troubleshooting tips:

• •If no requests appear, verify the script is in your Head Scripts field
• •If visits don't show in your dashboard, ensure your API key is correct
• •Home IP addresses typically won't match to companies
• •VPNs and mobile networks usually can't be identified

When implementing visitor identification:

• •Update your privacy policy to disclose the use of IP-based identification
• •Consider cookie consent requirements in your jurisdiction (GDPR, CCPA)
• •B2B identification is generally lower risk than personal data collection since it identifies companies, not individuals
• •Check your provider's compliance certifications and data handling practices

Most deanonymization tools only identify business IP addresses and cannot identify individuals without explicit form submissions.

Most visitor identification tools integrate with popular CRMs and marketing platforms:

• •Salesforce - Sync identified accounts and create leads
• •HubSpot - Enrich contacts and trigger workflows
• •Slack - Get real-time alerts when target accounts visit
• •Outreach/Salesloft - Trigger sales sequences automatically

Configure these integrations in your provider's dashboard, not in Flint. The script you add to Flint only handles data collection; routing and actions happen in the provider's platform.