Handoff vs bounce
A bounce is an exit you cannot interpret. A handoff is a designed continuation — the visitor explicitly chooses to explore your topic in an assistant with your page as grounding.
Most analytics stacks treat the handoff as invisible noise. ContinueWith names it, measures it, and lets you improve prompts and page context where continuations concentrate.
What travels across the boundary
Typically: canonical URL, page title, optional text selection, and a prompt template label you configured.
What does not travel: conversation content after the assistant opens. ContinueWith never sees or stores what visitors ask inside ChatGPT or Claude.
Why teams instrument handoffs in 2026
AI assistants are a default research step for technical buyers, creators, and consumers. Fighting that behavior is expensive; designing for it is infrastructure.
Handoff analytics are leading indicators — which docs pages need clearer context, which assistants your audience prefers, which prompts visitors actually choose.
FAQ
Common questions
- What is an AI handoff in one sentence?
- The intentional moment a visitor leaves your website to continue in ChatGPT, Claude, or another assistant — with your URL, title, and prompt context attached.
- How is a handoff different from a bounce?
- A bounce is an unmeasured exit. A handoff is an explicit continuation choice you can design, prompt, and measure at the website boundary.
- Does ContinueWith see what users ask in ChatGPT?
- No. ContinueWith only records the transition from your site to the assistant — not the private conversation that follows.
Next step
See it on your site
ContinueWith measures AI continuations at the website boundary — which assistant, which page, which prompt — without seeing private conversations. Install takes minutes.