Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Basic Information
    • Demand Tag Name - this should be a user friendly tag name for your own reference.
  • Environments
    • Select the environment(s) where the tag is enabled and allowed to deliver ads.
  • Tag Type
    • VAST – LKQD accepts VAST 1.0, 2.0, and 3.0 tags.
    • VPAID – LKQD accepts VPAID 1.0 and 2.0 tags.
    • LKQD - Platform Connection tags. For more information, please see: LKQD Platform Connections
    • Hosted - LKQD hosted assets.
  • Ad Delivery Type
    • Guaranteed - Any tag that is guaranteed to return an ad for 100% of ad requests (typically a direct ad buy).
    • Non-Guaranteed - Any tag that is not guaranteed to return an ad for 100% of ad requests.
  • Tag Weight
    • Weight determines the chances of this tag being selected for ad serving, when multiple tags of the parent deal are eligible.  Keep weight of all tags at 100 for even delivery.  Tag weight is only available for Ad Delivery Type 'Guaranteed'. 
  • Start & End Dates
    • To enable flight dates:
      • Click the 'Custom' button.
      • Select the time zone.
      • Select a start and end date.
  • Status
    • Active – the tag is eligible for delivery.
    • Inactive – the tag is not eligible for delivery.
    • Testing – the tag is not eligible for delivery except on the tag test page.
    • Complete - delivery is fulfilled.  This automated status will be applied when a Demand Tag reaches an applied Overall Delivery Cap. 
  • Demand Tag URL
    • Input the tag and add any macros required.
    • For more information on macros available, please see: Adserver Macros
    • For common 3rd party tag templates with macros already placed, please see: Demand Tag Templates
    • Supports SSL
      • If your demand tag supports SSL via protocol relative responses, leave the Supports SSL box checked. 
      • If your demand tag does not support SSL or protocol relative responses, uncheck the Supports SSL box.
        • Non-Secure: Input the Demand Tag URL that should be used for non-secure requests.
        • Secure: If a separate tag was provided by the demand vendor that supports SSL requests, input this alternate URL in the Secure field.  If a secure tag was not provided, leave this field empty, and the Demand Tag will be considered ineligible for secure requests.
  • Required Macros
    • If any of the macros in a Demand Tag are required by the demand source, you can list them (comma separated) in the Required Macros area. The demand tag will only be eligible for delivery if these macros are available.  For macro values that come from publishers (such as 'appname'), please ensure they are being passed correctly.
  • Delivery Caps
    • Click the blue '+' icon to add delivery caps to the Demand Tag.
    • Caps can be added for any of the ad events in the 'Event' drop down.
    • Remove caps by clicking the red '-' icon.
    • For more information, please see: Delivery Caps
  • Frequency Caps
    • Select to cap by User ID or IP Address.
    • Click the blue '+' icon to add frequency caps to the Demand Tag.
    • Caps can be added for any of the ad events in the 'Event' drop down.
    • Remove caps by clicking the red '-' icon.
    • For more information, please see: Frequency Caps

Targeting

