What Happens Between a Website Visit and a Lead?

 

A lot. Between a visit and a lead, your site can load analytics and ad tags, set cookies, log the source and device, recognise return visits and link all of it to a contact once a form is filled. Most of this starts on page load, before the visitor makes any consent choice.

Here is how it works, stage by stage.

Stage 1: The page loads

Your tag manager reads its rules. Tags set to run on all pages start at once. Each request carries the page address, the referrer, the browser type and the visitor's IP address. Cookies may be set in the same moment.

Stage 2: The visitor browses

Analytics records page views, scroll depth, clicks, downloads and video plays. A heatmap or session recording tool may capture mouse moves and taps. None of this needs a name.

Stage 3: The visitor leaves

GA4 closes a session after 30 minutes without activity by default. Ad platforms may already have added the visit to a retargeting audience. The visitor gave no signal at any point.

Stage 4: The visitor comes back

The cookie ID is still in the browser. Your tools link the new visit to the old one. The source may be different this time. Now you see a path, such as a LinkedIn ad first and a search second.

Stage 5: The form

When the form is submitted, the CRM often matches the contact to that cookie ID. Earlier visits join the contact record. Lead scores may rise based on pages viewed. Conversion events go to ad platforms.

This is the point where anonymous data turns into data about a named person.

Which of this needs consent?

In the UK and EU, optional cookies need consent before they run. This includes analytics, marketing and tracking cookies. B2B sites are not exempt. The rule depends on what the cookie does.

Strictly necessary cookies are exempt. Login sessions and security cookies are examples. The SeersAI blog on B2B cookie consent requirements shows the full split between essential and optional cookies. It uses Google Analytics, the LinkedIn Insight Tag and Meta Pixel as examples.

How to check your own site

1. Open a private window and load your site. Do not touch the banner.
2. Open DevTools and check Application, then Cookies.
3. Check the Network tab for requests to analytics and ad domains.

Anything that appears before you choose ran without consent.

How SeersAI helps

SeersAI scans your site to find every cookie and tag. It shows visitors a banner with accept, reject and customise options. Optional scripts wait until the visitor agrees. Each choice is stored as a consent record. Your marketing stack stays in place. It just runs in the right order.

Frequently asked questions

Can a website collect data before a form is filled? Yes. Analytics, ad pixels and recording tools can all run on page load.

Do analytics cookies need consent on B2B websites? Generally yes, when they are not strictly necessary for the site to work.

Which cookies do not need consent? Strictly necessary ones, such as security cookies and session cookies that hold no personal data.