We do the absolute best we can to implement Google Analytics as fully as possible.
Some things, unfortunately, slip through the cracks:
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:
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.
If you want support for mobile apps, vote for AC-2225 or ask Atlassian to do something about it.