The Journal
Publishers2 Nov 2026 · 4 min read

Serving Scrollabar Through Google Ad Manager: A Publisher's Guide

Learn how to integrate Scrollabar with Google Ad Manager. This guide covers tag implementation, SafeFrame settings, and CSP requirements for publishers.

Integrating new ad formats into a complex stack like Google Ad Manager (GAM) can often feel like a hurdle. This guide provides a clear, step-by-step walkthrough for publishers looking to serve Scrollabar through their existing GAM infrastructure, ensuring a smooth setup without compromising your site performance.

Key Takeaways

  • Scrollabar utilizes a lightweight, single-line script tag for seamless publisher integration.
  • Disabling SafeFrame isolation is a requirement for the ad slot to function correctly.
  • Your page's Content Security Policy (CSP) must explicitly allow connections from https://www.scrollabar.com.
  • All impressions and clicks are tracked and reported in your dedicated Scrollabar publisher dashboard.
  • The format provides a non-intrusive user experience by pinning to the viewport only upon upward scrolling.

Understanding the Integration Process

Scrollabar is designed to be as unobtrusive as possible, both for the end-user and the developer. By pinning to the top of the viewport only when a reader scrolls up, it maintains the integrity of your page layout. When serving this via Google Ad Manager, the process involves standard ad ops procedures but requires two specific configuration changes to ensure the script executes properly within the GAM environment.

The One-Line Script Tag

The foundation of the Scrollabar integration is a lightweight script tag. This script is designed to be efficient, ensuring that load times are prioritized. You simply place this tag within the creative or directly into your site template to trigger the bar's functionality. For publishers using GAM, this script tag functions as the primary delivery mechanism for the campaign.

Managing SafeFrame and CSP Requirements

Google Ad Manager uses SafeFrame to isolate advertisements from the primary page content, which enhances security. However, this isolation layer can sometimes block the interactions required for a dynamic, scroll-dependent format like Scrollabar. To resolve this, you must disable SafeFrame isolation for the specific ad slot hosting the bar.

Disabling SafeFrame

Within your GAM ad unit settings or creative configurations, you will find an option to enable or disable SafeFrame. For the Scrollabar placement, ensure this is set to "disabled." This allows the script to properly interact with the viewport and trigger the pin-on-scroll functionality. Failing to do this often results in the bar failing to appear or failing to respond to user scrolling.

Content Security Policy (CSP)

Modern websites use CSP headers to prevent unauthorized scripts from executing. Because Scrollabar requires resources from its own domain, you must update your site's CSP to allow traffic from https://www.scrollabar.com. Without this allow-listing, the browser may block the ad assets from loading, leading to empty slots.

"Proper configuration of your ad slots not only ensures delivery but also protects your user experience. Always test new ad formats in your staging environment before pushing them to live traffic."

Monitoring Performance in the Dashboard

Once the technical implementation is complete, the focus shifts to data. Every impression and click registered by the Scrollabar format is captured and displayed in your publisher dashboard. This interface provides the transparency needed to evaluate how the format is performing across your various pages and campaigns.

Because the format is highly visible, you may find that it encourages higher engagement compared to static banners. The dashboard allows you to view these metrics in real-time, helping you optimize your placement strategies. You can view live demonstrations of how these formats perform on premium sites by visiting our demo page.

FAQ

Is SafeFrame isolation required for all ad slots?

No, SafeFrame isolation is not mandatory for all slots. You only need to disable it for the specific slot where the Scrollabar script is served to allow it to communicate with the page viewport.

What happens if I forget to update my CSP?

If the CSP does not include https://www.scrollabar.com, the browser will likely block the script's network requests. This will cause the bar to remain hidden, as it cannot fetch the necessary branding and campaign assets.

Can I rotate multiple campaigns in one slot?

Yes, you can rotate multiple campaigns through the same bar placement. The Scrollabar platform is built to handle this logic, allowing you to maximize the revenue potential of that prime screen real estate.

How does Scrollabar handle page layout shifts?

Scrollabar is specifically engineered to never shift your page layout. It pins to the top of the viewport when triggered, meaning the content underneath remains static and unaffected by the presence of the bar.

The Bottom Line

Integrating Scrollabar into your Google Ad Manager stack is a straightforward process when you account for the necessary SafeFrame and CSP configurations. By following these steps, you gain access to a high-engagement, non-intrusive ad format that respects the reader's experience while driving performance. If you have any further technical questions or require assistance during your setup, please reach out via our contact page. We are here to ensure your ad operations run efficiently and effectively.

See the format for yourself

The Scrollabar runs live on recreations of premium publisher layouts — no signup needed.