In  normal implementations of Google Analytics, you simply add some tracking JavaScript onto the page and all the features of Google Analytics are available to you. This add-on cannot do everything that normal Google Analytics does. The reason for this is that Google Analytics JavaScript code runs in an iframe on a completely different domain to your Jira Cloud instance. With this restriction comes limitations in what data can be collected.

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:

    • 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.

• 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.