add initial subtitles for 2022

2024-09-19 16:03:52 +02:00 · 2022-12-03 22:35:41 +01:00 · 2022-12-03 22:35:41 +01:00 · e7377fe2a9
commit e7377fe2a9
parent 68360bbee3
14 changed files with 21596 additions and 0 deletions
--- a/Visualization/output.srt
+++ b/Visualization/output.srt
--- a/Matomo/output.srt
+++ b/Matomo/output.srt
@ -0,0 +1,884 @@
 1
 00:00:00,000 --> 00:00:20,040
 Hi, everyone. Glad to be here to talk about the topic for today, which is imagine an ideal
 2
 00:00:20,040 --> 00:00:32,680
 Matomo. So just before I start, I just want to say a few words about the context of this
 3
 00:00:32,680 --> 00:00:43,360
 presentation. Typically here, what I'm going to be talking about is providing a better experience
 4
 00:00:43,360 --> 00:00:51,840
 to marketing people, non-technical people, because a lot of what I'm going to be talking about can
 5
 00:00:51,840 --> 00:01:03,280
 be addressed using what I call some more technical strategies or resources. This is just my few ideas
 6
 00:01:03,280 --> 00:01:10,960
 and I really like that at the end of the presentation you can share your ideas also so we can build some
 7
 00:01:10,960 --> 00:01:19,600
 kind of list of our expectations regarding the tool in the future. So what we're going to be talking
 8
 00:01:19,600 --> 00:01:29,760
 about is Matomo itself, the Tag Manager, DataVis tool and Consent Management Platform. So let's dive
 9
 00:01:29,760 --> 00:01:36,160
 in directly. First of all, when we're talking about Matomo, there is something really annoying
 10
 00:01:36,160 --> 00:01:44,680
 that I have encountered many times is when you have a lot of websites and you want to find a
 11
 00:01:44,680 --> 00:01:52,360
 specific one. In this situation, you have to use the site's search field, but this site's search
 12
 00:01:52,360 --> 00:01:59,800
 field is located at the bottom of the page. So in my dreams, I would like to have the search site
 13
 00:01:59,800 --> 00:02:08,920
 panel right above so you can just type the name of the website and it's going to be right in front
 14
 00:02:08,920 --> 00:02:19,280
 of your house. This is the first thing, place search fields above. The second one is a bit more
 15
 00:02:19,280 --> 00:02:25,680
 annoying, I think, because when you're doing web analytics, you're talking about digital performance
 16
 00:02:25,680 --> 00:02:35,520
 and you're talking about metrics. And in some cases, those metrics are talking about specific
 17
 00:02:35,520 --> 00:02:44,080
 segments of audience. And unfortunately, for the moment, when you build your dashboard, you are
 18
 00:02:44,080 --> 00:02:55,440
 forced to segment your whole dashboard. You cannot segment just a metric within your dashboard. And
 19
 00:02:55,440 --> 00:03:03,920
 here, again, is some kind of footage that I made with my metric and the ability to have here the
 20
 00:03:03,920 --> 00:03:13,520
 segment directly based on this particular metric. Because otherwise, what we have to do is to take
 21
 00:03:13,520 --> 00:03:21,640
 the data out of Matomo and bring it to an external data visualization tool. It can be done, but for
 22
 00:03:21,640 --> 00:03:29,800
 some users, for some teams, I have encountered the situation where they just want to remain within
 23
 00:03:29,800 --> 00:03:39,120
 Matomo and not go outside of it. So this one is, I think, a really interesting one, because the
 24
 00:03:39,120 --> 00:03:49,000
 whole idea behind presentation is to have some kind of complete web analytics suite. And this
 25
 00:03:49,000 --> 00:04:00,240
 feature, I think, is quite valuable. Another example of stuff that are annoying in the
 26
 00:04:00,240 --> 00:04:09,640
 projects is the situation where you want to follow users cross-domain. So for instance, you have a
 27
 00:04:09,640 --> 00:04:17,640
 client who says, OK, I have three, four, five websites, and I want to see what people do on
 28
 00:04:17,640 --> 00:04:24,080
 these different websites. Is there some cross user journey through these websites? And for that,
 29
 00:04:24,080 --> 00:04:32,960
 you create a Matomo site ID, and you configure it so that the journeys are captured through the
 30
 00:04:32,960 --> 00:04:40,600
 different domains. But unfortunately, in this situation, and this is the example that I display
 31
 00:04:40,600 --> 00:04:49,920
 here, you just have in the report page URL. In fact, you just have the URI. I think you don't
 32
 00:04:49,920 --> 00:04:56,280
 have the domain, and it's quite annoying because you don't know what you're talking about. So this
 33
 00:04:56,280 --> 00:05:02,760
 is the reason why I just added here in my dreams what it would look like. So for instance, here,
 34
 00:05:02,760 --> 00:05:11,240
 mysitea.com, slash FRFR, mysiteb.com, slash, et cetera, et cetera. Again, you can do some work
 35
 00:05:11,240 --> 00:05:18,640
 around with the Tag Manager, for instance. But again, the idea of the presentation is I am not
 36
 00:05:18,640 --> 00:05:26,880
 a technical person, and I encounter this situation that made me unhappy and thinking that Matomo is
 37
 00:05:26,880 --> 00:05:41,720
 not that interesting as a tool. Situation number three is when you look at the events reports,
 38
 00:05:41,720 --> 00:05:50,040
 most of the time you have people that are used to using Google Analytics reports. And it's quite
 39
 00:05:50,040 --> 00:05:57,200
 surprising for them not to see the whole variables, the whole event variables. So you have event
 40
 00:05:57,200 --> 00:06:03,680
 category, event action, but where is my event action? And again, the way I present it here is
 41
 00:06:03,680 --> 00:06:11,920
 when you want to separate the variables, but by default it's not presented that way. So it's,
 42
 00:06:11,920 --> 00:06:19,960
 again, more annoying for most people. So the idea here is that we could have event category,
 43
 00:06:19,960 --> 00:06:31,760
 event action, event names, and of course, event value. So I don't think it's a big deal, but yes,
 44
 00:06:31,760 --> 00:06:38,480
 you have to navigate through the different event variables, and that can be a bit disappointing.
 45
 00:06:38,480 --> 00:06:45,600
 In the same logic, when we're navigating through the different event variables,
 46
 00:06:45,600 --> 00:06:53,280
 and you're using, for instance, a search field. So here, for instance, I typed conversion here,
 47
 00:06:53,280 --> 00:07:00,360
 and I am on the event category level. I have my conversion, so it's filtered the way I want it.
 48
 00:07:00,360 --> 00:07:09,920
 But if I want to go down to the event action level, then my conversion, what I had typed here,
 49
 00:07:09,920 --> 00:07:19,880
 is lost. So again, it would be great if I could keep what I have typed here in the browser,
 50
 00:07:19,880 --> 00:07:29,200
 and also if the search filter could be located right above here, because if you have hundreds
 51
 00:07:29,200 --> 00:07:33,320
 of lines, then you have to scroll down all the way, and it's not hiding.
 52
 00:07:33,320 --> 00:07:43,960
 Another really annoying situation when I'm talking with my clients is why is that not
 53
 00:07:43,960 --> 00:07:52,080
 possible to combine more than three dimensions in custom reports? What do I do when I want to
 54
 00:07:52,080 --> 00:07:58,560
 have event category, event action, event name, and another custom dimension? And again,
 55
 00:07:58,560 --> 00:08:08,240
 for just regular marketing people, it's some kind of situation where they want to reject the tool,
 56
 00:08:08,240 --> 00:08:16,520
 because they think that it's not normal that you cannot, by default, and simply combine more than
 57
 00:08:16,520 --> 00:08:24,720
 three dimension. And again, they always make the comparison with Google Analytics. And since now,
 58
 00:08:24,720 --> 00:08:32,160
 it's obvious that we will have a lot of people migrating from GA to Matomo. I think that we
 59
 00:08:32,160 --> 00:08:46,560
 should address this specific topic. In the same field, talking about the custom reports,
 60
 00:08:46,560 --> 00:09:00,400
 I was a bit surprised to see that not all metrics are available in the custom reports. So for
 61
 00:09:00,400 --> 00:09:08,680
 instance, I had clients wanting the average time on page in a custom report, and I discovered that
 62
 00:09:08,680 --> 00:09:17,880
 this metric is not available on the custom reports. So I think that at least there should be somewhere
 63
 00:09:17,880 --> 00:09:29,080
 where it is explained that this metric or this dimension will not be available by default so that
 64
 00:09:29,080 --> 00:09:35,200
 people can be prepared so that we can explain. And it's really disappointing because you have
 65
 00:09:35,200 --> 00:09:40,480
 something in mind, you're quite sure of what you're going to be doing, and you discover that
 66
 00:09:40,480 --> 00:09:49,240
 unfortunately, it's not possible. So what I suggest is that all metrics available in Matomo
 67
 00:09:49,240 --> 00:10:03,480
 should be available in custom reports. Another situation, and it's regarding the moments where
 68
 00:10:03,480 --> 00:10:12,840
 you have dozens of websites to configure. And the example that I have in mind is the custom
 69
 00:10:12,840 --> 00:10:25,120
 dimension. Yes, if you have maybe 20, 30 custom dimensions to configure for 20, 30 websites,
 70
 00:10:25,120 --> 00:10:32,080
 it can take a lot of time. And if you do that manually, then you can make mistakes. So I again
 71
 00:10:32,080 --> 00:10:43,840
 assume that it can be done using maybe different APIs or technical stuff. But for regular marketing
 72
 00:10:43,840 --> 00:10:52,200
 people, I think it could be a good thing to have some kind of copy configuration button in the
 73
 00:10:52,200 --> 00:11:01,000
 admin section. And in my mind, then you can decide that yes, I want to copy a custom dimensions.
 74
 00:11:01,000 --> 00:11:11,800
 For the customers also, you can decide that you want to duplicate them. For the segments,
 75
 00:11:11,800 --> 00:11:19,360
 it's a bit different because when you create them, you can decide that it's for one website
 76
 00:11:19,360 --> 00:11:27,000
 or all of them. But yes, the idea here is to not lose time in the configuration. And I'm reading
 77
 00:11:27,000 --> 00:11:34,760
 in the conversation, Thomas. Yes, regarding the other side, I've made a change request. Yes,
 78
 00:11:34,760 --> 00:11:46,320
 I think that obviously we should be a lot more indeed to ask these kind of changes. Because if
 79
 00:11:46,320 --> 00:11:57,480
 we are allowed to ask that, then it be prioritized, of course. Thank you, Thomas, for coming. Another
 80
 00:11:57,480 --> 00:12:08,720
 thing is about API testing. And again, this is in my ideal world, because I know that it's something
 81
 00:12:08,720 --> 00:12:18,400
 that may take a lot of time, resource tests and so on. But if we want to have a complete analytics
 82
 00:12:18,400 --> 00:12:26,480
 suite, then I think that we should have a with you. We get each other for any tests. That's what
 83
 00:12:26,480 --> 00:12:35,720
 Google did with the feature that was in the beginning in GA for the test. And then they
 84
 00:12:35,720 --> 00:12:45,560
 launched optimize. So again, you can use the testing feature in that is, I think, quite well
 85
 00:12:45,560 --> 00:12:53,560
 made when we are talking about building the tests. But when it's about, again, you are someone with
 86
 00:12:53,560 --> 00:13:04,040
 not a lot of resources and not able to build pages and have to ask for developers to build
 87
 00:13:04,040 --> 00:13:10,360
 pages to run your tests, it's a bit disappointing. And it would be a great advantage if we could have
 88
 00:13:10,920 --> 00:13:19,720
 everything in a box. And the editor, I think, is also something that might be really valuable for
 89
 00:13:19,720 --> 00:13:35,240
 the two as a global analytics suite. Something again, quite annoying is about the unique visitor
 90
 00:13:35,240 --> 00:13:45,480
 metric. It appears that by default, this metric is not available for custom periods in the reports.
 91
 00:13:45,480 --> 00:13:56,920
 It is documented. But you have to have a look in the documentation. Because what happens is that,
 92
 00:13:56,920 --> 00:14:05,880
 for instance, here I have this metric in a Google Data Studio. And at the first site, I'm thinking,
 93
 00:14:05,880 --> 00:14:12,600
 oh, something went wrong with my dashboard. Something is not working. And in fact, it's just
 94
 00:14:12,600 --> 00:14:20,760
 that unique visitors is not activated for custom dates and custom periods. So again, you have to
 95
 00:14:20,760 --> 00:14:31,800
 ask the people that handle the Matomo instance to make a change in some kind of technical file.
 96
 00:14:31,800 --> 00:14:40,040
 And then it's activated. And apparently, it's not activated by default because it costs a lot in
 97
 00:14:40,040 --> 00:14:46,600
 terms of resources on the servers. I'm not quite aware of that because, again, I'm not a technical
 98
 00:14:46,600 --> 00:14:52,680
 person. But this is something not acceptable for most people, for most marketing people. The unique
 99
 00:14:52,680 --> 00:14:58,680
 visitor metric is some kind of basic metric. And when you encounter the situation firstly,
 100
 00:14:58,680 --> 00:15:04,680
 and you explain to the customer that, oh, yes, in fact, the metric is not available by default,
 101
 00:15:04,680 --> 00:15:09,720
 they just don't get it. They just don't understand why can it be, how can it be possible that this
 102
 00:15:09,720 --> 00:15:18,120
 simple standard metric is not by default available on that tool. And this is the situation I
 103
 00:15:18,120 --> 00:15:24,760
 encountered a lot where people rejected it because they thought that, no, this is not possible. It's
 104
 00:15:24,760 --> 00:15:32,120
 not acceptable that this simple metric we cannot access simply. And we have to ask our IT department
 105
 00:15:32,120 --> 00:15:40,120
 to do some kind of stuff, or we have to ask the Matomo team to do something on the server so that
 106
 00:15:40,120 --> 00:15:51,000
 we can have a metric. So it's just a proposition. Yes, yes, yes, of course. Yes, in the config level,
 107
 00:15:51,000 --> 00:16:03,240
 but IMEI.php, clearly, it's something that can be done. But this is annoying when you have, let's
 108
 00:16:03,240 --> 00:16:12,280
 say, organizations where you have thousands, no, hundreds of people using a tool named Google
 109
 00:16:12,280 --> 00:16:18,120
 Analytics, and they migrate, and they are quite forced to migrate to another tool. And
 110
 00:16:18,120 --> 00:16:26,520
 they discover that this metric, this simple thing, you have to ask your IT department to do something
 111
 00:16:26,520 --> 00:16:36,040
 to access it. And yes, I think that there should be a simple button somewhere in the UI, in the
 112
 00:16:36,040 --> 00:16:42,280
 Matomo UI, saying, do you want the unique visitor? Or just a warning saying, OK, by default, it's not
 113
 00:16:42,280 --> 00:16:48,840
 activated, but you can choose to activate it. Again, it's a presentation that's really
 114
 00:16:48,840 --> 00:16:58,440
 orientated for non-technical people. And yes, this is something I encountered a lot of times.
 115
 00:16:58,440 --> 00:17:06,600
 And now I can warn my clients about that. But in the beginning, when it happened, it was a bit
 116
 00:17:06,600 --> 00:17:15,720
 disturbing. And thank you again, Thomas, for the comments about that.
 117
 00:17:19,800 --> 00:17:34,360
 Another thing that I think could be interesting is that—I'm sorry, I'm reading Thomas' comment,
 118
 00:17:34,360 --> 00:17:55,640
 but I think the stuff could be a little bit strange. OK, let's go on. OK, the other thing
 119
 00:17:55,640 --> 00:18:03,080
 is about generic segments, because by default, you don't have anything like that in the interface.
 120
 00:18:03,080 --> 00:18:12,680
 So I think that you should have, by default, some kind of generic segments that you have within
 121
 00:18:13,640 --> 00:18:29,320
 Google Analytics. So again, it's a marketing guy talking. Some tools like Adobe Analytics or other
 122
 00:18:29,320 --> 00:18:41,640
 don't even have those generic segments available. But again, for people that are used to something
 123
 00:18:41,640 --> 00:18:50,600
 and that are moving to a new tool, not having the basics is something that is a bit annoying.
 124
 00:18:50,600 --> 00:19:00,680
 So I think that at least there could be some kind of generic ones like the direct accesses,
 125
 00:19:00,680 --> 00:19:15,320
 new users, stuff like that. Another stuff that existed in Google Analytics and that people
 126
 00:19:15,320 --> 00:19:26,120
 don't find in Matomo and about what they're a bit disappointed is the value page metric.
 127
 00:19:28,920 --> 00:19:34,840
 This metric is interesting because it was a simple way to identify
 128
 00:19:37,400 --> 00:19:43,800
 what pages were contributing to performance to conversions. And I think it could be interesting
 129
 00:19:43,800 --> 00:19:54,440
 to have this data within Matomo. I'm reading the comments. Sorry for joking a bit.
 130
 00:19:54,440 --> 00:20:00,680
 It's a very complex tool and you just read that we can adopt it for different needs. However,
 131
 00:20:02,040 --> 00:20:12,440
 you should know these details. Of course, configure it with the setting above
 132
 00:20:13,880 --> 00:20:23,560
 enable as an example. Yes, I totally agree. It was the situation that I encountered in
 133
 00:20:23,560 --> 00:20:34,680
 the beginning when I started working with the tool. But yes, it's something that I know now.
 134
 00:20:35,320 --> 00:20:41,320
 But for people that are going to be using the tool in the future since there are going to be a lot of
 135
 00:20:42,120 --> 00:20:47,480
 adoption of the tool because of the legal situation in different countries, I think that
 136
 00:20:47,480 --> 00:20:58,120
 at least the tool should warn users that they have to do something about that. Because not anyone
 137
 00:20:59,480 --> 00:21:07,320
 has the immediate knowledge about this specific topic, the unique visitor topic.
 138
 00:21:07,320 --> 00:21:25,080
 The tag manager. Another thing that could be done is just to allow us to sort the different assets
 139
 00:21:25,080 --> 00:21:35,640
 by name types because here you have really few things, few tags. But when you have really big
 140
 00:21:35,640 --> 00:21:42,600
 containers, I think that if you could sort by name, by type, or even have a search field
 141
 00:21:42,600 --> 00:21:54,360
 somewhere could be a good thing as well. In the tag manager area, again, something
 142
 00:21:54,360 --> 00:22:00,520
 that I think could be interesting is just to have a way to duplicate, copy, paste some sets
 143
 00:22:00,520 --> 00:22:10,600
 because right now you can just edit or delete the assets. Something else that already exists in
 144
 00:22:10,600 --> 00:22:19,000
 Google Tag Manager is the folder feature. So maybe could be also a good thing to be able to have a
 145
 00:22:19,000 --> 00:22:31,000
 clean vision of what's inside your container. A way also to post tags, something you have quite
 146
 00:22:31,000 --> 00:22:36,760
 easily in Google Tag Manager that you don't have in Matomo. Of course, you can decide that you
 147
 00:22:37,640 --> 00:22:47,000
 put some kind of starting day and ending day of the tag file for a campaign, for instance. But
 148
 00:22:47,000 --> 00:22:58,040
 this is quite easy to use here to just post the tag. Number three is about data visualization.
 149
 00:23:00,040 --> 00:23:09,640
 Again, I'm talking only for me. I don't know an open source Google Data Studio alternative.
 150
 00:23:09,640 --> 00:23:16,840
 I think that there are some, so for instance, here, I think it's Grafana, and I think that there's a
 151
 00:23:17,400 --> 00:23:27,560
 talk soon about Apache superset. But again, you have to go outside of Matomo. So I think that if
 152
 00:23:27,560 --> 00:23:36,760
 we can have something that allows us to stay within Matomo, could be a good thing. If we can
 153
 00:23:36,760 --> 00:23:46,680
 do that, could be a good thing. Or another option is to enhance the existing dashboard
 154
 00:23:47,480 --> 00:24:00,840
 system and maybe make other connections possible because with the existing dashboard, you cannot
 155
 00:24:00,840 --> 00:24:10,520
 connect external data sources. So yes, just as the A-B testing feature, I think that it's a big
 156
 00:24:11,080 --> 00:24:20,680
 work to do, but to have something complete, I think it's important to have a complete data
 157
 00:24:20,680 --> 00:24:32,200
 visualization solution within Matomo. The last thing I wanted to talk about regarding my ideal
 158
 00:24:32,200 --> 00:24:40,280
 vision, it's not exhaustive, but just a few ideas I had in mind, is about the consent management
 159
 00:24:40,280 --> 00:24:50,360
 platform. So again, if you have the technical resources for that, you can address
 160
 00:24:50,360 --> 00:25:03,960
 this topic. But I think if we had something internal inside of Matomo that can allow us
 161
 00:25:03,960 --> 00:25:14,760
 to create the cookie consent banner and configure it easily, it would help to adopt the tool.
 162
 00:25:14,760 --> 00:25:21,720
 So there is a comment here, page metric about goal conversion is a new feature since two months.
 163
 00:25:24,040 --> 00:25:31,560
 Goal conversion. Thank you Udo for your comment.
 164
 00:25:31,560 --> 00:25:43,960
 Yes, and now it's your turn. Do you have any ideas about what could make Matomo even a better tool?
 165
 00:25:45,720 --> 00:25:51,480
 Just feel free and we'll take note of that and add it to the presentation. So
 166
 00:25:52,760 --> 00:25:57,720
 if you want to add something, just don't hesitate.
 167
 00:25:57,720 --> 00:26:03,160
 Regarding consent management, I would like that it would be nice
 168
 00:26:04,840 --> 00:26:13,720
 if it can be possible to process content to geo location with a full IP address.
 169
 00:26:15,800 --> 00:26:23,480
 Thank you Udo for your comment. Small improvements to the current dashboard solution
 170
 00:26:23,480 --> 00:26:31,880
 would help a lot. Building a completely new dashboard solution is a big test. Yes, totally agree.
 171
 00:26:34,200 --> 00:26:48,920
 Again, I'm just dreaming awake, but it's the name of the presentation. It's ideal. Imagine an ideal Matomo.
 172
 00:26:48,920 --> 00:27:03,160
 Michael Johnson is saying, would also like to have faster responses, but it is surely a technical thing.
 173
 00:27:05,960 --> 00:27:13,800
 Faster, also like to have faster. Yes, I think they were talking about
 174
 00:27:13,800 --> 00:27:28,120
 server responses on your Matomo UI. Typically, you can be helped by your IT team, and you can also
 175
 00:27:28,120 --> 00:27:42,600
 ask some people. In particular, I'm thinking about Peter, with whom I have already been working.
 176
 00:27:42,600 --> 00:27:55,960
 His work brought a lot of improvement to the time response. Peter is definitely
 177
 00:27:55,960 --> 00:28:06,280
 someone you can reach out to when you want to address these technical issues that can cause low response.
 178
 00:28:06,280 --> 00:28:12,040
 Udo is saying, I totally agree. Marketing clients in particular see like you that some of your
 179
 00:28:12,040 --> 00:28:20,520
 improvements would help a lot. Thank you for your comments. I think that it's also a matter of
 180
 00:28:20,520 --> 00:28:28,760
 internal communication within the tool, just to, again, like for the unique business stuff, just
 181
 00:28:28,760 --> 00:28:33,320
 some kind of pop-up saying, okay, for the moment, you don't have access to that metric, but if you want
 182
 00:28:33,320 --> 00:28:39,400
 to have it, because it's a must-have, then you just have to go to the config in the PHP and make that
 183
 00:28:39,400 --> 00:28:46,280
 change. I think it's like when there's a conversation between people, it's a matter of
 184
 00:28:46,280 --> 00:28:56,120
 anticipate what can happen and communicate in a clear way. Yes, thank you again, Udo, for your
 185
 00:28:56,120 --> 00:29:06,440
 comment. Thank you, Thomas, for your comment also. Indeed, it's like in most cases, there are some
 186
 00:29:06,440 --> 00:29:16,520
 limitations in the architecture for some features as well. Yes, of course, and just like Thomas said,
 187
 00:29:18,360 --> 00:29:25,080
 yes, it is a very complex tool, and I know that in my position, I don't have an overall vision of
 188
 00:29:25,080 --> 00:29:37,720
 all the involvements to make the tool work, but I had this discussion with Mathieu some weeks ago,
 189
 00:29:37,720 --> 00:29:47,320
 months ago. There are at least, I think, three audiences for the tool. You have end users for
 190
 00:29:47,320 --> 00:29:52,200
 marketing people in an organization that are going to be looking at their campaign performance, for
 191
 00:29:52,200 --> 00:29:58,040
 instance. You have IT people that are going to be installing and managing the infrastructure,
 192
 00:29:59,240 --> 00:30:07,720
 and you have consultants like me, people like me, and these are really three different types of
 193
 00:30:07,720 --> 00:30:17,800
 audiences with different expectations. When we're talking about Matomo consultants, and I take my
 194
 00:30:17,800 --> 00:30:26,920
 example, I am a Matomo consultant, but with not that technical orientation, I'm more a digital
 195
 00:30:26,920 --> 00:30:37,720
 efficiency strategist, so I think it's really important to have communications, distinct
 196
 00:30:37,720 --> 00:30:45,720
 communication for these three different types of audiences. And Udo is asking, Thomas, what are your
 197
 00:30:45,720 --> 00:30:54,920
 thoughts on the technical limitations, not specifically on the technical limitations,
 198
 00:30:54,920 --> 00:31:04,920
 but not specifically on the technical limitations?
 199
 00:31:04,920 --> 00:31:15,480
 Yes, but regarding the limitations, I have to admit that I'm not that aware of all the limitations,
 200
 00:31:15,480 --> 00:31:19,560
 and I think that there is a page on the documentation that explains all the
 201
 00:31:19,560 --> 00:31:27,560
 all the documentations, and my final thought about that is that the tool needs improvement,
 202
 00:31:27,560 --> 00:31:34,600
 yes, it's clear, but I think that communication around the tool needs improvement as well,
 203
 00:31:34,600 --> 00:31:43,800
 because I'm going to give a last example about that. The example I want to give is the
 204
 00:31:43,800 --> 00:31:48,520
 Tag Manager implementation of the e-commerce tracking, and I have to admit that I struggled
 205
 00:31:48,520 --> 00:31:55,480
 a bit with the official documentation, and the solution with that came from Ronan Hélot,
 206
 00:31:56,040 --> 00:32:03,160
 who wrote an article on his blog, and that definitely changed my life to enable the tracking
 207
 00:32:03,160 --> 00:32:11,080
 of the e-commerce with the Tag Manager. So yes, I think that improvement around the tool can
 208
 00:32:11,080 --> 00:32:19,240
 is necessary, and improvement around communication documentation is also necessary, because
 209
 00:32:21,240 --> 00:32:27,480
 today, customers are used to have a Tag Manager, because they can handle their campaigns
 210
 00:32:28,040 --> 00:32:34,200
 more easily, and they expect the tracking to be done with the Tag Manager, and I see that
 211
 00:32:34,200 --> 00:32:42,680
 and I see that these different situations of, okay, am I going to use the regular JavaScript
 212
 00:32:42,680 --> 00:32:50,040
 tracker, or am I going to use the Tag Manager, or am I going to use an SDK for an application,
 213
 00:32:50,040 --> 00:33:06,040
 but you don't have some kind of detailed approach, or maybe I haven't seen it, but yes. Finally,
 214
 00:33:06,040 --> 00:33:13,000
 what I think is that the communication around the tool can be improved also.
 215
 00:33:13,000 --> 00:33:19,160
 Improved also. The limitations are mostly about not a mobile user. In relation to database, this
 216
 00:33:19,160 --> 00:33:25,560
 works for small sites, but when data grows, the query gets heavier from a tech perspective.
 217
 00:33:25,560 --> 00:33:30,040
 In some cases, then the need for super skilled DBA skills is needed.
 218
 00:33:30,040 --> 00:33:50,760
 Okay, so thanks a lot for your comments, your suggestions. I'm really glad that we had this
 219
 00:33:50,760 --> 00:33:59,720
 discussion all together. I think that we are going to end the talk. Just like I said, I'm going to ask
 220
 00:34:00,440 --> 00:34:10,040
 some of the propositions you suggested in the chat, and thanks for your attention,
 221
 00:34:10,040 --> 00:34:21,320
 and we talk soon. See you very soon, I hope. Bye.
