The publisher domain:

• in case of (mobile) web: the site domain (no http://, no www, no query string parameters)
• in case of app: the app bundle Id

Direct campaign data is approximate as the data for this dimension is sampled.

The authorization status to access app related data, as specified by Apple's App Tracking Transparency (ATT) framework. 

• -1 – ATT Not Supported (for older SDKs that do not recognize ATT)
• 0 – Not Determined
• 1 – Restricted
• 2 – Denied
• 3 – Authorized 

The Id of an audience targeting segment.

Direct campaign and programmatic data is approximate as the data for this dimension is sampled.

The status of the TCF consent string (GDPR):

• -1 – N/A (malformed/invalid)
• 0 – Empty
• 1 – Ok
• 2 – Fallback consent connected TV (more details about the TCF consent string on connected TV devices in chapter "Passing TCF consent signals to Equativ" in Comply with Global Privacy Platform (GPP).
• 3 – N/A (the Consent Management Platform (CMP) which provided the consent string is not a registered member of the IAB Europe's Transparency & Consent Framework)

The size (width and height in pixels) of the RTB creative that won the Equativ auction.

At bid level, the size of the creative that won the auction globally.

The monetization channel:

• RTB – programmatic monetization
• Header bidding – monetization through header bidding
• Direct – monetization through direct campaigns (direct insertions)

The environment type:

• 0 – Web
• 1 – Mobile Web
• 2 – App

The programmatic format type:

• 0 – Display
• 1 – Video InStream
• 2 – Native
• 3 – Video OutStream

The applicability of the GDPR legislation:

• 0 – GDPR does not apply (ad call does not come from EU territory)
• 1 – GDPR applies (ad call comes from EU territory)

The type of Header Bidding mechanism:

• 0 – No Header Bidding 
• 1 – Client Side Header Bidding
• 2 – Server Side Header Bidding

The keywords (keys or key=values) from the publisher site/app that were passed in the ad call. This dimension requires filtering specific keys / key=values (max. 3 keys/key=values).

Direct campaign and programmatic data is approximate as the data for this dimension is sampled.

The Keywords dimension is not compatible with viewability metrics. 

The type of placement for programmatic video ads:

• 0 – No Placement Type
• 1 – In-Stream
• 2 – In-Banner
• 3 – In-Article
• 4 – In-Feed
• 5 – Interstitial/Slider/Floating

The way a video ad is played (start automatically, with/without sound etc.):

• 0 – Unknown
• 1 – AutoPlaySoundOn
• 2 – AutoPlaySoundOff
• 3 – ClickToPlay
• 4 – MouseOver
• 5 – EnterViewportSoundOn
• 6 – EnterViewportSoundOff

The static size of the video player, grouped into the following buckets:

• No size – both player width and player height equal to or less than 0
• Small – Desktop: less than 400x225; Mobile: less than 20% of screen covered
• Large – Desktop: between 400x225 and 1280x720; Mobile: between 21% and 90% of screen covered
• Extra Large – Desktop: greater than 1280x720; Mobile: more than 91% of screen covered
• Not categorized – width between 1 and 49 or height between 1 and 29; any other sizes that do not match with the buckets Small, Large or Extra Large;

A "No size" or "Not categorized" player size indicates a technical or configuration-related problem that requires further investigation. To determine the exact size, use the Video Player Width and Video Player Height dimensions.

The type of deal that won the auction:

• 0 – OpenAuction (i. e. no deal)
• 1 – PrivateAuction
• 2 – DirectDeal
• 3 – ProgrammaticGuaranteed
• 4 – AuctionPackage