1
00:00:00,000 --> 00:00:03,360
Welcome back to The Deep Dive. Today we're jumping straight into a really

2
00:00:03,360 --> 00:00:05,840
interesting shift happening in web analytics.

3
00:00:05,840 --> 00:00:09,120
You know, for years if you wanted to understand website visitors

4
00:00:09,120 --> 00:00:12,080
it usually meant these huge complex platforms.

5
00:00:12,080 --> 00:00:15,600
Yeah, often loaded with cookies, complex tracking scripts,

6
00:00:15,600 --> 00:00:19,600
making things like GDPR and CCPA compliance a real headache

7
00:00:19,600 --> 00:00:25,760
and expensive too. Exactly. It felt, well, overwhelming, often intrusive, sometimes

8
00:00:25,760 --> 00:00:28,240
slow, and maybe just over-engineered for what

9
00:00:28,240 --> 00:00:32,160
many people actually need day to day. Right. So today we're cutting through

10
00:00:32,160 --> 00:00:35,360
that complexity. We're looking at a new kind of tool,

11
00:00:35,360 --> 00:00:38,960
specifically an open source project called Ribbit. Ribbit, okay. Yeah, its

12
00:00:38,960 --> 00:00:41,440
position is this open source privacy friendly

13
00:00:41,440 --> 00:00:45,920
alternative to the big players like Google Analytics. And here's the kicker.

14
00:00:45,920 --> 00:00:50,800
They claim it's 10x more intuitive. 10 times more intuitive. That's a bold claim.

15
00:00:50,800 --> 00:00:54,880
It is. So our mission today is pretty simple. We want to break down Ribbit for

16
00:00:54,880 --> 00:00:58,880
beginners. We want you listening to get a clear idea of what these

17
00:00:58,880 --> 00:01:02,880
next-gen lightweight, cookie-less analytics actually mean

18
00:01:02,880 --> 00:01:06,240
for your website, your data, and importantly your compliance.

19
00:01:06,240 --> 00:01:10,240
Okay, sounds good. And before we really dig into how this tool

20
00:01:10,240 --> 00:01:14,320
aims to redefine website analysis, we absolutely need to thank the supporter of

21
00:01:14,320 --> 00:01:17,360
this deep dive, Safe Server. They're dedicated

22
00:01:17,360 --> 00:01:20,720
to hosting software and helping with digital transformation.

23
00:01:20,720 --> 00:01:24,160
So if you're thinking about deploying open source solutions like Ribbit, which

24
00:01:24,160 --> 00:01:26,720
we're discussing, they can really guide you. You can find

25
00:01:26,720 --> 00:01:32,080
more info at www.safeserver.de. Definitely worth checking out if you're

26
00:01:32,080 --> 00:01:35,440
considering self-hosting. Okay, so let's unpack Ribbit. It's got some

27
00:01:35,440 --> 00:01:40,640
serious community buzz, 9.2 thousand stars, over 400 forks on

28
00:01:40,640 --> 00:01:43,920
GitHub. That's not insignificant. How does it

29
00:01:43,920 --> 00:01:46,800
actually redefine understanding visitors? What's the

30
00:01:46,800 --> 00:01:49,840
fundamental difference here? It can't just be a nicer looking dashboard.

31
00:01:49,840 --> 00:01:53,920
No, not at all. It's really about the commitment to compliance and simplicity

32
00:01:53,920 --> 00:01:57,680
right from its core. The foundational promise is structural.

33
00:01:57,680 --> 00:02:01,280
Ribbit is designed as a modern open source analytics solution that's

34
00:02:01,280 --> 00:02:04,720
inherently lightweight, meaning it's fast and

35
00:02:04,720 --> 00:02:08,800
crucially cookie-less. Cookie-less. That's the key phrase, isn't it?

36
00:02:08,800 --> 00:02:12,560
That's the absolute key because the platform uses, and I quote,

37
00:02:12,560 --> 00:02:16,480
no cookies or user tracking in the traditional sense. It claims

38
00:02:16,480 --> 00:02:19,840
full GDPR and CCPA compliance right out of the box.

39
00:02:19,840 --> 00:02:24,320
Wow. Think about that. For anyone running a site serving users in, say,

40
00:02:24,320 --> 00:02:29,440
California or the EU, that's a massive operational simplification.

41
00:02:29,440 --> 00:02:33,360
No more complex consent banners for analytics cookies, theoretically. That

42
00:02:33,360 --> 00:02:36,160
sounds almost too easy. For someone new to

