Header tag

Tuesday, 19 March 2024

Rollarama World Football Dice Game

Rollarama World Football is a "shootout dice and card game", and so when I saw it on the shelf of a charity shop recently, I decided to give it a try.




The game comes with full instructions on how to play it "properly", but I just liked the idea and the packaging which clearly showed a six-sided die, a 12-sided die and a 20-sided die.

The dice values aren't 1-6, 1-12 and 1-20; instead the values are the number of goals a particular team scores in a game.  Each country (there are 30 in total) has a card which shows if it's assigned the 6, 12 or 20 sided die and you roll that die for that country when it plays a match.  For example, Canada is a D6 team, while Portugal is a D20 team and Mexico is a D12 team.  There are rules included on how to play this as a two-player game, using the dice and the cards, but I found a more interesting game for one player using the same raw materials.

The questions I was most interested in answering are how fair the game is, and if the game could be won by one of the 'weaker' D6 teams.  To do this, I set up my own World Football championship, the 2023-4 Winter World Cup.  This comprises five groups of six countries (the 30 countries in total) who will play in their own mini-league.  The top team from each group goes forward, along with the top three performing runners-up, to give eight teams. These eight will play in quarter-finals, then semi-finals and a final.  The draw for the knockout stages will be entirely random, I'm not seeding any team.

Here's the starting roster and the groups, all drawn randomly from the deck of 30 cards.  As you can see, Brazil got a very good draw as the only D20 country in a group of D6s, while Group A has no D20s.

Group A:
D12: Serbia, Denmark, Mexico
D6: Saudi [Arabia],  USA, Cameroon, 

Group B:
D12: Croatia, Switzerland
D20:  Spain, England, Germany, France

Group C:
D6: Tunisia
D12:  S Korea, Senegal, Japan
D20:  Netherlands, Uruguay

Group D:
D6:  Scotland, Ghana, Canada, Wales, Morocco
D20:  Brazil

Group E:
D6:  Ecuador
D12: Iran, Poland
D20: Portugal, Argentina, Belgium

Each team in the group plays the other teams once, so in a league of six, there are 15 games altogether.  There are three points for a win, one for a draw and none for a loss.  In the event of a tie on points, then goal difference will be taken into account.

Here are the results:

GROUP A

Serbia

1

USA

3

Cameroon

2

Denmark

2

Mexico

2

Saudi

1

Serbia

3

Cameroon

2

USA

3

Mexico

1

Denmark

2

Saudi

1

Serbia

4

Denmark

3

USA

1

Saudi

0

Mexico

3

Cameroon

1

Serbia

4

Mexico

1

USA

1

Denmark

3

Saudi

0

Cameroon

3

Serbia

1

Saudi

1

Cameroon

3

USA

0

Denmark

2

Mexico

4


GROUP B

Spain

3

Croatia

1

Switzerland

3

England

3

Germany

1

France

3

Spain

5

Switzerland

2

Croatia

4

Germany

0

England

5

France

2

Spain

3

England

2

Croatia

0

France

2

Switzerland

4

Germany

3

Spain

1

Germany

1

Croatia

2

England

5

France

5

Switzerland

3

Spain

3

France

5

Croatia

2

Switzerland

1

England

5

Germany

0


GROUP C

South Korea

2

Senegal

3

Japan

4

Netherlands

2

Uruguay

4

Tunisia

3

South Korea

2

Japan

1

Senegal

4

Uruguay

1

Tunisia

0

Netherlands

5

South Korea

1

Netherlands

4

Japan

3

Uruguay

0

Senegal

1

Tunisia

2

South Korea

2

Uruguay

3

Japan

1

Tunisia

0

Netherlands

0

Senegal

2

South Korea

2

Tunisia

3

Senegal

4

Japan

0

Uruguay

2

Netherlands

4

 GROUP D

Brazil

0

Scotland

3

Morocco

2

Canada

2

Wales

1

Ghana

2

Brazil

1

Morocco

