I filed a bug back at the beginning of June regarding the 'BeaconElement with a VideoElement' example. You can't seek forward in the example and if you have BeaconElements in parallel with a VideoElement, the seekBar breaks.
The bug was closed and deferred with no fix and a low priority.
So, I know that people must be using BeaconElements to send tracking and analytics info with their videos. Seeing the low priority on the bug means that there absolutely must be a better way to do tracking. Any ideas?
I'm probably missing something very basic but I'm stuck so I'd appreciate any help with this.
Not sure you could call it best practices but i solved this problem by using the mod feature. Its limited to only send messages every n sec but it works a charm.
setup a Timer object to tick every second (1000)
timerTick = new Timer(1000); // check every second
var _sendInterval:Number = 10;
// Using the Modulo function to calulate if c is % by n
if(currentPosition % _sendInterval == 0)
/// send some tracking event
Thanks B3N$MITH for the reply,
I've looked into that solution as well and it does a good job of giving updates.
However, once there are multiple elements (main video, ads, etc) and you only want to track certain ones, it gets hard to keep making workarounds. You can try and insert IF statements to only track when certain traits are blocked but things can get tricky as the player gets more complicated.
I can use it as a temporary solution until BeaconElement starts working as advertised.
Does anyone have a solution that actually uses BeaconElement as intended?