Quote:
Originally Posted by BetBlowWhistler
The basic principle of the operation is a proxy service, which by default is an interception as it terminates your connection before making the onward connection on your behalf.
If they claim they are just mirroring the datastream for analysis, how the hell are they supposed to inject different adverts?
|
The same way that all the other targeted systems do. The script which displays the advert uses the UID in the domain cookie to talk to the Webwise/OIX UID databases - not within the ISP side of the firewall, and then deliver the advert.
As the code which calls the script is hosted by a webpage which the user has requested, the browser trusts it and calls the script. The same way that the browser trusts the google-analytics script. It gets around the usual 3rd party script/cookie blocking by using the domain name of the web page.
All the initial datastream will have is the ad script so there won't be any modification there by the proxy. Have to assume that there is no bouncing around when the ad script talks to the external ad serving database. If there were, by the time the advert was delivered, most people would already have clicked away from the page.
If you think of it - the script is delivered by the proxy, the analysis by the mirror, which advert you see/last saw is handled by the webwise/oix database server. (No wonder there were comments about power usage)
The above is open to correction: I just can't see any other way it could be done.