0

Scotland

2

Wales

2

Canada

0

Ghana

0

Brazil

2

Canada

2

Scotland

3

Ghana

3

Wales

0

Morocco

2

Brazil

0

Wales

1

Scotland

2

Canada

3

Ghana

2

Morocco

1

Brazil

0

Ghana

0

Scotland

0

Morocco

2

Wales

0

Canada

2

GROUP E

Iran

3

Portugal

3

Argentina

2

Belgium

5

Ecuador

1

Poland

4

Iran

3

Argentina

5

Portugal

3

Ecuador

1

Belgium

2

Poland

3

Iran

4

Belgium

2

Portugal

4

Poland

1

Ecuador

2

Argentina

1

Iran

3

Ecuador

0

Portugal

4

Belgium

3

Poland

2

Argentina

2

Iran

1

Poland

4

Portugal

5

Argentina

2

Ecuador

0

Belgium

3

Final tables (this game is a statistician's or an analyst's dream!)

GROUP A

Team

P

W

D

L

F

A

GD

Pts

Serbia

5

3

1

1

13

10

3

10

Mexico

5

3

0

2

11

11

0

9

USA

5

3

0

2

8

8

0

9

Cameroon

5

2

1

2

11

8

3

7

Denmark

5

2

1

2

12

12

0

7

Saudi

5

0

1

4

3

9

-6

1


GROUP B

Team

P

W

D

L

F

A

GD

Pts

France

5

4

0

1

17

12

5

12

England

5

3

1

1

20

10

10

10

Spain

5

3

1

1

15

11

4

10

Croatia

5

2

0

3

9

11

-2

6

Switzerland

5

1

1

3

13

18

-5

4

Germany

5

0

1

4

5

17

-12

1


GROUP C

Team

P

W

D

L

F

A

GD

Pts

Senegal

5

4

0

1

14

5

9

12

Netherlands

5

3

0

2

15

9

6

9

Japan

5

3

0

2

9

8

1

9

Tunisia

5

2

0

3

8

13

-5

6

Uruguay

5

2

0

3

10

16

-6

6

South Korea

5

1

0

4

9

14

-5

3


GROUP D

Team

P

W

D

L

F

A

GD

Pts

Canada

5

2

3

0

9

6

3

9

Ghana

5

2

3

0

7

5

2

9

Morocco

5

2

1

2

7

5

2

7

Scotland

5

1

2

2

10

10

0

5

Brazil

5

1

2

2

3

6

-3

5

Wales

5

1

1

3

4

8

-4

4


GROUP E

Team

P

W

D

L

F

A

GD

Pts

Portugal

5

4

1

0

19

10

9

13

Poland

5

3

1

1

14

10

4

10

Iran

5

2

1

2

14

14

0

7

Belgium

5

2

0

3

15

13

2

6

Argentina

5

1

1

3

12

17

-5

4

Ecuador

5

1

0

4

4

14

-10

3



Notes:

Serbia and Mexico were first and second in Group A, as would be expected as D12s.

Group B was won by France, and there were no major upsets.

Senegal won Group C, ahead of the two D20 teams Uruguay and Netherlands.  Senegal won four of their five games, including a 4-1 win over Uruguay and a 2-0 win against the Netherlands.

In a significant shock, Brazil game fifth in Group D.  As a D20 country playing D6s, Brazil were expected to come first, but only won one of their games.  It was very tight among the other teams, as they were all D6 teams and therefore had a high probability of drawing each other.  Six of the 15 games were drawn.

Portugal topped Group E easily, winning four of their five games and remaining unbeaten throughout.  Ecuador, the only D6 team in the group, came last, winning only one game.

The group winners were:
Serbia (D12), France (D20), Sengal (D6), Canada (D6) and Portugal (D20).

The best-performing runners-up were Mexico (A), England (B) and Netherlands (D).

The Quarter Finals, drawn from the eight qualifying teams:

Serbia vs Netherlands
France vs Senegal
Canada vs Portugal
Mexico vs Ghana

