The Team That Measures the Website Sees the Video
Almost every organization with a website already has a Google Analytics property, and someone whose week is organized around it. Video has usually been the exception to that, counted in a portal report that only the portal's owner opens, which is why a campaign review can describe every page a visitor saw except the one they actually watched. With Google Analytics enabled on a Nexus portal, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, playback events arrive in the property the marketing team already reports from. The property stays yours, and the portal's own reports carry on beside it.
How it connects
Setup is a measurement ID. The catalog calls the method a JavaScript widget, which is client-side instrumentation on the player and the portal pages, switched on by entering the Google Analytics measurement ID in portal settings. There is no tag manager to wire up and no code change, and because the identifier is entered per portal, a public site can report while an internal portal does not.
What travels is playback, not page views alone. Play, pause, seek and completion are forwarded, together with quarter-point milestones at 25, 50, 75 and 100 percent. That is what makes watch-through and drop-off readable in the property itself rather than only inside the portal, because a video someone abandoned at the first quarter no longer looks like a video someone watched.
The flow runs outbound only. Nothing is read back from Google Analytics, the media itself never leaves the portal, and what the property can do with the events is bounded by how your analysts have modeled it there. The platform sends events and does not configure goals or funnels on the far side.
What you can do together
Read the video beside the traffic that found it
Playback from Nexus lands in the same property as the landing page, the campaign and the referral, so one analyst answers what the visit was worth.
Measure watching, not clicking play
The quarter-point milestones distinguish a full view from an abandonment, so a long recording can be judged on how far people got.
Report it with what you already built
The events are ordinary events in your property, available to the segments, audiences and dashboards the team maintains for the rest of the site.
Keep the portal for what the events do not carry
Viewer identity, the engagement heatmap, embed locations and playback quality stay in the Nexus reports, which also cover content, users, assessments and achievements and export as CSV.
A scenario
- ThursdayThe web team enters the city's measurement ID in the portal settings. The internal staff portal is left without one, so its events stay in the portal.
- Tuesday, 18:00The council meeting streams. Residents arrive from the city's news page and from a post that the communications officer scheduled that afternoon.
- Wednesday, 09:15The analyst opens the property she has always used. The plays and the quarter-point milestones for the meeting sit beside the traffic of the page that carried the link, in the same report as the rest of the site.
- Wednesday, laterMost viewers stopped before the halfway milestone on a three hour recording. The office decides to publish short per-item clips of the next meeting rather than only the full stream.
- Month endFor what the property does not hold, the communications lead opens the portal's own reports on content and users, exports the CSV, and takes both numbers to the council briefing.
What stays where
The property stays yours
Events arrive in it as they do from any other page, and the reporting, retention and access on that property are governed by you in Google Analytics.
The portal keeps its own reporting
Nexus continues to report on content, users, assessments and achievements independently, with CSV export, whether or not the tracking is enabled.
The flow is outbound only
Playback events leave, nothing is read back, and the video and its access rules never move.
Configuration lives in portal settings
The measurement ID is entered per portal, so each portal's owner decides which property receives events, or that none does.
Products and solutions
Next step
See it on your own Google Analytics instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/google-analytics