 RARPSL
join:1999-12-08
Suffern, NY | reply to funchords
Re: Enhances my experience how??? said by funchords:I really can't follow that without a whiteboard and some Ritalin ... "Sorry about that" - Maxwell Smart
The Executive Summary is that the Content Provider is supplied with Ads to serve which are paid for by the Ad Client Companies (they pay so that for every X Ads served, theirs will be served Y times). When the ISP swaps Ad2 for Ad1 (due to being told to due to Targeting) the Ad Client is being charged for Ads that are not actually getting delivered (they get counted as being delivered by get hijacked/suppressed before getting delivered to the User's Browser). Thus the Ad Company is not only getting paid for Ads that never reach the User but also getting paid a premium for the Ads that get substituted for the suppressed Ads.
My explanation only documented the steps that are occurring when this scam happens. |
|
|
|
 funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | said by RARPSL:the Content Provider is supplied with Ads to serve which are paid for by the Ad Client Companies (they pay so that for every X Ads served, theirs will be served Y times). When the ISP swaps Ad2 for Ad1 (due to being told to due to Targeting) the Ad Client is being charged for Ads that are not actually getting delivered (they get counted as being delivered by get hijacked/suppressed before getting delivered to the User's Browser). Thus the Ad Company is not only getting paid for Ads that never reach the User but also getting paid a premium for the Ads that get substituted for the suppressed Ads. According to THEM (famous last words), it's not the ISP swapping the ads but its the ad network upon detecting the NebuAd cookie. So, in theory (or at least in hope), the ads delivered will be counted correctly. All the ads are presented from the same ad networks.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
HTTP is the new Bandwidth Hog...
|
|
RARPSL
join:1999-12-08
Suffern, NY | said by funchords:said by RARPSL:the Content Provider is supplied with Ads to serve which are paid for by the Ad Client Companies (they pay so that for every X Ads served, theirs will be served Y times). When the ISP swaps Ad2 for Ad1 (due to being told to due to Targeting) the Ad Client is being charged for Ads that are not actually getting delivered (they get counted as being delivered by get hijacked/suppressed before getting delivered to the User's Browser). Thus the Ad Company is not only getting paid for Ads that never reach the User but also getting paid a premium for the Ads that get substituted for the suppressed Ads. According to THEM (famous last words), it's not the ISP swapping the ads but its the ad network upon detecting the NebuAd cookie. So, in theory (or at least in hope), the ads delivered will be counted correctly. All the ads are presented from the same ad networks. OK - To be precise, I should have said "When the ISP receives Ad2 2 not Ad1 ...". This does not affect my main point of the page being sent with Ad 1 and arriving at the User's Browser with Ad2 when Ad 1 was paid for and counted as being served.
If the swapping code looks at the Ad that was there before it modified the HTML and decrements the counter for that Ad (so it will go back into the rotation as if it had not been given to a Content Provider to serve in the first place) then this is "fair" to the Ad Purchaser. I do not know the internals of the Ad Network's system so I can not state that this can be done. It would probably require that all the Ad Selection (and Monitoring) be done from one database so that the counting can be done. OTOH: I can see a setup where the Ads are spread over a number of databases (none of which share an Ad) so that if the swapping is done from a different database, the served times count correction can not be done unless the server talks to the server with the correct database. |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | Here's the disconnect:
There is no ad swapping code. (According to them.)
(but I don't blame you for believing that there is, because there is ad-swapping history in a couple points in this company's history.)
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
HTTP is the new Bandwidth Hog...
|
|
RARPSL
join:1999-12-08
Suffern, NY | said by funchords:Here's the disconnect: There is no ad swapping code. (According to them.)(but I don't blame you for believing that there is, because there is ad-swapping history in a couple points in this company's history.) In that case where in the process does my web viewing history trigger a targeted as opposed to random ad? Are they saying that when an ad is selected to be sent me by the content provider, that the ad supplied is a targeted as opposed to random (rotation) ad and thus what ends up a at my browser is what the content provider originally sent? |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | Yes, now you got it. And they can do this because NebuAd force loads cookies for its partner ad networks that identify you as a NebuAd profile when you visit that page. |
|