Serbia       2     Netherlands     2 (Netherlands 5-2 on penalties)
France       2    Senegal              1
Canada     1    Portugal             2
Mexico     1     Ghana                1 (Mexico 11-10 on penalties)

The Semi Finals, drawn from the four winners

Netherlands vs France
Portugal vs Mexico (who have done surprisingly well)

Netherlands 4 - France 5
Portugal 4 - Mexico 4 (Portugal win 3-2 on penalties)

The Final was unsurprisingly between two D20 teams, France and Portugal.

France 2 - Portugal 1


The dice:

Although I've described the teams as D6, D12 and D20, the dice aren't normal dice with values 1-6, 1-12 or 1-20.  Most football matches don't end with scores like Liverpool 18 - Man Utd 11.  The dice have duplicated numbers - here are the values for their sides:

D6:  0, 1, 1, 2, 2, 3 --> mean = 1.5
D12: 0, 1, 1, 1, 2, 2, 2, 3, 3, 4 --> mean = 1.58 (19/12)
D20: 0, 0, 1, 1, 1, 2, 2, 2, 2, 3, 3, 3, 3, 4, 4, 4, 4, 5, 5, 5 --> mean = 2.7 (54/20)

In conclusion - this is a great game.  I didn't play it according to the instructions, but took the raw materials from the game and made it my own - and thoroughly enjoyed it.  I didn't analyse all the maths (what's the probability of a D6 team drawing against a D12 team? Or winning?) but rolled the dice, recorded the scores, and built and Excel spreadsheet to solve the league maths for me!  Was it fair?  Yes - the D6 teams have a chance of winning (and the multiple upsets during the championship show this) and the D20s have a chance of being knocked out (Brazil in a league of D6 teams).  The values on the dice make sure that every team has a chance of winning, even if it's slim.

In a future post, I'll play a cricket-by-dice game, and compare the results!

Other articles I've written looking at data and football

Checkout Conversion:  A Penalty Shootout
When should you switch off an A/B test?
The Importance of Being Earnest with your KPIs
Should Chelsea sack Jose Mourinho? (It was a relevant question at the time, and I looked at what the data said)
How Exciting is the English Premier League?  what does the data say about goals per game?

Wednesday, 10 January 2024

Statistics: Type 1 and Type 2 Errors

 In statistics (and by extension, in testing), a Type I error is a false positive conclusion (we think a test recipe won when it didn't), while a Type II error is a false negative conclusion (we think the test recipe lost, when it didn't).  

Making a statistical decision always involves uncertainties, because we're sampling instead of looking at the whole population.  This means the risks of making these errors are unavoidable in hypothesis testing - we don't know everything because we can't measure everything.  However, that doesn't mean we don't know anything - it just means we need to understand what we do and don't know.


The probability of making a Type I error is the significance level, or alpha (α), while the probability of making a Type II error is beta (β).  Incidentally, the statistical power of a test is measured by 1- β.  I'll be looking at the statistical power of a test in a future blog.

These risks can be minimized through careful planning in your test design.

To reduce Type 1 errors, which mean falsely rejecting the null hypothesis - and calling a winner when the results were flat - it is crucial to choose an appropriate significance level and stick to it. Being cautious when interpreting results and also considering what the findings mean may also help mitigate Type 1 errors.  Different companies have different significance levels that they use when testing, depending on how cautious or ambitious they want to be with their testing program.  If there are millions of dollars at risk per year, or developing a new site or design will cost months of work, then adopting a higher significance level (90% or higher) may be the order of the day.  Conversely, if you're a smaller operator with less traffic, or a change that can be easily unpicked if things don't go as expected, then you could use a lower significance level (80% or higher).

It's worth saying at this point that human beings are lousy at understanding and interpreting probabilities, and that's generally.  Confidence levels and probabilities are related but are not directly interchangeable.  The difference in confidence between 90% and 80% is not the same as between 80% and 70%.  It becomes more and more 'difficult' to increase a confidence level as you approach 100% confidence.  After all, can you really say something is 100% certain to happen when you've only taken a sample (even if it's a really large sample)?  On the other hand, it's easy to the point of inevitable that a small sample can give you a 50% confidence level.  What did you prove?  That a coin is equally likely to give you heads or tails?


 Type 2 errors can be minimised by using high levels of statistical significance, or (unsurprisingly) by using a larger sample size.  The sample size determines the degree of sampling error, which in turn sets the ability to detect the differences in a hypothesis test. A larger sample size increases the chances to capture the differences in the statistical tests, and also increases a test's power. 

