The User has a time restraint on the video so there is a table that keeps this information along with the unique identifier for the User themselves.
id
video_uuid
user_uuid
available_from
available_to
Table data like so (example):
420
fdgdfg-sdfsd-3453-4535
assas–asasa-sasas-aqsasas
2024-03-14 00:00:00
2024-03-15 00:00:00
Then a views table which holds each view of the video as the User may need more than one viewing over their allotted time period (say the connection drops or another issue):
id
video_uuid
user_uuid
Each time the video is viewed this table receives an update (new record) with the User and video identifiers.
We use an Action to count the results based on the User and the video matching. If the count is less than 3 than show the video, if 3 then display a not available message (using a Conditional Region), and use the available from and available to (filter between) to dictate if the video is shown or not…
Something like that or there about.
Will try to explain more if you need me to tomorrow. I don’t, or rarely, drink. My 85 year old neighbour invited me around to share a cup with him which I could not refuse. Thus I’m a little skew-whiff right now if I’m honest!