...
Jira screens other than issue screens – Atlassian only allows us to track in issues screens within Jira and most JSM portal screens.
Areas where tracking cannot currently be loaded:JSM knowledge-base screens
Rapid boards
Jira dashboards
Referrer – We can't get the referrer of the parent frame. In fact, it's worse than that, Atlassian actually block the add-on from knowing the URL of the page in which is it present by using the
referrer-policy="no-referrer"
attribute on their iframes (find out more). This means that we cannot determine where the user was prior to arriving on your Confluence Jira Cloud instance.Source – this is based on a referrer from another domain. As we can't find the referrer, we certainly can't find the source
Search tracking - because we cannot find the URL of the page which the add-on is displayed on, we cannot read the URL of the search query to find out what people are searching for.
Tracking anonymous users – Right now, we can only track logged in users, so we cannot track anonymous users. This is due to a bug in the Atlassian Connect/Jira...
It doesn't work on mobile – Sorry about that, but it seems that Atlassian Connect is not supported on mobile devices right now.
If you want support for mobile apps, vote for AC-2225 or ask Atlassian to do something about it.