Want to use some “hot” new web fonts to pimp your Confluence wiki?

It’s really straightforward. This post describes a method by which you can change all the headings to use web fonts hosted by Google.

Site-wide web fonts

Using Rokkitt font

Browse to Confluence Administration | Look and Feel | Custom HTML

In At end of the HEAD paste:

<!-- Fonts for headings -->
<link href='http://fonts.googleapis.com/css?family=Rokkitt:400,700'
      rel='stylesheet' type='text/css'>
<style>
#com-atlassian-confluence h1,
#com-atlassian-confluence h2,
#com-atlassian-confluence h3,
#com-atlassian-confluence h4,
#com-atlassian-confluence h5,
#com-atlassian-confluence h6 {
	font-family: 'Rokkitt', serif;
	font-weight : bold;
}
</style>

Please note that adding inline styles is not big or clever, but it is quick and easy for the purpose of this blogpost.

This results in a layout similar to the screenshot below:

Using Leckerli One font

Was that too corporate? Then lets have some handwriting…

Browse to Confluence Administration | Look and Feel | Custom HTML

In At end of the HEAD paste:

<!-- Fonts for headings -->
<link href='http://fonts.googleapis.com/css?family=Leckerli+One:400'
      rel='stylesheet' type='text/css'>
<style>
#com-atlassian-confluence h1,
#com-atlassian-confluence h2,
#com-atlassian-confluence h3,
#com-atlassian-confluence h4,
#com-atlassian-confluence h5,
#com-atlassian-confluence h6 {
	font-family: 'Leckerli One', cursive;
}
</style>

Now, you’ll get something like this:

I’m not sure that this is a good look, but never mind.

Web fonts for a single space

Want to just mess up the fonts in a single space?

Then, duplicate the content of the Google hosted stylesheet — for example http://fonts.googleapis.com/css?family=Leckerli+One:400 and add to the space stylesheet…

Browse to Browse | Space Admin | Look and Feel | Stylesheet.

Click on Edit and paste in:

/* Duplicated from http://fonts.googleapis.com/css?family=Leckerli+One:400 */
@font-face {
  font-family: 'Leckerli One';
  font-style: normal;
  font-weight: normal;
  src: local('LeckerliOne'), url('http://themes.googleusercontent.com/static/fonts/leckerlione/v2/S2Y_iLrItTu8kIJTkS7DrKRDOzjiPcYnFooOUGCOsRk.woff') format('woff');
}

/* Targetting Confluence heading  */
#com-atlassian-confluence h1,
#com-atlassian-confluence h2,
#com-atlassian-confluence h3,
#com-atlassian-confluence h4,
#com-atlassian-confluence h5,
#com-atlassian-confluence h6 {
	font-family: 'Leckerli One', cursive;
}

This will only affect the space in which you add the CSS and will override the global styles.

I’m not sure whether the URL for the font will remain constant in the long term though, so you may have to repeat this process.

Be careful

There are plenty of web font services and many, many fonts to choose from. With great power comes great responsibility, so be careful.

Last week I released Analytics Plugin for Confluence 1.2 on the Atlassian Plugin Exchange.

It’s been 6 months since the initial release which was only tested on Confluence 3.0. This time I’ve added a new dashboard section, full support for Confluence 3.1 & 3.2 and a pile of macro parameters as requested by Guy Fraser. The release notes are here. Confluence 3.3 is just around the corner, so I’ll add an update for that when it comes out.

Thank you

The Confluence community has shown a great deal of support and encouragement since the plugin was originally released. For example, Atlassian blogged about it before I got a chance to. So thanks to all for your support.

The plugin was name checked by Sherif Mansour – Atlassian’s Product Manager for Confluence in the Confluence State of the Union presentation at Atlassian Summit 2010 at the start of the month. Watch it all, but concentrate especially around 5:10!

This week Google approved the plugin for their Google Analytics Application Gallery — take a look here. The Apps Gallery has only been going for about a month so I’m really excited about being a part of it. The slight name change and new logo were done to fit in with the Application Gallery Policy.

In the future

The next release should support Confluence 3.3 and also complete tracking of all pages in a space — not just those with a URL starting /display/spaceKey/ — based on this hack :

