...
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
Portal Articles – these can be tracked by using Google Analytics in Confluence and filtered by Where content is displayed = JSM Portal
Jira Project Pages – these can be tracked by using Google Analytics in Confluence and filtered by Where content is displayed = Jira Software or Where content is displayed = Jira Work Management
JSM search terms – these can be tracked by using Google Analytics in Confluence, but cannot be distinguished from searches performed ion Confluence
Areas where tracking cannot currently be loaded at all:
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 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
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...
AC-1908 Hosted data storage properties should be readable by anonymous users
💡 Starting in the November 2021 release of Google Analytics in Jira, we will no longer have this problem, because the Google Analytics configuration will be securely saved within our app rather than within Jira app propertiesIt 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.
...