Today we officially released Total Engagement. You can read the press release here.
Q: What is Total Engagement? Give me the elevator pitch.
A: Our Total Engagement release is comprised of two parts;
i) We now support analytics for Mobile Apps - meaning that we collect and report app user events
ii) we combine app usage measurement with traditional web reporting. As far as we know, we are the only company on the market who can display app user eventstreams and website visitor clickstreams in the same report on the same page.
Q: What does that actually mean?
A: That means that if you... Read full blog post
Technology and terminology are both changing.
Engagement patterns are changing and so is the way that we measure and report them.
We began ten years ago by measuring page views and the mouse clicks website visitors made between page views. This information is displayed in the form of a clickstream. We are now able to capture a much wider range of activity.
Our technology has expanded to keep pace with engagement patterns across the internet. Alongside clicks and page views, we also capture events. We group events into eventstreams. Alongside visitors we also measure users.
Definition of an event:
for Opentracker, anything can be an event. An event can be a view, swipe, click, pinch, download, ajax call, movie view, etc.
You can now send us custom events; inserting data (events) can be done by submitting the... Read full blog post
When we say that we have built Mobile App Tracking - that can raise some questions. Definitions are needed.
Q: What is mobile app tracking?
A: Mobile app tracking is combined data from native and web app usage on mobile devices. This means tracking and measurement of app usage. If you build, publish, advertise through or sell apps, you have users, it is important to know how these users make use of your app, and if they are loyal users, meaning retention.
What this amounts to is usability testing. Your app users effectively become testers. Individual profiles mean that you can inspect both one-night-stand installs and loyal users in order to determine what is successful and what is not.
For ten years, we have pioneered real-time website tracking, meaning we show what website users are doing while they do it. Using our... Read full blog post
Amsterdam, The Netherlands.
From April 25-27, 2012, the annual Next Web Conference will take place a few hundred meters from our Amsterdam office.
TNW2012 has a packed agenda as usual. We'll be there in person on Thursday 26 April the whole day. We've organized a Startup Table in the Business Area.
Why a Startup Table? Because after many months of hard work, we've just launched a new service. Our new offering is called Mobile App Analytics.
Our focus is realtime tracking of app users. We display individual Eventstreams and User Trends.
We are going to be... Read full blog post
Today i had to upgrade a tomcat server that used a keystore file for SSL, to a native tomcat 6 with APR and OpenSSL.
I thought this was easy until i realized i didn’t had the original private key anymore of when the certificate was created.
The steps we took with Keytool to generate the the original certificate request, do not save the private key as a separate file..
After some digging around i found this nice java app called Portecle that does the trick: it opens your keystore and allows you to export the private key.
It even lets you remove the encryption/password.
After that it was easy: saving the private key and issued certificate in a separate folder, changing the server.xml to this:
<Connector port="443" maxHttpHeaderSize="8192"
enableLookups="false"... Read full blog post
As we move a greater number of services towards the cloud (Amazon Web Services) we pioneer our way into an brand new universe of opportunity. We also come across technical issues for which no documentation exists on the internet (we know sounds a bit like Star Trek and Lucasfilm). So we are learning every day, which makes this process very enjoyable.
To give an example, take amazon’s Load Balance service (ELB).
We moved some of our script-serving traffic to an auto-scaling load balancer and watched the results with all types of monitoring tools. The response time is fantastic! On their instances, the scripts are served in 0.15 seconds, our previous provider (one of the largest of the US / world) served scripts in 0.20 seconds. Thats a 25% speed increase !!
There is, however, a downside: Once in a while it takes 1.5 seconds to load a script. We are currently... Read full blog post
Last week i had to configure a new tomcat server to work with ssl and the apr libary, i’m going to put my notes here cause it took me some time to figure it all out, and maybe it will help some other people too
Step 1. update your server to ahve all the nessacary stuff
We need OpenSSL including the devel-libs and ofcourse the APR libs
yum install openssl openssl-devel apr apr-devel
Step 2. Building the tomcat-native-apr libs
I assume you have a working tomcat allready installed, mine is in /home/tomcat change it to your tomcat home dir
you need to unpack the sourcefiles located in your tomcathome/bin directory
tar xvfz tomcat-native.tar.gz
go to the building directory
cd tomcat-native-*/jni/... Read full blog post
Step 1. Define your loadbalancer
As of now, Amazon only supports 2 ports: the default web-traffic on port 80 and ssl secure https traffic on port 443.
Unfortunatly you need to choose 1 of them, but i hope they will change it in the future. You also need to select a availabilityzone, make sure your servers are in the same zone..
elb-create-lb LoadBalancerNameHere --headers --listener "lb-port=80,instance-port=8080,protocol=HTTP" --availability-zones YourPreferedZone
Step 2. Define your LaunchConfiguration
The LaunchConfiguration stores the ami you want to autoscale and the instancetype to go with that
as-create-launch-config LaunchConfigurationNameHer --image-id YourAmiIdHere --instance-type YourInstanceTypeHere
Step 3. Define your... Read full blog post
Welcome to our new blog
I wanted to share some of my thoughts regarding our goal to move Opentracker to Amazon Webservices.
I started with creating my own EC2 ami’s based on a clean install of centos 5.3, and installed java and our default webserver wich is Apache Tomcat 6
the commands to make your own ami are pretty simple:
copy your keys to the instance:
scp -i id_rsa-your-key /path/to/keys/pk.pem /path/to/certificates/cert.pem root@public-ami-dns-name:/mnt
go to /tmp dir
create a volume for bundeling
ec2-bundle-vol -d /mnt --prefix centos-5.3_tomcat-6.0.18_jdk188.8.131.52 -k /mnt/pk.pem -c /mnt/cert.pem -u your-account-number
upload bundle volume to S3
ec2-upload-... Read full blog post