> For the complete documentation index, see [llms.txt](https://docs.relevant-digital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevant-digital.com/hb-manager/auction-behavior-and-optimization/ad-refresh-in-hb-manager.md).

# Ad Refresh in HB Manager

This document provides comprehensive guidance on configuring and optimizing refresh settings for Prebid calls in the HB Manager to enhance revenue generation while maintaining a positive user experience.

## Ad Refresh

Refreshing your Prebid calls on your placements in a proper and functional way can generate extra revenue without compromising the user experience. This is why we have added advanced reload functionality to the HB Manager, allowing you to handle, set, and test various refreshing scenarios.

### Recommendations

We recommend experimenting with a few placements at a time to find the right balance for your site. Excessive low-quality refreshes can lead to poor viewability and lower eCPMs, whereas quality refreshes can maximize inventory from your premium placements.

**Read more about what ad refresh is and how you can benefit from it** [HERE](https://blog.relevant-digital.com/header-bidding-management-how-to-get-started-with-ad-refresh?hsLang=en).

### Refresh Settings

{% stepper %}
{% step %}

### Reload Interval in Seconds

This is the number of seconds until the placement is refreshed (if using GAM, the minimum is 30 seconds).
{% endstep %}

{% step %}

### Count Reload Interval By

This defines what should trigger the initiation of the refresh count in seconds. As such, it can be understood how aggressive the refresh policy will be. There are three alternatives to select from:

* **Time Since Loaded**: This will refresh after x number of seconds since it was loaded for the first time.
* **Time Since First Viewable**: This will start the refresh count only when the placement has been viewable for the first time.
* **Time Being Viewable**: This will only count as long as the placement is in view.
  {% endstep %}

{% step %}

### Count the Page as Visible

This defines when the page should be considered for refreshing:

* **When Document is Focused:** If the user's cursor is actively working in the window, the document is considered to be in focus. Pages on another screen, or multiple tabs in the same browser does not count as viewable.
* **When Document is not Hidden:** This option allows for multi-screen ad refreshing, meaning that each visible surface will refresh while non-visible tabs in the same browser will not. This improves viewability for the end-user.
* **Always (no check, not recommended):** This option disregards checks entirely but is not recommended, as it will likely bring down both your viewability and CTR% score significantly.
  {% endstep %}

{% step %}

### Maximum Number of Reloads

This sets the number of times the placement will refresh.
{% endstep %}

{% step %}

### Minimum Viewability % for Reload

Sets how many % of the placement should be in view to qualify for a refresh.
{% endstep %}

{% step %}

### Set CSS Min-Width/Height When Reloading

Activating this option prevents "jumping" effects on reloads, as it will leave the ad slot open during refreshes, avoiding temporary collapses in columns.
{% endstep %}

{% step %}

### Continue Reloading After ad-div Replacement

{% endstep %}

{% step %}

### Allow Updating Settings via postMessage API

This setting is needed if you want to use the refresh filters to filter on creatives.
{% endstep %}

{% step %}

### Refresh if Empty Ad Return

This enables triggering the ad refresh faster if there is no ad returned. Systems like GAM expect a minimum of 30 seconds before triggering an ad refresh when an ad has been served, but if no ad has been rendered, there is nothing preventing a faster refresh.

{% hint style="info" %}
**Please note:** this might cause more “auctions” to be generated; so we suggest that you experiment with caution when using the function, and use the limitations we provide with the feature.
{% endhint %}
{% endstep %}

{% step %}

### Exclude/Include Line Item Types/Advertisers/Orders/Creatives (Only for GAM)

The option to either **include or exclude** specific things in the ad refresh options. If you are using this option, you do not have to utilize the advertiser/order blocking; however, you can combine both if desired.

Please note that enabling GAM real-time imports for HB Analytics is required to map out the line item types effectively.

![](/files/f2c26894b5a159a7e3c940880f44233b9879c86e)

In order to utilise the creative option, you will have to enable the **Allow updating settings via postMessage API,** which can be found in the **Prebid parameters.**
{% endstep %}
{% endstepper %}

### Activation Levels for Refresh

In Yield, you can work with our refresh on multiple levels: global, publisher account, site, placement type and placement. Below the activation on different levels is described in detail.

#### Placement Type Activation

**Path**: HB Management > Global HB management > Placement types > Prebid parameters > Generic Placement Data > Edit Built-in Setting

Setting up refresh settings on the placement type allows you to assign the same functionality to placement types across multiple sites. This is helpful when your sites share a similar structure and have similar repetitive patterns.

![](/files/be0ffeb172f16411daa4aa797494127e099e8bc0)

#### Account Level Activation

**Path**: Publisher Accounts > "Edit" Account settings > Account Prebid parameters > Generic Placement Data > Edit Built-in Settings

Setting up refresh settings at the account level allows you to assign the same functionality to placement types across the sites mapped under this publisher account. This is useful when these sites share a similar structure and have similar repetitive patterns.

![](/files/7b93cf00fd2c90917235ca608bec749c9a2b868d)

#### Website Level Activation

**Path**: Publisher Accounts > "Edit" Account settings > Website level Prebid parameters > Generic Placement Data > Edit Built-in Settings

This option allows for customization of refresh settings at the website level.

![](/files/842a25aeab3b284521406f2ba3c562fb1d7d245e)

#### Placement Level Activation

**Path**: Publisher Accounts > "Edit" Account settings > Open website > Open placement > Edit Built-in Settings

This is ideal for specific placements or if you would like to override any refresh settings that were set up at the higher levels.

![](/files/5fc582a697744b54b8e90137b73c346c3fe3118d)

### How to enable/disable/override ad refresh settings

![](/files/95f864324b087436d0fa8c92628bf5ea8a3e13c6)

#### Don't forget to save your changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.relevant-digital.com/hb-manager/auction-behavior-and-optimization/ad-refresh-in-hb-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.