Exit Intent

[jameskkv]

This is a brilliant alternative. But shouldn't this behave like bounceexchange where it captures exit intent, and not enter intent? How come all the demos ive seen on your site plus all other live sites has the code executed upon entry? Kind of defeats the purpose. Looks super spammy because it fires upon entry and makes me click X.

[carlsednaoui]

@dtdw, the plugin behaves as expected. As you mentioned, if you slowly move your mouse inside the window then the event will fire. To get rid of this (or limit it), move your mouse like a regular user (at regular speed) or decrease the sensitivity.

Closing this issue for now. Please re-open if there's anything actionable.

[jescalan]

Also, if you find that you users frequently wait more than 1s after getting to a site to move their mouse into the window, you can always adjust the delay time to be higher:

https://github.com/carlsednaoui/ouibounce#set-a-min-time-before-ouibounce-fires

[jameskkv]

I used a few scenario based on a few user's movement prediction and the default firing upon entry is just really odd. Almost all other alternative also uses this technique and i don't think it's optimal for user experience.

Let's say for example, a user opens link in a new tab and waited 5s before switching, and i set the delay to 5s. But what if another user leaves the page within 3s? Another example, a user clicks on a link that opens a new window, and re-enters page upon which pop up fires.

Unless there is 2 different pop-ups, 1 upon entry and another upon exit (not feasible in every situation), I think it needs a better way to fire only when mouse leaves after it entered.

[jescalan]

That's a very good point, I hadn't thought of that. The primary use-case @dtdw is talking about here being, I assume, when a user clicks a link to open in a background tab (which I do all the time honestly), but by the time they get there the delay has run and the popup appears on entry.

I'm sure there's a way we can fix this. For example, if that event fires once on entry and once on exit, we could always just record the first fire and only actually trigger the modal on the second, etc.

[carlsednaoui]

Good point @dtdw, have you tried playing with sensitivity? If you set it to ~5 (or maybe even less) the odds of this happening will decrease tremendously.

You can also try to implement an alternative fix and submit a pull request :)

[carlsednaoui]

/note: Maybe we can make use of this. The demo is really cool.

[jameskkv]

@Jenius Yes, besides the open in background tab, the other use case is when the user is already in your site and clicked on a link which opens in new window (which automatically focuses on it). And so when he re-enters your site the pop up would fire.

@carlsednaoui honestly i am just a beginner in this field and do not know much about the code behind it, still learning in fact, so i'm afraid i couldn't do much help for now.

[carlsednaoui]

That was good feedback @dtdw, I actually opened up a new issue — #26 — to look into it :)

[carlsednaoui]

And no worries about contributing, we're all learning as we go 😃