Why Cookie Matching Matters

Sortable Ad Ops

Did you know that if it weren’t for cookies, eCommerce shopping wouldn’t be a thing? We also wouldn’t be able to have our login information saved for the various websites we create accounts for, and we’d have to reconfigure the language for multilingual websites each time we visited a website. 

Browser cookies are essentially small pieces of data stored in users’ computers via their web browsers while they scroll through websites. The purpose behind cookies is to allow web browsers to “remember’ certain information in terms of a user’s web browsing activity. In other words, cookies provide a personalized user experience by storing bits and pieces of user information. Without them, our regular, everyday browsing would be quite frustrating.

Cookies are also used by advertisers and website owners to collect information about their sites’ visitors. This allows the advertisers and website owners to analyze user data to create better experiences, display more relevant ads, and so on. Of course, with tons of data piling into each website, and with the online display-advertising world expanding daily, targeting the right audience and creating a better user experience is becoming a never-ending challenge.

That’s where cookie matching, also known as cookie syncing, comes in handy.

In this article, we’re going to talk about cookie matching — what it is, how it works, and how it impacts publishers. 

To understand cookie matching, you must first understand that cookies are domain-specific. That means that cookies created by one third-party tracker program can’t be read by another. Only the creator can read the data collected, which can limit the amount of information an advertiser can potentially collect about a user.

Suggested Post:   What is Prebid User ID Module?

Therefore, to accurately target a specific audience, advertisers and website owners have to find a way to incorporate user data from multiple domains and sources, which involves using data-buying agreements and engaging in company partnerships.

One way to achieve this is by mapping user IDs from the various systems involved. For example, you could map a user’s ID from a demand-side platform (DSP) to a data management platform (DMP) — in other words, cookie matching.

We can define cookie matching as the mapping of user IDs from a data platform to a data management platform.

The cookie matching process can be used by most advertising technology platforms. This would include ad networks, the aforementioned demand-side platforms and data management platforms, ad exchanges, supply-side platforms (SSPs), and various other platforms and data providers.

The end results of cookie matching enable advertisers to exchange user data across multiple platforms, which in turn, allows them to better target their audiences via online advertisements.  

Third Party Cookies: Then and Now

You’ve probably come across a few headlines discussing the slow death of the third-party cookie, which began as early as 2017. So what’s happening to them? In this blog, we dive into the cookiepolypse.

For cookie matching to work, you need two different Ad Ops platforms (such as a DSP) to map out each other’s unique IDs and successively share their user information.

Each time a user visits a website containing ads or third-party tracking tabs, their browser sends an ad request to one of the Ad Ops platforms which creates a unique user ID. That ID is stored as a cookie. 

Suggested Post:   The Impact of GDPR on Publishers

In addition to the ad request, the Ad Ops platform of choice also draws in a pixel URL provided by a different Ad Ops platform (such as the DMP). This combination of the unique user ID and pixel URL is known as a pixel URL call. 

As the DMP and DSP communicate, the DMP’s server reads the DSP’s user IDs within their own domain to check and see if it already has a user ID for the particular cookie it’s reading. If a user ID doesn’t exist, then it creates a user ID of its own.

All of this information is stored in what is called a cookie-matching table, which the Ad Ops platforms can use as a resource to trade identifying information back and forth in a bidirectional sync process. 

Of course, this is a very simplified explanation of how cookie matching works. The actual process becomes a bit more complicated when you consider the following:

  • Sometimes users clear their cookies
  • Some browsers are set to block cookies by default
  • Some users employ cookie-blocking software
  • Some users browse through an in-app browser
  • Users may opt-out of cookies 

When any of the above occurs, the cookies must be recreated and the cookie matching has to start all over again for that user.

Cookie matching makes life a bit easier for publishers as it allows you to collect and share important user information. You can create better user experiences as well as come up with better marketing strategies and ad targeting for your audiences.

However, cookie matching is more or less handled by the buy-side platforms. That means there’s not too much that publishers can do to improve your cookie matching schematics to increase your revenue. 

Suggested Post:   Google’s Privacy Sandbox Explained

Cooking matching has become a critical part of the online advertising world thanks to its capacity to share information across multiple platforms. However, certain challenges such as ad blockers and opt-outs (to name a few), make it harder for publishers to increase their revenue stream. 

If you want to improve your cookie matching, you could partner with a more diverse group of demand partners. This is especially true if you’re working in a server-to-server environment, where cookie match rates tend to be much lower.

Fortunately, if you’re looking for more diverse demand partners for your cookie-matching endeavours, we can help you out with that. Contact us today to learn more about how we help you more successfully monetize your website.