A View Becomes a Step in Someone's Journey
Woopra is built around people rather than pages. It keeps a timeline per visitor and stitches events from each product an organization runs onto it, so the question it answers is what this individual did and in what order, not how many sessions a page had. Video is normally missing from that timeline, sitting in a separate report with a separate owner. Enabling Woopra on a Nexus portal, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, puts what was watched into the sequence with everything else.
How it connects
What is forwarded is playback. Play, pause, seek and completion travel, with quarter-point milestones at 25, 50, 75 and 100 percent, so an abandonment a quarter of the way in reads differently on the timeline from a recording watched to the end.
Those arrive in Woopra as ordinary events, which is what lets them fall into place between a sign-up and a support ticket. How a visitor is recognized is Woopra's own business, decided by the model you already run there. The portal's record of which named user watched what stays in the portal, along with the engagement heatmap, embed locations and playback quality, none of which the forwarded stream carries.
Setup is the account domain. The catalog calls the method a JavaScript widget, meaning client-side instrumentation on the player and the portal pages, switched on by entering the Woopra account domain in portal settings. No tag manager and no code change is involved, the identifier is entered per portal so a customer-facing portal can report while an internal one stays quiet, and the flow is outbound only. Nothing is read back, and the media itself never leaves the portal.
What you can do together
Watching joins the rest of the journey
A recording opened on a Nexus portal appears on the same Woopra timeline as the product and website events around it, in the order they happened.
Tell a finish from a false start
The quarter-point milestones separate someone who watched the whole walkthrough from someone who stopped at the first minute, which is the difference a customer conversation turns on.
Choose which audiences you track this way
The account domain is set per portal, so the portal your customers use can report to Woopra while an internal portal reports nowhere.
Ask the portal what a timeline cannot answer
Where viewers stopped inside a recording, which sites embedded it and how well it played stay in the Nexus reports, alongside content, users, assessments and achievements, exportable as CSV.
A scenario
- Setup, MondayOperations enters the Woopra account domain in the academy portal's settings. The company's internal all-hands portal is left without one.
- Tuesday, 21:10A trial user watches the getting-started walkthrough to the end. The play and all four milestones forward to Woopra and land on the timeline it already keeps for that visitor, between two events from the product itself.
- Tuesday, 21:25She starts the advanced configuration module and stops halfway. Woopra records the 25 and 50 percent milestones and no completion.
- Wednesday, 09:00Her customer success manager reads the timeline before the onboarding call and sees the finished walkthrough, the abandoned module, and the feature she tried in between.
- Wednesday, 09:30To find out where in the module people stop, the education lead opens the engagement heatmap in the portal's own reports, which the forwarded events do not carry, and reorders the first three minutes.
What stays where
Woopra remains the journey record
Events arrive there as they do from any other product, and profiles, retention and access on that account are governed by you in Woopra.
Identity is resolved on Woopra's side
What the portal sends describes playback. Which named user watched is held in the Nexus reports, which continue whether or not tracking is enabled.
Nothing comes back
The connection sends events and reads nothing, so the video, its access rules and its viewers stay in the portal.
Each portal decides for itself
The account domain is entered per portal, so whether a given audience's events reach Woopra at all is the portal owner's choice.
Products and solutions
Next step
See it on your own Woopra 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/woopra