AnchorBehavioral TargetingBehavioral Targeting 

  • Audience Targeting 
    • By default no audience targeting is applied.
    • To target specific segments:
      • Click on the + Profile button
      • Select a segment from the Available Segments list.
      • Select a Targeting Profile setting for your segment.
        • Single Device - Target a single user device.
        • Cross Device - Target a user across devices.
      • If more than one segment is applied, select a relationship type for the segments (AND or OR).
      • To remove a segment, click the red "X" icon from the Applied Segments list.
      • Click Apply Profile to apply the profile to your demand tag.
      • If required, create a second profile by clicking the + Profile button again and following the previous steps above. 
      • If a second profile is applied, apply a relationship between the Profiles (AND or OR).
    • All audience data is provided by third party vendors and contains a CPM fee. By enabling Audience Targeting you will pay the applicable fee for every impression delivered against it.
    • Not all data segments will overlap with your users so be conscious of targeting granular segments or small pools of users.
  • Browser Targeting
    • By default all browsers are eligible.
    • To target specific browsers or browser versions:
      • Choose Include or Exclude from the Targeting Type drop down.
      • Click the blue "+" icon to add a new line item
      • Choose your browser or browser version selections.  
    • Click the red “-“ icon to remove a targeted browser.
  • Connection Type Targeting
    • By default all connection types are eligible.
    • To target specific connection types:
      • Choose Include or Exclude from the Targeting Type drop down.
      • Click the blue "+" icon to add a new line item
      • Choose your connection type selections.
    • Click the red “-“ icon to remove a targeted connection type.
  • Custom Parameter Targeting
    • By default all custom parameter values are eligible.
    • To target specific custom parameter values:
      • Click into the custom parameter (Custom 1, Custom 2, Custom 3) that you would like to target.
      • Select to include or exclude selected entries.
      • Enter values via CSV upload or as newline/comma-separated values in the "Add Values" text field.
      • From the "Add Values" field, highlight the entries you would like apply targeting against.
      • Click the "Add" button.
    • To return to the targeting screen click the "All Custom Parameter Targeting" link.
  • Device / OS Targeting
    • By default all environment specific devices (i.e. for mobile: Smartphones, Tablets) and all environment specific operating systems (i.e. for mobile: Android, iOS) are targeted.
    • To target specific devices, operating systems, and/or operating system versions:
      • Choose Include or Exclude from the Targeting Type drop down.
      • Click the blue "+" icon to add a new line item
      • Choose your Device and/or OS selections.  
        • If choosing to target an OS, users can also specify operating system versions that they want to target.  
        • To do so choose an operator (=, >, <, >=, <=) and a operating system version.
      • Click the red “-“ icon to remove a device / operating system targeting.
  • Geo Targeting
    • Please view Geo Targeting for information on how to apply geo targeting.
  • Player Size Targeting
    • By default all player sizes types are eligible.
    • To target specific a specific player size:
      • Choose either 'Declared', to use the publisher declared player size, or 'Detected', to use the LKQD detected player size.
        • VPAID is required in order to detect the player size.
        • If 'Detected', choose whether to 'Restrict' supply requests where the player size is not detectable, or to use the declared player size instead ('Use Declared').
      • Choose Include from the Targeting Type drop down to enable player size targeting.  
      • To define a player size rule either:
        • Choose a LKQD defined player size from the Player Size drop down menu (Small, Medium, or Large)
        • Choose 'Custom' from the Player Size drop down to create a custom rule.
        • Click the blue "+" icon to create a custom rule.
          • Choose an operator (=, >, <, >=, <=), width, and height to target.
    • Click the red “-“ icon to remove a targeted player size rule.
  • Supply IVT Filter Targeting
    • LKQD IVT % allows users to specify the maximum LKQD IVT % Supply Sources may have to be eligible for this Demand Tag. All Supply Sources with LKQD IVT % greater than the threshold will not be eligible.  Values must be whole numbers between 0-100.
    • Minimum Days Live allows users to specify the minimum number of days Supply Sources must be live before being eligible for this Demand Tag (this ensures that IVT vendors have had a chance to analyze Supply Sources).  Values must be whole numbers between 1-4.
  • Supply Tag Targeting
    • The 'Supply Tag Targeting' option adds the ability to target Demand Tags to specific types of Publisher inventory based on the 'Tag Type' the Publisher uses (ex. VAST vs VPAID).  
    • To target a specific Supply Tag Type: 
      • Choose Include or Exclude from the Targeting Type drop down.
      • Choose an option from the Tag drop down. 
      • If another Tag selection is required, click the blue "+" icon and select another option from the Tag drop down.
  • Viewability Targeting
    • To target viewable* inventory, select the desired method (ex. "Realtime") from the Targeting Type drop down.
    • *Viewability targeting is assessed on the initial load of the supply tag.  Viewable impression rate is not guaranteed to be 100% due to time elapsed between the initial supply tag load, ad decisioning, and the impression event.  Use this feature at your own discretion.

...

  • Select (target) the supply sources that the demand tag can run on.  Check the box on the far left to make the tag eligible to run on a supply source.  
  • Only supply sources that are eligible to run on the demand tag's selected environment(s) are listed.
  • Priority
    • Auto - Use this if the Demand Tag does not have specific business rules requiring it to be prioritized over other Demand Tags.
    • Only Look - Use this if the Demand Tag should be the only tag attempted to fill the Opportunity.  Each Supply Source should only have one 'Only Look' Demand Tag at a time. 
    • First Look - Use this if the Demand Tag should always get considered first for ad selection over all other eligible Demand Tags.  Each Supply Source should only have one 'First Look' Demand Tag at a time. 
    • 1-10 - Use the numbered Priorities if the Demand Tag has business rules requiring it to be prioritized over other Demand Tags.  Priority 1 is the highest setting and Priority 10 is the lowest setting.
    • For more information, please see: Ad Selection

Verification

  • Apply 3rd party verification data to your Demand Tag.  

  • In order to access the proprietary reporting data from these third party vendors you must have a contract in place with the vendor and the vendor must be enabled by your LKQD client services representative.
  • To apply, click Enabled and input the desired sample rate.  Sample rates are applied to the Impression metric.

Traffic Filters

WhiteOps Pre-bid Filter - This product will allow LKQD platform partners to utilize WhiteOps' technology to detect invalid traffic in real-time, and block invalid opportunities at the supply source level.  This can also be set at the Account level or Supply Source level (see Supply Management or Account Management respectively).

  • Default - WhiteOps Pre-bid filter settings will be inherited from the Account level or Supply Source level.
  • On - WhiteOps Pre-bid Filtering is enabled Supply Sources the Demand Tag is aligned against.

Tracking Pixels

    • Add / Manage 3rd party tracking pixels for ad events.  
      • Click the 'Add Tracking Pixel' to add new tracking pixels.
      • Select the applicable ad event and add the tracking pixel URL.
      • Click the red “x“ icon to remove tracking pixels.