Warning: by using this method, your landing page will only work in displaying real content if someone goes through a Thrive campaign URL. This method hides real content from any organic visitors.
There is an unpublished token you can use called {epochtime}, which is the epoch time of when the click was generated.
You can pass this to your landing page URL, like:
http://lander.com/?when={epochtime}
What this will allow you to do is to check the epoch time the visitor is looking at your landing page.
Then, if it's not within say 60 seconds of the time from the token, redirect your unwanted visitor to a different page than your real page that you're trying to cloak.
On your landing pages, you can have the following code:
PHP: <?php if ( $_GET['when'] < (time() - 60) ) { //no match - redirect header('Location: http://safe-page-site.com/'); die(); } ?> ACTUAL LANDING PAGE CONTENT |
JavaScript (requires download of .js file attached to this article): <head lang="en"> <meta charset="UTF-8"> <script src="http://File-Location.com/ebb.js" type="text/javascript"></script> </head> <body> ACTUAL LANDING PAGE CONTENT </body>
Once you download the .js file, you need to edit it. What should normally be change in the .js file is: preventStaleLoading("http://example.com", "when", 60); |
The URL (http://example.com) is the safe page URL you want to show instead of your actual landing page content.
The "when" variable is the variable you're using in the landing page to pass when={epochtime}. You can edit this if you want to use a different variable.
60 is the number of seconds grace period to allow a visitor who has come through your Thrive campaign URL to be able to see the actual landing page content.
The "when" variable is named that for clarity, I highly recommend changing it so it's less obvious what it is. You can also reduce the 60 second grace but it seems like a reasonable amount to me.
There are other alternatives to this code, of course, such as just including different content for the page based on this criteria.
Comments
0 comments
Please sign in to leave a comment.