Practically speaking, Type 1 and Type 2 errors (false positives and false negatives) are an inherent feature of A/B testing, and the best ways to minimize them is to have a pre-agreed minimum sample size, and a pre-determined confidence level that everyone (business teams, marketing, testing team) are all agreed on.  Otherwise, there'll be discussions and debates afterwards about what's a winner, what's confident, what's significant and what's actually a winner.  

Thursday, 28 December 2023

Firsts of 2023

 
I've written these "firsts" for the last two years now, this being the third.  Even in my mid forties I'm doing things for the first time:

First time I saw a deer in the wild - while on holiday in Devon.  We were staying in a secluded bungalow - actually a converted horse stable- which overlooked some fields, and one morning saw a wild deer walking across the field.  We're going back to the same bungalow in 2024, and this time I'll have my camera on permanent standby!

First time dressed up as Captain Picard... and also as Hannibal from the A Team. I've decided to make my grey hair and receding hairline work for me and embrace it.  I mean - Darth Vader is still first choice, but I'm diversifying. The Hannibal costume needs work - I went with a friend who dressed as Murdock and people still couldn't tell who we were.  This meant this was the first year I dressed up as four different characters: Vader, Batman, Hannibal and Picard.

Hosted a colony of bees under a loose roof tile. This was during the summer, when a colony of bumblebees borrowed some of our roof space for about three weeks.  If you know me, you'll know I like bees, but this was a little too close for comfort.  They were very well behaved and kept themselves to themselves but it was still a little disconcerting and we'll get the tile fixed in spring.

First time I was in a group that was nominated for a community award.  I unofficially joined our local Star Wars/Cosplay group, the Endon Stormtroopers, in 2023 and in 2024 was made official (I have been given my own T Shirt).  We didn't win, losing out to a group that was doing even more for their community, but it was cool to be nominated.  That's me as Batman in the picture below.


2023 was also a challenging year. After discovering drops of blood in my wee in August, I was fast-tracked through the GP and hospital process to see if I had cancer.  This opened up a long list of firsts: first CT scan (lie on a bed and have a magnetic polo mint go backwards and forwards around me), first cannula (I forgot to mention they injected me with iodine to make my insides show up better in the scan), and also a little camera.

This is where I was injected, on the inside of my elbow: the red rash is from the sticky dressing that was an effective exfoliant!

I'm fine. I have learned a lot about the human body - my human body in particular - and been given the thumbs up. I'm having an ultra sound in January to check on my kidney stones (the most likely cause of this entire episode).

This year was also the first time one of my children has gone overseas for a school trip - Germany, by coach, for four nights.  

There were other highlights too, like the first time I got to see the Red Arrows fly over my house, watching them from my front doorstep (I wasn't expecting them, otherwise I'd have a photo to prove it).

I constructed my first scale model diorama this year - I'd dabbled with models during my time as a student, but this year I actually built and finished a full scene. Not just one, but three (with others in progress).


