The current endpoint for analytics callbacks handled by the core plugin is static. The issue is that the data we send to Moodle is only used for the built-in completion. Basically the idea is that we could use the data sent to Moodle for more than just completion, which would mean changes to how we do store the data.

In the future other plugins would then only need to process the data that is already there under the BBB Activity Plugin database. Instead of the need for exposing an endpoint, subplugins will only process the data as it is right now on installation (in the same way BigBlueButtonBN plugin imports recordings), and keep track of those that were processed (in the same way we do with recordings, with the state).