Amazing Facts About The Online Porn Industry
 

it's truly amazing, it doesn't matter what happens to an affiliate program or a processor, the entire building their servers are in could be on fire, they could have their entire network taken down by hackers, but amazingly enough none of it ever affects their ability to track transactions - ALL TRANSACTIONS ARE BEING RECORDED! THERE WAS A 9.8 EARTHQUAKE, OUR DATA CENTER WAS AT THE EPICENTER OF IT, THE BUILDING IS PANCAKED TO THE GROUND, NO POWER WITHIN 100 MILES, EVERYBODY IS DEAD, BUT PLEASE BE ASSURED ALL TRANSACTIONS ARE BEING TRACKED AND RECORDED!

that IS truely amazing...how in the world do they do it?


must be magic

http://dudes.super-site-1.com/male-p...blaine-005.jpg

Hehe, so true. I think the line "all transactions are being recorded despite the stats being down" is written in all affiliate manager training manuals.

lol, so true :glugglug

:1orglaugh

Very true though, I don't think I've ever recieved any communication from any processor or sponsor that didn't say that at least once.

:1orglaugh

:1orglaugh :1orglaugh :1orglaugh

And the funny part we believe them everytime they tell us that don't we?

:1orglaugh :1orglaugh :1orglaugh

yep everyone is always like " Ok cool, I was worried but I know that so and so at XYZ Cash are stand up guys":1orglaugh

I have a news flash for all of you...

transaction servers and stats servers are NOT in the same bank, the same place or even on the same power supply.

I'll speak for CCBill since I know without a doubt how their setup works, and I'd imagine I'm dead on with the other guys too. But imagination is a great thing.

Transaction servers are set apart from everything else in the processing world and the primary priority for any processor (or any bank for that matter since their's are structured the same way) under any circumstances.

Processors would have you bitch and go days without stats if that's what is needed to protect the transaction servers.

There is a God in the land of cc processing and it's called connectivity to your bank.

Even Jewcash was a standup guy for a while - till somebody pulled the rug out from under him.:1orglaugh

:1orglaugh :1orglaugh

he pulled the rug out from under himself screwing people over :winkwink:

those are really interesting facts.

It would seem to me that if the transaction is recorded, the information would be stored as well.

If the system went down the transaction would not happen. So no info to store.

Or is this too simplistic?

Anyway programming shaving into a website is a breeze according to my programmers, you can set the number or % of affiliate codes to change and what you change it to.

The only safe guard you have is your own stats, I would recommend Excel. Calculate it like this.

Amount of time spent x money x earnings per hour/dollar. Run it on a weekly basis.

The only stats that count are the ones in your bank account. If one sponsor makes more money than another switch the traffic to the other sponsor. You could make more on a guy paying $10 a join than $100 a join.

This solution only works for those using their own hosting and content, the rest of you are tied to the sponsor. Tough life. :winkwink:

i am still a standup guy

Guys. KK knows what she is talking about. She worked for CCBill for a long time. She is not just spewing trash like so much here on gfy.


Listen to her, and learn something while it is being offered.


Thanks KK

:1orglaugh :1orglaugh

Yes, it's way too simplistic. For starters, Visa/Mastercard and the acquiring banks mandate the security procedures that are used for transaction servers. They don't care about stats or anything else, since to them, it's all about transactions as well.

Next, why in the world would you store stats and transactions on the same server, even if there weren't a security vulnerability, since the load would be increased dramatically due to the stats using the database and the resources that run transactions?

Makes no sense whatsoever.

You set your transaction servers up, round robin, however you like, and those are the primary boxes and connections you sacrifice anything else to protect.

You then dump your stats from the transaction servers at fast, regular intervals into your stats system with a one way interface -- meaning no data from the stats system goes back into the transaction system to potentially cause harm.

Then you round robin your stats servers based on the load, which would come from the number of people checking stats on average at a time, and that's how you set up your stats servers.

IF there is a problem, then you yank the stats down or you stop feeding the new data into them until the problem is rectified.

Living by stats minute to minute is a waste of time in this business. Take rebills for instance, they are run daily at a scheduled time. Usually. However, if there's ever a problem with the transaction servers then rebills take a back seat since they are the closest thing to guaranteed revenue there is, and if you rebill them 8, 12, even 24 hours later than you originally intended, it doesn't change anything.

New sales are the lifeblood of this industry, followed by rebills, then you can stick stats in there as being important.

Hope that helps.

Enough with your "reason" and "logic", this is GFY. Unless you've got some pictures no one is going to be able to read that much text.

Thanks for such an informative post KK !! :thumbsup

rofl :1orglaugh :1orglaugh :1orglaugh

:1orglaugh :1orglaugh