Skip to main content

Video Delivery

Introduction​

Introduction to Video Delivery

Delivery covers the pipeline from the publically accessible video source, to the delivery of the video experience to the end user's device.

For 3rd party sites, like YouTube and Instagram, their processes should be followed (subject to agreed use).

For Essity hosted video, delivery is carried out using Akamai IMage and Video Manager (https://techdocs.akamai.com/ivm/docs/welcome-ivm)

Engagement​

Reach out to the Digital Marketing Platform Team

Review and Approval​

Follow standard content publishing guidelines at TBD.

Standards and Conventions​

Content is source primarily via Mediabank.

By exception, video hosted locally on a website, may be also leverage Akamai Image and Video Manager as part of the website's overall delivery via Akamai.

Public urls "inherit" the Mediabank publishing structure, namely

media.essity.com/video/ brand / identifier_brand_UUID/identifier_brand_UUID filename-suffix .mp4

Note: there is no concept of localization within the standard url at this time.

Architecture and Design​

Essity​

Delivery is done as follows:

Video Delivery Architecture

  • mp4 and HLS files are published to Azure Object storage
  • which is accessible to Akamai
    • if HLS artifacts, they are serves as static objects
    • if mp4, the are optimized by Akamai Image and Video Manager
  • both types are serves via media.essity.com/video urls
  • upon request of the video player referenced in the html page, loaded on the client device

3rd Party​

TBD

Operations and Support​

Essity​

Video streaming logs from Akamai, are available in NewRelic in Dashboard format.

Platform Team remain responsible for delivery performance.

3rd Party​

TBD