Download - Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Transcript
Page 1: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Designing evidence

vam.ac.uk/digital

Andrew LewisDigital Content Delivery ManagerVictoria and Albert Museum

Planning how to capture specific user behaviour as readable information to support evidence-based change

Page 2: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event tracking inGoogle Analytics

Making reportinglanguage readable

Planning datacapture schemas

Remote control using

Google Tag Manager

Page 3: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Before you start typing…

Page 4: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

@rosemarybeetleThis session’s data will be tweeted…

slideshare.net/AndrewLVandAThis session’s slides are here…

Page 5: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Interface use…

Page 6: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

…into evidence

Page 7: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Audience participation

Page 9: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Avoid data sad face

Page 10: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Fret not.

With these

techniques…

Page 11: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

you can…

Page 12: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

…see what works on your navigation

Page 13: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Why?

Page 14: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Why?

Page 15: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

See how people really use your touch services

Page 16: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

How much do users pinch to zoom?

How often do users scroll?

Page 17: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 18: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 19: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 20: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

…measure howgame results affect

the uptake of calls to action

Page 21: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

11.7%11.1%

10.6%19.4%

0.9%2.0%

3.5%3.4%

Game results affect impact of calls to action

“positive” result “negative” result

Page 22: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

….see where visitors really go

over your Wi-Fi

Page 23: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 24: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Where?

Page 25: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Language?

Page 26: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

...understand more about engagement

with your collections

Page 27: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 28: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 29: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 30: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 31: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 32: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

BrowsingTop 10 object pagesviewed, by country

EngagingTop 10 large images

downloaded, by country

Page 33: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Know what people do in your

audioguides

Page 34: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

tap, tap, taptappity tap

etc.

Page 35: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

All the interaction

s

of each individual

user

for every session

Page 36: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event tracking inGoogle Analytics

Making reportinglanguage readable

Planning datacapture schemas

Remote control using

Google Tag Manager

Page 37: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event Tracking converts

interactions into data in Google

Analytics

Page 38: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

I want to know …

…how effective each

promotional call-to-action is

on my home page

Page 40: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event Action 1.1Event Category 1

Event Label 1.1.1

Event Action 1.2Event Label 1.1.2

Event Label 1.2.1Event Label 1.2.2Event Category 2

Event Action 2.1Event Label 2.1.1Event Label 2.1.2

Categories Actions Labels

Page 42: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event tracking inGoogle Analytics

Making reportinglanguage readable

Planning datacapture schemas

Remote control using

Google Tag Manager

Page 43: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

With Tag Manager you configure data capture

through a web interface

Page 44: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

I want to know …

…how effective each

promotional call-to-action is

on my home page

Page 45: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Traditional Event Tracking

Page 46: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Tracking using Tag Manager

Page 47: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Tracking using Tag Manager

Page 48: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

TagContainer Tag Trigger Variable

Tag Manager concepts for beginners

How code gets in and data

comesout of the page

Defines the data sent

per interaction

Defines when data gets sent

Populates specific

values into tag

Page 49: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 51: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 52: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event tracking inGoogle Analytics

Making reportinglanguage readable

Planning datacapture schemas

Remote control using

Google Tag Manager

Page 53: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Reports that make sense have more

impact

Page 54: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 55: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 56: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 57: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 58: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event tracking inGoogle Analytics

Making reportinglanguage readable

Planning datacapture schemas

Remote control using

Google Tag Manager

Page 59: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Planning your data structure is how you get clear reporting to

work

Page 60: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Event Action 1.1Event Category 1

Event Label 1.1.1

Event Action 1.2Event Label 1.1.2

Event Label 1.2.1Event Label 1.2.2Event Category 2

Event Action 2.1Event Label 2.1.1Event Label 2.1.2

Categories Actions Labels

Page 61: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

SearchAudioguides - Europe 1600-1815 galleries

Search term used

Navigation - Clicked next item in a tour

Name of audio

Wi-Fi Web address visitors are trying to reach URL visited

Audio controls - Started playing an audio

Name of Tour

Navigation - Selected room tours option

Name of audioAudio controls - Paused an audio

Name of Room

Categories Actions Labels

Page 62: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Find out what your staff want in reports then design the data

structure to capture it

Page 63: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Design prototypes can be

rough and ready

Page 64: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

tap, tap, taptappity tap

etc.

Page 65: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 66: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 67: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 68: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 69: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

11.7%11.1%

10.6%19.4%

0.9%2.0%

3.5%3.4%

Game results affect impact of calls to action

Page 70: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 71: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 72: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 73: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Extracting largeamounts of data

Page 74: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Complex datasets can be created using

comma-separated event labels

Page 75: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 76: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 77: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Saving comma separated labels as CSV files

Page 78: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 79: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

The Google Analytics add-on for Google

Spreadsheetsis great for extracting

large sets of data

Page 80: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 81: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change
Page 82: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Checklist

Page 83: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

tweak! – once you get data you can always use it to adjust the capture if needed

what are the aims you want to test?what data would allow you to test those aims?Is the data you need already captured somehow?how do you name the data so staffwill understand it?what data structure will make reports look the way you want them to?make sure data structure you need is mirrored in your code (CSS classes, HTML element, ids, attributes, etc.)

once in place, see if it works!

apply triggers that capture data when the user behaviour occurs.

1. Agree objectives 2. Define success

measures 3. Do you need to

go bespoke?4. Consider ease of

reporting5. Design your data

hierarchy6. Apply hierarchy to page

code 7. Configure Google

Analytics8. Test 9. Tweak!

Page 85: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Things I wish I had known before I started…

Page 86: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Things to note about Tag Manager• Tag containers are essentially a hole in your page through which

to sneak stuff in

• Tag Manager allows retrospective application

• Published changes are updated even within cached pages as long as page is loaded (or reloaded unhanged)

• We use twin containers, but not officially recommended

• Now about a year into it but still learning

• Using a test property allows you to prototype without muddying real stats

Page 87: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Naming conventions• Start with the reports

• Naming your child – the future bar test

• Think about how two projects collide/cross-compare, not just one

• If you need to rename schema heading, NOTE it is not retrospective

• Grouping in event tracking can be extended with custom variables..

Page 88: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Advanced things that are cool• Cookies can control sessions

• Html element attributes can be set dynamically to store session data for tags to collect

• Date-stamping and random numbers can be used to differentiate anonymous users

• Clever naming extends three event tracking hierarchy layers into five or more

Page 89: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Further V&A Digital Media posts on this subject…How people really react when judged – as shown by game datahttp://www.vam.ac.uk/blog/digital-media/how-people-really-react-when-judged-as-shown-by-game-dataHow to gather data to show how visitors really use your site-specific featureshttp://www.vam.ac.uk/blog/digital-media/capturing-user-behaviour-specific-to-your-servicesWhy bother designing for tablet users?http://www.vam.ac.uk/blog/digital-media/why-bother-designing-layouts-for-tabletMaking visitor information easier for mobile phone usershttp://www.vam.ac.uk/blog/digital-media/making-mobile-users-experience-better

Page 90: Designing Evidence - Planning how to capture specific user behaviour as readable information to support evidence-based change

Thank you

vam.ac.uk/digitalVictoria and Albert Museum

Slides

@rosemarybeetleslideshare.net/AndrewLVandA

Follow