// Add a page-level custom variable to record the space-key
if (typeof jQuery('meta[name=confluence-space-key]').attr("content") == 'string')
{
  pageTracker._setCustomVar(
    1, // This custom var is set to slot #1 of 5

    // The name acts as a kind of category for the user activity
    'confluence-space-key',    

    // This value of the custom variable
    jQuery('meta[name=confluence-space-key]').attr("content"), 

    3 // Sets the scope to page-level
  );
}

— If you want to use this hack now, try out this custom Google Analytics report which will allow you to take advantage of it now.

I’d also like to add full space specific tracking for attachments too.

A quick demo

And finally, this is what the new version looks like:

Related Posts

• Tracking Atlassian Confluence usage with Google Analytics
• 4 Useful Tips on Google Analytics Reporting for Confluence
• Announcing: Google Analytics plugin for Confluence – original release

I’ve previously written a number of posts about Confluence and Google Analytics (GA), including how to set up GA on Confluence and pointers for GA reports you should consider. Lastly, I wrote the Confluence Google Analytics Plugin (CGAP) which provides space specific GA reports from within Confluence.

However, I’ve not been entirely happy because there wasn’t a method to allow complete tracking of all space specific Confluence pages using CGAP or the reports that I’ve previously described.

This has been documented elsewhere, but briefly, the problem is with…

• pages with punctuation in the title e.g. This page is bad for Analytics, isn’t it? (hover on the link to see the URI)
• short URLs e.g. /x/2Bq9Ag
• space administration e.g. /spaces/spaceadmin.action?key=spaceKey
• page edits e.g./pages/editpage.action?pageId=XXXX
• page creation e.g. /pages/createpage.action?spaceKey=spaceKey&fromPageId=XXXX
• add/view attachments e.g. /pages/viewpageattachments.action?pageId=XXXX
• page history e.g. /pages/viewpreviousversions.action?pageId=XXXX
• view wiki markup e.g. /pages/viewpagesrc.action?pageId=XXXX

…and so on. I think you get the picture.

For any page where there is a real interaction with the wiki — such as page creation or page edits, attachment viewing or uploading — it is very difficult associate that interaction to the space where the interaction took place. Damn. That’s the main point really. Wikis are for collaboration — editing and creating content — not just passively reading.

It really bugs me that the URIs in Confluence aren’t built up so that they always provide a context of where you are. But what can we do?

This post suggests 2 possible solutions to this problem:

1. A Javascript only method
2. A Javascript and velocity templating method

Both have their drawbacks, but they do let you get a little closer to understanding what your users are doing within your Confluence spaces. Try them out and please report back on your preference or your own alternative solution.

The Javascript only method

In this method, we track a custom variable in GA where possible, so that we can attach a page view to the corresponding Confluence space.

Atlassian handily provide the following (example) meta tag on every page that has an associated space:

<meta id="confluence-space-key" name="confluence-space-key" content="~cczdas">

We can check for that meta tag and pass it into a custom variable in Google Analytics.

In Confluence, go to Dashboard | Administration | Look and Feel | Custom HTML

Click on the “Edit” button and add this javascript snippet (with your tracker code) to the “At end of the BODY” section:

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">

	window.onload = function(){
		try
		{
			var pageTracker = _gat._getTracker("UA-XXXXX-XX");

			// Add a page-level custom variable to record the space-key
			if (typeof jQuery('meta[name=confluence-space-key]').attr("content") == 'string')
			{
				pageTracker._setCustomVar(
				     1,                         // This custom var is set to slot #1 of 5
				     'confluence-space-key',    // The name acts as a kind of category for the user activity
				     jQuery('meta[name=confluence-space-key]').attr("content"), // This value of the custom variable
				     3                          // Sets the scope to page-level
				);
			}
		}
		catch (err) {}
	}

</script>

This means for each page, we’ve added a custom variable which can later be check against. We can now therefore easily check which page belongs to which space.

In Google Analytics, the custom variables report looks like this:

This doesn’t really tell us much, other than the number of page views for a space and a little more. To get at the real power of custom variables, we need to create a custom segment for each space. This will allow us to see all the interactions for the space.

