Profile cover photo
Profile photo
Jos Meijerhof
You miss 100% of the shots you don't take
You miss 100% of the shots you don't take


Post has attachment
Add a comment...

Post has attachment
My team is hiring a Mobile Measurement Specialist with Mobile Development Skills in London or Amsterdam? Interested? PM me! #google  #hiring
Add a comment...

Post has shared content
NYT innovation report summary. Great read! #nytimes   #t  
Great summary of the leaked New York Times Innovation report. Nieman Lab calls it "one of the key documents of this media age". 
Must read. for anyone working with or for publishers these days.

The full NYT report is also available now: 
Add a comment...

Post has attachment
Add a comment...

Post has attachment
Getting ready for Think Performance Munich! #universalAnalytics #tp2014 #t
4 Photos - View album
Add a comment...

Post has shared content
Simple Split testing with Google Tag Manager. Concept by +Simo Ahava #t
Simple Split Test With Google Tag Manager

Learn how to conduct a simple variation experiment with Google Tag Manager.

Here's another silly-ish proof-of-concept that I just had to write about. I wanted to show you how easy it is to do a number things that are staples of A/B testing:

1. Modify an on-page element dynamically
2. Choose sample size for experiment and for variations
3. Set a cookie for the user so that assigned variation persists
4. Measure clicks on a call-to-action and distinguish between variants

I mean, it's not an ideal solution. Ideally the change in the on-page element should be done in the header of the page template, so that the visitor will not see the change. Because I'm running the modification in an asynchronously loading Custom HTML tag, the visitor will very briefly see the original version of the element before the change is applied.

And I'm definitely not a CRO or split test expert, so most of this is just off the top of my head. However, I do think this guide has some merits in revealing the power of GTM (once again). As you can see, creating persistent experiences for users is not that difficult. Nor is it to translate these experiences into annotated hits in your GA reports. Nor is it to change an element on-page and simulate a website redesign gone horribly wrong.
Add a comment...

Post has attachment
Add a comment...

Post has attachment
Some real gems amongst these 16 Amazon reviews! #mondayfun #t
Add a comment...

Post has shared content
This is a pretty major change to GA/UA if you're tracking websites and apps! #t #analytics  
Understanding User Behavior in a Multi-Device World

In this constantly connected world, users can interact with your business across many digital touchpoints: websites, mobile apps, web apps, and other digital devices. So to help you understand what users do in the increasingly diverse digital landscape, we’re enabling you to view web and app data from the same reporting view. This will be rolling out to all accounts over the next week.

Analyze app and web data in the same reporting view
Any data you send to the same property appears in all of the reporting views, regardless of how you collected that data. This means that if you send data from the web or from a mobile app to one property, both data sets appear in your reports. 

If you want to isolate data from one source, like if you only want to see web data in your reports, you can set up a filter to customize what you see. You can also use other tools to isolate each data set, including customizations in standard reports, dashboards, custom reports, and secondary dimensions. 

Measure web apps
We’ve also added some new app-specific fields to the analytics.js JavaScript web collection library, including screen name, app name, app version, and exception tracking. These changes allow the JavaScript tracking code to take advantage of the app tracking framework, so you can more accurately collect data on your web apps.

How these changes affect you
This product change can affect you in different ways, based on how your account is set up and what kind of data you collect and send to Google Analytics. 

The Visitors web metric and Active Users app metric are now unified under the same name, Users. And, Visits are now referred to as Sessions everywhere in all of Google Analytics. We’ll be making these changes starting today, and rolling them out incrementally over the next week. 

If you collect and send both web and app hits to one property in your Google Analytics account, all your hits will appear in all your reporting views starting today. If you want to keep your web and app data separate, you need to add a filter to your reporting views. 

If you don’t send web and app data to the same property in your account, your data stays the same. 

Everyone, however,  will see the unified metric, dimension, and segment names in their reports.  

Until today, some metrics and dimensions used different names in app views and in web views, even though they presented the exact same data. Now, all metric, dimensions, and segment names are the same, regardless if they’re used for web or app data. This gives you a clear and consistent way to analyze and refer to all of your Google Analytics data. 

Our developer site has more information on these changes:

Read the full list of dimension and metric names:
App / Screen Tracking developer guide:
Exception Tracking developer guide:

Posted by +Nick Mihailovski, Product Manager
Add a comment...

Post has attachment
Added photos to Analytics Summit 2014 in Zürich.
Commenting is disabled for this post.
Wait while more posts are being loaded