For an Heartbeat implementation, if we use Custom Conversion Variables, is it valid to set variable to expire after HIT instead of VISIT?
My hesitation is because there are multiple calls for one media tracking (Start, aa_start, play every 10 seconds, complete), so I am not sure if the "expire by HIT" is dangerous here?
I have a feeling that it is they only call sent to the SC server that is important for Custom Variable, so it would be okay to use Expire by HIT. Would there be problem with the Content Time Spent and Complete metrics?
I would use the processing rules and just set the value to "NULL" in the case information is not available. That way you can over time see when the fix has been applied. But as I see it, both of your options should work. Setting the eVar to expire on hit should work perfectly fine as well.
Yes i am using Custom evars from Video ContextData. The problem is that the solution is inside Native Apps that are already released and I am receiving "no value" for some meta that are not mandatory for each video. So the previous value persist for a second video that has no value for the same evar.
I was wondering if by setting that evar to expire after HIT instead of Visit would be a solution. (Solution #1)
Another solution, would be to keep it to Expire after VISIT, but use Processing rules and put a "NULL" value if the ContextData is not set (Solution #2)
I would prefer doing Solution #1, but I don't know if Evars set to expire after HIT is compatible with Heartbeat implementation
I'm assuming you are going to enable the video reporting for your report suite and have loads of the variables being set as they come out of the box (Video Measurement Parameters ) If you set custom evars as meta variables for your video play, then you just need to remember to set them to "NULL" in the code or else the variable will stay persistent in the code otherwise (documented here: Attaching Custom Metadata )
If you do as above, you wont have to worry about the expiration.