Here’s a short video guide to creating custom segments for Confluence spaces:

Pros

• It’s really simple. Anyone with Confluence administration rights can cut and paste this code.
• It’s pure. This should not be affected by upgrades to the platform.
• It’s easily to support. Lots of people know Javascript.

Cons

• You’re moving into slightly advanced Google Analytics territory here.
• You’ll need to set up a separate custom advanced segment for each space. This may be somewhat dull.

I really like this approach, but haven’t managed to successfully add it into CGAP yet whilst maintaining access to historical data.

Javascript and velocity templating method

In this method, we trick Google Analytics into reporting the URL in a the format that works with content drill-down e.g.

• /pages/viewpage.action?pageId=XXXX becomes /display/spaceKey/Page+Title
• /x/2Bq9Ag (short URL) becomes /display/spaceKey/Page+Title
• /pages/editpage.action?pageId=XXX becomes /display/spaceKey/Page+Title/edit
• /pages/viewpageattachments.action?pageId=XXX becomes /display/spaceKey/Page+Title/view-attachments

We do this by adding a custom meta tag named “analytics.url.fix” from which we read the “fixed” URL using a little Javascript.

Edits

page.vmd in your theme:

## Add Google Analytics support for page edits, attachment views etc.
## Called by $!sitemeshPage.getProperty("page.googleAnalyticsUrlFix") in main.vmd
<content tag="googleAnalyticsUrlFix">
	#if ($mode == "view")
		<meta name="analytics.url.fix" desc="$req.contextPath/display/$page.spaceKey/$page.title" />
	#else
		<meta name="analytics.url.fix" desc="$req.contextPath/display/$page.spaceKey/$page.title/$mode" />
	#end
</content>

main.vmd in your theme:
Add after the title node in /html/head/title

## Call the googleAnalyticsUrlFix content tag in page.vmd, fail silently:
$!sitemeshPage.getProperty("page.googleAnalyticsUrlFix")

In Confluence, go to Dashboard | Administration | Look and Feel | Custom HTML

Click on the “Edit” button and add this javascript snippet (with your tracker code) to the “At end of the BODY” section:

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
	window.onload = function(){
		try
		{
			var pageTracker = _gat._getTracker("UA-XXXXXX-X"); 

			// Test for the meta[name=analytics.url.fix] tag & fix the url
			if (typeof jQuery('meta[name=analytics.url.fix]').attr("content") == 'string')
			{
	 			// console.debug('corrected pageview');
	   			var pageUri = jQuery('meta[name=analytics.url.fix]').attr("content").replace(/s+/gi, '+');
				pageTracker._trackPageview(pageUri);
			}
			else
			{
				// console.debug('default pageview');
				pageTracker._trackPageview();
			}
		}
		catch (err) {}
	}
</script>

Pros

• You don’t have to do anything on the Google Analytics side at all
• This is just great for the content drilldown screen in Google Analytics.
  • It means that pages with punctuation in the title can now be seen within their correct space.
  • The space owners can now be sure of the stats for viewing and editing pages within their space.
• This is great for the Google Analytics plugin for Confluence (CGAP)
  • All the page edits should be shown in the analytics report
  • It’s easily supportable. Lots of people know Javascript

Cons

• It’s a bit messy.
• You’ll have to apply this to every theme you support.
• Editing velocity templates isn’t everyone’s cup of tea.
• I’ve no idea what will happen when you upgrade Confluence.
• It niggles me that we’re sending incorrect (though easily readable) pageview data to Google Analytics.
• It still doesn’t tie everything to the space, just the page interactions

To my mind, this is less elegant, but provides pretty much instant results.

Which one to choose?

I really like the simplicity of the first solution. Just a little bit of Javascript to read a meta tag that’s already there. It’s likely to easily survive an upgrade. But I’m disappointed that as yet, I can’t get it to work nicely with CGAP.

For ongoing support reasons, I’d always say don’t mess with the platform. Don’t do anything which makes it more difficult to upgrade to the latest and greatest version. If you agree, then steer well clear of the latter option. If however, you absolutely have to start complete space specific tracking right now, no matter what, then the latter is then choice for you.

