- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
looking for documentation or other sources to explain some use cases around trackTimedAction(start|update|end).
In particular, looking to understand how it handles non-ideal pairs/sets of timed actions. For example:
- One 'start' event followed by two consecutive 'end' events - does the report show two completions with separate times to complete for the two end events?
- Repeated 'start' events before an 'end' event - does the time to complete calculate against the first start event or does it reset every time a 'start' action occurs?
- 'starts' or 'ends' without any complement - if someone starts but doesn't complete, or gets a completion and somehow skips starting, are those just thrown out?
any insight or advice is appreciated, thanks in advance!
Solved! Go to Solution.
Views
Replies
0 Likes
Total Likes