EP258 - GA4

1
00:00:00,000 --> 00:00:02,700
Hello, and welcome to this
week's episode of the PBC chat

2
00:00:02,700 --> 00:00:07,100
Roundup in today's episode.
We have Julie taken us on a very

3
00:00:07,100 --> 00:00:09,700
unsurprising.
Topic, considering a deadline

4
00:00:09,700 --> 00:00:12,100
that we've got in the next
couple of days.

5
00:00:12,100 --> 00:00:16,100
We're talking about ga4gh a for
is about to be our only means

6
00:00:16,100 --> 00:00:19,600
of, you know, doing Google
analytics tracking and you a

7
00:00:19,700 --> 00:00:22,900
universal analytics is about to
be sunsetted in a couple of

8
00:00:22,900 --> 00:00:25,100
days.
So you need to have migrated

9
00:00:25,100 --> 00:00:27,700
down your own analytics,
migration created your new

10
00:00:27,700 --> 00:00:29,800
events and making sure you got
older.

11
00:00:30,000 --> 00:00:33,700
Ladies Jaipur tracking codes on
your side and all that fun

12
00:00:33,700 --> 00:00:35,700
stuff.
So yeah, we're talking about

13
00:00:35,700 --> 00:00:38,600
whether we're prepared for it
with our clients are prepared

14
00:00:38,600 --> 00:00:41,300
for it.
Whether we have we were using it

15
00:00:41,300 --> 00:00:45,200
properly what our challenges are
and resources of course because

16
00:00:45,200 --> 00:00:48,200
we're not just hair about, you
know, given doing Rants and, you

17
00:00:48,200 --> 00:00:50,800
know, Sharon are nuances.
But definitely also about

18
00:00:50,800 --> 00:00:54,700
sharing the ways that we're
trying to, you know, evolve with

19
00:00:54,700 --> 00:00:57,900
the industry evolving as well in
the resources that we're finding

20
00:00:58,100 --> 00:01:01,500
to allow us to stay.
A on top of things.

21
00:01:01,500 --> 00:01:04,900
So, yes, I hope you enjoy that
and take a lot of useful.

22
00:01:04,900 --> 00:01:07,300
Things out of this chat, hope
you enjoy.

23
00:01:16,700 --> 00:01:19,600
Hello and a warm, welcome to
this week's episode of the

24
00:01:19,600 --> 00:01:23,100
people see chat Roundup.
This is the podcast where I

25
00:01:23,100 --> 00:01:27,000
round up the Twitter discussion.
That happens on Tuesdays at 5

26
00:01:27,000 --> 00:01:28,600
p.m.
GMT.

27
00:01:28,800 --> 00:01:31,900
I'm your host, a new, and I'm
recording from my studio here in

28
00:01:31,900 --> 00:01:33,800
London UK.
And I use this platform to

29
00:01:33,800 --> 00:01:37,300
share, not just expert, but also
my ideas and considered best

30
00:01:37,300 --> 00:01:40,100
practices about pain.
Add media and the direction, the

31
00:01:40,100 --> 00:01:43,300
digital industry is going in.
So if you want to keep up to

32
00:01:43,300 --> 00:01:46,600
date with my tips and tricks in
the industry, and get the latest

33
00:01:46,800 --> 00:01:50,200
on the podcast that has been
called your go-to if you don't

34
00:01:50,200 --> 00:01:52,200
make it to the PPC chat live
discussions.

35
00:01:52,200 --> 00:01:56,000
And even if you do then like
foolish and retweet on that, try

36
00:01:56,000 --> 00:01:59,900
Twitter with my handle the
marketing, a new or join us in

37
00:01:59,900 --> 00:02:02,700
our LinkedIn Group, which is the
PPC chat Roundup.

38
00:02:02,900 --> 00:02:06,500
Or if you're on Instagram, why
don't you check us out at PPC,

39
00:02:06,500 --> 00:02:10,400
chat underscore Roundup to get
quite And Snippets from previous

40
00:02:10,400 --> 00:02:13,800
episodes.
So yeah, Julie takes us on what

41
00:02:13,800 --> 00:02:16,700
would be a historical chat?
Because we're no more.

42
00:02:16,700 --> 00:02:21,100
Will we be able to do a talk
about moving on to ga4 from next

43
00:02:21,100 --> 00:02:23,200
week?
We will be on GA for from next

44
00:02:23,200 --> 00:02:27,500
week it would be our only option
for, you know, doing analytics

45
00:02:27,500 --> 00:02:29,400
when it comes to Google
analytics.

46
00:02:29,700 --> 00:02:32,400
Anyway.
So yeah, quite historic moment.

47
00:02:32,400 --> 00:02:35,100
One of those historic moments
that Google likes to give us and

48
00:02:35,100 --> 00:02:38,700
I've been giving a lot lately
with the depreciation of Sarah.

49
00:02:38,800 --> 00:02:40,800
Cyril tools that we've come to
know and love.

50
00:02:40,800 --> 00:02:42,600
But yeah, it looks like this
time.

51
00:02:42,600 --> 00:02:45,300
This is one of those that would
have to say goodbye to another

52
00:02:45,300 --> 00:02:47,900
goodbye to.
I feel in a very emotional way

53
00:02:47,900 --> 00:02:50,700
for a lot of people are very
frustrated way for a lot of

54
00:02:50,700 --> 00:02:52,600
people before we get into the
questions.

55
00:02:52,600 --> 00:02:55,300
This chat is intended for PPC,
Professionals of all levels.

56
00:02:55,300 --> 00:02:59,100
If you have something you want
to share, please do we are a

57
00:02:59,100 --> 00:03:00,200
friendly and supportive
Community.

58
00:03:00,200 --> 00:03:03,600
Please don't be afraid to
participate, and yes.

59
00:03:03,600 --> 00:03:07,100
But if you are just a lurker and
you just want to listen to the

60
00:03:07,100 --> 00:03:11,400
podcast, you're also very Very
much welcome and thank you for

61
00:03:11,400 --> 00:03:15,500
listening to this episode.
And when terms of people who are

62
00:03:15,500 --> 00:03:20,600
participating people are in the
last goodbye farewell tour of

63
00:03:20,600 --> 00:03:24,600
the you a the universal
analytics.

64
00:03:24,600 --> 00:03:27,800
We've got actor River Minkoff
and have a Hopkins joins us for

65
00:03:27,800 --> 00:03:31,200
this as well, as well as Julie
advice, Lawrence Chase, Fraser

66
00:03:31,200 --> 00:03:33,100
Andrews.
He's been giving a lot of tips

67
00:03:33,100 --> 00:03:37,000
about what you need to do in
this last last week of you a

68
00:03:37,000 --> 00:03:40,500
Travis, as well.
Joins us and yeah, Julian,

69
00:03:40,500 --> 00:03:42,900
that's a new name.
So I hope he's going to be in

70
00:03:42,900 --> 00:03:46,800
future chats and shown early as
well, and I'm sure quite a few

71
00:03:46,800 --> 00:03:48,600
more.
So, yeah, let's get on to

72
00:03:48,600 --> 00:03:51,300
question 1.
So, Julie asks, are all of the

73
00:03:51,300 --> 00:03:56,900
sites you work with using GA for
if so for how long, if not, why

74
00:03:57,000 --> 00:03:59,200
not.
So yeah, it looks like quite a

75
00:03:59,200 --> 00:04:02,500
lot of my clients.
Yes, have have migrated, I'm not

76
00:04:02,500 --> 00:04:06,000
showing times of all of Marin
software's clients but yeah,

77
00:04:06,000 --> 00:04:10,000
quite a quite a number of my
clients have my Dated manatee

78
00:04:10,000 --> 00:04:10,900
Manatee goes.
Yes.

