Integrate with a Content Security Policy

Content Security Policy (CSP) is a means of securing your web page by limiting what resources and scripts are allowed to load and execute. You can enable CSP by setting a Content-Security-Policy header in HTTP responses from your web server.

There are two standard ways to configure CSP:

  1. Specify an allowlist of domains that can inject their resources on the page.

  2. Specify a random nonce, with which resources on the page must be marked in order to load. This approach is known as strict CSP.

Because the domains that Google Publisher Tag (GPT) uses change over time, we only support strict CSP (option 2). This approach removes the need to maintain a rolling list of domains that might become outdated and break your site.

Setting up CSP with GPT

  1. Enable CSP on your web server.

    Follow the steps outlined in adopting strict CSP to set up the CSP header and apply the nonce to every script tag on your page, including gpt.js. GPT specifically supports the following CSP directives:

      object-src 'none';
      script-src 'nonce-{random}' 'unsafe-inline' 'unsafe-eval' 'strict-dynamic' https: http:;
      base-uri 'none';

    You can choose a more permissive policy if it fits your use case. More restrictive policies may break without notice.

  2. Enable cross-domain rendering.

    Ad iframes can load external resources that might not be permitted by the CSP. Since same domain iframes inherit the top level window's CSP, and GPT cannot control the creative’s contents, same-domain creatives will generally not work properly with CSP headers.

    To enable cross domain rendering for all creatives, execute googletag.pubads().setForceSafeFrame(true) before loading any ad slots.

    <!doctype html>
        <meta charset="utf-8">
        <title>Hello GPT</title>
        <script src="" nonce="KC7tcz53FHqumKP1" async></script>
        <script nonce="KC7tcz53FHqumKP1">
          window.googletag = window.googletag || {cmd: []};
          googletag.cmd.push(function() {


We recommend that you test your policies first by setting the Content-Security-Policy-Report-Only header instead of Content-Security-Policy. The header reports violations but still allows them on the page.