Key data trends for Publishers in 2024

Familiar and reliable third-party cookies that have served the digital advertising industry for years are likely to disappear from the market in the future. Google has announced that it will end support for third-party cookies in the Chrome browser in 2025.

Safari and Firefox browsers already have removed support, and applications have always had limitations and technologies. With the removal of third-party cookies, the entire digital advertising industry will have to revamp its practices. We will need new ways to target advertising and measure its effectiveness.

In this post, we aim to provide publishers with a comprehensive picture of the current alternatives for targeted advertising. We start with the basics such as data types and storage technologies, then we discuss alternative ways of targeting and creating publisher-owned segments. Additionally, we evaluate how the removal of third-party cookies will affect different stakeholders. Finally, we share tips on where publishers should start.

Cookies and storage technologies

• 0 Party data: This is data that a visitor voluntarily provides about themselves, for example, by answering a survey on the website. Data can also be collected by the device manufacturer.
• First-party data (1st Party): This is data that a company owns itself, such as a customer database or browsing data collected with user consent on its website.
• Partner data (2nd Party): This is data that two companies have agreed to share, such as in the context of joint campaigns or partnerships.
• Third-party data (3rd Party): Data that comes from a third-party provider who does not have a direct relationship with the company.
  
  

It's important to note that different technologies can recognise and utilise primarily first- and third-party data. For example, programmatic advertising mainly targets third-party data, while website personalisation tools may utilise first-party data.

When data is stored about visitors online, it is linked to the visitors by storing a unique ID in their browser. This ID is typically stored either in a cookie or in the browser's local storage (HTML5 storage).

Cookies can be either first-party or third-party cookies. The determining factor is whether the cookie is set from the same domain where the visitor is currently located (1st party) or from a different domain (3rd party).

Reading/writing of 1st party cookies is limited only to the specific domain, meaning they are page-specific. The same limitation applies to the browser's local storage.

Third-party cookies are set from a different domain than where the visitor is. This allows the cookie to be used on multiple other websites. Browsers such as Safari and Firefox already block third-party cookie settings by default.

Client-side and server-side 1P cookie

It also matters how the 1P cookie is installed on the browser. There are two options: client-side and server-side.

A client-side 1P cookie is a cookie installed by a script in the browser. Its expected lifespan in the Safari browser is 7 days if the user doesn't visit the service during that week. If "link decoration" is used, which includes identifiers that make marketing measurement easier, the lifespan is limited to 24 hours in Safari.

A server-side 1P cookie is a cookie that is set by the server. Currently, the lifespan of this cookie is longer than that of the client-side cookie, but Apple is planning to limit the lifespan of these cookies to 7 days.

Cookies and browsers at the moment

Universal ID

A huge number of Universal ID (UID) providers have emerged in the market, aiming to solve the limitations on data usage across different domains that will arise due to the removal of third-party cookies.

Universal IDs typically work in two different ways:

• Based on login information - Visitors are connected based on email or other login credentials. The identifier is transmitted encrypted to the UID provider, who returns an ID based on the identifier, which is the same across sites.
• Model-based - Visitor data from the device is used to estimate whether the visitor has already been assigned an ID. If they have, the same ID is assigned to the visitor regardless of the site. If the visitor cannot be identified with sufficient certainty, a new ID is assigned

To work, UIDs also require the user's consent. Universal ID providers set a first-party ID (either a cookie or local storage) that is passed along with ad requests. Read more.

The segment data is typically transferred from a DMP to buying platforms using ID synchronisation between systems and utilising third-party cookies. In the future, this model will not work, and it also does not work today, for example, in Safari and Firefox.

This challenge has been addressed through different methods:

1. Publishers’ package segment data and inventory - The benefit of this approach is that it is likely to work in the future as well. Still, it may not be a very scalable way to operate with a large group of advertisers.
2. Utilisation of 1st-party ID for data transmission - For example, Adform supports the transmission of segment data based on 1P identifiers. The ID previously provided for use by DSP is also sent with the ad request so that the ad can be targeted based on segment data. At least for now, targeting based on 1P identifiers requires manual work.
3. Utilising Universal ID for transmitting data - This implementation is easy to adopt, but utilising it may incur additional costs. However, some UID vendors offer their technology free of charge to publishers. Moreover, there is no guarantee of its functionality in the future.

Adform ID Fusion

