Listed players
SST2.44▼ -7.58%TIG40.00▲ +3.90%TEAD0.56▲ +3.77%PERI8.50▼ -2.97%TBLA3.23▼ -2.71%INUV0.57▼ -1.74%AV10.06▼ -1.59%GOOGL343.50▲ +1.56%SNAP5.58▼ -1.24%PINS19.26▼ -1.03%MSFT517.53▲ +0.92%PPLI41.28▲ +0.81%IOS32.24▲ +0.44%META728.08▲ +0.30%GDDY97.21▲ +0.24%DV13.49▲ 0.00%MCHX1.29▲ 0.00%
Ticker byClearTrust

Search feeds · also called query, feed request, search request

Ad request

An ad request is a single call from a page to the search feed asking for ads to show for a particular keyword and visitor.

The short answer, from the The Arbitrage Desk glossary

Each time a results page loads, it asks the feed for ads. That ask is an ad request. It carries the information the search engine needs to pick ads and account for them: the publisher's ID, the keyword or query, the Style ID, any Channel ID, language settings and, where required, fields such as referrerAdCreative.

The engine answers with zero or more ads. A request that returns at least one ad is "matched", and the share of requests that are matched is coverage. How many ads come back is governed by ad depth.

Requests are the top line of feed reporting. From requests flow matched requests, impressions, clicks and revenue, and ratios such as RPS are calculated against them.

They are also where quality control begins. Engines inspect requests for signs of automation or tampering, and Google's ad code by default sets a cookie used only for detecting invalid traffic on consented traffic. Sending requests that no real person triggered, or with altered keywords, is query fraud. Many feeds also limit the volume of requests a partner may send through a feed cap.

An example

For example, 1,000 visitors click a keyword, producing 1,000 ad requests. 900 return ads (90% coverage), and those pages produce 500 ad clicks.

Related terms

Sources: Google Developers: Custom Search Ads reference, Google Developers: Custom Search Ads web implementation