79
00:04:10,900 --> 00:04:13,000
Ready to roll.
Pat ball bag sets.

80
00:04:13,000 --> 00:04:14,800
Yes.
But more than half are still

81
00:04:14,800 --> 00:04:17,200
checking you a data first and
not fully reliant.

82
00:04:17,200 --> 00:04:19,700
On ga4, not surprising Trappers
goes.

83
00:04:19,700 --> 00:04:21,899
The most forward-thinking brands
have had data.

84
00:04:21,899 --> 00:04:24,800
For the last six to nine months,
others are convinced, they are

85
00:04:24,800 --> 00:04:28,800
cut over process, should sign
with the Sunset date on Friday.

86
00:04:29,000 --> 00:04:32,000
It's a mixed bag surrounded by
continued apprehension.

87
00:04:32,300 --> 00:04:35,300
Desire respond saying, yes, six
months, everyone hates it,

88
00:04:35,300 --> 00:04:37,200
Google made.
One of the worst you eyes on the

89
00:04:37,200 --> 00:04:39,900
planet, huh?
Ray A bastard respond saying

90
00:04:39,900 --> 00:04:43,100
most of it I set up six months
ago but one Medical Practice

91
00:04:43,100 --> 00:04:46,200
client uses a locked-down
platform that only transitioned

92
00:04:46,200 --> 00:04:51,300
to J for this week's a bit late.
For that, that might be quite

93
00:04:51,300 --> 00:04:53,600
annoying.
Delivers respond saying it only

94
00:04:53,600 --> 00:04:56,800
certain ones, my restaurant
client actually has quite a bit

95
00:04:56,800 --> 00:05:00,200
of experience with it as they
installed it, when it first came

96
00:05:00,200 --> 00:05:05,000
over for app tracking now, it's
all getting migrated Julia's.

97
00:05:05,000 --> 00:05:07,900
Well, says, yes, all of the
sites I work with are running

98
00:05:07,900 --> 00:05:10,100
GTA 4 and half.
Infinitely six months.

99
00:05:10,100 --> 00:05:13,100
They only did it because I
insisted they do it.

100
00:05:13,200 --> 00:05:16,700
Otherwise I think that we all
also migrated cases so yes.

101
00:05:16,700 --> 00:05:21,500
If you don't migrate next week,
I believe that you will get also

102
00:05:21,500 --> 00:05:25,200
migrated Lawrence Chase response
saying yes, I had been pushing

103
00:05:25,200 --> 00:05:27,400
my clients to move GA for pretty
hard.

104
00:05:27,400 --> 00:05:31,100
A lot of Brands hate change and
hate to put in resources to

105
00:05:31,100 --> 00:05:36,000
making the change when there's
other work but it had to be done

106
00:05:36,300 --> 00:05:37,500
and you have phrase Andrews as
well.

107
00:05:37,500 --> 00:05:40,200
Say is a number of accounts.
I I work on haven't migrated in

108
00:05:40,207 --> 00:05:43,100
the last three to four months,
that being said, being involved

109
00:05:43,100 --> 00:05:47,400
with so many migrations in such
a short space of time has helped

110
00:05:47,400 --> 00:05:52,300
with understanding the platform,
big SO2 Brie and the same break

111
00:05:52,300 --> 00:05:56,600
big shout-out even whose content
I've been consuming and mass.

112
00:05:56,600 --> 00:06:00,000
And that the truth Ian anyone
that says hey I need you a full

113
00:06:00,000 --> 00:06:03,600
training, I just point them to I
point them to Bree be, eat

114
00:06:03,600 --> 00:06:06,300
Anderson and she's great
Lawrence goes as well yet.

115
00:06:06,300 --> 00:06:09,300
Few of us took her clothes
together together, A jump start

116
00:06:09,300 --> 00:06:11,300
on the new platform about a year
ago.

117
00:06:11,500 --> 00:06:15,200
Brie is a great teacher.
So yeah, we're all big fans in

118
00:06:15,200 --> 00:06:17,900
here as well and then never
Hopkins as well response to

119
00:06:17,900 --> 00:06:21,300
question one saying, for the
most part, yes, the biggest

120
00:06:21,300 --> 00:06:23,400
areas.
I see struggles are with

121
00:06:23,400 --> 00:06:27,300
e-commerce, particularly for
app, heavy sites lead gen have

122
00:06:27,300 --> 00:06:32,400
for the most part been on GA for
since the start of the year, now

123
00:06:32,400 --> 00:06:34,700
then continues.
It's worth noting that whilst

124
00:06:34,700 --> 00:06:37,600
most orangey for, I'm still
heavily reliant on Native

125
00:06:37,600 --> 00:06:40,900
conversion tracking For PPC
campaigns most brands.

126
00:06:41,100 --> 00:06:44,600
I work with don't qualify for GA
for audiences, do to

127
00:06:44,600 --> 00:06:48,400
thresholding.
However, for those that do I am

128
00:06:48,500 --> 00:06:52,400
in love and then Julian as well,
says, yes, all of the sites are

129
00:06:52,400 --> 00:06:56,000
wrong Google ads for have been
using GA for for about 4, plus

130
00:06:56,000 --> 00:06:59,300
months now.
However I am a much bigger fan

131
00:06:59,300 --> 00:07:03,600
of bidding primarily on website
conversion actions over g.

132
00:07:03,700 --> 00:07:06,900
A Chanel as well response to
question one saying, yes, to

133
00:07:06,900 --> 00:07:09,200
start with.
We tried to get Everything

134
00:07:09,200 --> 00:07:13,300
tracking first close to a year
as we could some clients have

135
00:07:13,300 --> 00:07:16,700
been a little behind the ball
but not from a lack of pushing

136
00:07:17,000 --> 00:07:20,200
on our side.
And then Julie takes us on to

137
00:07:20,200 --> 00:07:23,600
question 2 saying that, how
comfortable are you working in

138
00:07:23,600 --> 00:07:25,900
GA for?
I was like not yet.

139
00:07:26,300 --> 00:07:28,000
Yes.
Now they're not at all yet.

140
00:07:28,000 --> 00:07:30,500
Anyway, management goes getting
there slowly.

141
00:07:30,500 --> 00:07:32,800
Travis goes learning curve.
For sure early.

142
00:07:32,800 --> 00:07:36,700
Takeaway for me is the things
that are easier to find report

143
00:07:36,700 --> 00:07:40,900
on and draw insights from India.
A form must be a priority for

144
00:07:40,900 --> 00:07:43,100
Google and therefore deserve
attention.

145
00:07:43,300 --> 00:07:47,200
Custom reports should be a go-to
resource even in you a so that's

146
00:07:47,200 --> 00:07:50,900
less novel mattress, wanting
fairly comfortable for the easy

147
00:07:50,900 --> 00:07:53,800
stuff, but still find myself
frustrated, especially when

148
00:07:53,800 --> 00:07:56,800
other platforms still don't have
Integrations or clear

149
00:07:56,800 --> 00:08:00,500
documentation, Rabe acid
response saying, slowly getting

150
00:08:00,500 --> 00:08:02,500
there.
I've got custom dimensions and a

151
00:08:02,500 --> 00:08:06,000
few custom Explorations.
I can set up pretty easily now,

152
00:08:06,300 --> 00:08:10,800
but I still feel like the basic
things I Our missing basic

153
00:08:10,800 --> 00:08:13,000
things are missing.
That is very worrisome.

154
00:08:13,500 --> 00:08:15,600
There aren't response.
Same as comfortable as you can

155
00:08:15,600 --> 00:08:18,500
be with a newish platform
finding workarounds for data

156
00:08:18,500 --> 00:08:21,000
that used to be easily found in
you.

157
00:08:21,000 --> 00:08:23,200
A Julia virus.
Goes at this point.