43
00:02:36,160 --> 00:02:40,640
analytics, maybe even new to open source, the idea of complete control can feel

44
00:02:40,640 --> 00:02:45,120
a bit abstract. How does someone actually use this tool? What are the practical

45
00:02:45,120 --> 00:02:49,120
ways to get started? Good question. They give you two clear paths, which is

46
00:02:49,120 --> 00:02:52,800
great for choice. The quickest way is their hosted service. It's cloud-based,

47
00:02:52,800 --> 00:02:54,960
set up for you, and importantly, they have a pretty

48
00:02:54,960 --> 00:02:57,760
generous free tier. Makes it really painless to just try it out.

49
00:02:57,760 --> 00:03:00,800
Okay, so like a sauce offering, dip your toes in. Exactly.

50
00:03:00,800 --> 00:03:04,080
Then there's the second path, which is the classic open source advantage,

51
00:03:04,080 --> 00:03:07,920
self-hosting. This means you deploy and manage Rivet yourself

52
00:03:07,920 --> 00:03:11,040
on your own server, like a virtual private server,

53
00:03:11,040 --> 00:03:15,440
a VPS. This gives you what they call complete control.

54
00:03:15,440 --> 00:03:19,760
We're talking true data sovereignty here. Your data lives on your infrastructure.

55
00:03:19,760 --> 00:03:23,120
And that flexibility combined with the open source license, it's

56
00:03:23,120 --> 00:03:27,520
AGPL 3.0, right? Okay. That must put a huge draw. I mean, if you've ever felt

57
00:03:27,520 --> 00:03:31,120
locked into a proprietary system, struggling to get your data out,

58
00:03:31,120 --> 00:03:34,640
an open source license like AGPL means you control the software and the data.

59
00:03:34,640 --> 00:03:38,960
You're never trapped again. Precisely. That choice between speed and ease

60
00:03:38,960 --> 00:03:43,200
with the hosted option versus total data autonomy with self-hosting

61
00:03:43,200 --> 00:03:46,560
is built right in. It really speaks to that next-gen analytics idea.

62
00:03:46,560 --> 00:03:50,240
Okay. Let's shift from setup to the actual insights. You get it running,

63
00:03:50,240 --> 00:03:53,600
you log into the dashboard. What are the essential metrics Ribbit

64
00:03:53,600 --> 00:03:56,800
gives you right away? The things every site owner needs to keep an eye on?

65
00:03:56,800 --> 00:04:00,400
It covers all the basics you'd expect. Sessions, unique users, page views,

66
00:04:00,400 --> 00:04:04,720
that standard stuff. Then you get the key behavioral metrics like bounce rate,

67
00:04:04,720 --> 00:04:08,320
average session duration, all vital signs for engagement.

68
00:04:08,320 --> 00:04:10,960
What about location? Can you see where visitors are coming from?

69
00:04:10,960 --> 00:04:14,720
Yep, it includes pretty rich location tracking, three levels,

70
00:04:14,720 --> 00:04:19,040
country, then region, then city. And they have nice map visualizations to go with

71
00:04:19,040 --> 00:04:22,640
it. It's the standard set, but the presentation is really focused on

72
00:04:22,640 --> 00:04:26,160
being intuitive and clear. Okay, standard but clear. Now here's

73
00:04:26,160 --> 00:04:29,520
something that always gets me excited seeing activity as it happens.

74
00:04:29,520 --> 00:04:34,160
So many platforms have that frustrating delay, maybe 30 minutes, maybe more.

75
00:04:34,160 --> 00:04:39,200
What about Ribbit's real-time analytics? Ah, this is where it gets really cool.

76
00:04:39,200 --> 00:04:43,600
It's basically instantaneous data. The source material gives a great example.

77
00:04:43,600 --> 00:04:47,600
A dashboard showing 28 online visitors right now.

78
00:04:47,600 --> 00:04:52,080
Yeah, live. And tracking specific actions. It might show, say,

79
00:04:52,080 --> 00:04:55,760
someone performed a button click event in Great Britain 45 seconds ago,

80
00:04:55,760 --> 00:04:59,840
or a new visitor just landed on a page from Germany. That's incredibly useful

81
00:04:59,840 --> 00:05:04,000
for monitoring campaigns as they launch. Maybe catching a sudden traffic spike or

82
00:05:04,000 --> 00:05:07,120
even just confirming everything's working after pushing an update.

83
00:05:07,120 --> 00:05:10,000
Exactly. That real-time pulse is invaluable.

