4 years ago
Web: 8.11.10
Fix
Advertising
- Fixed an issue with the GDPR consent management provider where specifically requesting version 1.1 of the
getGDPRConsentData
ledconsentString
to not be populated.
getGDPRConsentData
led consentString
to not be populated.240000
error in Safari.adPlay
event only fired once per VPAID ad pod.skip
is set to 1
in the request when skip is defined in the ad schedule, and 0
when it is undefined.[DEVICEUA]
tracking pixel or __device-ua__
in the ad tag, which sends the user’s device agent. Also added the ad tag support in Google IMA.[PAGEURL]
tracking pixel, which sends the page where the ad is intended to play.[REGULATIONS]
and [GDPRCONSENT]
macros, which tell the ad server if GDPR regulations are being used and if consent has been granted, respectively.[ADSERVINGID]
macro, which adds the AdServingId value to the tracking pixel, which is parsed from the <AdServingId>
node.custParams
block were not being replaced by the correct values.vpaidcontrols: true
.aspectratio
, width
, height
, and stretching
configuration options via the setConfig() API.placement
). The options are: article
, banner
, feed
, floating
, interstitial
, slider
, or instream
. By default, the player will set instream
players to instream and outstream players to article
. These defaults can be overridden to reflect the appropriate placement type.”pauseAds”:
true
in the autoPause
block.jwplayer().skipAd()
with VPAID ads.