Google Analytics Metrics and Dimensions Cheatsheet

Google Analytics dimensions & metrics cheatsheet

There are times using Google Analytics when you don’t remember the name of a dimension, or wether it’s even a dimension or a metric … There also are times when you even wonder how much details does Google Analytics capture about a aspects of the user interaction on your website or app.

For such times, here’s a PDF cheatsheet of Google Analytics dimensions and metrics, as visual summary of the official documentation.

Tags: , ,

AEM dedicated squad @Liip LS

In 2013, two of our big clients started considering Adobe Experience Manager (AEM) for their CMS needs. In the market of integrated mega-CMS we at Liip came under the impression that Open Source solutions were most of the time not considered by potential clients. To continue collaboration with these key clients, and to offer our high-quality services in this specific market, we have decided to invest in the creation of a dedicated project squad.

We were in contact with AEM before, working on a PHP connector for its data-storage layer (Jackrabbit JCR). Also this new line of service complements rather than replaces our existing service offer.

The partnership with Adobe started at the beginning of 2014. It let us explore the product deeper and assess the market opportunity behind it. By february 2015, the “AEM Startup Squad” was launched. This squad is composed of Fabrice, a senior Java developer with an already solid AEM background, four experienced “bizdev”-people and myself. This is our task force dedicated to reach our goals.

We are presently working on a few business opportunities to realize complete AEM projects or to develop interconnected applications to plug on existing AEM systems. For example Richemont group, which has to resolve many interconnection issues between the brands. Some client projects will therefore start soon.

At the same time, we continue building up our know how and get involved in the community by doing an internal project and by participating to learning sessions and meetups. It’s really a chance to have some time to grow up our skills without the constraints of client-projects. Thank to this, we are now confident to offer a very good expertise in AEM, with focus on following features:

  • The data storage layer and requests resolutions with JCR and Sling ;
  • Authoring concepts and processes ;
  • Components architecture and development ;
  • AEM Key features such as user management, client-context and workflows ;
  • Continuous Integration process & integration tests.

As new projects are coming very soon, we are still looking for developers to extend the squad and build many awesome project based on AEM at Liip. We are now well launched on our roadmap to have a cross-functional team focused on Adobe Marketing Cloud solutions at Liip.

Tags: , ,

Halve-halve-halve : a group prioritization method

Priorities matter at every step of an agile design and development process, yet setting priorities is a daunting task and prioritization in group within a workshop even more.

Reaching general consensus on priorities is always hard

I remember many workshops I facilitated where the mood was open and friendly until I invited the participants to set priorities in the ‘big cloud’ of needs and wishes postit-ed on the wall. At this crucial moment, two distinct group behaviours would occur:

  1. All participants would turn their heads at the ‘boss int the room’, because after all that’s her/his responsibility,
  2. or every participant would get ready to defend his stake.

Funnily, 90% of the identified scope would in both cases be marked as ‘absolut priority’. As a process moderator, if you reach the consensus that “everything is absolutely needed”, well … you failed.

Yet the goal was simple: no two things should have equal priority. But the trick is that this is almost impossible to reach through group discussions. A more reasonable goal for prioritization in group is to define a pyramid of priorities.

I’ve come up with a little method to reach that pyramid of priorities – even with challenging groups of participants – and guess what? it borrows from algorithmic: roughly halving a set is a lot easier than ordering it absolutely. And halving again is easy …

Solution: build iteratively a pyramid of priorities

Split. Ask the group of participants to split the set of things in two subsets of equal size: the important things, and the more important things. Crucial here: never speak of less or not important things, you might hurt feelings.

Split again. Then focus on the higher priority set – the set of more important things – and ask participants to identify within it the very important things, again halving the set in two subsets of equal size. Iterate again and identify the most important things from the very important ones, the super-absolutely important ones, … slowly building the pyramid of priorities, bottom-up.

Yes, in every iteration there can still be quite some discussions and negotiations, but every iteration ends with an agreement, which is a firm step towards your goal: a common agreement on priorities.

It helps to present it to the group as a clear challenge with clear rules and to clearly timebox every iteration, it will get participants to switch to “game mode” and perform the task with open minds. Also don’t explain to them that the goal of the exercise is to build a pyramid, because everyone will merely focus on his top thing. Simply tell them that “now has come the time to work a bit on priorities” and launch the first halving iteration.

That little prioritization method has done marvels in uneasy group settings. I hope it will help you too.

Tags: , ,

