Global Parameters GET Flashcards

1
Q

nw

A

Required? Yes. Distributor’s FreeWheel network ID.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

resp

A

Required? Yes. Response format. Valid values include:ad: return ad creative directly. This is the default.smrx: SMART XML. FreeWheel proprietary ad response format.xml: same as “smrx”.json: FreeWheel proprietary JSON response format. Structurally the same as SMART XML.vast2: VAST 2.0 format. When use this value, also add crtp=vast2s in the global parameters section.vmap1: VMAP 1.0 format.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

prof

A

Required? Yes. Player profile. Specifies which types and formats of ads can be returned in this player environment. It’s pre-configured by FreeWheel.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

csid

A

Required? Yes. Custom site section ID. Indicates “where” the video is played.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

caid

A

Required? Yes. Custom content video asset ID. Either asid and caid is required for video asset requests. Indicates “what” video is being played.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

asid

A

Required? Yes. FreeWheel numeric Asset ID. Either asid and caid is required for video asset requests. Recommend to use caid since it is more human readable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

asnw

A

Required? No. Asset Network ID. If not present will default to nw value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

ssnw

A

Required? No. Site Section Network ID. If not present will default to nw value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

vdur

A

Required? No. Content video duration in seconds. Usually used to match Commercial Break Patterns. It’s recommended to put the actual video duration here, otherwise ad server will use the ingested duration value of the video asset.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

pvrn

A

Required? Yes. Page View Random. A random number generated per page view. It is required for forecasting system to work properly. Rule of thumb: when csid changes, generate new pvrn.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

vprn

A

Required? Yes. Video Player Random. A random number generated per video instance (re-randomize on a new video play even on the same page). It is required for forecasting to work properly. Rule of thumb: when caid changes, generate new vprn.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

flag

A

Required? No. Turn on/off any Capabilities (a.k.a flags) supported by MRM ad server, in the format of “flag=+flag1-flag2+flag3”, “+” means to turn on and “-“ means to turn off. Refer to HTTP GET Ad Request: Capabilities (Flags).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

metr

A

Required? No. Default metrics of all ads for this request. It’s a bitmap representing whether this integration supports some pre-defined metrics like clickable, pausable, mutable, etc. For example the first bit of metr value stands for quartile, so if it’s turned on, this request is considered “can report quartiles”, and all impressions from this request will counted against the number of “impressions that CAN report Ads Quartiles” in reporting system. If it is Not an AdManager integration, please make sure to set the metr parameter explicitly in the ad request. A few common seen values of “metr” include: 0: it means the ads can send impressions and click callbacks. 7: the ads can send impressions, 4 quartiles and click callbacks. For backward compatibility reasons, 1 works the same as 7. 1024: the ads can send impressions but can’t send click callbacks. 1031: the ads can send impressions and quartiles, but No click callbacks. For backward compatibility reasons, 1025 works the same as 1031. 1023: the ads can support all IAB metrics including impression, click, mute/unmute, expand/collapse, pause/resume, rewind, accept-invitation, close, minimize. “metr” is a complex part of MRM system. Please don’t hesitate to consult FreeWheel for the proper value to set in your integration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

afid

A

Required? No. Video asset fallback id. A FreeWheel video asset id when the video asset id in ad request is Not recognized. Note this needs to be a “FreeWheel id”, which is all digital. It is Not a custom id.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

sfid

A

Required? No. Site section fallback id. A FreeWheel site section id when the site section id in ad request is Not recognized. Note this needs to be a “FreeWheel id”, which is all digital. It is Not a custom id.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

vip

A

Required? No*. End user IP address. It’s optional if the request comes directly from end user, as FreeWheel ad server will get the IP address from http request. But if all requests to FreeWheel servers come from some other servers, this parameter is required.

17
Q

vclr

A

Required? No*. Custom visitor caller. Equivalent to the visitor/@caller attribute in XML request. It’s recommended to pass the app name and version information in this parameter. For example, FreeWheel Flash AS3 AdManager sets it to a string like “AS3-5.11.0-r10315-1312100615”, which is in the format of “[Platform]-[Version]-[Revision]-[Build Timestamp]”.

18
Q

vcid

A

Required? No. Custom visitor ID. Equivalent to the visitor/@customId attribute in XML request. https://hub.freewheel.tv/pages/viewpage.action?spaceKey=MUG&title=Custom+User+IDs

19
Q

vcid2

A

Required? No. Replaced by the reserved key _fw_vcid2. The param “vcid2” still works but is Not recommended. https://hub.freewheel.tv/display/MUG/Custom+User+IDs

20
Q

mode

A

Required? Required for live. Request mode. Valid values are: “on-demand”: default value. “live”: indicates this request is for live mode. Lots of live mode related behaviors will be activated.

21
Q

vdty

A

Required? Required for live. Video asset duration type. Valid values are: “exact”: if the content video duration is kNown as an exact value. “variable”: if the content video duration is unknown or can change. In live mode this type should be used, and “vrdu” should be used to specify the content video duration this request is to cover.

22
Q

vrdu

A

Required? Required for live. Video request duration, integer in seconds. This value replaces vdur (video duration) in live mode and is used to indicate the amount of time this ad request is to cover. For example, “this request should return enough ads to cover the next 300 seconds, as that’s how long I’ll be waiting before making another ad request.” If you are requesting ads for one immediate ad break, the request duration only needs to exceed the expected break duration.

23
Q

vtpo

A

Required? No. Video time position, integer in seconds. This value indicates the current playhead time of the content. Once it is specified, the “tpos” of temporal slots should be equal or greater than this value.

24
Q

cana

A

Required? No. Specifies candidate ad ids, separated by commas. This will replace any candidate ads. Example: cana=id1,id2,id3,…,idN;