WHAT ARE WEB-BEACONS
Although we think of a web page as a single document, in fact it can consist of many different bits of content, all pulled together into a single page by a browser. For example each image on a page will be distinct and could come from anywhere on the web. So for each image a browser makes a request to the site where the image is located, before showing the content. Typically a beacon consists of an image that a browser is told to display so small that it does not interrupt the view of the page. This is sometimes known as a “tracking pixel”, a “clear gif”, a “web bug” or similar. When a browser wants to display that tiny image, it sends a request to us (for example) and in that request it will send any cookies that have not expired and that are set for our domain (see above for more info).
WHY COOKIES AND WEB-BEACONS ARE USED
Cookies help us to recognise a browser we have already “met”. A web-beacon informs us when a computer/tablet or other device has seen a piece of content.
A typical scenario where this is useful is when you are on a site on which we have purchased advertising space. We show you an advert for (say) shoes that you find of interest, so you click on it. The ad is linked to a site called fabulousshoes.com which is managed by our advertiser. The advertiser puts our web-beacon on its site so that when you arrive there, we know that you have been safely redirected. If you subsequently make a purchase, another web-beacon might be put on the last page of the purchase process.
It is important to note that the Cookie does not identify you. It just identifies the browser that you are using. Unless you have chosen to give us your name (for example by registering with us), and are logged in to our site, the cookie does not tell us who you are.
Some companies pay thousands of web-sites to deploy their web-beacons so that they can build a large profiling database. We do not. We deploy web-beacons only as part of advertising campaigns for our clients. The web-beacons are placed on appropriate pages of our clients’ sites and help us analyse the performance of our clients’ advertising.
Currently we set and use some cookies ourselves but only on our site. These are called first party cookies.
When cookies are served by another domain they are called “third party cookies”. We use some third party cookies on our site.
We list these below:
First Party Cookies
|These cookies are set by google analytics.
More about google analytics is available here.
|CMSSESSIDc315bba0||www.infectiousmedia.com||session||This is a session cookies that remembers you as you browse our site|
Third Party Cookies
For advertising on most external websites, we use a variety of proprietary and third party technologies to ensure the ads are efficiently and anonymously targeted to the audiences requested by our advertisers. We primarily use our own Impression Desk (IDB) technology but sometimes employ the use of other ad-exchange platforms, including but not limited to those operated by AppNexus and Google.
Depending on which technology platforms are used, a set of their cookies will be sent to your browser:
- Whenever you visit a page that has advertising provided through that technology platform (whether or not it is us that eventually provides the advertising to you)
- When you visit any page that has a web-beacon embedded from one or more of the technology platforms we work with
These cookies, and in particular the Impression Desk/AppNexus/DoubleClick user IDs which are contained in the cookies called idb, uuid2 and id respectively, are used for behavioural advertising; in other words: to help us recognise a browser so that we can provide more relevant advertising; and to recognise a user who has opted out of behavioural advertising.
Impression Desk and our third party technology partners are also integrated with a number of other advertising exchanges and third parties. For example in some cases where Impression Desk, AppNexus or DoubleClick sets a cookie, they may also send a number of other pixels to your browser at the same time that allows those third parties to synchronise any cookies that they have previously sent to your browser (and you have not deleted) with the Impression Desk, AppNexus or DoubleClick cookies. This is known as “cookie-syncing”.
For more detailed information on Impression Desk cookies please see below. For AppNexus and Google Doubleclick cookies please see the following links – AppNexus, Google Doubleclick.
IMPRESSION DESK ADVERTISING COOKIES
|idb (opt out)||When a user opts out of having Impression Desk used to select ads based on online behaviour, the unique value in uuid2 is deleted and replaced with the non-unique value “AA”. For more information about Impression Desk opt out, click here.|
CAN I STOP GETTING COOKIES WHEN VISITING THE INFECTIOUS MEDIA WEBSITE
Not at the moment. But you can achieve the same result by changing your browser settings so that it does not store cookies. The site All About Cookies has good information about how to do this.
BUT, if you do stop cookies from being delivered then you may find your experience on our site to be quite limited. For example you may not be able to log in, or you may be asked to log in every time you click on a link.
CAN I STOP RECEIVING BEHAVIOURAL ADVERTISING FROM INFECTIOUS MEDIA
When you opt-out, we set the idb cookie to have an anonymous value. In this way the cookie still exists but it cannot be used to associate your visit with any of your previous visits. We also ask AppNexus to do the same with the uuid2 and DoubleClick with the id cookies.
Please note that the opt-out is browser specific. You must opt-out for every browser that you use. It is also reliant on the idb/uuid2/id cookies being alive. If you delete the cookies or they expire then on your next visit to a page with advertising provided by us or members of the AppNexus or DoubleClick services you will get a new idb/uuid2/id cookie and will need to opt-out again.
In particular we will honour Do Not Track browser requests when we feel that a cross-industry standard is sufficiently set in stone for it to be meaningful.
We are also very interested in the possibilities offered by an alternative set of information (known as device identification or Device ID). Using Device ID may mean that we could avoid using cookies altogether, or at least reduce our usage. It will also provide, we hope, a greater degree of permanence to any opt-out from behavioural advertising. We are trialling Device ID technology now and will evaluate its privacy advantages and efficacy in early 2013.