84
00:05:10,000 --> 00:05:13,200
And to get deeper than just traffic counts, you need

85
00:05:13,200 --> 00:05:16,560
event tracking and goal conversion, right? Understanding the

86
00:05:16,560 --> 00:05:20,400
impact of those visits. Absolutely. You don't just want page views. You want to

87
00:05:20,400 --> 00:05:22,800
know if people are doing what you want them to do.

88
00:05:22,800 --> 00:05:26,640
So Ribbit lets you monitor specific interactions, clicks, form submissions,

89
00:05:26,640 --> 00:05:30,320
downloads, whatever you define, and then you tie those to conversion goals.

90
00:05:30,320 --> 00:05:33,120
Like signing up for a newsletter or starting a free trial.

91
00:05:33,120 --> 00:05:37,040
Precisely. The examples they give are things like seeing a newsletter sign up

92
00:05:37,040 --> 00:05:42,800
goal, hitting an 8.7% conversion rate, or maybe a free trial registration at 12.4%.

93
00:05:42,800 --> 00:05:44,960
It makes tracking your key business

94
00:05:44,960 --> 00:05:48,320
outcomes really straightforward. Okay. And they mentioned something about

95
00:05:48,320 --> 00:05:52,960
custom events using JSON properties. Can you unpack that a bit? Why is that

96
00:05:52,960 --> 00:05:55,520
important? Especially for maybe a beginner. Right.

97
00:05:55,520 --> 00:05:59,840
JSON properties. It sounds technical, but the concept is simple

98
00:05:59,840 --> 00:06:03,280
and powerful. It lets you add context to your events

99
00:06:03,280 --> 00:06:07,280
without needing invasive tracking. How so? Instead of just tracking

100
00:06:07,280 --> 00:06:10,800
a generic click, you can track a button click and attach

101
00:06:10,800 --> 00:06:13,920
extra information properties to that event. For instance,

102
00:06:13,920 --> 00:06:18,000
track the click but include data like button.signupback to

103
00:06:18,000 --> 00:06:21,440
and maybe usersegment.newvisitor. Ah, okay.

104
00:06:21,440 --> 00:06:25,040
So you know which button was clicked and who, in terms of segment, clicked it.

105
00:06:25,040 --> 00:06:28,480
Exactly. All tied to an anonymous session ID, not some

106
00:06:28,480 --> 00:06:32,080
persistent cookie tracking them across the web. It allows for really deep

107
00:06:32,080 --> 00:06:35,040
segmentation and understanding of what's happening and why.

108
00:06:35,040 --> 00:06:38,720
But in a privacy preserving way. That detail is crucial.

109
00:06:38,720 --> 00:06:42,960
But let's get into what often feels like the magic. The advanced tools for

110
00:06:42,960 --> 00:06:47,680
understanding actual user behavior. You mentioned Ribbit is intuitive and

111
00:06:47,680 --> 00:06:51,760
next-gen and often that means features going way beyond just counting things.

112
00:06:51,760 --> 00:06:54,560
Yeah, this is where Ribbit really steps up from being just a lightweight

113
00:06:54,560 --> 00:06:58,640
analytics tool into the realm of, well, deep product

114
00:06:58,640 --> 00:07:02,160
analytics. They highlight three major features that give you that

115
00:07:02,160 --> 00:07:04,480
rich behavioral context. Okay, what's the first one?

116
00:07:04,480 --> 00:07:07,600
The first one, and maybe the most surprising given the privacy focus,

117
00:07:07,600 --> 00:07:12,080
is session replays. Session replays? Like watching a video of what a user did.

118
00:07:12,080 --> 00:07:15,040
Essentially, yes. It lets you, and I quote,

119
00:07:15,040 --> 00:07:19,120
watch real user sessions to understand their behavior and identify pain points.

120
00:07:19,120 --> 00:07:22,080
Wait a minute. If this whole thing is cookie-less

121
00:07:22,080 --> 00:07:27,680
and GDPR compliant, how on earth are session replays possible?

122
00:07:27,680 --> 00:07:31,280
Isn't watching someone's session the ultimate form of tracking?

123
00:07:31,280 --> 00:07:34,080
That's the million dollar question, right? And it comes down to a critical

124
00:07:34,080 --> 00:07:38,160
technical distinction. Traditional systems use cookies to stitch

125
00:07:38,160 --> 00:07:40,880
together a user's identity across multiple visits,

126
00:07:40,880 --> 00:07:44,000
maybe even across different websites. Right, the persistent tracking.

