Flags POST

Question 1

synchronizeSiteSectionSlots

Answer 1

Enables history exclusivity across multiple request in one session; The session is defined by the _pr and _vr values in the cookie. When the value pair in the cookie changes, the session changes.

Question 2

expectMultipleCreativeRenditions

Answer 2

Indicates that the player is able to select the best one among multiple creative renditions; asks the ad server to return multiple creative renditions for one ad so that the player can choose the best fit rendition to play; for example, the video ad renderer in FreeWheel SDK selects the best rendition according to the slot aspect ratio, the bitrate and the preference settings in MRM. https://hub.freewheel.tv/display/techdocs/Video+Ad+Rendition+Selection

Question 3

supportsSlotTemplate

Answer 3

Supports Commercial Break Pattern; asks the ad server to generate slots and deliver ads according to the CBP settings; https://hub.freewheel.tv/display/MUG/Commercial+Break+Patterns

Question 4

disableAdUnitInMultipleSlots

Answer 4

By default one ad can be delivered to multiple slots in one ad request. If this capability is turned on, the ad server will not deliver the same ad to different slots.

Question 5

supportsSlotCallback

Answer 5

Indicates that the player supports slot impression and slot end callbacks; Asks the ad server to return the slot impression/end callbacks in the SMRAT response so that the player can fire them when the slot starts/ends. If this capability is turned off, ad server will count avails by impressions, which means avails will only be counted when the slot is filled with ads and won’t be counted when the slot is empty. So it’s not an accurate way to count avail numbers. This way can be used when the player cannot be updated to support sending slotImpression callbacks.

Question 6

requiresAdvancedCallbackUrls

Answer 6

Indicates that the player supports additional IAB callbacks besides impression; asks the ad server to return all IAB callbacks in the response so that the player can fire them when necessary; a list of IAB standard callbacks can be found here, including mute/unmute, pause/resume, expand/collapse, quartiles, rewind, skip, etc. Only one of +/-amcb, +qtcb and +cpcb should appear in ad request. If two or three of these flags appears together, only the last flag will work. Different from other response format, in vast response flag=+amcb is default value.

Question 7

requiresQuartileCallbackUrls

Answer 7

Indicates that the player supports quartile callbacks besides impression. Similar as requiresAdvancedCallbackUrls/amcb, but only ask for quartile callbacks and doesn’t ask for other IAB callback URLs. Only one of +/-amcb, +qtcb and +cpcb should appear in ad request. If two or three of these flags appears together, only the last flag will work.

Question 8

requiresVideoCallbackUrl

Answer 8

Indicates that the player supports video view callbacks in the ad response; asks the ad server to return a video view callback for the specified video asset so that the player can fire the video view callback during the playback of the content video. +exvt and +vicb should not be combined in ad request. If both +exvtand +vicb appear in ad request at the same time, it may result in video views double.

Question 9

skipsAdSelection

Answer 9

Indicates that the ad request is issued merely for the videoView callback; No ad will be delivered in the response.

Question 10

supportsFallbackAds

Answer 10

indicates that the player supports fallback ads in FreeWheel ad response; asks the ad server to return a fallbacks ad (if any) for every ad in the response so that the player can still play the fallback ad when the ad fails to play.

Question 11

recordVideoView

Answer 11

Asks the ad server to implicitly record video view upon every ad request so that the player need not issue video view callbacks by itself Flags +exvt and +vicb should not be combined in ad request. If both +exvt and +vicb appear in ad request at the same time, it may result in video views double.

Question 12

synchronizeMultipleRequests

Answer 12

Enable exclusivity among multiple requests in one session.

Question 13

supportNullCreative

Answer 13

Turn on this capability to support 3rd party tracking url for embedded ads

Question 14

resetExclusivity

Answer 14

Resets exclusivity state for current session

Question 15

supportAdBundle

Answer 15

If turned on, the ad reference node in the SMART response will have an attribute “bundleId” set to distinguish ads from different networks.

Question 16

autoEventTracking

Answer 16

Enables autoEventTracking for inclusion of slotEnd and adEndevents for use by third-party beacons, and network-wide beacons (also known as data provider pingback) configured by your FreeWheel SE.

Question 17

refreshDisplaySlots

Answer 17

Indicates the player needs to refresh display slots according to the refresh settings in the MRM

Question 18

supportSlotInfo

Answer 18

Asks ad server to output maxAdDuration, maxAds and maxDurationattribute to node in the SMART response

Question 19

autoPlay=”true”

Answer 19

autoPlay is not a capability; indicates if content is played automatically. (for more on autoPlay, go here: Flags in Non-Temporal (Display) Ad Slots)

Question 20

unattendedPlay=”true”

Answer 20

unattendedPlay is not a capability. Indicates if user is NOT aware of the auto playing. It takes effect when autoPlay=”true”. Detail can be found here.

Question 21

requiresCompleteCallbackUrls

Answer 21

Indicates that player supports complete callbacks besides impression. Ad server will return complete callback in response and player can fire it. Only one of +/-amcb, +qtcb and +cpcb should appear in ad request. If two or three of these flags appears together, only the last flag will work. is not supported in HTTP POST ad requests.

Question 22

checkTargeting=”true”

Answer 22

Used with “cana”. When cana is enabled, adserver will not check targeting for the candidate ad by default. Specifying “flag=+targ” reenables adserver to check targeting for the candidate ad.

Question 23

disableTrackingRedirect

Answer 23

If this flag is NOT included in an ad request to FreeWheel, 3P impression URLs will be content redirects on the equivalent FreeWheel impression URL. For example, a 3P defaultImpression URL will be a content redirect on the FreeWheel defaultImpression URL like this (the 3P beacon shows after the cr= parameter): If this flag IS included in an ad request to FreeWheel, 3P impression URLs will no longer be a content redirect on the equivalent FreeWheel impression URL. Instead, the 3P impression URLs will now be split out into their own unique tracking URL like this:

Question 24

supportCreativeParametersInVast

Answer 24

Enables creative parameters to be returned in VAST responses.