Home >
The Newbie Zone >
Questions and Answers
Question about scrubbing ripped landers (7)
04-22-2018 07:15 AM
#1
daydreamer (Member)
Question about scrubbing ripped landers
I ripped a couple landers from Adplexity a few months ago, tweaked it a bit and I been running them since. Now I am second guessing if I actually scrubbed it enough or if there are any redirect coding left. What would be a good way to check?
One way I thought I could test the landers is by opening the location link saved in my amazon S3. The lander would show up in my internet browser, I click thru all of the questions, and then it shouldn't direct me to any offer links right? When I do try this, it does direct me to an offer that I unfamiliar with. Does that mean there is another code that I need to delete?
Since I didn't open the Voluum Campaign URL directly, it shouldn't have an offer linked to that lander saved in Amazon S3 right?
Thanks!
04-22-2018 11:31 PM
#2
thedudeabides (Moderator)
You'll need to check in the javascript itself if you've already changed the Voluum /click urls. If it's all compacted together you can use: http://jsbeautifier.org/
Typically you'd use the search function and look for things like urls and pieces of code like "document.location.href" and "document.location" followed by a url.

Originally Posted by
daydreamer
Since I didn't open the
Voluum Campaign URL directly, it shouldn't have an offer linked to that lander saved in Amazon S3 right?
It shouldn't unless you've previously clicked a campaign url, and had a cookie created on your machine. You can verify by trying it again in a new private/incognito browser.
04-23-2018 02:40 AM
#3
daydreamer (Member)

Originally Posted by
thedudeabides
You'll need to check in the javascript itself if you've already changed the
Voluum /click urls. If it's all compacted together you can use:
http://jsbeautifier.org/
Typically you'd use the search function and look for things like urls and pieces of code like "document.location.href" and "document.location" followed by a url.
It shouldn't unless you've previously clicked a campaign url, and had a cookie created on your machine. You can verify by trying it again in a new private/incognito browser.
Thanks!! this helped and it confirmed that I actually did remove all of the old links.
04-23-2018 04:05 AM
#4
erikgyepes (Moderator)
Yes this can be sometimes very challenging.
Here are more tips and ideas:
Always replace the javascript libraries by your own ie. their CDN versions. This will eliminate the fact that the traffic hijacker script can be hidden for example in the jQuery code itself.
Do a search for "http", "/click" and also the javascript redirect functions as @thedudeabides recommended.
Best is to open all files in your code editor (I recommend Sublime Text) and do a global search in all files.
Sometimes there can be external links in CSS that are pretending to load external image, but in fact it can be a malicious JS/HTML page request.
04-23-2018 07:28 AM
#5
manu_adefy (Veteran Member)

Originally Posted by
erikgyepes
Always replace the javascript libraries by your own ie. their CDN versions. This will eliminate the fact that the traffic hijacker script can be hidden for example in the jQuery code itself.
An extra benefit of this is that CDN versions are likely already cached on most devices so you improve your loadtimes too!
04-23-2018 12:08 PM
#6
erikgyepes (Moderator)
^^^ Yeah, there are definitely more benefits that I can think of in the morning :-)
04-24-2018 01:33 AM
#7
vortex (Senior Moderator)
Straight from the FAQ some of us TAs have put together during one of the 6WAMCs:
Q: How to detect sneaky redirect code in landers?
Depends what kind of functionality you are trying to find as redirection could easily be triggered by a timer, complex logics, cookie-based, etc. There are a bunch of ways to make sure it doesn't fire until it's live and in position.
Although if you watch the web console for it calling out to ANY external service, and it doesn't, and then check if it's dropping any cookies, and it's not, you should be OK.
But for just checking whether it's calling out, developer tools > network tab.
To check whether or not it’s dropping cookies:
-On Chrome: chrome://settings/
-And check for your domain.
-Check before you first visit the page on your domain, and then after.
Or use something like
http://www.cookie-checker.com/
Hope it helps!
Amy
Home >
The Newbie Zone >
Questions and Answers