Clear search
Close search
Google apps
Main menu

Counting impressions and clicks

One of the key strengths of digital advertising is that it can provide detailed metrics on how advertising campaigns are performing. The most fundamental metrics are impressions (the number of times an ad has been served) and clicks. Here are some insights into exactly how DFP counts those metrics.

Counting impressions
Counting clicks
Filtering invalid impressions and clicks
Use the Delivery Inspector to investigate why a line item isn't recording impressions, and creative preview to validate whether a creative will count clicks.

Counting impressions

DFP currently counts an impression each time a creative is sent, or "served," to an end user from the ad server. Note that the impression is counted before the creative is fully downloaded and viewed by the end user.

DFP transition to downloaded impressions
In 2017, DoubleClick is changing the way ad impressions are counted across buy-side and sell-side platforms to align with industry standards. Learn more

Delayed impressions

Some creative types, listed below, use delayed impressions. This means that DFP doesn't count an impression until the creative sends an impression request to DFP. Because of this secondary request, the "Total code served count" metric total can be greater than the "Total impressions" value for these creative types.

  • Native ads
  • Prefetched ads
  • Out-of-page ads
  • Video ads
  • Ad Exchange ads
DFP must receive a followup impression request from the creative within 1 hour from the time the creative code is delivered to the end user.

Google publisher tags single request mode

If single request architecture (SRA) is used, all impressions are counted upon the first call of the display() function, independent of how many ads actually display on the page. If SRA is not used, an impression is counted for each display() call made on the page. Learn more about GPT request modes

Manual impression counting for banner ads in mobile apps

By default, DFP counts an impression each time a creative is sent to a mobile app, but there is also the option to control impression counting for banners by using the manual impression counting feature of the Google Mobile Ads SDK, which utilizes delayed impression counting.

Manual impression counting (2:50)
Manual impression counting is compatible only with creatives trafficked directly in DFP. It should not be used when requesting ads to ad units that can serve backfill, such as Ad Exchange, AdSense or AdMob, or ads from third-party networks, including SDK mediation.

If your DFP-trafficked creative has first- or third-party impression tracking pixels, those will be triggered independently of the manual impression action. This can lead to big discrepancies between DFP impression reports and third-party numbers.

Interstitial impressions in mobile apps

DFP counts an impression when the interstitial is shown to the user, not when a creative is served from DFP. If an interstitial request is made and DFP sends the creative to the app, but the app never shows the interstitial, an impression isn't counted.

Counting clicks

When a user clicks on an ad creative, a click request is sent to the DFP ad server. DFP counts a click as soon as it receives the click request and then sends the user the defined click-through URL. Note that DFP counts the click when it's received, not when the user is redirected to the click-through URL.

Filtering invalid impressions and clicks

DFP discards impressions and clicks that are considered invalid. Learn more about DFP invalid traffic detection and filtration methodology

Was this article helpful?
How can we improve it?