Question 1

What can an exit layer actually recover? Show the arithmetic.

Accepted Answer

Start with a typical-shaped funnel, every figure illustrative: 10,000 visitors a month converting at 3% means 300 convert and 9,700 walk out - 97 of every 100 people the media budget paid to bring in. The exit layer works that 9,700, not the 300. If it engages even 4% of them - a deliberately modest, illustrative rate - that is 388 captures or conversations a month at zero additional media cost, because the traffic was already bought and was already leaving. The honest caveats: a capture is a conversation, not a customer, and the rate depends entirely on the offer matching the page - which is why oBounce reports per page and per trigger, never as one blended number. But the structure of the arithmetic holds at any scale: the largest population on your site is the one that leaves, and an exit prompt is the only way to address it without buying another click.

Question 2

Will the popup slow our site down?

Accepted Answer

No. The embed is asynchronous and non-blocking: the page renders first, oBounce loads after, and nothing in the critical rendering path waits for it. We measure page speed before and after installation and show you both numbers. This matters more than it sounds. Page speed feeds Core Web Vitals and the landing-page experience component of Quality Score, so a heavy capture tool quietly raises what every click costs you. A capture tool should add leads, not load time.

Question 3

Will popups hurt our Google rankings?

Accepted Answer

Done carelessly, they can. Google documents that mobile pages showing intrusive interstitials on arrival from search may not rank as highly - and a full-screen overlay the moment someone lands from a result is exactly what that guidance targets. oBounce is built around the guidance: mobile formats use partial-screen prompts that leave the content accessible, exit-based triggers fire on the way out rather than on arrival, and landing pages for search campaigns get the most conservative settings. The lead is never worth the ranking.

Question 4

How does exit-intent work on mobile, where there is no cursor?

Accepted Answer

On desktop, the Exit Velocity Trigger reads cursor velocity and trajectory toward the browser chrome - the move a hand makes just before closing a tab. On mobile, it reads the behaviour patterns that precede a bounce instead: a fast scroll back toward the top, and inactivity past a threshold. The triggers are tuned separately per device, because mobile attention behaves differently - and mobile formats are deliberately smaller, both for usability and to stay inside Google interstitial guidance.

Question 5

Will it annoy our visitors?

Accepted Answer

A badly run popup will, which is why the Suppression Stack exists. Frequency capping limits how often any visitor sees a prompt, suppression mutes it once they convert, and targeting keeps offers relevant to the page - the blog reader and the visitor deep in pricing see different prompts, or none at all. There is also a self-correcting force: an annoying popup converts badly. Because every variant is measured, the data retires aggressive settings on its own. The configurations that survive testing are, almost by definition, the ones visitors tolerate.

Question 6

What offer works best - a discount, a lead magnet or a callback?

Accepted Answer

It depends on what the page promised. Research-stage pages convert best with a lead magnet - a guide, a checklist, a price list. Carts and pricing pages respond to discounts or incentives. High-consideration services - the kind bought after a conversation - do best with a callback offer and a two-field form. We start from that mapping, then let A/B tests settle it per page. The honest answer is that nobody knows your best offer in advance; the product is built so you find out quickly.

Question 7

Why only name and phone on the form?

Accepted Answer

Because every field costs completions, and an exit popup asks at the lowest-commitment moment there is. Name and phone is enough to start a conversation, and everything else - budget, timeline, requirement - is better asked by a human on the call. Where a sales process genuinely needs another field we will add it, but it has to earn its place against the completion rate it costs. The default is two fields, and the burden of proof is on the third.

Question 8

How does oBounce work with live chat?

Accepted Answer

They hand off to each other. A leaving visitor who is not ready to fill a form can be offered a conversation instead - the prompt opens chat with a trained agent rather than a field set, which suits buyers with one blocking question. Run together, the two cover both temperaments: the visitor who will type a number into a form, and the one who wants to ask something first. Captures and chat transcripts land in the same CRM view, tagged by page and trigger.

Question 9

How do we know whether it is working?

Accepted Answer

The core read is capture rate - captures as a share of triggered impressions - reported per page, per trigger and per offer, never as one blended number that hides the losers. A/B results ship with the variable that was tested and what gets promoted. Captures are tagged by source page and trigger into your CRM, so you can follow them through to qualified and won, not just count form fills. If the leads do not progress, the offer changes - volume that goes nowhere is not a result.