158
00:08:23,200 --> 00:08:26,000
Not very, I'm so grateful for
all the training and tips I've

159
00:08:26,000 --> 00:08:29,000
received, but it's so
fundamentally different that I

160
00:08:29,000 --> 00:08:31,800
would likely wouldn't feel
comfortable for a while.

161
00:08:31,900 --> 00:08:35,200
Yeah, right there with you.
Julia Julie response to question

162
00:08:35,200 --> 00:08:37,000
2 as well.
Saying I would like to be way

163
00:08:37,000 --> 00:08:40,000
more comfortable than I am in g.
Day, four, I just find

164
00:08:40,000 --> 00:08:42,299
everything so hard in ga4 versus
you.

165
00:08:42,299 --> 00:08:47,200
A more steps more setup, endless
customization, which has meant

166
00:08:47,200 --> 00:08:50,800
way fewer, pre-setup, Matrix
reports, Etc.

167
00:08:51,100 --> 00:08:53,300
So, nearly as well response to
question to say, and I would say

168
00:08:53,300 --> 00:08:56,600
I can find most reports and set
up conversions, Etc, but still

169
00:08:56,600 --> 00:09:00,800
feel behind on creating custom
reports that are usable a lot of

170
00:09:00,800 --> 00:09:03,700
the stuff I want to create just
doesn't seem possible.

171
00:09:03,900 --> 00:09:07,200
He may be possible, but I
haven't figured it out yet.

172
00:09:07,500 --> 00:09:09,600
Julian response in on a Scale of
1 to 10.

173
00:09:09,600 --> 00:09:13,400
I'm a solid five to be honest.
I'd say, I'm a solid three.

174
00:09:14,700 --> 00:09:18,000
I've seen a bit of what others
can do with GA, for custom

175
00:09:18,000 --> 00:09:19,800
reports.
And I'm not there yet.

176
00:09:20,100 --> 00:09:23,700
I've been more focused on
setting up or deploying J. 4V G

177
00:09:23,700 --> 00:09:28,100
TM because it seems to be where
many of my clients get lost,

178
00:09:28,100 --> 00:09:29,500
apparently.
Yeah, definitely.

179
00:09:29,500 --> 00:09:32,400
I've used a lot of gtn to set of
my ga for as well.

180
00:09:32,900 --> 00:09:35,200
Ashton clock response to
question one saying it varies

181
00:09:35,200 --> 00:09:38,500
depending on the client some of
our newer ones.

182
00:09:38,700 --> 00:09:41,800
Only just started working
through this week in May or June

183
00:09:42,000 --> 00:09:45,900
usually because of past partner
or team, didn't make it a

184
00:09:45,900 --> 00:09:48,500
priority.
Others have been using GA for

185
00:09:48,500 --> 00:09:52,900
since early 2022 around.
When the announcement was made

186
00:09:53,200 --> 00:09:56,800
John Kagan response, saying they
will be that being said, having

187
00:09:56,800 --> 00:09:59,900
one client, who insists on doing
it on their own, and still

188
00:09:59,900 --> 00:10:02,100
hasn't migrated to it.
So, who knows?

189
00:10:02,400 --> 00:10:04,800
One client?
We migrated in January of last

190
00:10:04,800 --> 00:10:08,000
year, nice actor response to
question one as well.

191
00:10:08,000 --> 00:10:10,300
Said, I'll A different
perspective on this.

192
00:10:10,300 --> 00:10:13,200
I'm mostly working with tech and
SAS at the moment.

193
00:10:13,400 --> 00:10:16,700
You will not believe that there
are so many big SAS still

194
00:10:16,700 --> 00:10:20,200
running on you.
A moreover, they had not even

195
00:10:20,200 --> 00:10:23,400
downloaded the you a data for
future references.

196
00:10:23,900 --> 00:10:26,600
Never response to question to
say on a scale of one to ten.

197
00:10:26,600 --> 00:10:31,100
I'd put myself at a seven nice.
So I'd be a neutral on the MPS

198
00:10:31,100 --> 00:10:33,900
scale in all seriousness.
I don't think we ever raised

199
00:10:33,900 --> 00:10:37,600
ourselves as highly as others
would rate US compete comes with

200
00:10:37,700 --> 00:10:39,700
time.
She continues folks.

201
00:10:39,700 --> 00:10:42,300
I strongly recommend learning
from other.

202
00:10:42,300 --> 00:10:45,100
We do get to the resources
people yet, but hey, nice.

203
00:10:45,100 --> 00:10:46,700
To get a jump, start on that
Nava.

204
00:10:47,100 --> 00:10:49,600
She recommends and these are
handles.

205
00:10:49,600 --> 00:10:54,700
So that's why I have underscores
in some of these sayings at Brie

206
00:10:54,700 --> 00:10:58,800
on this code e on the school
Anderson at measure underscore

207
00:10:58,800 --> 00:11:04,600
Minds at team with TJ Jensen.
So that's JJ and soon at

208
00:11:04,600 --> 00:11:07,900
analytics Mania note.
If I didn't mention someone,

209
00:11:07,900 --> 00:11:09,500
it's not that.
The aren't useful.

210
00:11:09,500 --> 00:11:12,600
Just these are the folks who
helped me navigate continues.

211
00:11:12,600 --> 00:11:16,000
I will say we PPC folks got the
short end of the stick because

212
00:11:16,000 --> 00:11:20,600
most contents to get comfy with
GA for was very SEO focused.

213
00:11:20,700 --> 00:11:23,600
I think that might be part of
the reason so many cling to

214
00:11:23,600 --> 00:11:27,700
Native tracking and audiences,
even with a robust set up.

215
00:11:27,700 --> 00:11:31,000
So yeah, as he owes are having a
field engineer for, I don't

216
00:11:31,000 --> 00:11:32,500
know.
I'm not hearing them talk a lot

217
00:11:32,500 --> 00:11:34,400
about it.
For example, is response to

218
00:11:34,400 --> 00:11:37,500
question to sing comfortable,
but for sure have so much still

219
00:11:37,500 --> 00:11:41,000
to learn Main concerns really
are around tracking parameters

220
00:11:41,200 --> 00:11:43,400
and events.
But so much of my learning has

221
00:11:43,400 --> 00:11:46,700
been community-led taught at
Google for lack of training

222
00:11:46,700 --> 00:11:48,400
videos.
Can't fault them, however, in

223
00:11:48,400 --> 00:11:52,200
making advertisers aware, yeah,
there was countdown.

224
00:11:52,200 --> 00:11:56,400
Clocks in email signatures on
the platforms everywhere and

225
00:11:56,400 --> 00:11:58,300
then your actor goes follow up
on question one.

226
00:11:58,300 --> 00:12:01,600
How is keeping the past you a
data will ensure that we are not

227
00:12:01,600 --> 00:12:05,000
facing any data lost.
Even after we migrated to ga4

228
00:12:05,300 --> 00:12:08,200
and never goes downloading the
data into bigquery or other data

229
00:12:08,200 --> 00:12:09,700
management.
Tools is helpful.

230
00:12:09,700 --> 00:12:13,000
It's also useful to document
with your own year reports, you

231
00:12:13,000 --> 00:12:16,100
need versus they're nice to
have, so you can try to do

232
00:12:16,100 --> 00:12:20,100
oranges, two Clementines and
upcoming reporting cycle.

233
00:12:20,100 --> 00:12:22,900
So yeah, straight forward to
back up, actor goes and I think

234
00:12:22,900 --> 00:12:26,400
pretty sure it is.
We will make of response a much

235
00:12:26,400 --> 00:12:29,600
more comfortable than I was, but
I'm still not 100% confident

236
00:12:29,600 --> 00:12:31,700
that I'm using it to its full
potential.

237
00:12:32,000 --> 00:12:35,900
I don't think anyone is and she
continues what this is an answer

