Email submits and cakeslice idea!

Ok this is the first time i've suggested an idea, and im going over the theory of it in my head and im pretty sure its going to work, im going to implement it tonight, it will take a bit of setup (half hour or so?) and requires a bit of php/mysql knowledge but ill be glad to help people out if you think its gonna work, ok so here we go:

This is basically going to be an email/zip submit using the cakeslice technique. The cakeslice html page will basically allow you to select an area of a CPA offer where the input email is and the submit button so you just cut out that area and can copy and paste it into your own page. If you dont know about it check it out here:

Now were going to be using this to pick out the input name/email address section and the submit button from a CPA offer, you might have to pick out two seperate areas depending on how the CPA landing page is laid out.

Next, we need to quickly setup a WHITEHAT page for our offer, so stick a banner for the offer, some related text blar blar blar, make it look pretty so if your AM checks your page then it all looks legit.

We are ALSO going to setup a seperate part of the page where you are just displaying your input name/email and submit button from the CPA offer in your IFRAME (the code we got from cakeslice above)

This is where it gets a bit more complicated, what we need to do is setup a database with 1 table (call it whatever) and 1 column, again call it whatever! The way this method will work is we are going to be email responding to people from craiglist ads a url link to our IFRAME'ed offer, we are going to setup a querystring for each person we email and it MUST be different each time, now this can be automated but ill leave that to you for now.

Next populate your table with 100 records, they can either be random numbers or incrementing, incrementing is probably easier to keep track of when emailing

In our index page, we check the querystring, we do a mysql lookup to check that number exists in the table. if it DOESNT, we load the html for our WHITEHAT page, if it DOES, we load the html for our blackhat IFRAME offer. as soon as the querystring is read we do a mysql statement to DELETE that record from the database so it can never be loaded again.

so why are we doing this? so that when the AM checks your referer he sees the url with the querystring, BUT, if he visits that page he will be shown the WHITEHAT page because the record has been deleted from the database upon loading the first time.

Hope this makese sense, its quite long winded but i think the theory behind it works, its basically taking the cakeslice method without having to mess about with double meta refreshes and also keeps your tracks covered with your AM!

Any questions please ask

p.s the idea here is that when the people receive your email they will click the link, and it will load the iframe offer.. at this point your need to give them incentive to fill out their email and click submit but there are already hundreds of ideas on this forum to do that

Next populate your table with 100 records, they can either be random numbers or incrementing, incrementing is probably easier to keep track of when emailing

Click to expand...

Hmm.. I don't think incrementing would work very well. What happens when your AM decides to enter the next number in a sequential pattern that he notices? Pretty much screwed at that point.

If you made all the ids completely random then I guess it would work fine. But you're still likely to make your AM a lot more suspicious with all the strange ids compared to just normal cparedirect.

Sure, maybe they can't find your BH page at all with this method, but if they suspect something they may start watching you closer or checking your leads more. The less potential red flags you have, the better.

Hmm.. I don't think incrementing would work very well. What happens when your AM decides to enter the next number in a sequential pattern that he notices? Pretty much screwed at that point.

If you made all the ids completely random then I guess it would work fine. But you're still likely to make your AM a lot more suspicious with all the strange ids compared to just normal cparedirect.

Sure, maybe they can't find your BH page at all with this method, but if they suspect something they may start watching you closer or checking your leads more. The less potential red flags you have, the better.

Click to expand...

mybe use random ids, and cpa redirector.. so your faking the referer and only allowing the url supplied to be used once..?

Hmm.. I don't think incrementing would work very well. What happens when your AM decides to enter the next number in a sequential pattern that he notices? Pretty much screwed at that point.

If you made all the ids completely random then I guess it would work fine. But you're still likely to make your AM a lot more suspicious with all the strange ids compared to just normal cparedirect.

Sure, maybe they can't find your BH page at all with this method, but if they suspect something they may start watching you closer or checking your leads more. The less potential red flags you have, the better.

Click to expand...

I am far from a technical genius, but I'm pretty sure they the AM isn't able to see the query numbers - just the /index.html

Well just as an update I changed the method slightly, i redirect people to another page lets say xxyy.php, it then generates a random md5 on the fly, it uses the first 10 characters of that as the random character and inserts it into the DB, it then redirects to the index.php?id=[random md5] so its now completely random and since the AM wont know about the xxyy page it should be quite secure.

Yes its been tested, and yes it does work, ive had some conversions, will see if i get paid once i make minimum payout.

Note that adblockers might block our captcha, and other functionality on BHW so if you don't see the captcha or see reduced functionality please disable adblockers to ensure full functionality, note we only allow relevant management verified ads on BHW.