--- a/SEO/output.srt
+++ b/SEO/output.srt
--- a/Analytics/output.srt
+++ b/Analytics/output.srt
--- a/dashboard/output.srt
+++ b/dashboard/output.srt
@ -0,0 +1,760 @@
 1
 00:00:00,000 --> 00:00:14,180
 Hello everyone. Thank you for joining another session of MatomoCamp. In this one we have
 2
 00:00:14,180 --> 00:00:21,280
 Niklas who will tell us more about dashboards in Matomo. Niklas is a web analyst with a
 3
 00:00:21,280 --> 00:00:27,760
 background in digital marketing and communication. He has worked with Matomo for years supporting
 4
 00:00:27,760 --> 00:00:34,960
 governmental agencies and businesses in Sweden. Today we'll learn how to get insights and
 5
 00:00:34,960 --> 00:00:44,720
 how to adjust the dashboards in Matomo. Niklas I'm leaving the floor to you.
 6
 00:00:44,720 --> 00:00:54,880
 Thank you. Yes. So hi and welcome to my little talk about how to get a kick-ass dashboard
 7
 00:00:54,880 --> 00:01:02,560
 in Matomo. I think my talk is going to be a little bit more straightforward and hands-on
 8
 00:01:02,560 --> 00:01:11,960
 than other talks for example yesterday. And I'm not going to mention anything about code
 9
 00:01:11,960 --> 00:01:19,120
 or something like that. So you don't need to know anything about that to master how
 10
 00:01:19,120 --> 00:01:27,760
 to get a kick-ass dashboard in Matomo. You just need to master how to drag and drop basically
 11
 00:01:27,760 --> 00:01:40,760
 inside Matomo. Yes and yeah the chat is lagging so I think I'm going to answer questions at
 12
 00:01:40,760 --> 00:01:54,960
 the end of my talk. I think that's going to be the best way forward. So this is basically
 13
 00:01:54,960 --> 00:02:02,680
 what I'm going to talk about. Firstly just going to talk a little bit about what the
 14
 00:02:02,680 --> 00:02:12,160
 dashboard in Matomo is and why you should use it. And the main part of the talk is about
 15
 00:02:12,160 --> 00:02:22,520
 how to set up dashboards within Matomo. So I'm going to demo Matomo and I'm going to
 16
 00:02:22,520 --> 00:02:30,660
 go through how the dashboard works, the default dashboard like the first dashboard you see
 17
 00:02:30,660 --> 00:02:39,480
 when you log in to Matomo. And then I'm going to try to set up two dashboards for different
 18
 00:02:39,480 --> 00:02:50,200
 needs. One for basically for goals and conversions and one for how you can get a dashboard for
 19
 00:02:50,200 --> 00:03:06,400
 your or how to see how your campaigns perform. That's basically it I think. Just a short
 20
 00:03:06,400 --> 00:03:15,200
 notice about who I am. Niklas Tarnsett is my name as Silva mentioned. And I'm right
 21
 00:03:15,200 --> 00:03:23,120
 now a web analyst at the Swedish digital agency Whitespace. I think I have worked with Matomo
 22
 00:03:23,120 --> 00:03:33,680
 since 2016 and I have been a product owner for Matomo for the largest organization public
 23
 00:03:33,680 --> 00:03:44,600
 sector in Sweden. And yeah I have a background in digital advertising and marketing. And
 24
 00:03:44,600 --> 00:03:55,200
 I like to try to focus on what kind of actionable insights you can get with the right data so
 25
 00:03:55,200 --> 00:04:11,800
 you don't drown in all the data that is available for you. Yeah that's pretty much who I am.
 26
 00:04:11,800 --> 00:04:20,040
 So just to talk a little bit about what the dashboard in Matomo is. You can say that it's
 27
 00:04:20,040 --> 00:04:27,760
 like your home page in Matomo. It's the first thing you see when you log into Matomo. And
 28
 00:04:27,760 --> 00:04:36,560
 as I mentioned briefly before there is a default dashboard in Matomo that InnoCraft has set
 29
 00:04:36,560 --> 00:04:48,800
 up for you. That one you can change and adjust according to your different needs and so forth.
 30
 00:04:48,800 --> 00:04:55,320
 And I think it's around a hundred different widgets or reports you can choose between
 31
 00:04:55,320 --> 00:05:06,280
 when you set up or adjust a dashboard in Matomo. So the sky's the limit you can say. So the
 32
 00:05:06,280 --> 00:05:23,880
 thing to focus on is which widgets or reports you want to show in a dashboard. And you can
 33
 00:05:23,880 --> 00:05:30,040
 actually create I don't know I don't think it's a limit to how many you can create. Maybe
 34
 00:05:30,040 --> 00:05:35,440
 someone can correct me if I'm wrong there but basically you can create many different
 35
 00:05:35,440 --> 00:05:41,560
 dashboards for different needs and you can for example let your internal stakeholders
 36
 00:05:41,560 --> 00:05:49,600
 get one kind of report or dashboard so they can see maybe the overall performance of your
 37
 00:05:49,600 --> 00:05:57,440
 website and maybe your market department need one other kind of dashboard that is more detailed
 38
 00:05:57,440 --> 00:06:08,480
 about maybe goals and conversions for different campaigns or how your site perform regarding
 39
 00:06:08,480 --> 00:06:19,000
 SEO or something like that. So I think it's quite a neat tool to use and in my experience
 40
 00:06:19,000 --> 00:06:32,600
 I think it's not used so much that it should be I think. And the last point here is you
 41
 00:06:32,600 --> 00:06:44,320
 can get quite useful data so you can maybe get some more actionable insights regarding
 42
 00:06:44,320 --> 00:06:55,880
 how your website perform and maybe what you need to adjust or take action on regarding
 43
 00:06:55,880 --> 00:07:10,520
 maybe conversions or how your SEO performance is. So I think it's quite a nice thing to
 44
 00:07:10,520 --> 00:07:20,640
 use and definitely something you should look into if you don't have like work with the
 45
 00:07:20,640 --> 00:07:31,800
 different dashboards and adjust them to your different needs. That's it about the dashboard
 46
 00:07:31,800 --> 00:07:44,080
 in Matomo but the talk is not over yet. I'm gonna demo the dashboard and yeah this is
 47
 00:07:44,080 --> 00:07:58,680
 basically what I'm gonna demo I think. So shortly about how the dashboard works in Matomo
 48
 00:07:58,680 --> 00:08:08,280
 and the default dashboard that you get. And then these two examples how you can adjust
 49
 00:08:08,280 --> 00:08:19,280
 your dashboard for goals and conversions and one for how you can track the campaign performance
 50
 00:08:19,280 --> 00:08:27,720
 if you're running a lot of campaigns in other channels like social media or newsletter and
 51
 00:08:27,720 --> 00:08:39,600
 so forth. So I'm gonna jump over to Matomo I think. Let's see here. So I choose the right
 52
 00:08:39,600 --> 00:09:08,280
 window. Yes. So this is the dashboard in Matomo. I hope you can see my screen now. And yeah
 53
 00:09:08,280 --> 00:09:18,720
 this is the default dashboard when you log in to Matomo for the first time or if you
 54
 00:09:18,720 --> 00:09:26,240
 do it regularly and you haven't adjusted the dashboard or chosen which widgets you want
 55
 00:09:26,240 --> 00:09:35,840
 to see. And I should say this is the dashboard if you're a super user. So I have like some
 56
 00:09:35,840 --> 00:09:46,280
 kind of gamification attempt here from InnoCraft to like set up the Matomo. But yes this is
 57
 00:09:46,280 --> 00:09:57,200
 the default dashboard and you can actually remove a widget or report how you want to
 58
 00:09:57,200 --> 00:10:03,560
 like if I don't want to have the real time widget. And it's the same principle for every
 59
 00:10:03,560 --> 00:10:16,040
 widget that I can remove like this. So it's quite neat and quite adjustable how you can
 60
 00:10:16,040 --> 00:10:25,200
 change the visual representation of data in the dashboard. So maybe I don't want this
 61
 00:10:25,200 --> 00:10:35,640
 welcome message even it's a nice message to get. Yeah so it's quite long here. And here
 62
 00:10:35,640 --> 00:10:44,480
 is all the options you have for the dashboard. And as you can see it's a lot of options for
 63
 00:10:44,480 --> 00:10:56,240
 different things. So I'm going to show you how you can maybe create a better dashboard
 64
 00:10:56,240 --> 00:11:06,760
 for your needs. So maybe if I just remove all of these widgets. And basically these
 65
 00:11:06,760 --> 00:11:15,920
 widgets as they are called are reports that you can find in the left menu here. It's basically
 66
 00:11:15,920 --> 00:11:28,080
 the same reports but you can visualize them in the dashboard instead of clicking through
 67
 00:11:28,080 --> 00:11:41,120
 the left menu here. So I had a lot of widgets here. So now it's empty. And maybe you want
 68
 00:11:41,120 --> 00:11:54,800
 to have some kind of data about how your site is performing. So this KPI metric widget is
 69
 00:11:54,800 --> 00:12:08,560
 quite a good widget to use for different needs. And for this I want to show how you can use
 70
 00:12:08,560 --> 00:12:19,480
 it to see how much traffic you get to your site and from which sources. So you hover
 71
 00:12:19,480 --> 00:12:26,360
 over here to this little symbol and then you get a lot of options here. The default is
 72
 00:12:26,360 --> 00:12:42,540
 visits and as I said I want to show you traffic sources. So now we have four search engines
 73
 00:12:42,540 --> 00:12:50,040
 and to get another one you need to do this again. And go down and then I want to have
 74
 00:12:50,040 --> 00:13:04,320
 four visitors from social networks as well. And maybe four visitors from direct traffic
 75
 00:13:04,320 --> 00:13:15,600
 or direct entry. And here you can see like a spark line and how many visitors from direct
 76
 00:13:15,600 --> 00:13:22,420
 entry compared to the previous period. And now I have 3rd of November. Maybe I should
 77
 00:13:22,420 --> 00:13:38,760
 choose like one month instead, like October. Yes, now it looks better. Yes, so it's quite
 78
 00:13:38,760 --> 00:13:51,240
 quick to get like an overall view of how your site performs regarding, oh, sorry, regarding
 79
 00:13:51,240 --> 00:14:05,680
 your site. So I can get like, this is from, there, this is from websites and then maybe
 80
 00:14:05,680 --> 00:14:20,200
 this is from campaigns as well. Let's see here. There we have it, visitors from campaigns.
 81
 00:14:20,200 --> 00:14:33,880
 So, and now the dashboard is in three columns. I usually prefer to work with two columns.
 82
 00:14:33,880 --> 00:14:41,840
 So then you can scroll down here and change dashboard layout to, yes, you can see here
 83
 00:14:41,840 --> 00:14:50,320
 you can have just one, two or two, but the first column is wider than the other one.
 84
 00:14:50,320 --> 00:14:57,440
 So yeah, I prefer to work with two so the dashboard don't get cluttered with too much
 85
 00:14:57,440 --> 00:15:10,560
 data. Yes, so this is I think much better than the default dashboard that we saw earlier.
 86
 00:15:10,560 --> 00:15:21,920
 One more thing or two more things maybe for just this default dashboard. I really like
 87
 00:15:21,920 --> 00:15:37,880
 this one, insights and movers and shakers. You can say it's some kind of overall association
 88
 00:15:37,880 --> 00:15:46,760
 how or the biggest changes in October compared to September then, because I've chosen that
 89
 00:15:46,760 --> 00:15:57,720
 time period. We can see what kind of page titles or page URLs have had the biggest increase
 90
 00:15:57,720 --> 00:16:04,240
 or yeah, in this example, it's just increased, but it's also, sometimes it's maybe a big
 91
 00:16:04,240 --> 00:16:14,760
 decrease in traffic to some website, web page on your website. And then you get like, yeah,
 92
 00:16:14,760 --> 00:16:22,920
 the percentage here, but in red, if it's decreased then. So it gets like, yeah, from Facebook
 93
 00:16:22,920 --> 00:16:31,420
 it increased a lot. And I think it's because our client here had some kind of campaign
 94
 00:16:31,420 --> 00:16:43,320
 in social media about this one. This is in Swedish. It's about more collection, waste
 95
 00:16:43,320 --> 00:16:53,840
 collection in the municipality Höganästan. So then they can see that the campaign attracted
 96
 00:16:53,840 --> 00:17:17,960
 a lot of traffic from Facebook. And then we can also have, if they're using smartphone
 97
 00:17:17,960 --> 00:17:29,400
 or desktop or tablet or so. And then that one I want to have here on the right. And
 98
 00:17:29,400 --> 00:17:35,920
 then you can hover scroll. Now you can move your mouse down here and maybe change to pie
 99
 00:17:35,920 --> 00:17:46,920
 chart. So this is the device type. Oh, there I go. And then the screen resolution, maybe
 100
 00:17:46,920 --> 00:18:00,000
 it's a good thing to also have. And that one I also want to have as a pie chart. Then you
 101
 00:18:00,000 --> 00:18:12,480
 can see, yeah, the smartphone is like, yeah, around 65% for October month. And here we
 102
 00:18:12,480 --> 00:18:22,480
 can see which ones are the most common screen resolutions. And that's a quite, yeah, it's
 103
 00:18:22,480 --> 00:18:30,040
 not like so much insights you can get from that, but it's a nice thing to know, like
 104
 00:18:30,040 --> 00:18:37,200
 a hygiene factor for your website that the website performs as you want it to perform
 105
 00:18:37,200 --> 00:18:47,160
 in these screen resolutions and that it performs well on smartphone then. So like this page
 106
 00:18:47,160 --> 00:18:59,660
 should be very good in the mobile, especially as it was quite a big increase from last month.
 107
 00:18:59,660 --> 00:19:13,720
 And this is one way to adjust your dashboard so it gets, I think, more easier to interpret
 108
 00:19:13,720 --> 00:19:22,920
 and easier to digest the data and maybe get more relevant data. And the next thing, if
 109
 00:19:22,920 --> 00:19:31,240
 you want to have this as your default dashboard, you can actually go down here and pick this
 110
 00:19:31,240 --> 00:19:46,640
 one, set as default widget selection. And you can click yes there. And I forgot to mention
 111
 00:19:46,640 --> 00:19:58,560
 the dashboard is connected to the user, like the user account. So this is for me then when
 112
 00:19:58,560 --> 00:20:07,280
 I log into Matomo. But if you want your colleagues to have the same dashboard, you can actually
 113
 00:20:07,280 --> 00:20:17,640
 copy it, copy the dashboard to user and then select which user should have the dashboard.
 114
 00:20:17,640 --> 00:20:24,080
 But it's quite important to know that if you change your dashboard, you need to do a new
 115
 00:20:24,080 --> 00:20:36,920
 copy of the dashboard to your colleagues. Yeah, this is one way to adjust the default
 116
 00:20:36,920 --> 00:20:54,680
 dashboard. So I'm going to create a new one, create a new dashboard. And it goes, oh, goes
 117
 00:20:54,680 --> 00:21:06,840
 and conversions. And then you can choose if the dashboard should populate with a default
 118
 00:21:06,840 --> 00:21:14,200
 dashboard or just an empty dashboard. And I choose empty so I don't need to remove all
 119
 00:21:14,200 --> 00:21:25,600
 of the widgets. And then I click add a widget. And for this size, I'm going to again use
 120
 00:21:25,600 --> 00:21:47,960
 this KPI metric widget. I'm going to create a lot of KPI widget here. So yeah, this is
 121
 00:21:47,960 --> 00:21:59,960
 a start. And then I also want to change the layout, change dashboard layout. Something
 122
 00:21:59,960 --> 00:22:09,920
 like this. And now I want to visualize how my goals are performing on the website. So
 123
 00:22:09,920 --> 00:22:21,560
 for this is this is for our client NSR. So I want to have one that shows all the conversions
 124
 00:22:21,560 --> 00:22:35,840
 on the website. And then maybe one with conversion rate. See if I can find that one there. Conversion
 125
 00:22:35,840 --> 00:22:45,240
 rate. So this is kind of like the overall performance regarding all the conversions
 126
 00:22:45,240 --> 00:22:58,760
 on the website. And now I want to have for each of the goals. So I scroll down here.
 127
 00:22:58,760 --> 00:23:12,440
 This is one goal. The goal is in Swedish, but it says login to my pages. And I want
 128
 00:23:12,440 --> 00:23:30,320
 the same but for conversion rate as well. There you have that. And the next goal. Yeah,
 129
 00:23:30,320 --> 00:23:53,280
 now I need to create a new one. Yes. So now you have just a dashboard for how your goals
 130
 00:23:53,280 --> 00:24:02,800
 are performing or in this example how our client's goals are performing. This is the
 131
 00:24:02,800 --> 00:24:10,600
 overall for all conversions. And it has increased. But as you can see the conversion rate is
 132
 00:24:10,600 --> 00:24:20,960
 down but not as much. That can maybe one explanation is like the traffic to the site increased
 133
 00:24:20,960 --> 00:24:32,520
 a lot but maybe not the rate of how many converted on the website. And this is for login to my
 134
 00:24:32,520 --> 00:24:39,920
 pages and the conversion rate and here the conversions and the conversion rate for the
 135
 00:24:39,920 --> 00:24:54,200
 next goal. So I think it's a nice feature to use the dashboard to adjust it and show
 136
 00:24:54,200 --> 00:25:03,720
 it for your colleagues. Like this one I should think the market department is quite interested
 137
 00:25:03,720 --> 00:25:13,840
 in. So you can use it to yeah you can do like this as well and then use this link to send
 138
 00:25:13,840 --> 00:25:30,000
 it to your colleagues. Yes. And the last one I want to show is a dashboard for campaign
 139
 00:25:30,000 --> 00:25:49,280
 performers. So I'm going to create a new dashboard. Sample of campaign performance. I'm going
 140
 00:25:49,280 --> 00:26:00,760
 to choose to leave it empty. Then I'm going to add a widget. And again I'm going to use
 141
 00:26:00,760 --> 00:26:15,200
 KPI metric and some other widgets as well. But we start with KPI metric. And yes I forgot
 142
 00:26:15,200 --> 00:26:28,720
 this one I want to have just as one column. I think you're going to understand why shortly.
 143
 00:26:28,720 --> 00:26:47,480
 So we're going to create more KPI widgets here. Something like this. And I want to have
 144
 00:26:47,480 --> 00:27:00,600
 this one visitors from campaigns. And I also want to have the percentage from campaigns.
 145
 00:27:00,600 --> 00:27:12,280
 Presenter visitors from campaigns. And I also want to have data for SEO traffic. Because
 146
 00:27:12,280 --> 00:27:20,640
 campaigns often affect your SEO or traffic that comes from search engines. Because it's
 147
 00:27:20,640 --> 00:27:27,440
 not always the user clicks on the link on like social media directly. Maybe they Google
 148
 00:27:27,440 --> 00:27:41,040
 it later or something like that. So then I want to have visitors from search engines.
 149
 00:27:41,040 --> 00:27:57,120
 And also direct traffic. Like all other traffic that Motomo can't identify basically. And
 150
 00:27:57,120 --> 00:28:13,120
 I want to have let's see here. Yes this one under acquisition campaigns and then campaign
 151
 00:28:13,120 --> 00:28:29,160
 names. And I want to have that one in the bottom of the dashboard like this as well.
 152
 00:28:29,160 --> 00:28:42,320
 And I think a couple of releases of Motomo or some releases lately released the ability
 153
 00:28:42,320 --> 00:28:52,280
 to show the spare table with goals metrics. So I think I'm going to do that. So yeah this
 154
 00:28:52,280 --> 00:29:02,320
 is in October so they had just two campaigns. And if you regard conversions for goals that
 155
 00:29:02,320 --> 00:29:09,160
 I had set up it wasn't so successful. But I actually don't know what the campaigns were
 156
 00:29:09,160 --> 00:29:19,280
 about but here you can get a glimpse of how the campaigns perform regarding your goals
 157
 00:29:19,280 --> 00:29:33,000
 that you have set up in Motomo. And you also get how the traffic to the website from the
 158
 00:29:33,000 --> 00:29:42,880
 campaigns for October. And also how the traffic from search engines and direct entry was for
 159
 00:29:42,880 --> 00:29:59,120
 October month. And this one is quite easy to grasp I think. And again it's something
 160
 00:29:59,120 --> 00:30:12,120
 maybe the market department is interested in to look at how their campaigns have performed
 161
 00:30:12,120 --> 00:30:24,400
 for a given period and see if it gave theirs the effect that they wanted or if it was just
 162
 00:30:24,400 --> 00:30:36,160
 basically a waste of time. So now I've just chosen like campaign names but you can also
 163
 00:30:36,160 --> 00:30:44,480
 see if you want if you see how it performed based on which source the traffic came from
 164
 00:30:44,480 --> 00:30:52,040
 like if it was Facebook or a newsletter or something like that. And then you can also
 165
 00:30:52,040 --> 00:31:06,760
 add let's see here acquisition and campaigns. And then you can take campaign source medium.
 166
 00:31:06,760 --> 00:31:17,160
 And you can yeah I'll put it here. Yeah it was a newsletter they sent out. But here again
 167
 00:31:17,160 --> 00:31:29,880
 you can change to goals metrics. Yes and here you have the campaign names. So yeah for this
 168
 00:31:29,880 --> 00:31:39,920
 example it's maybe not so relevant but if you communicate in different channels I think
 169
 00:31:39,920 --> 00:31:48,880
 it's quite neat to have one widget for your source medium as well to see if it was Facebook
 170
 00:31:48,880 --> 00:32:00,440
 or Instagram or a newsletter as in this example that performed best. Not performed best like
 171
 00:32:00,440 --> 00:32:14,080
 in visits but in conversions if that was your intent with the campaign. Yes I think it was
 172
 00:32:14,080 --> 00:32:25,120
 all that I had to show I think. Let me see here. Yeah I'll leave it there. So I don't
 173
 00:32:25,120 --> 00:32:34,080
 know if someone. Yeah I got a question here from Marcus. Is there any frequently asked
 174
 00:32:34,080 --> 00:32:43,000
 question from users transitioning from Google Analytics? Yeah well one question is how they
 175
 00:32:43,000 --> 00:32:56,000
 can get like the easy dashboard or visualization of data in Google Analytics. How they can
 176
 00:32:56,000 --> 00:33:04,560
 have the same in Matomo. And my answer is this is the closest you can get to like Google
 177
 00:33:04,560 --> 00:33:11,440
 Analytics have some similar solution. Like when you see the numbers you see the sparkline
 178
 00:33:11,440 --> 00:33:21,080
 and you see the comparison from the previous period. That's one question they have. One
 179
 00:33:21,080 --> 00:33:29,640
 common one that I don't have any good solution on is like secondary dimension. Or you can
 180
 00:33:29,640 --> 00:33:37,800
 if it's possible to use that in Matomo. And I don't think it's possible without some customized
 181
 00:33:37,800 --> 00:33:52,840
 code if I'm correctly. Maybe someone else have a better answer that. Yeah and got another
 182
 00:33:52,840 --> 00:34:01,480
 question from Diana. Is it possible to embed the dashboard in an external website? Yes
 183
 00:34:01,480 --> 00:34:18,200
 that's possible. You can use. Yes the short answer is yes. You can do that. I think I
 184
 00:34:18,200 --> 00:34:27,320
 think like adjusted dashboard in Matomo is very good for people that have not have not
 185
 00:34:27,320 --> 00:34:38,000
 the analyst skills that most of you have. Like you don't need to have an external tool
 186
 00:34:38,000 --> 00:34:46,080
 to get like some kind of improvement of the visualization in Matomo. But this is for like
 187
 00:34:46,080 --> 00:34:59,760
 the basic the basic things I think. Yeah I don't I can't I can't see any more questions
 188
 00:34:59,760 --> 00:35:08,600
 in the chat room. But if you have any questions regarding this you can always email me if
 189
 00:35:08,600 --> 00:35:23,440
 you want to. I'll write my email in the chat here. Yeah I think I'm going to say goodbye
 190
 00:35:23,440 --> 00:35:39,240
 and thank you for your time. Bye.
--- a/Kubernetes/output.en.srt
+++ b/Kubernetes/output.en.srt
--- a/Kubernetes/output.it.srt
+++ b/Kubernetes/output.it.srt
--- a/Docker/output.srt
+++ b/Docker/output.srt
--- a/Analytics/output.srt
+++ b/Analytics/output.srt
--- a/Hardening/output.srt
+++ b/Hardening/output.srt
--- a/2022/Standortermittlung/output.de.srt
+++ b/2022/Standortermittlung/output.de.srt
--- a/2022/Standortermittlung/output.en.srt
+++ b/2022/Standortermittlung/output.en.srt
--- a/solutions/output.srt
+++ b/solutions/output.srt
--- a/plugin/output.srt
+++ b/plugin/output.srt