Skip to main content

Docs / Setup

Consent mode and privacy

Hold all tracking until your cookie banner grants consent, honor Global Privacy Control, and understand what VisiLead never stores.

Reflects product behavior as of August 2026.

By default the VisiLead tracker starts on page load. If your cookie banner needs to gate analytics, switch the snippet to consent mode: nothing is stored and no events are sent until your banner calls visilead.consent(). In manual mode the visitor id is only created after consent.

Privacy protection goes beyond the consent switch. Browsers that send the Global Privacy Control signal are not tracked in either mode. Junk filtering protects both privacy and lead quality: government (.gov and .mil), education (.edu), residential ISP and consumer webmail domains are never turned into lead records, and person-level identification runs on US traffic only.

VisiLead also keeps its data footprint narrow. Screen size, language, timezone, utm_term and utm_content are not retained server-side.

Before you start

  • The tracking script installed (see the tracking script guide)
  • A cookie banner or consent tool that can run JavaScript when the visitor accepts or declines
  1. 1

    Switch the snippet to consent mode

    Add data-consent="manual" to your existing script tag. From this point the tracker stores nothing and sends no events until consent is granted, and no visitor id is created before consent.

    <script src="https://visilead.co/tracker.js" data-id="YOUR_TRACKING_ID" data-consent="manual" defer></script>
  2. 2

    Grant consent from your cookie banner

    When the visitor accepts, call visilead.consent(). Tracking starts from that moment.

    <script>
  // From your cookie banner, once the visitor accepts:
  visilead.consent();
</script>
  3. 3

    Handle refusal

    When the visitor declines, call visilead.revokeConsent(). It stores the refusal and deletes the visitor id.

    visilead.revokeConsent();
  4. 4

    Check consent state when you need it

    Call visilead.hasConsent() to read the current state. It returns a boolean, which is useful for keeping your banner UI in sync.

    visilead.hasConsent(); // returns true or false
  5. 5

    Test the flow

    Load your site in a fresh browser profile. Before accepting the banner, confirm in your browser's network tab that no VisiLead events are sent. Accept the banner, then confirm events start flowing into the dashboard.

Global Privacy Control

A browser sending the GPC signal is not tracked, in both default and manual mode. The one exception: an explicit visilead.consent() grant overrides GPC. This override is documented behavior.

What VisiLead does not store

Screen size, language, timezone, utm_term and utm_content are not retained server-side.

Junk filtering protects privacy and lead quality

Government (.gov and .mil), education (.edu), residential ISP and consumer webmail domains are never turned into lead records. Person-level identification runs on US traffic only.

Frequently asked questions

What are best practices to respect privacy while tracking pricing page visitors?+

Run the tracker in consent mode so nothing is stored before your banner grants consent, rely on the built-in Global Privacy Control handling, and let the junk filter keep government, education, residential ISP and webmail visitors out of your lead records. VisiLead identifies companies rather than profiling consumers, and person-level identification runs on US traffic only.

How do I track website visitors without violating privacy and consent rules?+

Add data-consent="manual" to the VisiLead snippet so all storage and events wait for your cookie banner to call visilead.consent(). On top of that, browsers sending the Global Privacy Control signal are not tracked in either mode, and government, education, residential ISP and consumer webmail domains are never turned into lead records.

Does VisiLead honor Global Privacy Control?+

Yes. A browser sending the GPC signal is not tracked, in both default and manual consent mode. The only exception is an explicit visilead.consent() grant, which overrides GPC; this override is documented behavior.

What happens when a visitor declines my cookie banner?+

Call visilead.revokeConsent() from your banner's decline handler. VisiLead stores the refusal and deletes the visitor id, and no events are sent.

Does VisiLead create a visitor id before consent?+

Not in manual mode. With data-consent="manual" on the snippet, the visitor id is only created after your banner calls visilead.consent(). In default mode, tracking starts on page load.

What visitor data does VisiLead never store?+

Screen size, language, timezone, utm_term and utm_content are not retained server-side. Government, education, residential ISP and consumer webmail domains are never turned into lead records, and person-level identification runs on US traffic only.

Related

Two minutes from script to first identified company

Install the tracking script, connect your CRM, and see which channels drive revenue. Free plan, no credit card.

Start freeView pricing