Hi guys, we are new to Snowplow, but very excited to start using the platform. We have an use case that we’d like to validate for using with Snowplow.
Imagine we have a front-end app sending events to the server every 3 seconds while certain content is being displayed on the screen - like a pulse/heartbeat. Depending on the size of the content (which we know in the back-end), we need to wait for X heartbeats until we consider enough time has passed for the content to be properly “viewed”.
So, basically, if the video has 60 seconds, we’d need to see about 20 heartbeats to consider it “watched”.
We used to do this in Dataflow, but now we are considering moving the whole thing to Snowplow.
What we thought was to create an “enrichment” API that Snowplow would call for each beat and the API would have its logic to decide whether the content has been consumed or not. Does this architecture make sense? Still seems like we are missing something.