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
It's assumed in this example that your primary ad server is
223
223
<ahref="https://admanager.google.com/home/">Google Ad Manager</a> (GAM) and that you are integrated with it
224
224
using the
225
225
<ahref="https://developers.google.com/publisher-tag/guides/get-started">Google Publisher Tag</a> (GPT), so
226
226
we also pass matching active cohorts to GAM.
227
227
</p>
228
228
<p>
229
-
In this example, we use the <code>prebidORTB2FromCache()</code> API to retrieve any targeting data from browser
230
-
LocalStorage, in order to pass it to Prebid.js via <ahref="https://docs.prebid.org/features/firstPartyData.html#segments-and-taxonomy">seller defined audiences</a>. We also call the SDK <code>targeting</code> API
231
-
which will fetch the latest targeting data from our DCN and cache it locally for later use. Since these
232
-
two events happen asynchronously, it's possible that the targeting data passed to GAM is slightly outdated.
229
+
In this example, we use the <code>targetingFromCache()</code> API to retrieve any targeting data from browser
230
+
LocalStorage, in order to pass it to Prebid.js via RTD modules. It also uses <code>targetingKeyValues()</code> to retrieve gam key values and send them to GAM.
233
231
To ensure ad targeting accuracy, it is recommended to call <code>targeting</code> to update the local cache on
234
232
page load.
235
233
</p>
234
+
<p>
235
+
If you want to override GAM targeting you can set localStorage key <code>disableGamTargeting</code> to <code>true</code> before loading the page. This will prevent the SDK from sending any targeting data to GAM.
0 commit comments