Know who came back from your outreach.
Beacon is one script tag on your site. When a prospect arrives through a link Operator sent, it ties the visit to them and to the email that brought them.
How does Beacon know which prospect visited my site?
Every link Operator puts in an email to your domain carries a signed token. Beacon is one script tag on your site. When a visitor arrives through one of those links, the script reads the token, measures the visit and reports it, and LaunchSurface ties it to the exact prospect and email that sent them. Visitors without a token are ignored, so Beacon never tries to identify anonymous traffic. It sets no cookies, keeps its session in the browser tab's sessionStorage, and does nothing when the browser sends Do Not Track. An engaged visit raises the prospect's heat and can move them to interested.
Of a visit's engagement score comes from active time on the page, at full credit after 90 seconds. Scroll depth is 20%, a click on pricing, demo or sign-up 20%, extra pages 15% and other interactions 10%.
Beacon stores nothing in cookies, and exits immediately when Do Not Track is set, checked both in the browser and at the server.
One line to install
A single script tag. No tag manager and no events to wire up.
Exact, not guessed
Matches the signed link a prospect clicked, not a company guessed from an IP address.
Measures engagement
Active time, scroll depth, pages viewed and clicks on buying steps.
Feeds Operator
An engaged visit raises the prospect's heat so the next touch is timely.
A cycle you can watch, step by step.
Every visit from outreach, attributed.
When someone you emailed lands on your site, Beacon ties the visit to that person and the exact email that sent them. Traffic that did not come from your outreach is left alone.
One line, then it just works.
The script reads the token from the link, stitches page loads in one tab into a session, and reports when the page is hidden. There is nothing else to configure.
<script async src="https://beacon.launchsurface.ai/b/ls_8f3a••••.js"></script>CopyHow engaged, not just whether.
Beacon records active time, how far they scrolled, which pages they read and whether they clicked pricing, a demo or sign-up. A bounce scores near zero; a long, deep, high-intent session scores near one.
Built to run, not to sit in a dashboard.
Exact, not estimated.
It recognizes the people you already emailed from the link they clicked, not from an IP range.
Privacy by construction.
No cookies, no anonymous identification, and Do Not Track is honored on both ends.
Closes the loop.
A real on-site action reaches Operator as heat, so attribution becomes the next touch rather than a chart.
The details, answered.
How is this different from web analytics?
Analytics counts anonymous traffic. Beacon names the specific prospect who visited and the email that sent them, because it reads the signed token on the link they clicked. It is built to close the loop on outreach, not to report pageviews.
Does it identify anonymous or cold visitors?
No. Without a token from one of your emails the script does nothing. That boundary keeps attribution exact and keeps Beacon out of the business of de-anonymizing strangers.
How do I install it?
Add one script tag to your site. It starts attributing visits from your outreach as soon as it loads.
What about privacy and consent?
Beacon sets no cookies, keeps its session in the tab's sessionStorage, only reports visits that arrived from your own outreach, and does nothing when Do Not Track is on. You are still responsible for disclosing it in your site's privacy notice.
What does Operator do with a visit?
The visit's engagement score raises the prospect's heat, which moves them up Operator's ranking. An engaged visit can move them to interested, so the next touch lands while the interest is real.