238
00:12:35,900 --> 00:12:38,700
question 1.
Now saying she says, I think we

239
00:12:38,700 --> 00:12:41,600
finally have gotten almost
everyone over but it's not an

240
00:12:41,600 --> 00:12:44,400
easy setup and it can be
challenging to push the change

241
00:12:44,400 --> 00:12:48,000
management through big complex
organizations or teeny tiny ones

242
00:12:48,000 --> 00:12:52,600
with no development teams.
And I'm just also to note that

243
00:12:52,600 --> 00:12:56,800
there is a mg, a full resources
page and I think this is

244
00:12:56,800 --> 00:13:00,300
response to navigating a list of
resources and people to follow

245
00:13:00,500 --> 00:13:05,100
and if you go to official PPC,
chat.com, forward slash, Google

246
00:13:05,300 --> 00:13:10,600
hyphen analytics, Hyphen for
hyphen, Ta for hyphen resources,

247
00:13:10,900 --> 00:13:13,200
you'll get there.
Go to official, PPC, chat book,

248
00:13:13,200 --> 00:13:16,600
calm, and yeah, drop down from
the resources page, and you'll

249
00:13:16,600 --> 00:13:19,300
see the option for Google
analytics for sir.

250
00:13:19,600 --> 00:13:22,800
That won't be hard to find at a
response to question two Saints.

251
00:13:22,800 --> 00:13:26,600
So, so far, I'm not impressed by
the ability to download the data

252
00:13:26,600 --> 00:13:28,000
feature.
So, no, no.

253
00:13:28,200 --> 00:13:31,700
However, I'm working on SAS with
my partner to work.

254
00:13:31,700 --> 00:13:35,400
Somewhat like, what ga4?
But without complex dashboards,

255
00:13:35,400 --> 00:13:38,500
we are still working on getting
it up and running.

256
00:13:38,600 --> 00:13:41,900
Running and Ashton response to
question 2 as well, as in I can

257
00:13:41,900 --> 00:13:44,500
get the essentials of what we
need for reporting, pretty

258
00:13:44,500 --> 00:13:47,100
easily like Channel and campaign
breakdowns.

259
00:13:47,100 --> 00:13:49,200
But beyond that, there is a lot
to learn.

260
00:13:49,200 --> 00:13:52,100
And unfortunately, I haven't
really had the time or capacity

261
00:13:52,100 --> 00:13:56,800
to dive deeper into the platform
and in response to Navas

262
00:13:56,800 --> 00:14:00,200
suggestion to actor, about
downloading the data into

263
00:14:00,200 --> 00:14:01,900
bigquery Julie, girls.
Sure.

264
00:14:01,900 --> 00:14:05,900
Wish bigquery was accessible to
Mac users.

265
00:14:05,900 --> 00:14:09,900
So yeah, be aware guys bigquery
Accessible to Max.

266
00:14:09,900 --> 00:14:12,100
Oh yeah.
And Julie check, but it's not

267
00:14:12,300 --> 00:14:14,300
and exercise.
That's why I bought a Windows

268
00:14:14,300 --> 00:14:16,900
laptop recently to run cracked
software.

269
00:14:16,900 --> 00:14:21,200
So yeah, get a PC if you're
going to need big query for your

270
00:14:21,200 --> 00:14:25,100
data and then Julie gives us a
question. 3 saying what are your

271
00:14:25,100 --> 00:14:27,400
biggest challenges working in
GA?

272
00:14:27,400 --> 00:14:30,300
For Travis response saying the
biggest challenge is now

273
00:14:30,300 --> 00:14:34,100
juggling two properties.
Regardless of my ga for data set

274
00:14:34,100 --> 00:14:36,400
I still have different
comparisons across two

275
00:14:36,400 --> 00:14:39,700
platforms.
I also find Holding extremely

276
00:14:39,700 --> 00:14:43,100
frustrating, always in the name
of privacy, but I find Google's

277
00:14:43,100 --> 00:14:46,000
Russian.
Now inconsistent Matt response,

278
00:14:46,000 --> 00:14:49,500
same threshold inquiry, but also
getting new features in the last

279
00:14:49,500 --> 00:14:52,600
month that should have been
released for six months, for

280
00:14:52,600 --> 00:14:56,300
advertisers before the switch
date, split data and broken

281
00:14:56,300 --> 00:14:58,700
Integrations.
Like not seeing calls tracked

282
00:14:58,700 --> 00:15:02,300
back to campaigns and needing to
add them manually.

283
00:15:02,800 --> 00:15:05,400
And we have John Kagan
responding to question, 3 about

284
00:15:05,400 --> 00:15:08,200
his biggest challenges saying
they are so many but the most

285
00:15:08,200 --> 00:15:10,500
annoying One.
At least for me, is that the

286
00:15:10,500 --> 00:15:13,800
navigation of the you, I still
doesn't make sense.

287
00:15:14,100 --> 00:15:17,700
Julia voice response saying, QA
nothing to check against and

288
00:15:17,700 --> 00:15:20,900
conversion rebuilding.
I'm now in very fun

289
00:15:20,900 --> 00:15:24,600
conversations about why
conversions are dropping.

290
00:15:24,600 --> 00:15:28,000
Because the way events and
sessions are measured has

291
00:15:28,000 --> 00:15:31,700
fundamentally changed year on
year, comparisons for nany.

292
00:15:31,700 --> 00:15:35,200
Cam is effectively over a while.
Sean goes.

293
00:15:35,200 --> 00:15:38,400
Yeah, this luckily, we started
reporting in, q1 from both.

294
00:15:38,500 --> 00:15:42,300
Thew a and ga4 to show clients
the difference in conversions

295
00:15:42,400 --> 00:15:45,100
but some are still struggling
Jesus.

296
00:15:45,100 --> 00:15:48,700
So what is Right?
Ah, that's annoying.

297
00:15:49,100 --> 00:15:52,300
So Emily responds saying yeah to
question 3 same the usability.

298
00:15:52,300 --> 00:15:56,500
Nothing seems like it was
created from the users point of

299
00:15:56,500 --> 00:15:57,400
view.
Yeah.

300
00:15:57,400 --> 00:16:01,700
In that right Julie response
saying getting reporting set up

301
00:16:01,700 --> 00:16:04,400
and being able to easily view
segmented data.

302
00:16:04,400 --> 00:16:07,600
The report Builder gives me a
headache as soon as I open it.

303
00:16:07,900 --> 00:16:10,900
How worse?
Handed you a reports, not ported

304
00:16:10,900 --> 00:16:14,600
into GA for Travis goes.
I think Google's current

305
00:16:14,600 --> 00:16:18,300
reasoning different measurement
certain metrics naturally sun

306
00:16:18,300 --> 00:16:22,800
setting makes sense.
Does it mmm still way too big, a

307
00:16:22,808 --> 00:16:26,800
Band-Aid to rip off at once?
I wish certain changes could

308
00:16:26,800 --> 00:16:30,600
have been woven into you a over
a span of years.

309
00:16:30,600 --> 00:16:33,300
Instead of trying to learn a new
language overnight, Julie goes,

310
00:16:33,300 --> 00:16:36,600
I saw someone tweet that calling
this product ta for is really a

311
00:16:36,600 --> 00:16:39,600
big misnomer.
It is Is not a new version of

312
00:16:39,600 --> 00:16:42,100
the existing Analytics tool.
It is an entirely new

313
00:16:42,100 --> 00:16:46,400
application and probably should
have been named as such, right?

314
00:16:46,400 --> 00:16:49,000
It is a brand new thing and
Travis goes fully agree.

315
00:16:49,000 --> 00:16:51,500
Google's product, naming leaves
much to be desired.

316
00:16:51,500 --> 00:16:54,800
So many have such a thin coat of
varnish applied.

