How Clinch works

What triggers the offer

On desktop, Clinch watches for the classic exit-intent signal: the cursor moving up and off the top edge of the browser, the way it does when someone reaches for the tab bar or the back button. On mobile there is no cursor, so Clinch reads a different set of signals instead: a fast upward scroll, the back gesture, or the shopper going idle on the page. Every signal is reported separately in Analytics, including how often each one is dismissed within two seconds, so you can turn off any one that misfires on your store.

No trigger can fire in the first 3 seconds a shopper is on a page. That floor exists so a quick bounce, someone who lands and leaves immediately, never counts as an exit worth interrupting.

Two more triggers are optional and off unless you turn them on: a cart-value threshold, so the offer only appears once a cart is worth recovering, and a home-page trigger for a visitor who spends a long time browsing without settling on a product.

What the offer says

The offer names whatever the shopper was actually looking at: a specific product on a product page, or a collection name on a collection page. On a cart or any other page without a specific product in view, the copy is generic. This is deliberate. A discount that names the exact item a shopper hesitated on reads as relevant; a discount that names nothing reads as a popup.

What the code applies to

Whenever a shopper was viewing a specific product or collection, the discount code Clinch mints is scoped to that product or that collection only, never the whole cart. If the shopper was on the cart page or somewhere with no product in view, the code falls back to store-wide, since there is nothing to scope it to. That scoping is the default behaviour, on from install, with no configuration required.

Each code is single-use and expires 60 minutes after it is issued by default. You can shorten that down to 15 minutes or lengthen it in Settings.

Stopping abuse

• 3 codes per IP address per day. Generous for a real shopper comparing products across a few sessions, tight enough to stop someone farming codes by reopening incognito windows.
• 500 codes per store per day. A ceiling on total exposure regardless of traffic spikes.
• One offer per browsing context, per session. Seeing the offer once on a product does not mean seeing it again on the same product, though a different product in the same session is a different context.
• Dismiss once, stay quiet. Closing the offer, by the close button, Escape, clicking outside it, or "continue shopping", stops Clinch from showing anything else for the rest of that session.
• Returning customers excluded, by default. A shopper who has already bought from the store is the one most likely to have learned to wait for a discount, so Clinch leaves them out unless you turn this off.

Related

How the margin guard changes the percent that gets offered · Choosing which products and collections Clinch runs on · A deeper look at exit-intent detection and when it backfires