Drupal Dev Days 2015 wrap up

Last week, I was at Drupal Dev Days in Montpellier with a few other Liipers. It was, as often is with such conferences in the Drupal community, greatly encouraging to see the passion and effort of the many Drupal developers there.

Throughout the week, hundreds of people were working on different projects in the “sprints” (as such code-marathons are called in the Drupal community). Drupal 8 core was (unsurprisingly) the biggest group, but there were many other efforts related to Drupal 8. I was primary involved in the Rules for Drupal 8 effort, which was a fairly large group. We managed to get quite a few issues solved, and the road to a user interface for Rules in Drupal 8 was begun, which is one of the biggest outstanding issues.

It was challenging work, at times, but there was a good mood in the group, and the D8rules team were really great at helping beginners getting started, so many thanks to them for that.

I was unfortunately forced to forgo the conference part of the event due to illness, but I hear it was great. In total, I think the organisers of DDD did a great job – especially with the food. So thanks to them as well. See you in the issue queues.

This blog is now faster than ever

After we changed silently to using WordPress a few weeks ago for this blog (from the ageing Flux CMS software), we now also upgraded the server software to the latest and greatest versions. We finally use HHVM 3.6, nginx with SPDY 3.1 support, deliver everything in SSL only (but of course redirect from port 80), updated our certificate to use SHA256, disabled all “known-as-weak” ciphers and protocols (sorry IE 6 users), do OCSP Stapling and even send an HSTS header for being extra secure. We also switched to a server not on the edge of the continent anymore and deliver it additionally via IPv6.

With all that, this site should be faster and more secure than ever. Enjoy!

(We also applied the SSL/SPDY settings to www.liip.ch, so you may enjoy a better experience there as well)

Tags: , ,

Rails Girls Summer of Code

The Rails Girls Summer of Code is a global initiative that provides 3-month stipends to women to work full-time on an Open Source project of their choice. The students work in teams of two from July 1st to September 30th, aided by local coaches; applications are still open until April 14th, 23:59 UTC (that’s tomorrow!) and anyone can apply if they fulfil the requirements.

The program is now in its third year and has successfully collected enough money to fund 10 student teams for 2015, thanks to wonderful sponsors (one of which is Liip!) and individuals, through a crowd funding campaign  For the first time in RGSoC’s history, we are attempting to fund an 11th team. The crowd funding campaign is still open, and we’d love to have your support  Follow us on twitter or check out our blog to stay up to date.

Help us foster diversity in Open Source!

Tags:

Estimates or #NoEstimates

NoEstimates might be the way to profit from estimation without the burden of dealing with Story Points.

Prediction is very difficult, especially about the future.

—Niels Bohr (and others)

For years now, agile teams have been using planning poker and other methods to estimate the effort needed to implement a product backlog item (PBI). The practice not only helps to prepare future iterations; it’s also a helpful indicator for the prioritisation of PBIs. Of two items with similar expected benefit, you’ll usually want to implement the one first that will cost less to build.

Perhaps most importantly, estimating effort has proven to strongly support conversations about the details of a PBI. Understanding the requirement precedes building an opinion on its required effort.

Continue reading about Estimates or #NoEstimates

8 years at Liip

David LinkedIn 8 years

A couple of congratulations on linkedin made me notice that I now have been working for Liip since 8 years.
This is a very long time indeed. But I am not tired of working at Liip at all.

Of course, i occasionally thought whether I should move on and see other companies. But there was always some cool project to do or some interesting new challenge to tackle. When looking back at what I did in those past 8 years, it actually feels like I got a new job every couple of years.

Continue reading about 8 years at Liip

Time for Coffee for iOS and Apple Watch

Jan Hug, Cyril Gabathuler and myself worked hard in our free time the last few weeks on an iPhone app for the great website timeforcoffee.ch, a private project started by François Terrier and his friends Serge Pfeifer, Jean-Luc Geering and Kristina Bagdonaite. It also has newly addded support for the upcoming Apple Watch. As this is a project done by Liipers and non-Liipers alike, we talk about it more on medium.com, go and read it! And apply for the beta and follow us on twitter: @time4coffeeApp

Tags: , , ,

WebSpeech APIs

Ever since I saw the film Iron Man I wanted to build a voice controlled personal assistant, similar to Tony Stark’s Jarvis. Thanks to the WebSpeech APIs provided by Chrome you can now build something similar in your browser.

Continue reading about WebSpeech APIs

Tags: , , ,