How to add custom fields to Media Analytics to support Media Acceleration

Document created by Alan Green Employee on Mar 17, 2017
Version 1Show Document
  • View in full screen mode

These are the required steps to see accelerated vs non-accelerated stats in the Media Analytics reports:

LUNA Media Analytics Configuration:

  • A custom dimension to reflect ‘Accelerated vs Non-accelerated” traffic needs to be created against your report packs for QoS monitor and Audience Analytics. This can be done in the Media Analytics configuration/provisioning page under “customizations”.  A new custom dimension that matches the “key” used in the “setData” call should be added as the dimension/property name (details in the next step). Please see a mock UI below:
  • Include the above dimension to your report pack by adding them to “Additional Dimensions” under “Enhance Standard Reports”.

  • Check your beacon.xml after an hour or so to ensure that the dimension shows up there.


App Changes -

  • There is a response header called “Quic-Version”. As you can imagine, this would carry the QUIC version negotiated if QUIC was used. You would want to use the presence or absence of this header to set a custom dimension in the code using the setData API call. This should be tracked for each response. Sample pseudo code is below:


// Point in code where you can intercept each response

var quicVersion = getResponseHeader ("Quic-Version");

    if (quicVersion) {


    } else {

      deliveryAcceleration =”Non-Accelerated”;          


return deliveryAcceleration;


//Point in code where in-playback/onProgress callbacks can be made

//Use “key” as “Accelerated_vs_Non-Accelerated” and “value” as value of deliveryAcceleration.

akaPlugin.setData(String key,String value)


This is just a sample. Please change the key and value to anything appropriate.

The above dimension should appear in the QoS and Audience Analytics reports with selected metrics reported separately by “Accelerated” and “Non-Accelerated”.