Talk given at #IWMW16 Watch the recording at https://youtu.be/dr1cpjWKY0Q?t=5h5m24s
The majority of websites are using Google Analytics for tracking and reporting (W3Techs report 82.9% of tracked sites are using Google Analytics). Since launching Google Analytics in November 2005 the Internet has radically changed moving away from static content to fully interactive web applications. Google have addressed this with the integration of event tracking and other collection techniques, including deployment within mobile apps. As Google Analytics continues to evolve there are a number of features and use cases you might not be aware of. This presentation is designed to highlight some of the emerging Google Analytics hacks which will hopefully inspire you to look at your analytics problems and opportunities in new ways. For example, we look at how Google Analytics can be used as part of the Internet of Things, using low cost computing like Raspberry Pis for recording and analysing everything from sensor data to physical switches. We also look at bridging offline and asynchronous tracking sending measurement data in batches when connectivity is re-established as well as pushing data from third party APIs into Google Analytics using free tools.
13. Event Tracking
Event tracking is a piece of code with custom values that
you fire off when you want to track something
ga('send',
'event', // Required: type of tracking
'category', // Required: Category of event
'action', // Required: Action of event
'label', //optional value
value); //optional number
ga('send','event','category','action','label',value);
Slide Credit: Nico Miceli nicomiceli.com
15. Warning: “Google Analytics does not allow
Personally Identifiable Information (PII) (such
as names, email addresses) stored in the
Application. Your Analytics account could be
terminated if you use any of this information”
NO PERSONALLY IDENTIFIABLE INFORMATION
Slide Credit: Nico Miceli nicomiceli.com
16. “If your site has its own authentication system, you
can use the User ID feature, in addition to the
client ID, to more accurately identify a user across
all the devices they use to access your site.”
… BUT
// At a later time, once the `userId` value is known,
// sets the value on the tracker.
ga('set', 'userId', USER_ID);
JavaScript
24. The measurement protocol lets you send event/hits data to
Google Analytics via HTTP Requests:
https://www.google-analytics.com/collect
Name Parameter Example Description
Protocol Version v v=1 The protocol version.
The value should be 1.
Tracking ID tid tid=UA-123456-1 The ID that
distinguishes to which
Google Analytics
property to send data.
Client ID cid cid=xxxxx An ID unique to a
particular user.
Hit Type t t=pageview The type of interaction
collected for a particular
user.
Slide Credit: Nico Miceli nicomiceli.com
27. VLE
Script
Google
Analytics
Web View
• Runs every 15 min
• Identity stripped
• Text processing producing counts
Interacting with 3rd party APIs
https://mashe.hawksey.info/?p=17088
28.
29. Parameter Value Type Default Value Max Length Supported Hit Types
qt integer None None all
Image Credit: CC-BY-SA per Corell
https://flic.kr/p/7BYwFa
Queue Time
Used to collect offline / latent hits
30. Image Credit: CC-BY Mikael Leppä
https://flic.kr/p/pdkyS3
Batch
Send multiple hits in a single request
● A maximum of 20 hits can be specified per request.
● The total size of all hit payloads cannot be greater than 16K bytes.
● No single hit payload can be greater than 8K bytes.
44. Hopefully, you now know
a little more what is
possible
Image credit: CC-BY-NC-ND
Joe Foley https://flic.kr/p/Drgv6
Slide Credit: Nico Miceli nicomiceli.com
45. Image credit: timmacpherson.com
Now it’s time to get
creative!
Rethink the interactions
and engagement
Ask questions
Slide Credit: Nico Miceli nicomiceli.com