Adform has developed a new solution called "ID Fusion" that aims to solve the challenge of ad targeting by combining different 1st party IDs within its ecosystem. The goal is to find connections between the same user across various devices and websites to make ad targeting and measurement work while respecting user privacy.

The ID Fusion solution relies on user consent and connects different 1st party IDs to each other. If the same ID is available on different websites, that real ID is used. If there is no matching ID available, the solution tries to connect different IDs together by predicting them.

This new solution helps to understand user behaviour across different platforms better and provides a better understanding of the type of advertising that should be targeted. ID Fusion is already available on Adform's platform and is expected to offer new opportunities for ad targeting. Read more.

Privacy Sandbox

Google has been working on the Privacy Sandbox project for the past few years to find alternative solutions to third-party cookies and improve user privacy. One of the latest proposals is the Topics API, which suggests that the browser returns a few interest groups that can be used for ad targeting without personal information.

However, the W3C TAG (Technical Architecture Group of the organisation that sets standards for the web) has rejected this proposal and recommends that its development should not continue. One reason was that Topics API does not provide sufficient privacy protection for users and is not secure enough. Apple and Mozilla have also expressed that they do not support this proposal in their browsers, which poses additional challenges to its adoption. Read more.

Seller Defined audiences

Seller Defined Audiences (SDA) is a standard published by IAB Tech Lab in early 2022. It enables visitor segmentation into over 1700 audience categories based on three classifications: intent, interest, and demographics. SDA technology works synergistically with contextual categories, allowing publishers to combine page-level context with SDA-defined behaviour for more precise targeting for advertisers. SDA audience data is transferred in the auction according to the ORTB standard, making it platform-agnostic.

SDA technology provides publishers with a standardised way to classify and sell first-party data cohorts across browsers and devices. It allows publishers to leverage their private audience targeting on a larger scale without third-party cookies or data processors. The technology leverages several existing programmatic technologies, such as ORTB, Prebid, and IAB's data transparency standards.

However, there are still challenges to the widespread adoption of Seller Defined Audiences, as DSPs must enable SDA audience groups to be used on their platforms. Read more.

Impact on different stakeholders

• Advertisers will need to reconsider retargeting and targeting of advertising.
• Measuring advertising effectiveness will become even more difficult without third-party cookies.
• Safety solutions are of interest.
• Media agencies face the same challenges as advertisers.
• Running their own data business is no longer possible with the old tools.
• "Classic" modelling becomes more valuable.
• Media agencies can seek new partners and partnership opportunities with new technologies.
   

Sellers of Advertising: 

• Media companies with a lot of logged-in users are in a stronger position.
• Contextual targeting allows for the commercialisation of contexts through direct sales and deals.
• The ability to deliver quality profiles, impactful environments, and formats is emphasised.
• Small sites with low profiling capabilities may find the change difficult.
• The change could open up opportunities for high-quality networks to curate targeted deals for a broader range of publishers.
• Overall, sellers are more agile adapters than buyers.
  
  

Others:

• In addition to technical challenges, global giants face legal issues, as the removal of third-party cookies and Apple's restrictions make it difficult to prove the effectiveness of advertising. Meta may not be able to track users based on their terms of service, and Google is also under constant review. 
• Data traders are likely to focus on UID opportunities, and businesses based on 3rd party cookies are likely to end. 
• Cleanrooms are growing in importance, but they can provide the most value to those with significant first-party data. 
• Retailers have a lot of 1st party data and distribution channels, giving them a strong negotiating position with brands and opportunities to increase their market share. However, they may not yet be very skilled in local media sales so that partnerships may be found here. 
• DSPs and SSPs who are openly receptive to different identifiers may increase in popularity compared to those who are unwilling to work with publishers and advertisers.

• Publishers should evaluate whether they can increase their first-party data assets by encouraging visitors to log in, participate in surveys, or subscribe to newsletters.
• It is also worth considering whether developing contextual targeting capabilities can provide growth opportunities.
• Targeting profiled sites is easier because they already allow advertisers to reach consumers interested in a particular topic. Deals and direct campaigns are good options for this.
• UID operators who actively operate in the domestic market are worth testing, and it is worth delving into the added value they offer.
• Naturally, we should all closely monitor the development of new standards, especially the promising journey of the Seller Defined Audience from design to implementation.
  
  

We are not alone in facing this situation, as the change affects the entire industry. By sharing our experiences, we can achieve the best results. At Relevant Digital, we closely monitor the developments in the situation.