This year also saw me learn to play "All Things Bright and Beautiful" on the piano.  It's a sneaky little tune. Most of us sang it at primary school, so we think it's easy to play, because it's easy to sing.  Ha!  It's a very complicated little ditty, with sharps and modulations all the way through it.  And it's written as a hymn with close four-part harmony, so you can't just whack out some chords and hope for the best.  I had to learn to play it from memory (I can't sight read fast enough to read and play).  Why? I played at my brother-in-law's wedding and this was the song he'd requested.

Having seen a wild deer while on holiday, this year also saw the first time I've chased a fox off the front garden, early in one summer morning.

Finally, in 2023, I carried out Careers Interviews with Year 10 and Year 11 students (aged 14-16) at my children's high school. For two days, I interviewed students to help them practise their interview technique, asking them the kinds of questions they'd be asked during interviews for jobs or college places.  It was fascinating to see the difference between the Year 10 and Year 11 students, and between those who had prepared and those who hadn't!  Those who hadn't probably thought they'd done well, but were not even close to those who had.

So, 2023 had some firsts that I would have preferred to have dodged, but which have given me useful experience for the future.  Happy New Year!

The Lists of Firsts

A first time for everything: 2018
2019 in reflection
First times in 2021 list
First times of 2022
First times in 2023
Things I did for the first time in 2024

Tuesday, 29 August 2023

Team-Building Exercises and Games for Remote Workers

 The pandemic and lockdown period of 2020-2021 generated a quantum leap in the way in which we work.  I mean - I was working remotely for nine years before the pandemic, but for the vast majority of my colleagues, there was a significant change in working patterns.  My team went completely remote - all working from home - and in September 2021 I became the team's manager.  Since then, we've had some team members leave; I've recruited some new team members, and had the challenging task of building a team.

My team comprises eight project managers plus me, spread across four countries and multiple timezones, so you can imagine that meeting in person isn't going to happen any time soon.  However, that did not stop us from building a strong positive team ethos, and getting to know each other better.  

How?  By playing games.  I mean 'completing exercises' ;-). Here's a list, and a few additional points at the end.

1.  Whose Desk Is This?

Each team member takes a photograph of their desk, and uploads the picture to a shared PowerPoint Deck.  On a team call, we all review the photographs one by one, and try to determine whose desk this is.  It's fun, it's different, and it works as the team tries to deduce who is most likely to have a tidy desk, and untidy desk, toys on their desk... pictures on their wall... the widescreen monitor and so on.  The hilarity follows when the team realise they were completely wrong!


2.  Whose Fridge Is This?
Same principle, but more personal than the fridge.  We discovered that one team member keeps a thermos flask in the fridge (it's her husband's, and she goes mad about it), and that fridges are a lot more expensive in Brazil than in Europe.  We also quizzed each other about our eating habits, and what that stuff is in the glass bowl on the top shelf.  Again, entertaining and a better ice-breaker than 'tell us about yourself'.

3.  Whose Car Is This? and its near neighbour, Whose Front Door Is This?
You get the idea.  For Whose Car Is This, we went further by actually finding stock photos of our cars instead of just taking photos (although this was included as usual).  We were getting so good at looking around the photos (for example, clues for items on top of the fridge, the general scene of the kitchen) that we stepped it up by having the web-source photos as well.  Front doors are front doors, there's no disguising them.

For an added bonus, when you get close to the holiday season, you can have Whose Christmas Tree Is This?  We did, and everybody took part - Christmas tree, seasonal decorations, whichever.  

4.  Online Pictionary (draw the object).  

For this, I prepared a list of seasonal objects - snowflake, Santa Claus, elf, snowman, wise man, shepherd, and so on.  The team split themselves into two groups, and each person shared their screen and used Paint to draw the word.  I am sure there are better online versions of this game, but there was something charming and hilarious about watching everyone try and draw using MS Paint that worked well.  It worked for us in the pre-Christmas period, but could work at any time of year with a given theme.

5.  Two Truths and a Lie

This has become our team favourite, and it requires no extra work from the manager.  You just tell everyone to prepare two truths and a lie, and to either update a shared deck or mail their statements to you.  They don't even have to tell you which is the lie, and then you can play along too.  And, if you take notes and listen to what everyone says, you'll have some great source material for the next activity...

6.  Online Quizzes

