You can choose to have Google host your match table. This may improve reporting of table size and match rates, and reduce the amount of infrastructure you need to support. A Google-hosted match table offers a mechanism whereby data which you pass to Google for storage is later passed back to you in bid requests. Typically, when you have placed a match tag for a user whom you have identified with your own internal cookie ID, you include that cookie ID in the cookie match request that you send to Google. Google hosts the data you sent, and includes it in subsequent bid requests for impressions viewed by the same user.
This enables you to:.
Only appears if the attempt to write data to the hosted match table fails. When that happens, its value is one of the following status codes:. The simplest form of a Cookie Match request is one with no extra parameters. The match tag URL in this case would be:. In the case where the user has a doubleclick.
An error response would add the extra parameters in a similar way, while reporting the error as in the first example. If there is an overall error e. The redirect URL in case of error is similar, but the status code would be different. Suppose you don't have permission to add users to user list , the redirect URL would be:. Note that you can specify a timestamp on each independently:. Here the user has been added to the list , but there was a permission error for list These parameters do not otherwise modify the result of the request.
The Cookie Matching Service may not always succeed in setting the cookie if, for example, the user has disallowed cookies generally or the doubleclick. If the Cookie Matching service needs to set a cookie, it verifies that the user's browser has accepted the cookie by issuing a self-redirect with the Set-Cookie header.
- The Complete Cookie®.
- Please choose a region.!
If the user's browser does not send the cookie in the self-redirect, it is classified as not accepting the doubleclick. If the user does not have the doubleclick.
Join Javatpoint Test Series
For this example, assume that there is no doubleclick. We'll also assume that the configured redirect URL is:. Typically the buyer supplies Google with a base cookie matching URL to which cookie matching parameters are appended. For example, a URL configured for cookie matching could be as follows:. The following URL would produce the same result:. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4. For details, see the Google Developers Site Policies. Guides Reference Support Videos.
82 Amazing Cookie Recipes You'll Be Baking All Year Long
Ad Request. Ad Response. Best Practices. The Cookie Matching Service enables a buyer to associate two types of cookies: A cookie associated with a web browser within the buyer domain. A doubleclick. Benefits of hosted match tables Buyers who choose to have Google host their match tables stand to gain the following benefits: Lower infrastructure investment Mapping the Google User ID to a useful form does not require a table lookup During pretargeting, there is the option to filter on whether or not a cookie match exists, which can reduce unwanted bid requests How cookie matching works To build an association in the match table, the buyer must serve a tag provided by Google, called the match tag.
Entries are added to the match table at the rate at which match tags are served to unique users. Example scenarios How would cookie matching look to a typical web user, and what's happening behind the scenes? Scenario 1: Cleared cookies Jane clears her cache of all cookies. She then visits the homepage of ExampleNews.
Here's what happens: ExampleNews. FinestDSP processes the bid request in its bid engine, and sends its bid response to Authorized Buyers. The match tag calls Google's Cookie Match Service.
The Ruff Ruffman Show . Games . Ruff's Cookie Creator | PBS KIDS
FinestDSP drops its cookie in Jane's browser and responds to the redirect with an invisible 1x1 pixel. Based on the information associated with its cookie, FinestDSP decides to bid on the impression, and wins the auction. Jane might see an ad tailored to her or her interests, again based on information that FinestDSP possesses. Serve cookie match tag You must have the ability to place the Google-supplied match pixel tag on the user's browser. Serve pixels Your servers must recognize the redirect URL, and serve a 1x1 empty pixel to the user's browser in a timely fashion.
Pixel matching In cookie matching, the buyer that wins the auction for an impression can associate a cookie with a Google User ID. This sets the stage for the following interaction: When the page loads in the user's browser, the match tag generates a pixel request to the buyer. If you are the chosen buyer: You receive your own cookie along with the Google User ID, enabling you to associate the two in your match table. You must redirect the request back to Google.
The chosen buyer responds with a redirect.
Google receives the redirect and stores the match between user and buyer. Google serves the pixel to the browser. Cookie Match Assist CMA is an additional feature for exchanges that enables them to build match tables with their own bidders. This endpoint is intended to implement a service that selects and redirects a pixel request to one of the exchange's bidders in order to match the user ID with their cookie.
Quota : the maximum number of Cookie Match Assist requests that the exchange can receive every second. This is intended to prevent CMA requests from overloading the exchange's server with requests. The exchange's Cookie Match Assist endpoint receives the request, where its own cookie matching service is responsible for matching the user ID with one of its bidders. In the diagram below, the exchange's cookie matching service responds to the user's browser with a redirect to one of its bidder's endpoints.
The bidder receives the request, along with any parameters specified by the exchange to match the user ID with their cookie. Restrictions This section describes the restrictions that Google has put in place to protect user privacy and ensure a pleasant user experience. Respects user privacy The Cookie Matching Service respects user privacy by adhering to the following principles: Google does not accept any user information provided by the buyer such as the cookie, user demographics, etc. Google prohibits multiple buyers from joining data they receive from the Cookie Matching Service.
The purpose of the match table is to allow buyers to use the information they own about the user in transacting with Google. The use of the Cookie Matching Service for the purpose of data harvesting is strictly prohibited by the Authorized Buyers contract and policies. Cap frequency You, as the buyer, are responsible for frequency capping the Cookie Matching Service so that it is not used for users who already have a fresh entry in the match table. Respond to all pixel match requests If you sign up to use the Pixel Matching service you are expected to respond to all Pixel Match requests.
Adhere to maximum request rate When you sign up for the Cookie Matching Service, Google provides a maximum request rate. The Cookie Matching service supports several operations: Perform cookie matching -- the basic cookie matching operation described above. Add the user to a user list -- adds the user to a user list, avoiding the need for a separate tag.
Set cookie if missing -- normally the Cookie Matching Service does not set a doubleclick. When this option is set, the Cookie Matching Service sets the doubleclick. This is a buyer ID. Here, "network" refers to the typical buyer, an ad network. The value the parameter is ignored and may be omitted. The value of the parameter is ignored and may be omitted.
Copyright 2019 - All Right Reserved