127
00:07:44,000 --> 00:07:47,280
Exactly. Ribbit, being cookie-less, doesn't do that.

128
00:07:47,280 --> 00:07:52,080
For each specific visit, it generates an anonymous, unique session identifier.

129
00:07:52,080 --> 00:07:55,280
The replay isn't based on tracking you personally over time.

130
00:07:55,280 --> 00:07:59,120
It reconstructs that specific session's journey based on the stream of

131
00:07:59,120 --> 00:08:03,360
anonymized events, page views, clicks, scrolls, mouse movements, tied

132
00:08:03,360 --> 00:08:06,800
only to that single temporary session ID. Ah, okay, so it's

133
00:08:06,800 --> 00:08:09,680
recreating the session, not tracking the person long term.

134
00:08:09,680 --> 00:08:13,200
That makes sense. It's anonymized playback of a single visit.

135
00:08:13,200 --> 00:08:16,960
Precisely. They're reconstructing the what happened during that visit, not

136
00:08:16,960 --> 00:08:20,080
building a permanent profile of who you are. And the source mentioned an

137
00:08:20,080 --> 00:08:24,320
anecdote about seeing a user who clicked add to cart three times in a replay.

138
00:08:24,320 --> 00:08:28,000
That kind of insight is gold. It tells you instantly there's friction or

139
00:08:28,000 --> 00:08:31,200
confusion right there. Absolutely. Friction points become

140
00:08:31,200 --> 00:08:34,240
immediately obvious, and that leads perfectly into the second

141
00:08:34,240 --> 00:08:38,960
big feature, user profiles. User profiles? But you just said it's anonymous.

142
00:08:38,960 --> 00:08:42,240
It is anonymous, but they can still link all the events and sessions

143
00:08:42,240 --> 00:08:46,560
from what appears to be the same browser or device, using probabilistic methods

144
00:08:46,560 --> 00:08:51,040
or fingerprinting likely, to a generated anonymous profile ID.

145
00:08:51,040 --> 00:08:56,320
The example given is an ID like 84F43D7E associated with, say,

146
00:08:56,320 --> 00:08:59,440
48 separate sessions and 134 page views over time.

147
00:08:59,440 --> 00:09:03,760
So you can see repeat anonymous visitor behavior without personal data?

148
00:09:03,760 --> 00:09:07,680
Correct. You understand the patterns of activity associated with that anonymous

149
00:09:07,680 --> 00:09:11,520
ID, like how often they return or what features they use, without knowing their

150
00:09:11,520 --> 00:09:14,880
actual identity. You know, what they did, not who they are.

151
00:09:14,880 --> 00:09:17,760
Okay, that's clever. And the third piece for behavior,

152
00:09:17,760 --> 00:09:22,880
visualizing the journey. Yes, user flow analysis or user journeys.

153
00:09:22,880 --> 00:09:26,640
This maps out the common paths users take through your site or app.

154
00:09:26,640 --> 00:09:29,600
Super important for optimization. Like seeing where people drop off.

155
00:09:29,600 --> 00:09:33,600
Exactly. The source example showed a top path. Home products back check out

156
00:09:33,600 --> 00:09:37,040
converting at 26%. If you see a huge drop off

157
00:09:37,040 --> 00:09:40,080
between products and checkout, you know immediately where to focus your

158
00:09:40,080 --> 00:09:43,680
efforts to improve things. Makes sense. Visualizing the flow is key.

159
00:09:43,680 --> 00:09:46,720
Now quickly, you also mentioned technical performance monitoring,

160
00:09:46,720 --> 00:09:50,800
web vitals. Right, web vitals. This isn't just about behavior, but the technical

161
00:09:50,800 --> 00:09:53,440
experience. It monitors those core metrics Google

162
00:09:53,440 --> 00:09:59,120
uses for page experience and rankings. LCP, FID, CLS, FCP.

163
00:09:59,120 --> 00:10:03,280
Can you define those for beginners? Sure. LCP, largest contentful paint, is

164
00:10:03,280 --> 00:10:08,160
basically how fast the main content loads. FID, first input delay, is how

165
00:10:08,160 --> 00:10:11,360
quickly the page responds when you first click or interact.

166
00:10:11,360 --> 00:10:15,040
CLS, cumulative layout shift, measures how much things jump around

167
00:10:15,040 --> 00:10:18,880
unexpectedly while loading really annoying. Oh yeah, hate that. So these feed

168
00:10:18,880 --> 00:10:21,040
into an overall performance score like the example