We use Kahoot, which is simple, straightforward and requires no costs if you have 10 or fewer team members.  As the manager, you become the question master and ask a series of multiple choice or true/false questions.  You'll need to write the questions in advance, and these can cover any (or multiple) topics.  Some questions are work-related - "What is your analysis of this data?" "What does this data show?" "What is the most important thing to remember about XYZ situation?" and some aren't - "Which member of the team said they most wanted to spend an afternoon with Agatha Christie?" "Which member of the team said that they wanted to do a parachute jump?"

The great thing is that most of these games can be used with teams of any size and discipline (engineers, sales, purchasing and HR can all play these games). What else works well in generating and building team spirit?

A.  Regular team meetings.
I can't emphasise this enough.  Even if you don't have a team-building exercise planned for the week, and everybody's rushed off their feet, and there isn't much to add to all the emails, keep the call anyway.  Your team will appreciate face-time with you, and a chance to catch up with you.  You might not have much to say, but they may have questions for you, so don't cancel!

B.  Regular one-to-ones alongside the team meetings
I meet with each member of my team once a fortnight (or once every two weeks, or bi-weekly).  This gives each member chance to ask you questions that are specific and relevant to them, on any topic that they want to discuss, and which may not be suitable in a team forum.  Cancel these at your own risk!

Friday, 30 June 2023