I recently started building Confluence plugins. The first one being my Google Analytics plugin for Confluence. This post outlines my “journey” into Confluence plugin development. It documents a beginner’s pitfalls when developing with the Atlassian Plugin SDK. Hopefully others can learn from, or at least laugh at my mistakes.

Where I was starting from:

• No experience of maven
• No understanding of how Confluence plugins work or how they are written
• Some experience of Java – Mainly uPortal/Luminis portal development for the University of Nottingham and some consultancy work e.g. for Astra Zeneca, Documentum and 3Com
• No experience of unit testing or integration testing in Java – oh dear
• I prefer UI work to real programming

Initial failure

I tried to setup a development environment for plugin development using Atlassian’s documentation a little before the beta release of version 3 of the Atlassian Plugin SDK. It was a pain. This was no fault of the documentation — it was really just to do with my schedules and available time to experiment.

The problem was two-fold:

1. I’d not done this before, so was clueless to what was involved
2. The setup was a complete ball-ache considering the time restraints

I was well aware of point 1 and the pain it was likely to cause. Point 2 seemed to be the old chestnut – install and configure the exact correct versions of the software you need in the correct sequence, then start.

Wait. I don’t know what that means, see point 1. Yes, I’ve got maven installed on my MacBook! Woo! Let’s go. Hang on, it’s not the correct version. Where do I get that from?

In many ways, it reminded me of my initial experience of building and installing Apache 1.x on Solaris SPARC boxes back in the day:

cd /path/to/apache/source; make; make install;
Oh. Wrong version of make. Where do I get that from? Hmmm.
Install correct version of make. Damn, make needs the correct version of gcc. Where do I get that from?
And so on. Moving further and further away from the problem you’re trying to solve.

So, I stopped there. No shiny Confluence plugins for me. I’ve got plenty of other things to do anyway thank you very much.

Reboot

Then Atlassian released the Plugin SDK beta and all this nastiness was removed. Everything you need to build an Atlassian plugin was bundled in one place. Refreshing. All commands have been wrapped and so are prefixed with atlas- to prevent conflict with whatever else you’ve got installed.

For the impatient, this really drives down the barriers to entry for plugin development.

Following the documentation for installing the Plugin SDK was a piece of cake. It just worked.

• Download
• Unzip
• Add some environment settings. Edit ~/.profile and add:

  PATH=$PATH:.
  PATH=$PATH:$HOME/
  PATH=$PATH:$HOME/bin
  PATH=$PATH:$HOME/atlassian-plugin-sdk/atlassian-plugin-sdk-3.0-beta3
  PATH=$PATH:$HOME/atlassian-plugin-sdk/atlassian-plugin-sdk-3.0-beta3/bin
  export PATH
  

• Start building a plugin

Starting out to build your Atlassian plugin is documented here. It’s a fairly straightforward set of instructions.

You start by doing something like this:

mkdir ~/projects/davidsimpson.me/
mkdir ~/projects/davidsimpson.me/confluence
cd  ~/projects/davidsimpson.me/confluence

atlas-create-confluence-plugin
...
...
...
When prompted
Define value for groupId: : me.davdsimpson.confluence.plugins
Define value for artifactId: : googleanalytics
Define value for version:  1.0-SNAPSHOT: :
Define value for package:  me.davdsimpson.confluence.plugins: :
Confirm properties configuration:
groupId: me.davdsimpson.confluence.plugins
artifactId: googleanalytics
version: 1.0-SNAPSHOT
package: me.davdsimpson.confluence.plugins

Then type…

cd googleanalytics
atlas-run

…and sit back. If maven doesn’t fall over for lack of memory at this point, you’re laughing. Go away, have a beer or two. This may take some time.

On your return, maven will hopefully have finished dragging all manner of nonsense from Australia and installed a working copy of Confluence, together with an empty plugin onto your computer. Nice. Next, write some code.

I like to run before I can walk. It seems like much more fun to attempt something that’s harder. You do fall over a lot more often though. So rather than some kind of silly little hello world or equivalent plugin, my first plugin was an integration of Google Analytics with Confluence using the Google Analytics API to fetch data from Google. It requires some additional JARs from Google.

