You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have to be able to differentiate Slot-level customized targeting (we have a PR created that will add this functionality) from Page-level customized targeting, here is an explanation for each one from Google:
* Slot-level customized targeting: You can set custom targeting attributes for individual ad slots on your page. Use .setTargeting to utilize slot-level targeting, as in the Google Publisher Tag samples.
Typically, we recommend using slot-level implementation for customized targeting, as it covers all targeting scenarios (both when the custom targeting is the same throughout the page, and when it varies by individual slots).
* Page-level customized targeting: You can use this to set custom attributes across all ad slots on your page. Use googletag.pubads().setTargeting to utilize page-level targeting, as in the Google Publisher Tag samples.
Page-level targeting allows clients to use less code in their tags and ensures that all ad slots have the same set of custom targeting attributes. For example, clients could set the key-value pair gender=m on all ad slots using page-level customized targeting.
I found that solution but please you are welcome to submit a PR that will implement it in a way that we always call it setTargeting and depending on another parameter we will know if its slot level or page level.
setPageTargeting
is a bit misleading. this could be documented also!The text was updated successfully, but these errors were encountered: