disableInitialLoad deprecated: What every Publisher must do now

With disableInitialLoad deprecated by Google, publishers running header bidding need to pay attention. But this is not an isolated change. Google has deprecated over a dozen legacy methods in the Google Publisher Tag (GPT) library as part of a migration to a new unified configuration API. The legacy calls still work today, but they will be removed in a future GPT release. The exact sunset date has not been announced, which makes now the right time to prepare.

What does disableInitialLoad() do?

By default, calling googletag.display() on an ad slot triggers three things at once:

1. Registers the ad slot
2. Sends an ad request to Google Ad Manager
3. Renders the returned creative

This is a problem for publishers using Prebid or other header bidding technologies. The wrapper needs time to collect bids before the ad request goes to GAM. If GPT fires instantly, bid data never reaches the ad server and the publisher loses revenue.

disableInitialLoad() fixes this by splitting the process in two (see Google’s guide on controlling ad loading):

• display() only registers the slot (no ad request is sent)
• The ad request is deferred until the publisher explicitly calls googletag.pubads().refresh()

This gives the header bidding auction time to complete and attach bid targeting to the slots before GAM sees the request.

Nearly every Prebid.js integration in production today depends on this mechanism. Other common use cases include:

• Holding ad requests until user consent is granted (GDPR/TCF flows)
• Implementing custom lazy loading logic
• Controlling ad loading on single-page applications where slots are defined dynamically

What is changing now that disableInitialLoad is deprecated?

Google is not removing the ability to disable initial load. The feature remains fully supported. What is changing is how you configure it.

As part of a broader migration to a unified configuration API, Google deprecated several legacy PubAdsService methods and replaced them with the new googletag.setConfig() interface. Now that disableInitialLoad is deprecated, the old method call no longer represents best practice.

Similarly, the companion check method has changed:

• Old: googletag.pubads().isInitialLoadDisabled()
• New: googletag.getConfig("disableInitialLoad")

The legacy methods still work today. Behind the scenes they already route through the new config framework. But Google has stated they will be removed in a future GPT release. No specific date has been announced, and Google does not typically publish sunset timelines far in advance.

It is not just disableInitialLoad: other deprecated GPT methods

While disableInitialLoad is deprecated and gets the most attention from header bidding publishers, Google has deprecated over a dozen other PubAdsService methods in the same migration. Depending on your ad stack, some of these may be equally critical for your setup. The fact that disableInitialLoad is deprecated alongside so many other methods signals that Google is serious about moving the entire ecosystem to the new API.

Here are the most important deprecated methods grouped by what they control:

Ad loading and rendering

• disableInitialLoad() controls when ad requests are sent. Critical for header bidding. Replaced by googletag.setConfig({ disableInitialLoad: true }).
• enableSingleRequest() enables Single Request Architecture (SRA), which batches all ad requests into one call. Important for roadblocks and competitive exclusions. Replaced by googletag.setConfig({ singleRequest: true }).
• enableLazyLoad() enables lazy loading of ads based on viewport proximity. Replaced by googletag.setConfig({ lazyLoad: {...} }).
• collapseEmptyDivs() hides ad slots when no creative is returned. Affects layout stability and CLS scores. Replaced by googletag.setConfig({ collapseDiv: "ON_NO_FILL" }).

Targeting and key-values

• setTargeting() / clearTargeting() manage page-level key-value targeting sent to GAM. Replaced by googletag.setConfig({ targeting: {...} }).
• setCategoryExclusion() / clearCategoryExclusions() manage ad category blocking labels. Replaced by googletag.setConfig({ categoryExclusion: [...] }).
• setLocation() passes geo-location data for line item targeting. Replaced by googletag.setConfig({ location: "..." }).

SafeFrame and rendering controls

• setForceSafeFrame() / setSafeFrameConfig() control whether ads render inside SafeFrame containers. Replaced by googletag.setConfig({ safeFrame: {...} }).
• setCentering() controls horizontal centering of ads. Replaced by googletag.setConfig({ centering: true }).

Video and AdSense

• enableVideoAds() / setVideoContent() configure video ad settings and content exclusions. Replaced by googletag.setConfig({ videoAds: {...} }).
• set() / get() / getAttributeKeys() manage AdSense attributes. Replaced by googletag.setConfig({ adsenseAttributes: {...} }) and googletag.getConfig().

The same pattern applies to slot-level methods on the googletag.Slot object: setTargeting(), clearTargeting(), setCategoryExclusion(), setCollapseEmptyDiv(), setClickUrl(), setForceSafeFrame(), setSafeFrameConfig(), and set() are all deprecated in favour of slot.setConfig().

In every case the underlying feature is preserved. Only the method you use to configure it is changing. The new setConfig() API groups all settings into a single, structured interface, which makes configuration easier to manage and less error-prone.

How does the disableInitialLoad deprecation affect publishers?

Every publisher using header bidding needs to check whether their ad tag still relies on the now deprecated disableInitialLoad method. With disableInitialLoad deprecated, the tag must be updated before Google removes the legacy API. But the audit should not stop there. Any tag using the legacy methods listed above needs attention.

The migration itself is typically a one-line code change per method. But the timing is unpredictable. Google does not pre-announce removal dates, so there is a real risk of missing the window.

Yieldbird Platform is ready

Key takeaways

• Google has deprecated over a dozen legacy GPT methods as part of a migration to the new googletag.setConfig() API. The features remain, only the syntax is changing.
• For header bidding publishers, disableInitialLoad deprecated is the most critical change. Without updating, your Prebid integration will silently break.
• Other commonly used methods like enableSingleRequest(), enableLazyLoad(), collapseEmptyDivs(), and setTargeting() are also deprecated and need the same migration.
• Google has not announced a removal date, but they rarely give advance warning. Audit your tags now.
• If you are a Yieldbird Platform client, we have it covered. All deprecated methods used by Yieldbird Tag are already migrated.