Skip to content

Visitor ID Setup

Install and configure Visitor ID tracking on your website.

Before setup:

  • ✅ HubSpot connected
  • ✅ Website access (ability to add JavaScript)
  • ✅ Privacy policy updated
  • ✅ Compliance reviewed

Navigate to Visitor ID and click the Configuration button.

Exclude if Company Only: Toggle to filter visitor types

  • ON: Only create records when person is identified
  • OFF: Create company records even without person data

Pricing Display: “2 per visitor” shows cost per identified visitor

Two-panel layout for installation:

Choose tracking method:

1. Default Tracking (Simple implementation)

Recommended for most users:

  • Standard identification
  • Automatic person/company detection
  • No custom configuration needed

2. Custom Tracking (Advanced)

For advanced use cases:

  • External ID mapping
  • First-party data stitching
  • Custom user identification

Copy the script snippet:

<script async src="https://cdn.sellestial.com/cs?cid=YOUR_CUSTOMER_ID"></script>

Parameters:

  • cid — Your unique customer ID (pre-filled)
  • async — Non-blocking load
  1. Choose Tracking Method

    Select Default or Custom based on your needs

  2. Copy Script

    Click copy button to copy complete script

  3. Add to Website

    Place script before closing </body> tag:

    <!DOCTYPE html>
    <html>
    <head>
    <title>Your Site</title>
    </head>
    <body>
    <!-- Your content -->
    <script async src="https://cdn.sellestial.com/cs?cid=YOUR_CUSTOMER_ID"></script>
    </body>
    </html>
  4. Verify Implementation

    Check Network tab for requests to cdn.sellestial.com

Where to Place:

  • ✅ Before closing </body> tag
  • ✅ After main content
  • ✅ With other tracking scripts

Why:

  • Non-blocking page load
  • Doesn’t affect performance
  • Loads in parallel with other scripts

Don’t Place:

  • ❌ In <head> (blocks rendering)
  • ❌ Before critical content
  • ❌ Inline in content

async attribute:

  • Loads script asynchronously
  • Doesn’t block page rendering
  • Improves page load time

src parameter:

  • Points to Sellestial CDN
  • Globally distributed
  • High availability
  • Fast load times

For advanced implementations with first-party data:

<script>
// Set before Sellestial script loads
window.sellestial_external_id = 'your_user_id_123';
</script>
<script async src="https://cdn.sellestial.com/cs?cid=YOUR_CUSTOMER_ID"></script>

Existing User Database: Link Sellestial identifications to your user IDs:

  • Match with internal systems
  • Connect multiple sessions
  • Track user journey across devices

CRM Integration: Map to existing CRM IDs:

  • Deduplicate records
  • Prevent duplicate creation
  • Maintain data consistency

Analytics Integration: Connect with analytics platforms:

  • Google Analytics user ID
  • Segment anonymous ID
  • Custom tracking IDs
  1. Open Website

    Navigate to page with tracking script

  2. Open Developer Tools

    Press F12 or right-click → Inspect

  3. Go to Network Tab

    Filter by “sellestial” or “cdn.sellestial.com”

  4. Look for Requests

    Should see requests to Sellestial CDN

  5. Check Response

    200 OK status means working correctly

On Page Load:

Request: GET cdn.sellestial.com/cs?cid=YOUR_CUSTOMER_ID
Status: 200 OK
Type: script

On Identification:

Request: POST cdn.sellestial.com/identify
Status: 200 OK
Type: xhr/fetch

No Network Requests:

  • Script not installed correctly
  • Ad blocker interfering
  • Browser privacy settings

404 Errors:

  • Incorrect customer ID
  • Typo in script URL
  • Account not active

Script Not Loading:

  • CDN blocked
  • Network issues
  • Corporate firewall
  1. Visit Your Website

    Open site in browser

  2. Browse Multiple Pages

    View 2-3 different pages

  3. Check Dashboard

    Go to Visitor ID dashboard in Sellestial

  4. Wait 2-5 Minutes

    Identification may take a few minutes

  5. Look for Your Visit

    Should appear in Recent Visitors feed

Dashboard Shows:

  • Your visit appears
  • Location is correct
  • Pages viewed are listed
  • Timestamp is recent

HubSpot Shows:

  • New contact created (if identified)
  • Company created (if applicable)
  • Page views logged
  • Properties populated

Update your privacy policy to include:

**Visitor Identification**
We use Sellestial to identify website visitors
for marketing and sales purposes. This service
may collect:
- IP address
- Pages viewed
- Visit duration
- Browser information
- Device type
To opt out of visitor identification, email
privacy@yourcompany.com.

Provide easy opt-out:

Option 1: Email Request

  • Provide email address in privacy policy
  • Process opt-out requests promptly
  • Confirm opt-out to requester

Option 2: Cookie Banner

  • Include Sellestial in consent options
  • Respect “do not track” selections
  • Don’t load script if consent denied

Option 3: Dedicated Page

  • Create /opt-out page
  • Form to submit email/ID
  • Automatic opt-out processing

Only load for certain visitors:

<script>
// Only load for non-customers
if (!userIsCustomer) {
var script = document.createElement('script');
script.async = true;
script.src = 'https://cdn.sellestial.com/cs?cid=YOUR_CUSTOMER_ID';
document.body.appendChild(script);
}
</script>

Exclude certain pages:

<script>
// Don't track checkout or account pages
var excludedPaths = ['/checkout', '/account', '/admin'];
var currentPath = window.location.pathname;
var shouldTrack = !excludedPaths.some(path => currentPath.startsWith(path));
if (shouldTrack) {
var script = document.createElement('script');
script.async = true;
script.src = 'https://cdn.sellestial.com/cs?cid=YOUR_CUSTOMER_ID';
document.body.appendChild(script);
}
</script>

Track specific events (if supported):

<script>
window.sellestialTrack = window.sellestialTrack || [];
// Track button click
document.getElementById('cta-button').addEventListener('click', function() {
window.sellestialTrack.push({
event: 'button_click',
properties: {
button_id: 'cta-button',
page: window.location.pathname
}
});
});
</script>

Check:

  1. Script installed correctly?
  2. Enough traffic to identify?
  3. Visitors mostly US-based?
  4. Time delay for processing?
  5. Dashboard filters applied?

Remember: Only ~25% of US visitors identified

Possible causes:

  • Multiple tracking scripts
  • Script loaded multiple times
  • External ID not consistent

Solutions:

  • Check for duplicate scripts
  • Ensure single script load
  • Verify external ID logic

Common issues:

  • VPN usage by visitor
  • Corporate proxy servers
  • Mobile carrier locations

Note: Location is approximate based on IP

Concern: Site speed affected

Reality:

  • Async loading (non-blocking)
  • CDN delivery (fast)
  • Minimal payload
  • No noticeable impact

Verify:

  • Check Google PageSpeed
  • Monitor load times
  • Test with/without script