169
00:10:21,040 --> 00:10:24,320
82 Good. Helps you keep the site fast and user friendly.

170
00:10:24,320 --> 00:10:27,600
Okay, good overview, but important caveat here.

171
00:10:27,600 --> 00:10:30,640
The source material does note that these advanced features,

172
00:10:30,640 --> 00:10:33,920
web vitals, session replays, user profiles,

173
00:10:33,920 --> 00:10:38,400
these tend to be in the paid tiers or sometimes noted as cloud only.

174
00:10:38,400 --> 00:10:42,960
Yes, that's a crucial distinction. The core analytics are often free,

175
00:10:42,960 --> 00:10:46,560
but these deeper behavioral and performance tools usually require a paid

176
00:10:46,560 --> 00:10:50,240
subscription. Standard practice really. Okay, so let's

177
00:10:50,240 --> 00:10:54,080
connect this back to the bigger picture. Someone's using Google Analytics, maybe

178
00:10:54,080 --> 00:10:57,280
another tool like Plausible or Cloudflare Analytics.

179
00:10:57,280 --> 00:11:00,320
Why would they switch to Ribbit? The comparison table in the source seems

180
00:11:00,320 --> 00:11:02,480
pretty direct about this. Yeah, it makes a

181
00:11:02,480 --> 00:11:05,920
strong case focusing on control and the depth of insight you get despite the

182
00:11:05,920 --> 00:11:08,400
privacy focus. So what are the highlights from that

183
00:11:08,400 --> 00:11:11,600
comparison? Where does Ribbit really stand out against GA4,

184
00:11:11,600 --> 00:11:15,840
Plausible, Cloudflare? Well first, the fundamentals of control.

185
00:11:15,840 --> 00:11:19,840
Ribbit is explicitly open source. GA4 is obviously not.

186
00:11:19,840 --> 00:11:23,680
Ribbit fully supports self-hosting. GA4 doesn't.

187
00:11:23,680 --> 00:11:27,440
Even competitors like Plausible might only offer limited self-hosting

188
00:11:27,440 --> 00:11:31,440
in, say, a community edition. So for developers or organizations where data

189
00:11:31,440 --> 00:11:36,640
control and transparency are paramount, Ribbit has a clear edge there. A huge edge.

190
00:11:36,640 --> 00:11:40,560
But then there's the insight side. Features like detailed session details,

191
00:11:40,560 --> 00:11:45,030
session replays, and user profiles. These are often core parts of Ribbit's paid

192
00:11:45,030 --> 00:11:45,840
offering.

193
00:11:45,840 --> 00:11:50,080
But when you look at the comparison table for GA4, Plausible, Cloudflare,

194
00:11:50,080 --> 00:11:54,080
those features are often just marked with an X or not available.

195
00:11:54,080 --> 00:11:58,320
So the implication is you get the privacy compliance without sacrificing those deep

196
00:11:58,320 --> 00:12:01,440
user experience insights. That's kind of the holy grail, isn't it?

197
00:12:01,440 --> 00:12:05,120
That seems to be the core value proposition. You don't necessarily have to choose

198
00:12:05,120 --> 00:12:05,520
between

199
00:12:06,080 --> 00:12:10,800
GDPR compliance and understanding user friction through replays or flows. Ribbit

200
00:12:10,800 --> 00:12:11,440
aims to give you

201
00:12:11,440 --> 00:12:16,320
both. That blend of privacy and power is compelling and accessibility matters,

202
00:12:16,320 --> 00:12:16,880
especially for

203
00:12:16,880 --> 00:12:20,480
beginners. Let's quickly touch on the pricing tiers again, just to reinforce how

204
00:12:20,480 --> 00:12:20,880
someone can

205
00:12:20,880 --> 00:12:25,050
get started. Absolutely. The free tier is really designed to remove any barrier to

206
00:12:25,050 --> 00:12:25,920
entry. First

207
00:12:25,920 --> 00:12:30,340
10,000 events per month are free. That's plenty for many small sites or projects.

208
00:12:30,340 --> 00:12:30,720
It covers up

209
00:12:30,720 --> 00:12:35,070
to three websites, one user, and gives you six months of data retention. And

210
00:12:35,070 --> 00:12:35,840
critically,

211
00:12:35,840 --> 00:12:40,720
no credit card needed to sign up for the free tier, right? Correct. No credit card

212
00:12:40,720 --> 00:12:41,120
required