317
00:16:54,800 --> 00:16:58,100
It's easy to see through Auto
applied recommendations

318
00:16:58,100 --> 00:17:01,500
performance, max value based
bidding additional conversion

319
00:17:01,500 --> 00:17:05,000
value from new customers most
offensive.

320
00:17:05,599 --> 00:17:08,300
Julia vitals are response to
like Julie's answer to her

321
00:17:08,300 --> 00:17:09,500
question.
Sandwich was like getting

322
00:17:09,500 --> 00:17:12,900
reporting set up and being able
to easily view segmented data

323
00:17:12,900 --> 00:17:16,400
and the report Builder gives her
a headache as soon as she opens

324
00:17:16,400 --> 00:17:20,300
it and delivers goes I'm taking
the report rebuilding pretty

325
00:17:20,300 --> 00:17:22,700
personally.
It's should have been mapped

326
00:17:22,700 --> 00:17:26,599
over with support if warranted.
Not everyone has sales data as a

327
00:17:26,608 --> 00:17:30,200
single point of Truth in that
the truth and never goes

328
00:17:30,200 --> 00:17:33,300
honestly I think half the reason
we got the gift of audiences

329
00:17:33,300 --> 00:17:37,000
based on enhanced conversions
was to make up for the glitches

330
00:17:37,000 --> 00:17:41,000
- of ga.
For based on size of scope of

331
00:17:41,000 --> 00:17:44,900
Brands and Fraser response to
question, 3 saying.

332
00:17:44,900 --> 00:17:48,400
Yeah, biggest issue for me is
data processing times.

333
00:17:48,800 --> 00:17:51,800
The shift in going from
real-time data updates and you a

334
00:17:51,808 --> 00:17:56,400
to sometimes having to wait 24
hours for data has meant extra

335
00:17:56,400 --> 00:17:59,300
expectation.
Managing for clients that being

336
00:17:59,300 --> 00:18:03,200
said, debug mode is a godsend
for GTM checks.

337
00:18:03,500 --> 00:18:05,300
Julie goes.
Yeah, I have heard complaints

338
00:18:05,300 --> 00:18:08,400
about the lack of live data
viewing to yeah.

339
00:18:08,500 --> 00:18:10,900
I think even Chris Ridley this
morning was like, we've not

340
00:18:10,900 --> 00:18:13,700
they've not been showing the
conversion data since 9 a.m. and

341
00:18:13,700 --> 00:18:17,200
this was already early afternoon
maybe was a matter of him

342
00:18:17,200 --> 00:18:21,700
needing to wait many more hours
to see his data and rivermen

343
00:18:21,700 --> 00:18:24,600
cough response to question 3
say, saying the inability to

344
00:18:24,600 --> 00:18:28,100
pull year-on-year reports in the
platforms, especially for

345
00:18:28,100 --> 00:18:32,300
accounts with long histories.
Oh, Lord, and never Hopkins

346
00:18:32,300 --> 00:18:35,600
response to question three
saying, biggest challenge to

347
00:18:35,600 --> 00:18:39,900
working in GTA 4 is thresholds
and balancing In privacy versus

348
00:18:39,900 --> 00:18:43,400
utility, ga4, is a really
powerful tool and provides

349
00:18:43,400 --> 00:18:46,400
Enterprise level resources
across the board.

350
00:18:46,500 --> 00:18:51,100
The problem is not everyone has
enterprise-level data, PS.

351
00:18:51,100 --> 00:18:55,800
Google signals is a GDP, our
trap or Lord, never continues.

352
00:18:55,800 --> 00:18:59,000
Unless you take the time to
unselect countries for the

353
00:18:59,000 --> 00:19:01,700
modeling of data.
You might be putting yourself at

354
00:19:01,700 --> 00:19:05,600
risk for GDP.
Our safest is to not use them,

355
00:19:05,800 --> 00:19:09,700
but for us us, folks, it's hard
to say no to That data

356
00:19:09,900 --> 00:19:12,700
enrichment.
So remember if you're looking at

357
00:19:12,700 --> 00:19:17,100
modeling of data and you're
looking to use it be careful

358
00:19:17,100 --> 00:19:20,000
about GDP, our roles and make
sure that you're on the right

359
00:19:20,000 --> 00:19:23,600
side of the law, Julie response
to that scene and we and our

360
00:19:23,600 --> 00:19:26,600
clients have grown so accustomed
to having detailed data that

361
00:19:26,600 --> 00:19:30,800
this shift to less detailed
data, involves a level of trust

362
00:19:31,000 --> 00:19:33,800
that companies like Google
simply have not learned,

363
00:19:33,900 --> 00:19:37,700
especially when they are
reporting on the success of an

364
00:19:37,700 --> 00:19:40,300
entity.
That makes them money.

365
00:19:40,700 --> 00:19:43,200
Colin Harris response to.
I'm never saying that.

366
00:19:43,200 --> 00:19:45,600
Yeah, they are few times I'm
grateful that the US doesn't

367
00:19:45,600 --> 00:19:49,100
really believe in privacy rules
and this is one of them.

368
00:19:50,200 --> 00:19:53,000
Yeah, their lives have rules.
I feel America does not believe

369
00:19:53,000 --> 00:19:55,600
in but let's not another
conversation for another

370
00:19:55,600 --> 00:19:58,200
podcast.
A certain response to question 3

371
00:19:58,200 --> 00:20:02,000
seen echoing, everyone sentiment
on usability, hair, feels clunky

372
00:20:02,000 --> 00:20:06,500
are trying to do anything
compared to you a govern sing

373
00:20:06,500 --> 00:20:09,000
response.
Question 3 saying, yeah, Ports,

374
00:20:09,000 --> 00:20:12,400
even very simple reports are
used to generate in you a takes

375
00:20:12,500 --> 00:20:15,000
hours.
Sometimes, Julian response to

376
00:20:15,000 --> 00:20:17,600
question 3 saying it's
definitely using the report

377
00:20:17,600 --> 00:20:21,600
Builders and he gives a
mind-blowing Emoji to that one.

378
00:20:21,600 --> 00:20:23,200
And Julie goes, I feel you on
this.

379
00:20:23,200 --> 00:20:27,400
That report Builder is clearly a
devs flex, but for regular folks

380
00:20:27,500 --> 00:20:32,600
even technically Savvy ones like
PPC has it is a nightmare.

381
00:20:32,600 --> 00:20:37,000
So yes that's that's going to be
fun for us and going on to

382
00:20:37,000 --> 00:20:40,800
question for Asks, what is
missing in GA for that?

383
00:20:40,800 --> 00:20:44,300
You regularly use in Universal
analytics and I feel people are

384
00:20:44,300 --> 00:20:46,500
going to say everything, Travis
response.

385
00:20:46,500 --> 00:20:50,700
First of all saying I already
miss the behavior flow report,

386
00:20:50,800 --> 00:20:52,900
not a ton of folks.
Leverage.

387
00:20:53,000 --> 00:20:56,300
This historically possibly
explaining its depreciation

388
00:20:56,400 --> 00:21:00,400
having a visual map of average
Parts through a site was

389
00:21:00,400 --> 00:21:03,300
invaluable for me.
It can be recreated, but it's

390
00:21:03,300 --> 00:21:07,400
not the same Rabe acid respond
saying, this is so stupidly

391
00:21:07,400 --> 00:21:10,400
basic by Miss.
Able to view charts by week or

392
00:21:10,400 --> 00:21:13,400
month.
It made Trends spotting so much

393
00:21:13,400 --> 00:21:16,700
easier.
So we can't view charts by week

394
00:21:16,700 --> 00:21:19,500
or month anymore.
Or do we have to recreate that

395
00:21:19,500 --> 00:21:21,200
you've got to be able to do
that?

