As we spend more and more money with video tracking we need to see the payoff and if it’s leading to extra revenue. All the big platforms have analytics built in but we still want to capture events in Google Analytics or Adobe so we can apply see how they affect conversion rate in this visit or future ones. To do this you need to tap into their JavaScript player APIs and use the API events to push data to your analytics platform. This is a common thing for developers but isn’t always used by technical analysts for implementation.

Here are the following four biggest player APIs:

· Youtube [detailed walk through]
· Wistia(detailed walk through)
· Vimeo
· JW Player

Here is an example of using the youtube API, note sometimes you have to create your own player events for specific metrics based on logic. For example, there is no start video metric but there is a play event and you can check the time when a play event is triggered. So check if the time is 0 when the play is triggered and boom! you got your start event.

Virtually every page-load milestone is contained in the browser's performance.timing object. This includes the following milestones (and more):

- server request time
- redirect start time
- the time the browser starts rendering the page
- the time when the page is interactive to the user
- the time when the page is fully loaded.

Using some pretty simple JavaScript, any of these timestamps can be captured in your analytics tool of choice. You will want to make sure that the values you capture are representative of what your company considers to be the full and accurate view of page load time. A code sample exists on the following blog post that you can adjust in any way that you choose, and then the data made available can be passed to your analytics tool using your tag management system:

http://analyticsdemystified.com/google-analytics/hard-truth-measuring-page-load-time/ (Link 1)

RELATED: Link 1