Right now the mod_h5pactivity send all attempt tracking data at the end of the activity.

The H5P player can send xAPI statements every time the user interacts with the content and the activity can store them before finishing.

The main difficult is that during the activity only some statements are posted and only in the end the player will send the full tracking information. The activity should decide the best way to handle attempts this way and avoid repeated tracking information by rejecting repeated xAPI statements.