396
00:21:21,200 --> 00:21:23,800
That's got to be a custom report
that you can do it be

397
00:21:23,800 --> 00:21:26,400
ridiculous.
We can't see starts by week and

398
00:21:26,400 --> 00:21:28,300
month anymore, that's a bit
annoying.

399
00:21:28,300 --> 00:21:30,900
Anyway, actual response,
question 3 saying, they are

400
00:21:30,900 --> 00:21:33,700
minimum data threshold, is the
inability to download the

401
00:21:33,700 --> 00:21:36,200
reports.
The inability to connect old.

402
00:21:36,200 --> 00:21:38,300
You a data with the new, you a
date.

403
00:21:38,400 --> 00:21:40,600
Te.
No GA alternative.

404
00:21:40,600 --> 00:21:44,400
Well, there is alternative to
Jay's just whether you feel that

405
00:21:44,600 --> 00:21:46,600
it is worth it or worth the
money.

406
00:21:46,600 --> 00:21:50,100
I do bi analytics for one
companies and not understanding

407
00:21:50,100 --> 00:21:52,100
why they have to switch to GA
for.

408
00:21:52,100 --> 00:21:57,300
She continues media buyers in
the mid with an inaccurate data,

409
00:21:57,300 --> 00:22:00,700
lovely delivers response.
Question forcing aside.

410
00:22:00,700 --> 00:22:06,000
From all my conversions, I'd say
segments, I'm a click around and

411
00:22:06,000 --> 00:22:09,800
find out kind of lady never His
response question for saying

412
00:22:09,800 --> 00:22:12,700
this is a bit of a cop out by
miss the stability of data.

413
00:22:12,700 --> 00:22:16,400
We can recreate most of the
reports and metrics from you a2j

414
00:22:16,400 --> 00:22:20,600
for but I find I am on shaky
aground entrusting the data /,

415
00:22:20,600 --> 00:22:25,600
formatting it also knowing it
will be purged after a time is a

416
00:22:25,600 --> 00:22:28,900
mood isn't adjust it to respond
saying I'm waiting for

417
00:22:28,900 --> 00:22:32,300
everyone's answer here as I
shared mine in a three even

418
00:22:33,100 --> 00:22:36,600
Julie goes out where to start in
reply to question 4.

419
00:22:37,000 --> 00:22:41,000
How about any useful people?
See reports, just existing or

420
00:22:41,000 --> 00:22:44,800
any PC navigation, or The
Disappearance of segments or the

421
00:22:44,800 --> 00:22:48,900
fact that everything has to be
set up or customized.

422
00:22:48,900 --> 00:22:53,400
No one wants this as the only
level dashboards easy sharing

423
00:22:53,400 --> 00:22:56,400
and everything else.
Never goes, the PPC navigation

424
00:22:56,400 --> 00:22:59,600
is solvable by adding in those
reports to the library

425
00:22:59,600 --> 00:23:02,400
collection.
One of my best golden nuggets

426
00:23:02,400 --> 00:23:05,300
from Bri Anderson.
Do they respond saying the

427
00:23:05,300 --> 00:23:08,300
product team actually said that
the you a navigation?

428
00:23:08,600 --> 00:23:11,600
Too hard.
Sony made it simpler in GA for I

429
00:23:11,608 --> 00:23:16,300
was providing feedback to them
for a hot second, a while ago.

430
00:23:16,300 --> 00:23:19,600
Wow, yeah.
Providing feedback to the

431
00:23:19,600 --> 00:23:21,800
producting.
Actor, goes, is the data from

432
00:23:21,800 --> 00:23:23,900
you.
A will go wish for the companies

433
00:23:23,900 --> 00:23:26,300
who haven't switched to GA for
yet.

434
00:23:26,300 --> 00:23:29,400
Well, they'll be auto-switching
happening at some point.

435
00:23:29,600 --> 00:23:33,200
Julian response saying you a had
better ready to go reports out

436
00:23:33,200 --> 00:23:36,200
of the box.
I feel as though you a was much

437
00:23:36,200 --> 00:23:38,300
more powerful out of the box
than ga.

438
00:23:38,400 --> 00:23:41,000
If or when it comes to this,
right?

439
00:23:41,000 --> 00:23:43,400
Exactly.
And Julie goes Google will tell

440
00:23:43,400 --> 00:23:46,200
you that ga4 is much more
powerful while that is

441
00:23:46,200 --> 00:23:50,900
technically true statement from
an ease of use perspective.

442
00:23:51,000 --> 00:23:54,800
It fails who cares if you can
customize into Oblivion, if you

443
00:23:54,800 --> 00:23:58,100
can't recreate reports, you've
been sharing with clients for

444
00:23:58,100 --> 00:24:02,000
the last 10 years.
Yeah I hope you're listening

445
00:24:02,000 --> 00:24:03,900
Google doubt.
They are but I really hope they

446
00:24:03,900 --> 00:24:07,300
are shontella response saying
I'm not sure if they are missing

447
00:24:07,300 --> 00:24:09,000
or just not easily.
Accessible.

448
00:24:09,000 --> 00:24:12,800
But segments, some secondary
Dimensions, easy to read graphs,

449
00:24:12,800 --> 00:24:14,800
good luck.
If you are color, blind

450
00:24:15,000 --> 00:24:18,900
distinguishing between six lines
of different Blues, Lord, ain't

451
00:24:18,900 --> 00:24:20,600
that the right Judy goes the
colors.

452
00:24:20,600 --> 00:24:22,700
Good Lord yes.
Julia voice goes.

453
00:24:22,700 --> 00:24:24,700
Thank you for mentioning the
color situation.

454
00:24:24,700 --> 00:24:28,300
Accessibility is not it with
Google these days.

455
00:24:28,300 --> 00:24:32,000
It's all Hues and shades and a
prayer that you can see it all

456
00:24:32,300 --> 00:24:35,600
correctly.
Jesus, ain't that the truth?

457
00:24:35,900 --> 00:24:37,300
Tim Holloman response to
question.

458
00:24:37,300 --> 00:24:41,800
Forcing And tab by Source or
medium with Goal, set columns

459
00:24:41,800 --> 00:24:46,600
customized By Priority had a lot
of default views that exist in

460
00:24:46,600 --> 00:24:49,000
different forms.
Now, haven't found a way to

461
00:24:49,008 --> 00:24:54,200
recreate all of them yet, that's
tough and then you are never

462
00:24:54,200 --> 00:24:55,400
have Kings goes.
I'm not sure.

463
00:24:55,400 --> 00:24:56,600
We questions.
She's answering them.

464
00:24:56,600 --> 00:25:00,400
But just in terms of the chat in
general, she says I think the

465
00:25:00,400 --> 00:25:03,500
point about Sherwood data is
where third-party Solutions like

466
00:25:03,500 --> 00:25:07,100
optimize ants wider and others
will come in to save the day.

467
00:25:07,100 --> 00:25:11,200
We also don't have Have to stick
with GA for if it doesn't meet

468
00:25:11,200 --> 00:25:13,500
our needs.
Yes, you really don't perfect

469
00:25:13,500 --> 00:25:18,100
segue into question 5.
So what's question 5gd goes?

470
00:25:18,300 --> 00:25:20,100
Yeah.
Are you actively investigating

471
00:25:20,100 --> 00:25:22,300
and or testing other analytics
solution?

472
00:25:22,300 --> 00:25:25,300
If so which ones and what are
your thoughts on them?

473
00:25:25,600 --> 00:25:28,200
Me know, personally, because
it's all about what my clients

474
00:25:28,200 --> 00:25:31,900
need of have been asking for.
And yes, they have been added OB

475
00:25:31,900 --> 00:25:35,300
analytics as I mentioned before
a droll as well as been.

476
00:25:35,300 --> 00:25:38,000
Another one that clients have
mentioned that they're switching

