Why Google Tag Manager with Jive?

You can update the tracked objects or metrics without having to edit your Jive instance configuration each time. That is especially useful for people on Cloud instances who cannot edit the script call themselves.

The value for Hosted customers is that you have less risks of hanging the system as you don’t fiddle with it!

Google Tag Manager also allows you to have multiple access and version control: you don’t need to give full system administrator access to your community to people only maintaining the metrics…

The detailed principle is not only usable on Jive communities as it is generic. I have transposed my “legacy” Tags/Rules/Macros to the new beta Tags/Triggers/Variables. If you encounter issues using my description, please let me know so I can correct/ improve it.

continue reading…

Today I was invited by The Community Roundtable (TheCR) to discuss with other members how we thought about Chinese members to launch the ARM Connected Community in October 2013.

I had been invited to present with Premier Farnell‘s Christy Zurcher from the excellent Element14 community at Jive World in October 2014. This was very interesting to see our totally different yet both successful approaches. Depending on which language or culture you are considering, you have to adapt the solution.

For TheCR members, I tweaked my presentation to make it less linked to the platform we run, and more about the ideas, the principles. Even if I didn’t add everything, I created a slide deck with more text compared to the one I use when presenting to be a bit more self-sufficient. In this post, I summarise and give the presentation.

continue reading…

After some Google Analytics report review, it became apparent that the Not Found page was displayed to a few visitors. I have been working on several ways to limit that not so good experience. If you look at the page below, I was a bit underwhelmed.

Default 404 Error Page

continue reading…

Introduction

Because Jive discussions, videos, documents and some other content types don’t include the place name in the content URL, you don’t have an easy way to segment or filter for all content viewed in a particular group or space. So I have been looking at capturing the place ID along the pageview.

Also, as I run an external community, we were interested in learning the proportion of people browsing as guests and logged in. This was suggested to me as a useful metric to increase the relevance of our homepage.

I therefore looked at how I could capture a bit more information to help improve the community whilst keeping my members’ privacy!

Respect Your Member Privacy

The rule in Google Analytics is very clear. You MUST NOT capture information you can assign to a particular individual. So, even if the Jive platform allowed me to save the userid, I could not save it.

That’s fine as I had absolutely no intention to spy on the members! I have been very transparent about what script runs.

Google Analytics Configuration

I needed to create 2 new Custom Dimensions to capture these two new metrics.

Google Analytics Custom Dimensions

continue reading…

Introduction

At the time of writing, I am looking after the ARM Connected Community. Not only as Enterprise Community Manager but also system administrator of our Jive community. So, when our members and community owners (the people who own an area in the community) asked for features, I want to see what I could do. If don’t intend to do anything with user feedback, what’s the point in asking for it?

Why do Custom Theme in Jive

Out of the box, you cannot find any social sharing capability. Most likely because Jive software was primarily used for internal communities. Social media is an important way to promote content. Part of the project delivery included adding social sharing capability, so I didn’t start from scratch. However, shortly after launch we discovered that our requirements were quite sub-optimal (not to say wrong). The major flaw was that the social sharing buttons (icons) were only visible to members who logged in, and not to simple visitors. Also, community owners indicated that they were more likely to share content they have read… so having the social sharing buttons at the bottom of the content was also judicious.

continue reading…