213
00:12:41,120 --> 00:12:45,690
upfront. Just sign up and go. Then if you need more. If you grow, the standard tier

214
00:12:45,690 --> 00:12:46,160
is listed

215
00:12:46,160 --> 00:12:50,990
at $19 a month. That adds important features like web vitals tracking, funnels,

216
00:12:50,990 --> 00:12:51,840
goal tracking,

217
00:12:51,840 --> 00:12:56,090
and error tracking. Really rounds out the core analytics. And for the power users

218
00:12:56,090 --> 00:12:56,720
needing those

219
00:12:56,720 --> 00:13:01,680
deep behavioral tools. That's the pro tier at $39 a month. This is where you unlock

220
00:13:01,680 --> 00:13:02,160
the session

221
00:13:02,160 --> 00:13:06,490
replays. Plus you get unlimited websites and team members. So it scales pretty

222
00:13:06,490 --> 00:13:07,360
logically as your

223
00:13:07,360 --> 00:13:12,320
needs for detail and collaboration increase. Okay. That makes sense. A clear path

224
00:13:12,320 --> 00:13:12,880
from free

225
00:13:12,880 --> 00:13:18,560
exploration to professional tooling. So to sort of wrap up the key takeaway for you,

226
00:13:18,560 --> 00:13:19,520
the learner,

227
00:13:19,520 --> 00:13:23,670
Rivet is offering this suite of next gen analytics tools. You get everything from

228
00:13:23,670 --> 00:13:24,320
the real time

229
00:13:24,320 --> 00:13:28,270
dashboards to those detailed session replays. But it's all built on a foundation

230
00:13:28,270 --> 00:13:28,720
that's

231
00:13:28,720 --> 00:13:33,080
cookie lists and designed for privacy compliance, meeting standards like GDPR and

232
00:13:33,080 --> 00:13:34,160
CCPA. It's

233
00:13:34,160 --> 00:13:37,840
essentially bringing powerful product analytics insights without the traditional

234
00:13:37,840 --> 00:13:38,320
baggage of

235
00:13:38,320 --> 00:13:43,940
invasive tracking. Okay. So let's reflect on that. What does this really mean? If a

236
00:13:43,940 --> 00:13:44,880
tool is fully

237
00:13:44,880 --> 00:13:50,830
GDPR and CCPA compliant, because it ditches cookies technically, but it still lets

238
00:13:50,830 --> 00:13:51,600
you watch

239
00:13:51,600 --> 00:13:56,340
detailed session replays minute by minute and build up these comprehensive, albeit

240
00:13:56,340 --> 00:13:56,960
anonymized,

241
00:13:56,960 --> 00:14:01,820
user profiles, it raises a really interesting question, doesn't it? Where do you

242
00:14:01,820 --> 00:14:02,480
draw the line?

243
00:14:02,480 --> 00:14:07,360
Exactly. When you achieve technical privacy compliance, how does the sheer detail

244
00:14:07,360 --> 00:14:07,680
of the

245
00:14:07,680 --> 00:14:11,540
data you can still collect, like seeing exactly how someone navigated, where they

246
00:14:11,540 --> 00:14:12,240
hesitated,

247
00:14:12,240 --> 00:14:16,400
what they clicked three times, how does that redefine your ethical responsibility

248
00:14:16,400 --> 00:14:16,960
as a site

249
00:14:16,960 --> 00:14:21,140
owner? Understanding the user journey is vital, no doubt, but navigating that space

250
00:14:21,140 --> 00:14:22,160
between necessary

251
00:14:22,160 --> 00:14:26,320
insight and potentially excessive surveillance, even if technically compliant. That's

252
00:14:26,320 --> 00:14:26,560
something

253
00:14:26,560 --> 00:14:29,360
we all need to think about in this new era. Definitely something to mull over.

254
00:14:29,360 --> 00:14:33,300
That's a great point to end on. The tools change, but the ethical considerations

255
00:14:33,300 --> 00:14:33,600
evolve

256
00:14:33,600 --> 00:14:37,440
right alongside them. And once again, we really want to thank Safe Server for

257
00:14:37,440 --> 00:14:38,000
supporting this

258
00:14:38,000 --> 00:14:41,840
deep dive. Yes, absolutely. You can find out more about their hosting and digital

259
00:14:41,840 --> 00:14:42,640
transformation

260
00:14:42,640 --> 00:14:47,440
solutions at www.safeserver.de. Check them out.

261
00:14:47,440 --> 00:14:50,240
Thanks for joining us and we'll catch you on the next deep dive.