CTV Asset Handling

CTV Asset Handling

Starting Monday, June 24, 2024, there will be a change in how CTV materials will need to be delivered to AdOps.  The change comes because of challenges with assets and the very specific renditions needed for 3p served CTV.

 

What’s new?

For CTV, there should be individual assets per site/deal site for 3p serving.  THIS IS FOR CTV ONLY.

 

Why?

  1. More and more CTV sites/deal sites are requiring specific settings within the CM360 served assets.  Those assets cannot be used across multiple suppliers because of their settings.   The only way around this is to have CTV assets to traffic by site/deal site.  
  2. CTV assets by supplier ensure the proper renditions can be selected for the site/deal site ’s needs and makes sure we can apply 4th party tracking, like Neustar, appropriately. This leads to less back and forth between all of us on tickets.  
  3. Less back and forth = your ticket is completed faster. 

 

What does that mean? 

If you’re running CTV via direct supplier,  you should be providing the CTV assets per site

  • Example:  If you have 3 different CTV video assets and you’re running on 4 different suppliers, there should be twelve video assets provided to AdOps.  You have a 1) green video, 2) a red video, and a 3) purple video (these colors represent different creative concepts for brands).  You’re running CTV on 1) Buzzfeed, 2) NYTimes, 3) ESPN, and 4) Roku .
  • You would provide AdOps with 3 video files for Buzzfeed, 3 video files for NYTimes, 3 video files for ESPN and 3 video files for Roku.  
  • The assets should have the supplier’s name in them in the description area like below:
        • Imaginary Client_Summer Sale_Green CTV Buzzfeed_video_15s
        • Imaginary Client_Summer Sale_Green CTV Roku_video_15s
        • Imaginary Client_Summer Sale_Green CTV ESPN_video_15s
        • Imaginary Client_Summer Sale_Green CTV NYTimes_video_15s

     If you’re running CTV via DSP,  you should be providing the CTV assets per deal site:
    • Example:  If you have 3 different CTV video assets and you’re running on 4 different deal sites vis TTD, there should be twelve video assets provided to AdOps.  You have a 1) green video, 2) a red video, and a 3) purple video (these colors represent different creative concepts for brands).  You’re running CTV on 1) TTD-Washington Post, 2) TTD-dotdash, 3) TTD-disneyplus, and 4) TTD-HGTV.
    • You would provide AdOps with 3 video files for Buzzfeed, 3 video files for DV360, 3 video files for ESPN and 3 video files for Roku.  
    • The assets should have the supplier’s name in them in the description area like below:
        • Imaginary Client_Summer Sale_Green CTV TTD TTD Washington Post_video_15s
        • Imaginary Client_Summer Sale_Green CTV TTD dotdash_video_15s
        • Imaginary Client_Summer Sale_Green CTV TTD disneyplus_video_15s
        • Imaginary Client_Summer Sale_Green CTV TTD HGTV_video_15s

 

Should we provide one set of assets per supplier for all 3p media types?

Heck no! THIS IS ONLY FOR Just for CTV. 

 

 

Note that it’s recommended to review the CTV suppliers you are using with your respective programmatic/buying team to ensure that no one is left off when trafficking, and that you have the accurate number of assets. Staying in lock-step with MKTP in the set-up process will make trafficking and getting live that much easier.  


    • Related Articles

    • HTML5 assets - what good looks like, what bad looks like

      The static backup file cannot be included in the zip ifile for the HTML5 file.  You can receive a zip file with a static in it that also has an HTML5 zip in it. If you try to import the zip file and you get an error, it's because there are files ...

    • IAS on Hulu

      IAS currently does not have a solution to track Viewability on OLV (online Video aka non-CTV/OTT video) tags. It does not have a direct integration either, so below is what we can offer for IAS tracking on Hulu: 1P served video IMG tag solution - Use ...

    • Static Asset QA Tips for Account & PM

      Please review this QA list prior to submitting tickets with static assets to AdOps. Standard/Static Creative QA Checklist  Check the assets are compliant  Asset is the correct file format (jpg, gif, png)  Asset is the correct dimension   Asset is the ...

    • Need a rush request?

      Please make sure the director or group director on your account is emailing Nickki & Julie to request the reprioritization of your ticket. If your account doesn't have a director, the supe may send the email. Requests submitted from anyone else on ...

    • Difference between add, pause and swap when requesting creative updates

      USE THE NOTES COLUMN ON YOUR TRAFFICKING WORKBOOKS TO COMMUNICATE THIS TO ADOPS. You must provide context and clear direction. AdOps will only complete the request as written, so be clear! Add means to add new assets to the currently assigned ...