With a grower voice speaking up against the use of cookies, cookies have been seen as something bad. But be honest, what exactly are cookies, and why have they become such a hot topic on privacy concerns?
A cookie is a small text file that a website stores on your device, usually in your web browser. Cookies help websites remember your past interactions, such as whether you’re logged in, what's in your shopping basket, and your preferred browsing language.
By storing this kind of information, cookies make your browsing experience smoother, so you don't need to log in every time you visit a site.
1st-party cookies are set by the website you're visiting, like ayudante.jp. These help the site remember your preferences and activity on their pages.
3rd-party cookies are set by other websites, such as advertisers or analytics companies (like bing.com and google.com). These track your browsing behaviour across different websites.
In simple terms, 1st-party cookies mostly help the site remember your preferences within the website, making your browsing experience smoother. In contrast, 3rd-party cookies are mainly used for audience retargeting.
First, we need to understand that a cookie has a name and value. The cookie name is the name assigned by the developer to distinguish the cookie, while the cookie value is normally an ID for attribution. For example, instead of your name, it might show a hashed value like a123456. This allows marketing platforms to remember your assigned identity and what you've viewed and shown interest in, without knowing your real personal information.
And then, each time you visit a website, a cookie is placed on your device or browser. This cookie tracks your browsing activity and interests. The website can then use this data to identify you on other sites and show you ads related to what you previously looked at. For example, if you visited a hotel website, the cookie would allow that hotel to show you ads on other sites.
To see which company placed a cookie to retarget you, check your browser's cookie settings. Look at the domain name of the cookie, and you'll find the company or media platform responsible.
Let me use a 3rd-party cookie (name: IDE) set by Google Campaign Manager (previously known as “DoubleClick”) as an example for demonstration:
On web page A, the cookie value is “AHWqTUnY_-InO31aZ4ZBi3pfWSHFgoUHI3ZQMg8E_rCt4HClO1x9xRtORyWpmr8Mabo”.
On the another web page, you would fine the cookie value still stay the same “AHWqTUnY_-InO31aZ4ZBi3pfWSHFgoUHI3ZQMg8E_rCt4HClO1x9xRtORyWpmr8Mabo”.
This means that the entity setting the cookie (doubleclick.net) understands your identity and interactions across different web pages. Consequently, they can build a database based on your interests and sell this audience data to ad sponsors.
I understand retargeting with 3rd-party cookies might make you uncomfortable. That's why there are campaigns happening around the phasing out of 3rd-party cookies. In my next blog, I will discuss the background of 3rd-Party Cookie Deprecation (3PCD) and what digital marketers can do next.
