Events
Custom Event
event
Released in version 1.92
Definition: Add any user or system behavioral event to the Datazoom data stream. Requires custom coding on the page or in the app by customer developer.
Use Case
Record that a user entered a comment on the video during playback. Capture a button from outside the player that was pressed by the user during video playback.
Technical Name: {custom_event_name}
Applicable for: Ad, Content, Live, VOD
Node Location: event.type
Datazoom Loaded
event
Released in version 1.89
Definition: Signifies that the Datazoom SDK has been loaded and activated. At this point, the video player can be instantiated or custom events can be sent by the application.
Technical Name: datazoom_loaded
Applicable for:
Node Location: event.type
Media Loaded
event
Released in version 1.91
Definition: Fired when the video is fully loaded into the player & ready to begin playback.
Use Case
Part of the startup sequence of video playback so you can identify time taken to complete each step.
Technical Name: media_loaded
Applicable for: Content, Live, VOD, Ad
Node Location: event.type
Media Request
event
Released in version 1.91
Definition: Event signifies the video player requests the video from the server. The could be triggered by the user clicking on a play button of a thumbnail. If the video is played automatically, this may be fired when the player starts loading.
Use Case
Identify problems that may be occurring in the video player which prevent successful playback after a user requests a video
Technical Name: media_request
Applicable for: Content, Live, VOD, Ad
Node Location: event.type
Pause
event
Released in version 1.91
Definition: Pause event is fired when the player enters a paused state. This can be triggered when the user hits the Pause button to temporarily halt video playback or it can occur as part of the player's normal state changes as media is loading, resuming or concluding.
Technical Name: pause
Applicable for: Content, Live, VOD, Ad
Node Location: event.type
Rendition Change
event
Released in version 1.91
Definition: When the Player's Adaptive Bitrate Streaming upshifts or downshifts during Content Playback to a different quality level available in the manifest. This event includes absShift attribute identifying the direction of the change.
Use Case
How often does an video change quality during playback due to network bandwidth conditions?
Technical Name: rendition_change
Applicable for: Content, Live, VOD, Ad
Node Location: event.type
Seek Start
event
Released in version 1.92
Definition: This event records when the user interacts with time controls within the player to move forward or backward in the video timeline. It can be triggered by dragging the scrub bar or auto advancing using controls exposed by the app.
Use Case
Count the number of times users choose to seek to another part of the video.
Technical Name: seek_start
Applicable for: Ad, Content, Live, VOD
Node Location: event.type
Seek End
event
Released in version 1.92
Definition: Event is fired when the player stops moving the playhead position to jump to a specific point on the timeline. This event includes attributes Seek Start Point & Seek End Point to mark the starting & ending points of a seek event.
Use Case
Determine what parts of a video were skipped over or re-watched frequently.
Technical Name: seek_end
Applicable for: Ad, Content, Live, VOD
Node Location: event.type
Event Attributes
ABS Shift
metadata
Released in version 1.91
Definition: Describes the direction of the rendition change that occurred during Adaptive Bitrate Streaming. Values ‘up’ or ‘down’ depends on the value of the previous rendition. 'absShift' is an attribute of the Rendition Change event.
Use Case
Monitor how often the video player is downshifting video quality to account for network conditions.
Technical Name: abs_shift
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: event.attributes
Permitted Values: value list
Example Value: up
Value List: up, down
Error Code
metadata
Released in version 1.92
Definition: Error object representing a code explicitly identified by the player
Technical Name: error_code
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: event.attributes
Permitted Values: any
Example Value: 1001
Message Metadata
Configuration ID
metadata
Released in version 1.89
Definition: Datazoom Collector configuration ID. Allows customers to differentiate data on the Connector from different Collectors. This could be useful for separating test content from production data.
Technical Name: configuration_id
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: root
Permitted Values: UUID
Example Value: 3bba4192-8105-4498-ae34-587154d56fa6
User Details
App Session ID
metadata
Released in version 1.92
Definition: Unique identifier for the user's current Datazoom session. Session will persist as long as the user is viewing content uninterrupted. A 20 minute pause in activity will close the session.
Use Case
This is the primary identifier for grouping events generated by Datazoom for analysis and unique user counts.
Technical Name: app_session_id
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: user_details
Permitted Values: any
Example Value: 43DHE-EROILKER-EREOATE
Client IP Address
metadata
Released in version 1.92
Definition: IP address of the user's device
Technical Name: client_ip
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: user_details
Permitted Values: IP address
Example Value: 173.19.65.222
Content Session ID
metadata
Released in version 1.92
Definition: A unique id for the current video playback session.
Technical Name: content_session_id
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: user_details
Permitted Values: UUID
Example Value: 3bba4192-8105-4498-ae34-587154d56fa6
Device
Device ID
metadata
Released in version 1.89
Definition: Unique identifier of the user's device.
Use Case
This can be used as a proxy for User if user is anonymous.
Technical Name: device_id
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: device
Permitted Values: any
Example Value: 93fb4310be52415e
Device Name
metadata
Released in version 1.89
Definition: Name of the device model used by the viewer.
Technical Name: device_name
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: device
Permitted Values: any
Example Value: iPad Mini 4
Device Type
metadata
Released in version 1.91
Definition: Describes the type of device category being used during the session such as phone, tablet, desktop, connected device, game console, etc.
Use Case
Can be used to group attributes by device platform type for better understanding of app performance on different platforms.
Technical Name: device_type
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: device
Permitted Values: value list
Example Value: pc
Value List: pc, mobile, tablet, ott device, tv, game console, wearable
OS Name
metadata
Released in version 1.89
Definition: Operating System of the user's device
Technical Name: os_name
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: device
Permitted Values: any
Example Value: OS X
OS Version
metadata
Released in version 1.89
Definition: Version of Operating System being used during the session
Technical Name: os_version
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: device
Permitted Values: any
Example Value: 10.14
Video
Media Type
metadata
Released in version 1.91
Definition: Specifies whether the event relates to an Ad or Content asset.
Technical Name: media_type
Applicable for: Ad, Content, Live, VOD, Ad
Field Type: string
Node Location: video
Permitted Values: value list
Example Value: Ad
Value List: ad, content
Location
City
metadata
Released in version 1.89
Definition: The city or town where the user is located
Technical Name: city
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: geo_location
Permitted Values: any
Example Value: Santa Rosa Beach
Country
metadata
Released in version 1.89
Definition: Full name of the user's country
Technical Name: country
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: geo_location
Permitted Values: any
Example Value: United States
Country Code
metadata
Released in version 1.89
Definition: The country from which the browser initiated the event. For a list of country codes, see ISO 3166-1 alpha-2 .
Technical Name: country_code
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: geo_location
Permitted Values: 2 letter code
Example Value: US
Latitude
metadata
Released in version 1.89
Definition: Location information for the user
Technical Name: latitude
Applicable for: Ad, Content, Live, VOD
Field Type: number
Node Location: geo_location
Permitted Values: any
Example Value: 30.3659
Unit: degrees
Max Decimals: 4
Scale: -90 .. 90
Longitude
metadata
Released in version 1.89
Definition: Location information for the user
Technical Name: longitude
Applicable for: Ad, Content, Live, VOD
Field Type: number
Node Location: geo_location
Permitted Values: any
Example Value: -86.2458
Unit: degrees
Max Decimals: 4
Scale: -180 .. 180
Postal Code
metadata
Released in version 1.89
Definition: The specific administrative division within a country where the event occurred. In the United States, zip codes correspond to postal region locator
Technical Name: postal_code
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: geo_location
Permitted Values: any
Example Value: 32459
Region
metadata
Released in version 1.89
Definition: The specific administrative division within a country where the event occurred. In the United States, regions correspond to state names ; for example, Washington or New York.
Technical Name: region
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: geo_location
Permitted Values: any
Example Value: Florida
Region Code
metadata
Released in version 1.89
Definition: The specific administrative division within a country where the event occurred. In the United States, regions correspond to state codes ; for example, WA or NY.
Technical Name: region_code
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: geo_location
Permitted Values: 2 letter code
Example Value: FL
Network
ASN
metadata
Released in version 1.92
Definition: Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end-user. Client ASN as determined from a lookup of the client IP
Use Case
ASN is a proxy for the customer's ISP which can be used for analyzing usage by ISP to identify problems that might be related a specific part of the ISP infrastructure.
Technical Name: asn
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: network
Permitted Values: any
Example Value: AS30036 Mediacom Communications Corp
ASN Org
metadata
Released in version 1.92
Definition: The organization that owns the Autonomous System Number. Often an ISP, sometimes a private company or institution.
Use Case
ASN is a proxy for the customer's ISP which can be used for analyzing usage by ISP to identify problems that might be related to the ISP
Technical Name: asn_org
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: network
Permitted Values: any
Example Value: MEDIACOM
ISP
metadata
Released in version 1.89
Definition: Name of the end-user's internet service provider.
Use Case
Can be used for analyzing usage by ISP to identify problems that might be related to the ISP
Technical Name: isp
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: network
Permitted Values: any
Example Value: Mediacom Communications Corp
Page
DZ SDK Version
metadata
Released in version 1.91
Definition: Version number of the Datazoom SDK that generated the event message.
Use Case
Used for troubleshooting data issues or isolating data differences stemming from alternate versions of the SDK used.
Technical Name: dz_sdk_version
Applicable for: Ad, Content, Live, VOD
Field Type: string
Node Location: page
Permitted Values: Any
Example Value: 1.40
Custom
Custom Metadata
metadata
Released in version 1.92
Definition: Customers can add any user or system data to the Datazoom data stream. Requires custom coding on the page or in the app by customer developer.
Technical Name: {custom_metadata_name}
Applicable for: Ad, Content, Live, VOD
Node Location: custom
Permitted Values: any
|
Comments
0 comments
Article is closed for comments.