477
00:25:38,000 --> 00:25:40,600
to To Travis response team for
now.

478
00:25:40,600 --> 00:25:43,200
I am in the devil.
You know, Camp if Google ads.

479
00:25:43,200 --> 00:25:46,800
Prioritizes ga4 signals need to
master that platform and

480
00:25:46,800 --> 00:25:49,700
accelerate the ad serving
machine learning.

481
00:25:49,700 --> 00:25:52,800
The door, is open, sea
attribution for host of new tech

482
00:25:52,900 --> 00:25:55,600
Solutions.
I still think the default will

483
00:25:55,600 --> 00:26:01,300
be GA for by Year's End.
Surviving a sassy lady, even

484
00:26:01,300 --> 00:26:03,900
respond saying not currently,
but keeping an eye out for

485
00:26:03,900 --> 00:26:06,600
something useful to a small
business.

486
00:26:06,600 --> 00:26:08,700
Yes.
I think some a lot of Will be

487
00:26:08,800 --> 00:26:10,100
novel.
Hopkins goes.

488
00:26:10,100 --> 00:26:12,600
It's almost like I read read
your mind.

489
00:26:12,600 --> 00:26:15,200
Currently.
Most of my folks are still team

490
00:26:15,200 --> 00:26:18,300
GTA 4, but that's also because
ga4 is free.

491
00:26:18,600 --> 00:26:21,700
I think we'll see a big shift
from Enterprise and be to beat

492
00:26:21,700 --> 00:26:23,900
other Solutions.
I think we will too, as well.

493
00:26:24,400 --> 00:26:26,000
River response to question for
same.

494
00:26:26,000 --> 00:26:29,400
Bounce rates and e-commerce.
Conversion rates are two big

495
00:26:29,400 --> 00:26:32,700
missing pieces actor.
Response question, five, same

496
00:26:32,700 --> 00:26:35,700
pure Python and coding.
If I think it looks good we end

497
00:26:35,700 --> 00:26:38,900
up having an alternative.
I would like to hear What others

498
00:26:38,900 --> 00:26:41,500
are testing.
Yeah, Chanel response saying I

499
00:26:41,500 --> 00:26:45,400
would like to be but wanted to
get GA for all set up first and

500
00:26:45,400 --> 00:26:47,200
of course as sort of data to
see.

501
00:26:47,200 --> 00:26:50,200
In response to question five, I
am quietly waiting for the

502
00:26:50,200 --> 00:26:55,200
Microsoft uet analytics in hopes
that the actually saw what was

503
00:26:55,200 --> 00:26:57,500
happening.
And recreated, a more you a like

504
00:26:57,500 --> 00:27:00,100
Platform One Can Dream?
Yes.

505
00:27:00,100 --> 00:27:02,900
Microsoft.
Get in there on that Julie

506
00:27:02,900 --> 00:27:05,300
response to question.
Five saying, I have not looked

507
00:27:05,300 --> 00:27:08,900
at other options very seriously
but I want to The site.

508
00:27:08,900 --> 00:27:13,600
If anyone wants to do a write up
of alternatives to GA for, let

509
00:27:13,600 --> 00:27:16,300
me know and there might be one
out there already.

510
00:27:16,800 --> 00:27:18,700
Julia Vice response to question
five saying yes.

511
00:27:18,700 --> 00:27:21,100
And no as a spoiled, hold Co
brat.

512
00:27:21,400 --> 00:27:25,600
We have our own data Lake that
we can visualize from but that

513
00:27:25,600 --> 00:27:29,000
isn't a solution for everything
like when I onboard a new client

514
00:27:29,000 --> 00:27:33,000
and now can't get their
historical data, easily data

515
00:27:33,000 --> 00:27:38,200
portability, and ownership is a
major flow with a response to

516
00:27:38,300 --> 00:27:42,600
Question 5 saying had a fun time
exploring at arise 23 and

517
00:27:42,600 --> 00:27:46,300
checking out other options.
Adobe seems to be one of the

518
00:27:46,300 --> 00:27:49,900
bigger competitors there.
They really are she continues?

519
00:27:49,900 --> 00:27:52,800
I doubt, we'll see a lot of
people switching off of GA,

520
00:27:52,800 --> 00:27:55,400
though.
Most clients don't have a budget

521
00:27:55,400 --> 00:28:00,300
for analytics and GA is powerful
and free Julie goes, I have said

522
00:28:00,300 --> 00:28:03,800
for years that when Google needs
Revenue ad dollars cannot

523
00:28:03,800 --> 00:28:07,300
continue to grow forever, that
they would introduce a paid tier

524
00:28:07,300 --> 00:28:10,600
of Analytics.
Where you got more PC settings

525
00:28:10,600 --> 00:28:13,700
and actual support for maybe $50
a month.

526
00:28:13,900 --> 00:28:17,700
River goes, they have GA 360
which isn't switching over for

527
00:28:17,700 --> 00:28:20,000
another year, but it's pretty
expensive.

528
00:28:20,000 --> 00:28:23,300
I believe Tim Halloran response
saying your agreed until there's

529
00:28:23,300 --> 00:28:26,900
a worthy Contender or disruptor,
even with the upheaval.

530
00:28:26,900 --> 00:28:30,500
It's still the most integrated
into every facet of the paid

531
00:28:30,500 --> 00:28:33,600
Media or cross-channel
Department experience.

532
00:28:33,900 --> 00:28:37,100
It would take quite a bit of
time to completely switch over

533
00:28:37,500 --> 00:28:40,100
from it.
It and we have Tim hollering

534
00:28:40,100 --> 00:28:42,100
responding to question five as
well saying.

535
00:28:42,100 --> 00:28:45,400
Haven't found a replacement per
se, but I do like having

536
00:28:45,400 --> 00:28:49,100
redundancies in place
redundancies, especially lately

537
00:28:49,100 --> 00:28:51,900
with the unpredictability right
now, the other analytics

538
00:28:51,900 --> 00:28:55,600
software's are specific to
clients Industries or Rocker

539
00:28:55,600 --> 00:28:59,300
Box.
Adobe also use a few for reports

540
00:28:59,300 --> 00:29:03,900
like Optimizer shape Optimizer
and comma shape, a shape and

541
00:29:03,900 --> 00:29:05,200
analytics.
Uh, I'm not sure.

542
00:29:05,600 --> 00:29:09,700
So one more question to go and
really are What have been the

543
00:29:09,700 --> 00:29:14,400
most helpful resources you found
for setting up and using GA for

544
00:29:14,400 --> 00:29:15,900
Bree Anderson?
For me?

545
00:29:15,900 --> 00:29:19,400
Is it?
So I, but also unofficial PPC

546
00:29:19,400 --> 00:29:22,100
chat.com.
There are a list of resources

547
00:29:22,100 --> 00:29:25,400
that Julie has gathered as well.
So I highly recommend you check

548
00:29:25,400 --> 00:29:28,400
that out.
I started with everything Google

549
00:29:28,400 --> 00:29:30,900
self Publishers and Travis
response.

550
00:29:30,900 --> 00:29:34,700
To question 6 saying, hear it
from the horse's mouth and learn

551
00:29:34,700 --> 00:29:37,900
through the that lens first from
there, I crowdsource.

552
00:29:38,400 --> 00:29:41,400
People are brilliant, many
solutions and reports are also

553
00:29:41,400 --> 00:29:46,400
published ready to see Excel
udemy and others, reinforce some

554
00:29:46,700 --> 00:29:48,400
paid.
So yeah, people are having to

555
00:29:48,400 --> 00:29:51,900
pay to train to get this
information which is really

556
00:29:51,900 --> 00:29:54,600
interesting Chantelle.
Irresponsible I signed up for

