The Tour.getEngagement API method is called on every page load (including modals) even if there is no tour widget visible. Shouldn't need to call it this often, instead it should only be used if there's a tour widget visible.
@diosmosis there is no such API. I suppose you mean a different API?
Tour.getEngagement (though it looks like it could be a controller method?). That's what I was seeing.
Didn't look too much into it but I reckon this is only once the dashboard was opened and it contains the default dashboard. And it should only do it after the window was focused again (like moved to another tab and then back). Might not be big of an issue but ideally definitely should be only executed when we're on the dashboard and when the widget is on the dashboard.
That event isn't actually unloaded when switching the page. So it's executed on every page once the dashboard was loaded with the widget.