Skip to main content
Skip table of contents

Legacy version - Configuration (until June 2020)

The configuration steps changed in the June 2020 release of Google Analytics in Confluence. This page is for the legacy version of the app.

For users of the current version, view https://dsapps.atlassian.net/wiki/pages/resumedraft.action?draftId=1670512650 .

If you are using a current version of this app, stop. Do not read further.


For users of legacy versions, the following is still applicable...

There's an overview video here for the installation steps:

Configuration Steps

Basic Configuration

In Google Analytics

This will send basic data only to Google Analytics

  1. Sign in to your Google Analytics account and setup a new property

  2. In Property Settings, copy the Tracking Id ready for use later

In Confluence Cloud

  1. After installation, configure the add-on using the Tracking ID created in Google Analytics earlier

     

Advanced Configuration

If you want to make use of the Google Analytics Custom Reports, then continue with the configuration...

In Google Analytics

Create custom dimensions for Space Key, Content ID, Content Type, Content Context and User Key Atlassian Account ID.

  1. Select the Admin tab and navigate to the property to which you want to add custom dimensions.

  2. In the PROPERTY column, click Custom Definitions, then click Custom Dimensions.

  3. Click New Custom Dimension.

  4. Add a Name.
    This can be any string, but use something unique so it’s not confused with any other dimension or metric in your reports.

  5. Select the Scope.
    Choose to track at the Hit, Session, User, or Product level. Read more about scope and how custom dimensions are processed in our Developer Guide.

  6. Check the Active box to start collecting data and see the dimension in your reports right away. To create the dimension but have it remain inactive, uncheck the box.

  7. Click Create.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.