Frequently asked questions - Google Analytics

How do I log in to the Google Analytics app?

Once you have had the training, you will be instructed to provide a gmail address to the RDS team. The RDS team will then request that Tactuum provide this email account with access to Google Analytics and will email you once this has been granted. After that, you simply need to log into your Google Account, and head to the Google Analytics app within Google Apps, and you should see Right Decisions appear as an account to which you have access.

How does it identify users?

Users are identified when Google notices a device accessing the site and gives it an IP address, which is then its point of reference for future visits to the site, so it counts the device as the same user returning to the site.

This gives us a more accurate representation of how many people visit the site within a specific time period, and how many page views on average are conducted per user.

Can I see how often a particular document has been downloaded from our toolkit?

We have a section within Engagement called “Events”, which is where we measure specific interactions with the RDS site. Within events, we have set up a specific event measure entitled “file_download”, which will show you how many times a user has downloaded a file from the RDS website or app. This includes documents, presentations, compressed files, videos and audio files.

Please note: while you will be able to use the “Add Filter” option to filter the event results to your specific toolkit, or even a specific page within your toolkit, there is currently no function which will allow for you to filter these results to see the download numbers for specific documents. For example, if you have a page within your toolkit with several downloadable documents, it will only show you the total amount of downloads for that specific page, it cannot be specific as to the number for each document.

Sometimes the term “not set” appears in the results, what does this mean?

A “not set” result in Google Analytics happens when there’s not enough information in that area to categorize a piece of data properly, so GA use this as a kind of placeholder to account for this data.

A “not set” result usually happens when The IP address allocated to the device used to access the site cannot collect the information we require. This can be for several reasons including:

  • The user has extensive privacy settings on their device
  • The user has disabled cookies allowing the IP address to gather their search data
  • The user has the location services turned off or disabled on their device
  • Google analytics has not had time to process all the data collected due to a high volume of traffic, so needs more time to process further information.

In some cases, it can take google analytics up to 72 hours to process all data it receives from the users/IP addresses, so it is possible that the “not set” data in some sections is referring to data which has come in during the last 72 hours and has not been fully processed. In these cases, GA should have still counted users and views accurately as this is basic data, but it has not processed the rest of the data from the device yet such as acquisition data or demographic information.

Top tip: to minimise the amount of “not set” data found in your reports, it is usually best to avoid running reports right up to the current date. Instead, you should run reports ending at least two days prior to the current date so that it gives GA extra time to process the most recent data and fill in the blanks as best as possible. It is not a guarantee that all “not set” data will be categorised as it may fall under one of the other reasons, but leaving 48-72 hours for the data to be processed gives you the best chance of accuracy.