557
00:29:54,600 --> 00:29:57,400
Bree underscore underscore
understands course.

558
00:29:57,600 --> 00:30:01,100
Watched a lot of webinars, read
a lot of e-books and spent a lot

559
00:30:01,100 --> 00:30:06,000
of time playing around and I
still feel about a five or six

560
00:30:06,400 --> 00:30:10,300
on the comfortability.
Gail Sheehy continues by the

561
00:30:10,300 --> 00:30:12,200
way.
That is not a knock on any of

562
00:30:12,200 --> 00:30:15,100
the courses or webinars.
It is more about the DraStic

563
00:30:15,100 --> 00:30:18,900
change of ga4 and the complexity
of the usability.

564
00:30:18,900 --> 00:30:21,100
So, yeah.
So even with all the help they

565
00:30:21,100 --> 00:30:24,300
and expertise getting, it's just
so complex.

566
00:30:24,700 --> 00:30:28,200
We were goes, Google has so many
good ones to be honest on their

567
00:30:28,200 --> 00:30:32,700
services, that google.com page,
and Miatas, very versys, is a

568
00:30:32,700 --> 00:30:36,100
good place to start.
Julian goes measure school and

569
00:30:36,100 --> 00:30:38,100
team has excellent explainer
video.

570
00:30:38,300 --> 00:30:41,300
Is on Google analytics, their
YouTube channel has been a

571
00:30:41,300 --> 00:30:44,900
One-Stop shop for me and Julia
Vice response and custom

572
00:30:44,900 --> 00:30:47,200
Training for me.
And my team though it's still

573
00:30:47,200 --> 00:30:49,900
pretty confusing never Hopkins
as well saying.

574
00:30:49,900 --> 00:30:53,400
I listed a few folks earlier but
we'll highlight a few more one

575
00:30:53,400 --> 00:30:58,400
Google's tutorials to Foxwell.
Founders and 3, this chat always

576
00:30:58,400 --> 00:31:02,000
helpful for anything, PPC.
And the difficulties that we're

577
00:31:02,000 --> 00:31:06,100
facing and on that note, we come
to the end of this chat.

578
00:31:06,100 --> 00:31:08,900
I hope you found that useful.
I hope you've listed On and made

579
00:31:08,900 --> 00:31:11,900
note of the resources that you
have for ga4.

580
00:31:11,900 --> 00:31:15,900
I hope you're not having a
stressful last week before the

581
00:31:15,900 --> 00:31:19,500
ga, for a migration.
So yeah, I hope you're hanging

582
00:31:19,500 --> 00:31:22,300
there.
Join a community joined, the PVC

583
00:31:22,300 --> 00:31:26,900
chat Community joined the our,
the PLU chat WhatsApp Community

584
00:31:26,900 --> 00:31:32,300
as well.
Just go to be it .l, y /pl, you

585
00:31:32,300 --> 00:31:35,300
WhatsApp, and you'll be able to
get the link to.

586
00:31:35,300 --> 00:31:38,100
Yeah, join us on there.
So, you know, if you have

587
00:31:38,200 --> 00:31:41,700
Questions about ga4, if you have
any questions about getting paid

588
00:31:41,700 --> 00:31:44,900
in the industry, we have any
questions about P, Max data

589
00:31:44,900 --> 00:31:46,300
that.
You're seeing how to get ahead

590
00:31:46,300 --> 00:31:49,600
in the industry.
Join the PLU chat community on

591
00:31:49,600 --> 00:31:51,800
WhatsApp and I'm sure we'll be
able to answer you.

592
00:31:52,200 --> 00:31:54,600
So yeah, hope you've taken some
great takeaways.

593
00:31:54,600 --> 00:31:57,900
If you want to continue the on
this chat, tho please join on

594
00:31:57,900 --> 00:31:59,000
Thursday.
At 5:00 p.m.

595
00:31:59,000 --> 00:32:03,000
June GMT, as well as Julie, will
be continuing the chat there for

596
00:32:03,000 --> 00:32:06,500
any feedback about the podcast,
or maybe even some correction on

597
00:32:06,500 --> 00:32:09,500
anything that has been shared.
Do get in touch with me on

598
00:32:09,500 --> 00:32:14,100
Twitter, my DMs are open on the
handle, at the marketing, a new,

599
00:32:14,400 --> 00:32:16,900
or on LinkedIn.
We have a PVC chat Roundup

600
00:32:16,900 --> 00:32:19,100
group.
It would also be great for

601
00:32:19,100 --> 00:32:21,400
long-standing, a brand new
listeners, to give the podcast a

602
00:32:21,400 --> 00:32:23,500
rating or review.
You just go to the link,

603
00:32:23,500 --> 00:32:28,600
tree.com /p P c-- chat on the
score round up, you will be able

604
00:32:28,600 --> 00:32:31,700
to get that.
Also exciting news in

605
00:32:31,700 --> 00:32:35,900
anticipation for PPC, live UK's
first year anniversary, that's

606
00:32:35,900 --> 00:32:40,200
happening on the 27th of July.
By three weeks before them.

607
00:32:40,200 --> 00:32:45,700
IE next week, Thursday on the
6th of July at 5:00 p.m.

608
00:32:45,700 --> 00:32:49,600
GMT, top p.m. eastern time,
we're going to be doing a free

609
00:32:49,600 --> 00:32:52,300
webinar.
Maybe, just go to the PPC live.

610
00:32:52,300 --> 00:32:55,200
UK LinkedIn page, and look at
our events.

611
00:32:55,500 --> 00:32:58,700
You'll be able to see this loads
of post about it.

612
00:32:58,700 --> 00:33:01,900
And yeah, I'll be reminding you
next week for a couple of days

613
00:33:01,900 --> 00:33:04,900
before the webinar to check it
out.

614
00:33:04,900 --> 00:33:07,600
We are going to have Indian
indoor pool ride.

615
00:33:07,600 --> 00:33:09,500
We're going to have Russell
Russell.

616
00:33:09,900 --> 00:33:12,300
So, two of our speakers are in
the pool, right?

617
00:33:12,300 --> 00:33:15,700
And Gemma Russell, two of our
speakers, two out of the four of

618
00:33:15,700 --> 00:33:20,300
our speakers to to clarify as
well as Jon Paula Larusso, who

619
00:33:20,300 --> 00:33:23,400
is the founder of add World
Experience, who are also one of

620
00:33:23,400 --> 00:33:26,100
our sponsors.
So excited with that amongst

621
00:33:26,100 --> 00:33:30,500
them, that is about 30 plus
years of paid media experience,

622
00:33:30,700 --> 00:33:33,700
that will be involved including
mine that's more like 40 years

623
00:33:33,700 --> 00:33:38,000
of experience in in and there's
going to be talking about aiga

624
00:33:38,200 --> 00:33:41,000
For and conversion tracking.
And you know how that is

625
00:33:41,000 --> 00:33:43,000
changing a lot.
Because those are the kind of

626
00:33:43,000 --> 00:33:45,100
topics we're going to be talking
about on the 27th.

627
00:33:45,100 --> 00:33:47,800
So join us.
Sorry for giving you confusing

628
00:33:47,800 --> 00:33:49,700
dates.
Join us next week.

629
00:33:49,700 --> 00:33:51,900
Thursday on the 6th of July for
the webinar.

630
00:33:51,900 --> 00:33:55,100
Go to our LinkedIn page.
To check that invent out because

631
00:33:55,100 --> 00:33:57,800
it's going to be a LinkedIn
livestream.

632
00:33:58,100 --> 00:34:00,900
Finally, for your campaigns and
businesses to Glide smoothly.

633
00:34:00,900 --> 00:34:03,700
There's a lot of hard work
needed beneath the surface, so

634
00:34:03,900 --> 00:34:06,500
keep this one's kicking by and
speak to you next week.