Goals (and why I haven't posted recently)

I'll probably blog sometime soon about goals, objectives, strategies and measures.  They're important in business, and useful to have in life generally.  For now, though, I'll have to explain why I haven't blogged much recently at all:  I've found a new (old) hobby:  constructing Airfix models.  I started with Airfix models when I was about 10 or 11 years old - old enough to be patient to wait for the glue to dry, and careful enough to plan how to construct each model.  I had a second wave of interest in my late teens and early 20s, and more recently earlier this year (courtesy of my 11-year-old, now 12-year-old son).

So this is what's been filling my time - building with my son.

Here's my first solo-ish project for 25 years:


  

The set is the Airfix 25 pdr Field Gun with Quad - one that I bought and built during my time at university.  I enjoyed the set, mostly because of the various figures that come with the set.  I've not painted any of my sets in snow camouflage before - and you'll soon see that I'm not a stickler for historical accuracy: I paint what I like!

   

I identified this figure as a troop commander (his flat cap compares with the helmets that the rest of the troop are wearing).  The Quad truck has a gap in the roof, and I decided I was going to stand the commander in the vehicle, peering through the roof.  Yes, he's a very easy target standing there like that, but I figure - why not? 

  

I drew out the overall scene on a piece of wooden board, sketching the position of the vehicle, trailer and gun, and the key figures.  We also have some injured casualties in our collection, and they featured too.  The trees were obtained cheaply from Amazon, and they are cheap, low-quality and quite small for 1/72 scale.  I used scenic roll (green) and white spray paint (generic matt paint) to deliver the snow.  The spray paint was cheap and it didn't spray evenly, but that worked to my advantage to give patchy but heavy coverage.




 

 

  
The final diorama included a Metcalfe model pillbox (the square version), some additional bushes (not shown here) and a good complement of trees.  I added some crater marks (but no depth to the scene) to explain the casualties, and then added some medics too (they were trickier).

Next?  A village scene, with a pair of Tigers ploughing through the remains of a continental village (somewhere).  As ever, it's all about the modelling, and has very little to do with historical accuracy!























Sunday, 30 April 2023

Personalization, Segmentation or Targeting

Following all my recent posts on targeting (or personalization), I was discussing website content changes with a colleague. I was explaining how we could test some form of interactive, real-time changes on our site.  His comments were that this wasn't real 1-to-1 personalization and what I was actually doing was just segmentation and content retargeting.  This started me thinking, and so I'd like to share my thoughts on 1-to-1 targeting is possible, easy and worth the effort.  Or should we be satisfied with segmentation and retargeting?


1-to-1 targeting requires the ability to show any content to any user. It probably needs a hige repository of content that can be accessed to show content that isn't shown to other users, but which is deemed optimal for a particular user.

1. How do you decide which type of user this particular user should be classed as?  
2.  How do you determine which content to show this particular user (or type of user)?
3.  When the targeting doesn't give great results, how can you tell if the problem is with 1. or 2.?

And, as a follow-up question, why is "targeted" content drawn from a library held in higher esteem than retargeting existing content? Is it better because it's so difficult to set up?

Content retargeting - moving existing content on the page - does not require new content, but "isn't real 1-to-1 targeting."  This is true, but I would argue that the difference - mathematically at least - is negligible.  The huge library of targeted content isn't going to be able to match the potential combinations of content that can be achieved just by flipping page content around to promote a particular group of products.

In previous examples on targeting, I've looked at having four product categories that can be targeted.

How many combinations are there for the four products A, B, C, D?

4 * 3 * 2 * 1 = 24

There are four options for the first placement, leaving three for the second placement, two options for the third and only one left for the final place.

This is a relatively simple example - most websites have more than just four products or product categories in their catalogue (even Apple, with its limited product range, has more than four).

Let's jump up to six products:
6 * 5 * 4 * 3 * 2 * 1 = 720.

At this point, retargeting is going to start scaling far more easily than 1-to-1 personalization. 

Admittedly, it's highly unlikely that all 720 combinations are going to be used and shown with equal probability - we will probably see maybe 6-10 combinations that are shown most often, as users visit just one or two product categories and identify themselves as menswear, casual clothes, or womenswear customers.  The remaining three or four categories aren't relevant to these customers, and so we don't retarget hat content.  I mean: if a user is visiting menswear and men's shoes, then they aren't going to be interested in womenswear and casual clothing, so the sequence of those categories is going to be irrelevant and unchanged.

So, we can group users into one of 720 "segments", not based on how we segment them, but how they segment themselves.  This leads to a pseudo-bespoke browsing experience (it isn't 1-to-1, but the numbers are high enough for it to be indistinguishable) that doesn't require the overhead of a huge library of product content waiting to be accessed.

When does the difference between true personalization and segmented retargeting become indistinguishable?  Are we chasing true 1-to-1 personalization when it isn't even beneficial to the customers' experience?

I would say that it's when the number of combinations of retargeted content becomes so large that users are seeing a targeted experience each time they come to the page.  Or, when the number of combinations is greater than the number of users who visit the page.  Personalization is usually perceived - and presented - as the holy grail of Web experience, but in my view it's unnecessary, unattainable and frequently unlikely to actually get off the drawing board. Why not try something that could give actual results, provide improved customer experience and could be set up this side of Christmas?




Tuesday, 28 March 2023

Non-zero Traffic

Barely a month ago, I wrote about a challenge I was having tracking the traffic on this blog.  I had identified that I wasn't seeing any visitors on mobile phones.  Not one.

I'd taken some steps to fix this, and I had been able to track me using my own phone, but only from organic search.  I was still not tracking actual traffic.

Then I found an article that explains how to connect Blogger to Google Analytics 4 (and this has become justification for me to move to GA4).  

All I had to do was to enter my GA4 ID number into the Blogger setting for tracking... and that was it.  It took me weeks to track down the solution, but since then, I've been tracking mobile traffic:

At the time of writing, I've had the fix live for three weeks, and this is how it's looking compared to the three weeks prior to the fix.

I've carried out a number of checks to make sure the data is valid: 

are the mobile and desktop numbers different (or am I double-counting users?)?

are the desktop numbers even numbers (another indication of double counting)?

are the mobile numbers cannibalising the desktop numbers, or are they additional (and thankfully they look good).

In all cases, the data look good, showing clear and distinct differences between the mobile and desktop traffic, but I'm still glad I was able to validate the data accuracy. 

Other articles I've written on Website Analytics that you may find relevant:

Web Analytics - Gathering Requirements from Stakeholders