- Joined
- Oct 15, 2019
- Messages
- 1,596
I think just about everyone knows about the back button script. It’s an affiliate landing page staple – and if you’re still learning then you’ll find a great resource from @Nick here:
afflift.com
We use it because when a visitor comes to a landing page they’re likely to give it one quick look and decide, “Yeah nah, not today buddy” and reach for their back button... at which point we’re like, “Yeah nah, not today buddy”... and redirect them to another offer.
It’s a bit dodgy, but muhaha!
Your standard back button hack looks like this:
I love it!
With a few lines of code I can control someone’s forward (with a click) or backward (with the back button script) destination.
But what about when they go forward then back – that is, they click through to my offer and then come back to my landing page? Do people do that? And do they then click their back button again and trigger my back button script?
Well, I was kinda curious about that so I started playing around with the Performance API, which includes a navigation object that stores various types of entries, including:
The Back Button Script (Affiliate Guide)
Are you using a back button script on your affiliate marketing campaigns? Back button is a great way to squeeze more revenue out of each click!

We use it because when a visitor comes to a landing page they’re likely to give it one quick look and decide, “Yeah nah, not today buddy” and reach for their back button... at which point we’re like, “Yeah nah, not today buddy”... and redirect them to another offer.
It’s a bit dodgy, but muhaha!
Your standard back button hack looks like this:
I love it!
With a few lines of code I can control someone’s forward (with a click) or backward (with the back button script) destination.
But what about when they go forward then back – that is, they click through to my offer and then come back to my landing page? Do people do that? And do they then click their back button again and trigger my back button script?
Well, I was kinda curious about that so I started playing around with the Performance API, which includes a navigation object that stores various types of entries, including:
- navigate
- reload
- back_forward
- prerender.
Last edited: