Operations · Videos
See how far each video was watched.
The progress bar always shows the real time, and a minute counts only after the click. Among people who identified themselves, you know who watched and how far. People who did not identify themselves stay anonymous and become a count.
Same login as Analytics. A code arrives in your email; you paste it once. The dashboard is in Portuguese for now.
Why this exists
A play says someone pressed it. It does not say
HOW FAR.
Whether the person left at second three, reached the offer or watched it all, the play count is the same. Here the measure is the minute, and the watched minute starts counting only when someone clicks.
- The count that adds people who left at second three
- Muted autoplay counted as if someone were watching
- The progress bar that does not match the video length
The whole path
Upload, embed, measure, act.
And what happened goes out wherever you want.
1 · Upload
From your computer, from a link, or through your agent.
Uploads can resume and go straight from the browser: MP4, MOV, MKV or WebM, up to 20 GB. You can also give an https link to the file. The video plays as soon as the first quality is ready, and the others are added on their own.
from your computer MP4 · MOV · MKV · WebM
up to 20 GB, resumable
from a link https://…/aula-01.mp4
YouTube, Vimeo and social networks: refused
through the API or the agent
the file never goes through the chat2 · Embed
One script, and the player goes on any page.
The player is ours: a component with Shadow DOM, in plain JavaScript, that does not inherit or break the page CSS. Muted autoplay with "Click to listen", resume where you left off, speed, full screen and keyboard shortcuts. The code points to the video, not to a version: publishing again does not ask you to paste anything.
<script async src="https://videos.worker.myoperations.click/player.js" data-video="<video id>"></script> <!-- or, with the script already on the page --> <videos-player video="<video id>"></videos-player> → plays only on your account's domains
3 · Measure
A minute counts only after the click. Skipping does not count.
Three separate minute measures: delivered, watched and owned. The 7-day and 30-day retention curve shows the chapters and the point of the button, for the whole audience or only for known people.
delivered all time played, with or without sound watched only after the click; skipping does not count owned watched by an identified person milestones 25% · 50% · 75% · 100%
4 · Act
The video does something at the right moment.
A button below or over the video, a page block that appears, a card, an email request (always skippable) or an event. Each action fires at a minute, at the start of a chapter, at a progress point, at the first pause or at the end, once per session.
when minute · chapter · 10–90% · pause · end
does button · block · card · email · event
for everyone · known · anonymous
once per session
the email request can always be skipped5 · Send out
Events go out by signed webhook, wherever you want.
Up to 20 endpoints per account, each with the events it subscribes to, in the Standard Webhooks format. Send a test, rotate the secret, see the history and resend. If the destination fails, it retries after 1 min, 5 min, 30 min, 2 h and 12 h.
video.watched video.cta_clicked video.reached video.converted person.identified video.ready signed: Standard Webhooks, x-ccm headers
Model Context Protocol
Your agent does what the dashboard does. Deleting needs you.
Four light tools do everything the dashboard does: the agent reads retention, who watched and the transcript, creates an upload, edits and publishes the player, generates links with identity and replies to a comment. Deleting happens only after your yes, in the conversation. The whole catalog costs the agent less than 3,400 characters.
The server’s limits
- Approving what the agent asked for is always yours, in the dashboard. The agent reads the request and tells you.
- Deleting only after your yes, in the conversation: the first call only asks and shows what will happen.
- The file through the chat never. The upload tool returns an upload link valid for 1 hour; the file goes from where it is, through that link.
The account comes from the token and never from an argument: a text read by the agent cannot point a tool at another account.
The yardstick
What It Does, and Where It Stops
The limits, stated before you need to ask.
Where the file is stored
In Germany, with a replica in São Paulo
Storing, converting and delivering are done by a video provider. What is ours is the player, the measurement, the video document and the integrations.
Where the video plays
Only on the account’s domains
The domains are checked before the video address is signed, and the signature is valid for 6 hours.
What is counted
Minutes, not plays
Delivered, watched and owned. A play alone does not say how far the person stayed.
Who gets a name
Only people who identified themselves
By link, email, login or purchase. A cold visitor stays anonymous: no fingerprint, no stored IP.
Streaming address
Carries the provider’s name
There is no custom domain in the player or in delivery.
For the agent
MCP, four tools
They do everything the dashboard does; deleting asks for your yes, in the conversation. The full documentation is in this site’s llms.txt.
Pricing
3, 9, 99 or 500 videos
Free to start: 1 video, no card and no time limit. What changes between plans is how many videos the account keeps, and the minutes of each one; the player, retention, transcript, webhooks and the MCP server are in every plan, including Free.
FAQ
The Questions, in the Order They Come Up
Found a limit that is not written here?
Talk directly to the person who wrote the code. If you found where it breaks, we want to publish it before the next visitor finds out alone.
Operations · Videos
The progress bar always shows the real time.
Among people who identified themselves, you know who watched and how far.