Google doesn’t have a public maven repository to my knowledge and I’d no idea how to get these JARs added into maven. Luckily, people had already written about parts of this, so I put 2 and 2 together.

Add Google Analytics JARs to maven:

atlas-mvn install:install-file -DgroupId=com.google.gdata
    -DartifactId=gdata-core
    -Dversion=1.0
    -Dpackaging=jar
    -Dfile=/path/to/gdata-core-1.0.jar
    -DgeneratePom=true

atlas-mvn install:install-file -DgroupId=com.google.gdata
    -DartifactId=gdata-analytics
    -Dversion=2.0
    -Dpackaging=jar
    -Dfile=/path/to/gdata-analytics-2.0.jar
    -DgeneratePom=true

atlas-mvn install:install-file -DgroupId=com.google.collect
    -DartifactId=google-collect
    -Dversion=1.0
    -Dpackaging=jar
    -Dfile=/path/to/google-collect-1.0-rc3.jar

Edit the Project Object Model (POM) to add the dependencies

Edit the pom:

vi ~/projects/davidsimpson.me/confluence/googleanalytics/pom.xml

Add this bit to the end of the dependencies node:

<!-- Add Google Analytics dependencies: -->

       com.google.gdata
       gdata-core
       1.0

       com.google.gdata
       gdata-analytics
       2.0

	com.google.collect
	google-collect
	1.0

Next, fire up your IDE

My chosen IDE is IntelliJ IDEA.

• Open the pom.xml in IntelliJ IDEA (File | Open project)
• Override/set the maven home directory:

  /Users/davidsimpson/atlassian-plugin-sdk-3.0-beta3/apache-maven

• Set the JDK for build as 1.5 or 1.6
• Start editing the plugin

Hiccups

It’s not all straightforward. Here’s some of the annoyances that I came across.

Maven needs more memory

I needed more memory for maven. Not really a problem – append to ~/.profile:

MAVEN_OPTS=-Xmx512m
export MAVEN_OPTS

Annoying warnings on atlas-run

I noticed this on running atlas-run – it probably shouldn’t be there:

[WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent!

Of course, someone has already blogged about it — Red Leopard — and it’s easily fixed by editing the POM to add the correct encoding.

3.0.2
    3.0

    <!-- Fix for MacRoman warnings on build -->
    UTF-8
    UTF-8

Now, we have no nasty warnings.

The macro browser icon

I love the Macro Browser in Confluence. It’s a nice step forward in the evolution of the UI. So as a result, I wanted my macro to have a shiny icon in the macro browser. That damn Macro Browser icon ate up several hours of my life. Looking at the comments on the documentation page, several other people have had a whole load of fun getting their pretty icon to show up too.

The macro browser icon: What we

Could I get the Macro Browser to show my plugin’s icon. No. I followed the documentation. It did not work. I looked again. This time I really paid attention. Was it my fat fingers? Was I just being stupid? (Probably.) I ignored this for a while — maybe it would be better after a night’s sleep.

Everything seemed to work a whole lot better when I dropped the beta and moved to version 3.0.2 of the Plugin SDK.
Note: I had to update my ~/.profile to point to the new version of the SDK and update the references to maven in Intelli-J at this point.

I also followed a different tack on getting the macro browser icon to work

• Find a macro that has a custom icon in the macro browser
• Go to the Atlassian public subversion repository and browse to the source for that macro plugin.
• Copy the exact syntax from the atlassian-plugin.xml and paste into your macro’s own atlassian-plugin.xml
• Name the icon exactly the same as in the atlassian-plugin.xml and put it in the correct place in the directory structure

I’m not entirely sure whether it was the copy and paste approach that helped or moving away from the beta. It works now, so I’m not going to loose sleep on why.

Adding a configuring UI to the plugin

My plugin needed to store Google account credentials and display a list of Google Analytics sites, so you can choose the correct profile. How do you do that? Hmmm. Go back to the documentation. It wasn’t nearly detailed enough for my liking, so time to vent a little.

Again, it seemed the best way to learn was to find a plugin that has a similar kind of configuration to that you’re hoping for and start appropriating the code.

Unit testing and integration testing

This is a good idea. Period. Did I have a clue how to do it for Confluence? Of course not.

Again, the community helped out. Atlassian partners at Adaptavist, Comala Technology and Customware have written about this:

• Integration Testing of Confluence Plugins by Bo Wang
• Unit testing a Confluence Action by Edward Robertshaw
• Unit testing a Confluence Macro by Edward Robertshaw
• Confluence plugin integration testing by Roberto Dominguez

Browsing around the Atlassian public subversion repository was also a help. I’ve got to say that I’m an easy convert to testing. It just makes sense.

Update (2010-05-04): A nice feature of the SDK is running or testing your plugin against different versions of the product. This is straightforward:

# Integration tests for different versions
atlas-integration-test -v 3.0
atlas-integration-test -v 3.1
atlas-integration-test -v 3.2
# Run different versions of Confluence
atlas-run -v 3.0
atlas-run -v 3.1
atlas-run -v 3.2

Wrapping up

After a good deal of stumbling around, it turns out that I can write a Confluence plugin after all. Everything started working a lot better after I updated from the beta version, but that could just be coincidence. The documentation could be a little better to help the uninitiated but it was equally my fault for not learning to walk first. There is a lot of good information, but it is spread over a few different spaces.

My next step was to get the plugin added to Atlassian Plugin Exchange. It took a little while to get this done — maybe that’s best saved for a follow up post. The plugin is now available on Atlassian Plugin Exchange. I hope other people get some use out of it.

Updated 2011-06-30: Changed to asynchronous Google Analytics tracking
You’ve chosen Confluence as your Enterprise wiki and got it installed. People are using it. But how many people?

You could have a look at the Global Activity page on Confluence, but this might confuse matters.

You’ll get to see graphs, but what do they really mean? The Global Activity statistics are at best very basic.

Better still, install Google Analytics and you’ll have a much more accurate idea of what’s going on. Best of all, it’s really easy to install.

How to install Google Analytics on Confluence

I’m assuming (for my sake) that you already know your way around Google Analytics.

In Google Analytics

Login to Google Analytics and add a new website profile

The settings will roughly mirror those in the screenshot below

Make sure that you check “Do Track Site Search” against Site Search. Add queryString as the Query Parameter. This will allow you to monitor who is searching for what.

Update (2009-11-12)
Edit the Search Settings configuration like in the image to see search terms grouped by spaceKey in the internal search categories reports. Further details why can be seen here

A screenshot of the Site Search Setting section

The top search terms will suggest either content that’s missing from the site, or something that is not easily found in the current information architecture. Either way, tracking this and acting on the findings should improve the user experience.

In Confluence

Login to Confluence as an administrator and add the GA tracking javascript code to the end of the page body…

Navigate to:

Dashboard | Administration | Look and Feel | Custom HTML

Click on the “Edit” button and add the javascript sample (with your tracker code) to the “At end of the HEAD” section:

<script type="text/javascript">
  // See: http://davidsimpson.me/2009/03/18/tracking-atlassian-confluence-usage-with-google-analytics/
  // Put this in Confluence Administration | Look and Feel | Custom HTML -- "At end of the HEAD"

  var _gaq = _gaq || [];
  _gaq.push(['_setAccount', 'UA-XXXX-XX']); // Your GA code here
  _gaq.push(['_trackPageview']);

  // Add a page-level custom variable to record the space-key
  if (typeof jQuery('meta[name=confluence-space-key]').attr("content") == 'string') {
    _gaq.push(['_setCustomVar',
      1,                        // This custom var is set to slot #1 of 5
      'confluence-space-key',   // The name acts as a kind of category for the user activity
      jQuery('meta[name=confluence-space-key]').attr("content"),  // This value of the custom variable
      3                         // Sets the scope to page-level
    ]);
  }

  (function() {
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
  })();

</script>

Results

This works nicely, particularly as the custom variable allows us to easily track all space related content separately, and thus facilitate the use of the (Google) Analytics reporting plugin for Confluence.

Screenshot of Content by Title report:

Screenshot of Site Search Terms report:

Related Posts (Updated)

• 4 Useful Tips on Google Analytics Reporting for Confluence
• Announcing: Google Analytics plugin for Confluence
• How to track Confluence usage with Google Analytics by Remo Siegwart