Avoid undisplayed requests in Single Request Architecture (SRA)

This article describes a common pitfall when implementing Google Publisher Tags (GPT) in Single Request Architecture (SRA). It explains the consequences of this problem and how to avoid it.

Causes

When using GPT in Single Request Architecture, a common pitfall is to define more ad slots on your page than are actually displayed.

Consequences

  • The following warning appears in the Google Publisher Console:

    [ad slot name] : googletag.defineSlot was called without a matching display call

  • Omitting a display call prevents an ad from serving, causing you to miss an opportunity to serve impressions and earn revenue.

  • Since Ad Manager only accepts a maximum of 30 slots per SRA request, any slots that you define but not display may put you over this limit, causing additional ad slots to remain unfilled.

Troubleshooting

  • Using the Google Publisher Console, inspect your pages and ensure there are no warnings of the following form on the “Page Request” tab of the console:

    [ad slot name] : googletag.defineSlot was called without a matching display call

    Correct implementations display “Page tagged correctly!” instead.
  • If you find such warnings, determine whether a display() call was actually missing and add it if necessary, or remove the defineSlot call for the unused ad slot.
  • In general, if you only call display() on an ad slot under certain conditions, make sure to only call defineSlot in the same cases where you are also using display(). For example, if you have a responsive site, ensure that all the different layouts of your site remain consistent when declaring and displaying ad slots.
Was this article helpful?
How can we improve it?