Publishers have the possibility to pass information to Pubstack regarding a single slot on a given page, by injecting specific fields in the relevant div.
This can for example be useful when a globally-used Pubstack adUnit needs specific config on only a few pages, or when a publisher wants to send specific targeting tied to dynamically injected ads.
Override a slot's adUnitPath
If your slot must have a different GAM adUnitPath than the one that would be applied based on the current configuration (for example, if it must have fewer/more levels than other slots on the page), you have the possibility to override the default GAM adUnitPath by using the field "data-adunitpath" with the following syntax:
<div id="article-top" data-adunitpath="/1234/special/path/article-top">
</div>
Apply slot-level Key-Value targetings
In order to send specific KV targeting to GAM for a single slot on a given page, you have the possibility to add the following field, as many times as necessary: data-ad-$key=$value
For example:
<div id="article-top" data-ad-key1="value1" data-ad-key2="value2">
</div>
Prevent a slot from being monetised
In order to prevent a specific slot from being monetized on a given page, you have the possibility to apply the style "display: none" to the adUnit's div. This will prompt Pubstack to entirely ignore this div for monetisation purposes. The corresponding adUnit will not be monetised, and if it already was, it will not get refreshed.
Note that dynamically removing/adding this style on a given div will prompt Pubstack to dynamically re-activate/deactivate monetisation on the div.
<div id="article-top" style="display: none;"></div>