EP244 - GA4 - Figure It Out or Find An Alternative

1
00:00:00,900 --> 00:00:03,800
Hello, and welcome to this
week's episode of the PPC chat

2
00:00:03,800 --> 00:00:07,500
Roundup in today's episode.
We have the awesome Julie bikini

3
00:00:07,700 --> 00:00:11,100
taken us on the Helm of a
fantastic topic right now and we

4
00:00:11,100 --> 00:00:14,200
couldn't be talking enough about
it.

5
00:00:14,200 --> 00:00:19,400
It's Google analytics for so ga
for figuring it out or find an

6
00:00:19,400 --> 00:00:21,900
alternative.
So yeah, I saw it on a search

7
00:00:21,900 --> 00:00:25,200
engine land, being on search
engine lands, home page, there

8
00:00:25,200 --> 00:00:28,600
is a countdown they've got going
on if there's a hundred and

9
00:00:28,600 --> 00:00:34,100
twenty one days left, Right now
is 121 days. 21 hours, 55

10
00:00:34,100 --> 00:00:39,100
minutes, and 57 seconds to yeah.
Google analytics.

11
00:00:39,100 --> 00:00:43,500
You a is properly sunsetted and
you only have G A for to you.

12
00:00:43,500 --> 00:00:47,300
So yeah, we've got that amount
of time to talk about it.

13
00:00:47,300 --> 00:00:52,800
Figure it out and learn bigquery
and just realize how to properly

14
00:00:52,800 --> 00:00:55,200
use it.
I remember that there was a time

15
00:00:55,200 --> 00:00:59,100
where saying that you need to
have made sure that at least you

16
00:00:59,100 --> 00:01:04,500
started Migrating to the ga for
way of doing things like a year

17
00:01:04,500 --> 00:01:08,700
before so that you can have
like, a Year's worth of data and

18
00:01:08,708 --> 00:01:11,800
being able to do year-on-year
analysis when the you a

19
00:01:11,800 --> 00:01:15,100
sunsetted.
But from the sounds of how

20
00:01:15,100 --> 00:01:17,900
complicated, the communities
finding it and the frustrations

21
00:01:17,900 --> 00:01:21,900
people are talking about.
Yeah, it sounds like that that

22
00:01:21,900 --> 00:01:24,700
one-year Mark has gone by with a
lot of people still being

23
00:01:24,700 --> 00:01:28,700
frustrated and not quite
grasping properly ga4 yet.

24
00:01:28,700 --> 00:01:30,800
So yeah, we talked about that we
talked about Out the

25
00:01:31,000 --> 00:01:34,000
frustrations we are having what
we're using were Alternatives.

26
00:01:34,000 --> 00:01:38,300
We are possibly thinking of and
yeah hoping that we get through

27
00:01:38,300 --> 00:01:41,600
this next 121 days together and
sane.

28
00:01:41,700 --> 00:01:52,900
All right, let's go.
Hello and a warm, welcome to

29
00:01:52,900 --> 00:01:55,900
this episode of the PPC chat
Roundup a podcast way.

30
00:01:55,900 --> 00:01:58,700
I round up the Twitter
discussion that happens on

31
00:01:58,700 --> 00:02:00,800
Tuesdays at 5 p.m.
GMT.

32
00:02:01,100 --> 00:02:04,100
I'm your host, a new and I'm
recording from my studio Hair in

33
00:02:04,100 --> 00:02:07,200
London UK.
And I use this platform to

34
00:02:07,200 --> 00:02:10,699
share, not just expert but also
my ideas and considered best

35
00:02:10,699 --> 00:02:14,000
practices about paid medium, the
direction, the digital industry

36
00:02:14,000 --> 00:02:16,100
is going in.
So if you want to keep up to

37
00:02:16,100 --> 00:02:18,600
date with my tips and tricks in
the industry, and get the latest

38
00:02:18,600 --> 00:02:20,800
on the podcast that has been
called your go-to.

39
00:02:21,400 --> 00:02:23,700
If you do, make it to the PPC
chat live discussions.

40
00:02:23,700 --> 00:02:27,000
And even if you do then, like,
follow Sharon retweets on,

41
00:02:27,000 --> 00:02:29,200
that's right.
Twitter with my handle, the

42
00:02:29,200 --> 00:02:32,600
marketing, a new or join us on
our LinkedIn Group, which is the

43
00:02:32,600 --> 00:02:35,600
PPC chat Roundup.
Or if you're on Instagram, why

44
00:02:35,600 --> 00:02:40,000
don't you check us out at PPC,
chatter Round Up to PPC, chat

45
00:02:40,000 --> 00:02:44,300
underscore Roundup, even PVC
chat underscore, Round Up to get

46
00:02:44,300 --> 00:02:46,800
quotes, and Snippets from our
previous episodes.

47
00:02:47,200 --> 00:02:50,500
So, yeah, we have Julie taken us
on a great topic about Google

48
00:02:50,500 --> 00:02:54,700
analytics for For or ga4 as I'll
be referring it to from now on.

49
00:02:55,000 --> 00:02:58,500
And yeah, figuring it out or
find an alternative.

50
00:02:58,600 --> 00:03:02,500
But first, how we doing?
Diana joins us as well as Guild.

51
00:03:02,500 --> 00:03:04,700
Now we've got govind Singh.
Who is that?

52
00:03:04,700 --> 00:03:06,900
A new name in the group?
Julie, advice shoes.

53
00:03:06,900 --> 00:03:11,600
As a picture of a snowy morning.
Wow, everywhere is covered in

54
00:03:11,600 --> 00:03:13,700
snow and she's all the way in
Canada over there.

55
00:03:14,100 --> 00:03:15,800
And yeah, I'm sure got many
more.

56
00:03:15,800 --> 00:03:18,900
Why not web as well, joins as
well as actor and Weaver Minkoff

57
00:03:18,900 --> 00:03:22,900
and shown early many.
Excited to talk about their

58
00:03:22,900 --> 00:03:26,100
frustrations frustrations with
ga4, before we get to the

59
00:03:26,108 --> 00:03:28,600
questions.
This chat is intended for PPC,

60
00:03:28,600 --> 00:03:32,000
Professionals of all levels.
Julie says, if you have

61
00:03:32,000 --> 00:03:35,400
something you want to share,
please do we are friendly and

62
00:03:35,500 --> 00:03:38,100
supportive Community.
Please don't be afraid to

63
00:03:38,100 --> 00:03:41,100
participate.
Lurkers are of course, always

64
00:03:41,100 --> 00:03:45,000
welcome lurkers as well as
podcast, listeners as always.

65
00:03:45,400 --> 00:03:47,800
So yeah, let's get straight into
the questions.

66
00:03:47,800 --> 00:03:49,500
I know we all have thoughts on
ga4.

67
00:03:49,500 --> 00:03:51,200
So let's do it.
Question one.

68
00:03:51,300 --> 00:03:55,000
One is Google analytics for GA
for running on the sites that

69
00:03:55,000 --> 00:03:58,500
you are working with if not why
not and was it difficult to get

70
00:03:58,500 --> 00:04:04,700
it deployed and collecting data.
So and if not why not and if so

71
00:04:05,500 --> 00:04:07,900
was it difficult to get it
deployed and collecting data

72
00:04:08,200 --> 00:04:12,700
Rush goes setting ga4 is not an
issue but the data discrepancy

73
00:04:12,700 --> 00:04:15,700
between platforms and the lack
of support is causing many

74
00:04:15,700 --> 00:04:19,100
headaches.
Custom CMS plus C DP and trying

75
00:04:19,100 --> 00:04:22,900
to get GA for working.
To nightmare looks like we need

76
00:04:22,900 --> 00:04:24,700
to update our acronyms page
there.

77
00:04:25,200 --> 00:04:28,100
Dan Alina response saying, we
have a deployed since February

78
00:04:28,200 --> 00:04:32,500
last year, another agency helped
us with it but I admit I still

79
00:04:32,500 --> 00:04:36,600
use you a more often Gil gonna
respond saying, deployed on all

80
00:04:36,600 --> 00:04:40,000
clients sites and I internal
sites implementation isn't

81
00:04:40,000 --> 00:04:43,200
difficult but we have seen
issues with incorrect data,

82
00:04:43,200 --> 00:04:45,800
links with Google ads, not all
conversions.

83
00:04:45,800 --> 00:04:49,100
Are accurately.
Imported lots of lost data

84
00:04:49,300 --> 00:04:52,200
compared to you a Ivan.
A sponsoring interesting.

85
00:04:52,200 --> 00:04:53,700
How about compared to Google
ads?

86
00:04:53,700 --> 00:04:56,300
Pixels govind response to a
question.

87
00:04:56,300 --> 00:04:58,400
Wanting ga4 is running on the
side since day.

88
00:04:58,400 --> 00:05:01,300
One of its release.
Never find installation hard

89
00:05:01,500 --> 00:05:03,900
with Google tag manager.
Good tip.

90
00:05:03,900 --> 00:05:07,000
There some responses in setup,
wasn't too bad with tags

91
00:05:07,000 --> 00:05:10,800
manager, but I haven't invested
time getting used to it and find

92
00:05:10,800 --> 00:05:15,100
myself constantly going to you a
for data instead.

93
00:05:15,100 --> 00:05:19,400
Yeah, so, people still relying
on you a even when j4 has been

94
00:05:19,400 --> 00:05:23,200
installed, Reva man, coverage,
I'm saying GTA 4 is on some

95
00:05:23,200 --> 00:05:27,100
sites and not others, but I'm
not sure that it's running with

96
00:05:27,100 --> 00:05:29,500
100% confidence on any of them
yet.

97
00:05:29,800 --> 00:05:32,100
Chanel irresponsible.
Yes, it's running and collecting

98
00:05:32,100 --> 00:05:35,300
data on all client sites.
It was not difficult to get it

99
00:05:35,300 --> 00:05:38,700
running and most sites which are
easy to set up conversions.

100
00:05:39,000 --> 00:05:43,200
There were a couple tricky sites
to set up events for the tough.

101
00:05:43,200 --> 00:05:47,000
Part is turning the data into a
usable report.

102
00:05:47,000 --> 00:05:49,500
Yeah, reporting still quite a
headache.

103
00:05:49,800 --> 00:05:53,300
We then have Julie herself.
Senior j4 is running on all the

104
00:05:53,300 --> 00:05:55,300
sides.
I'm involved with both clients

105
00:05:55,300 --> 00:05:58,300
and the ones I managed.
It was not easy to get it

106
00:05:58,300 --> 00:06:02,000
configured even as someone who
has been doing, analytics for 20

107
00:06:02,000 --> 00:06:05,400
plus years and who knows a
decent bit about coding and

108
00:06:05,400 --> 00:06:08,900
Google tag manager.
And then, Reverb mentions a

109
00:06:08,900 --> 00:06:12,000
psycho mantis in, I'm struggling
to understand why, or how it is

110
00:06:12,000 --> 00:06:14,200
acceptable.
That there would be a difference

111
00:06:14,200 --> 00:06:17,900
between ga4 and whatever the
actual back-end source of Truth

112
00:06:17,900 --> 00:06:20,700
is for the client.
And yeah, actor goes very good

113
00:06:20,700 --> 00:06:23,100
point p.
As well, we are yet.

114
00:06:23,100 --> 00:06:26,500
Not sure about the correct data
from GA for something I have

115
00:06:26,500 --> 00:06:31,100
noticed for most of our clients
and then we have that

116
00:06:31,100 --> 00:06:34,200
ill-advised as well saying only
on a couple it wasn't difficult

117
00:06:34,200 --> 00:06:38,500
to apply per se but the actual
setup took some time.

118
00:06:38,700 --> 00:06:41,400
Yeah Julie goes getting the code
on pages was not any more

119
00:06:41,400 --> 00:06:44,400
difficult than you.
A it gets hairy when you want to

120
00:06:44,800 --> 00:06:48,700
want it to see conversions and
actually pass back data to

121
00:06:48,700 --> 00:06:51,100
itself, Julie advice for getting
cozy.

122
00:06:51,200 --> 00:06:54,600
Yeah, quietly kind of glad that
many of my clients can't use GA

123
00:06:54,600 --> 00:06:57,300
at all.
It's been annoying until right

124
00:06:57,300 --> 00:06:58,200
now.
Yeah.

125
00:06:58,200 --> 00:07:02,300
Why not work with lucky and do
the rice goes in this one tiny?

126
00:07:02,300 --> 00:07:04,800
Incredibly specific way?
Yes.

127
00:07:05,300 --> 00:07:07,000
Yeah.
Tiny specific way.

128
00:07:07,000 --> 00:07:09,700
Why not web response to question
one saying, all our current

129
00:07:09,700 --> 00:07:12,900
clients have had at least a
minimal ga4 setup.

130
00:07:12,900 --> 00:07:15,900
Since last June, several are
still waiting to be fully

131
00:07:15,900 --> 00:07:19,500
integrated and then we have
Sophie responding to question.

132
00:07:19,500 --> 00:07:22,000
One saying the switch has been
very The cold as for the

133
00:07:22,000 --> 00:07:25,700
majority of our clients we have
had to rely on their web dev

134
00:07:25,700 --> 00:07:28,700
team to make the changes and she
continues.

135
00:07:28,700 --> 00:07:32,600
Not only have we been having to
inform our direct contacts as to

136
00:07:32,600 --> 00:07:35,400
why it is important and What
needs doing.

137
00:07:35,600 --> 00:07:39,200
But we've had to help the web or
death teams, a lot to make the

138
00:07:39,200 --> 00:07:41,900
changes.
So if your response continues,

139
00:07:41,900 --> 00:07:44,600
they're finally seeing we found
this to be very hard to do.

140
00:07:44,600 --> 00:07:48,100
Not only are we still learning
about it ourselves, but when

141
00:07:48,100 --> 00:07:51,100
you're not an expert in
something, it's hard to guy.

142
00:07:51,200 --> 00:07:54,600
Guide troubleshoot and instruct
someone else on what to do

143
00:07:54,600 --> 00:07:58,700
without having any access
yourself and actors as well

144
00:07:58,700 --> 00:07:59,900
response to question.
One thing.

145
00:07:59,900 --> 00:08:02,000
Absolutely thanks to the bomb
dropped.

146
00:08:02,000 --> 00:08:06,600
Last year of you, a sunset
eventually have migrated to ga4

147
00:08:06,600 --> 00:08:10,000
and for new account, starting
from birth, you a and g.

148
00:08:10,000 --> 00:08:12,600
A very, very much difficult for
migration.

149
00:08:12,600 --> 00:08:15,900
Especially for those who had
multiple locations different

150
00:08:15,900 --> 00:08:19,600
stores lead gen.
Julie, ran swiftly takes us on

151
00:08:19,600 --> 00:08:22,700
to question 2 saying, You
working in GA for for your

152
00:08:22,700 --> 00:08:26,200
analytics needs and Reporting.
If so how is it going?

153
00:08:26,200 --> 00:08:30,700
If not, why not Diana goes?
I used GA for the most for

154
00:08:30,700 --> 00:08:34,799
creating lots of new audiences.
I know the limit is of 100 so

155
00:08:34,799 --> 00:08:38,600
this cuts through my enthusiasm.
I also created some reports but

156
00:08:38,600 --> 00:08:42,200
more for learning purposes not
for delivery to anyone else

157
00:08:42,600 --> 00:08:46,300
Gilda respond saying yes because
we have to I'd say in general,

158
00:08:46,300 --> 00:08:49,200
it's okay but not perfect.
We have worked around a lot of

159
00:08:49,200 --> 00:08:53,400
problems by building.
Very extensive dashboards inside

160
00:08:53,400 --> 00:08:57,200
looker data Studio but it's
still not entirely perfect ga4gh

161
00:08:57,700 --> 00:09:01,800
for still miss attributes.
A lot actor, respond saying how

162
00:09:01,800 --> 00:09:04,200
much error rate as the general
Trend.

163
00:09:04,200 --> 00:09:07,900
Think have you noticed Gil, Gil
response bigger in EU than in.

164
00:09:07,900 --> 00:09:10,700
U.s. we are seeing upwards of
40% of conversions,

165
00:09:10,700 --> 00:09:14,600
misattributed to direct in EU
markets hard to say.

166
00:09:14,600 --> 00:09:18,800
In other markets, seems to vary
by account and I took as you

167
00:09:18,808 --> 00:09:21,000
have been working with Sweden,
Norway the Netherlands.

168
00:09:21,000 --> 00:09:23,800
I More from EU data is a
disaster.

169
00:09:24,000 --> 00:09:27,700
Then I wonder what it would look
like if you then go to like

170
00:09:27,800 --> 00:09:31,000
African countries because yeah,
I kind of imagine the data will

171
00:09:31,000 --> 00:09:35,300
be great there either we have
killed responding to a question

172
00:09:35,300 --> 00:09:39,100
to say no given up.
And and now use matomoto can't

173
00:09:39,100 --> 00:09:41,700
get page performance for
specific conversion.

174
00:09:41,700 --> 00:09:46,100
Type when importing into Data
Studio, why not web response in

175
00:09:46,100 --> 00:09:49,100
the bigger issues, clients
allocating the extra costs of

176
00:09:49,100 --> 00:09:52,400
time for setting up properly.
Some would lower budgets, just

177
00:09:52,400 --> 00:09:56,200
can't allocate the resources,
people or money to finish setup.

178
00:09:56,200 --> 00:09:59,100
When they have other things,
they want those resources

179
00:09:59,100 --> 00:10:02,100
working on convincing response
to a question to saying.

180
00:10:02,100 --> 00:10:04,600
Yes, trying.
But it's so much hard to get a

181
00:10:04,600 --> 00:10:08,100
report you need last week, I
wasted one to two hours to get a

182
00:10:08,108 --> 00:10:11,300
simple report visitor, reported
by hour of day.

183
00:10:11,300 --> 00:10:14,900
And day of week, still didn't
find the answer while it's just

184
00:10:14,900 --> 00:10:18,200
45 clicks work in Universal
analytics.

185
00:10:18,800 --> 00:10:21,000
Yeah, if it's just getting
harder.

186
00:10:21,200 --> 00:10:24,500
You know, Google supposed to
come up with a solution, not you

187
00:10:24,500 --> 00:10:26,600
tools to make things harder for
us.

188
00:10:26,600 --> 00:10:29,600
Anyway, device responds to
question 2 saying, it's

189
00:10:29,600 --> 00:10:33,100
incorporated into our local
reports where applicable but

190
00:10:33,100 --> 00:10:37,400
it's not the end-all or be.
Also, look at is now be the new

191
00:10:37,408 --> 00:10:41,000
name for data studio.
So watch out for that, Julia

192
00:10:41,000 --> 00:10:44,000
herself, respond saying I am
trying but it's so frustrating

193
00:10:44,000 --> 00:10:48,000
and unsatisfactory.
Then we have shown Ellie

194
00:10:48,000 --> 00:10:50,800
responding to question 2 saying
that I could really.

195
00:10:51,200 --> 00:10:53,900
Try to buy.
Take just take so much more time

196
00:10:53,900 --> 00:10:57,600
because of the suckiness to pull
data that you can easy find

197
00:10:57,600 --> 00:11:00,500
easily in you.
A I do have time scheduled in

198
00:11:00,500 --> 00:11:03,700
March, to work to build our
templates, which should help.

199
00:11:03,700 --> 00:11:06,800
Yeah, that's Today Show.
And I hope you started working

200
00:11:06,800 --> 00:11:10,200
on that.
Well, it's been much for an hour

201
00:11:10,200 --> 00:11:13,600
17 minutes.
So, I am definitely, I love it.

202
00:11:13,700 --> 00:11:15,700
It's much already.
I hope you started working on

203
00:11:15,700 --> 00:11:18,900
that.
Yeah, at 1:17 a.m. on March, in

204
00:11:18,900 --> 00:11:21,000
March.
Ignore that everybody except

205
00:11:21,200 --> 00:11:24,500
Wants to watch John had said,
and if she goes, please do share

206
00:11:24,500 --> 00:11:27,700
that once you get some templates
up, that will be super helpful.

207
00:11:27,700 --> 00:11:29,900
It would be great.
If we can create something like

208
00:11:29,900 --> 00:11:34,000
a template for PPC, chat
website, what's, what's a you

209
00:11:34,000 --> 00:11:35,600
Neptune Moon?
So that's Julie.

210
00:11:35,600 --> 00:11:39,000
She's referring to their Tim
Heller and response to question

211
00:11:39,000 --> 00:11:42,200
one saying, yes, we have it set
up for all our clients but since

212
00:11:42,200 --> 00:11:46,000
we're managing both you a and
for right now it's a lot of

213
00:11:46,000 --> 00:11:50,100
duplicating learnings happening
across teams and yes and in

214
00:11:50,100 --> 00:11:51,800
answer to question 2.
To Tim goes.

215
00:11:51,800 --> 00:11:54,200
Yes.
Both for some though, we only do

216
00:11:54,200 --> 00:11:56,200
ga4, it's difficult to be
honest.

217
00:11:56,400 --> 00:11:58,400
I'm having a tough time with it
still.

218
00:11:58,900 --> 00:12:01,800
So if you log in response to
question 2 scene, yes, I forced

219
00:12:01,800 --> 00:12:05,400
myself a few months ago to only
use Geo for when reporting or

220
00:12:05,400 --> 00:12:08,300
looking into things, still, not
as confident in there.

221
00:12:08,300 --> 00:12:13,500
As I am with you either, I know
clients are finding using GA for

222
00:12:13,600 --> 00:12:17,000
very difficult, Julie's
continues, a response to

223
00:12:17,000 --> 00:12:20,400
surfacing the learning curve
from where Mortals non-experts

224
00:12:20,400 --> 00:12:24,700
and Looks like Mount Everest,
Champs Elysee also responds to

225
00:12:24,700 --> 00:12:27,800
serve, he saying at some point,
I'm going to have to do this to

226
00:12:27,800 --> 00:12:31,000
myself and I'm not looking
forward to it, and so he goes,

227
00:12:31,000 --> 00:12:34,100
it was a very long reports day
my day.

228
00:12:34,100 --> 00:12:37,200
We just spent the whole day
trying to do reports in Google

229
00:12:37,200 --> 00:12:39,100
analytics, your eyes will go
cross-eyed.

230
00:12:39,100 --> 00:12:41,600
I'm sure why not web response to
question 2.

231
00:12:41,600 --> 00:12:44,700
Saying only says the simplest of
clients are using it for

232
00:12:44,700 --> 00:12:47,900
reporting and data right now.
Those with more complex needs

233
00:12:48,100 --> 00:12:50,900
are still evaluating the cost
resources on money.

234
00:12:51,300 --> 00:12:56,600
Of getting fully integrated or
using other analytics Riverman

235
00:12:56,600 --> 00:12:59,900
cough response to question to
say, no it's less user-friendly

236
00:12:59,900 --> 00:13:03,200
hard to get the info.
We need out and the data isn't

237
00:13:03,200 --> 00:13:06,500
very reliable so far.
It's a response saying, again,

238
00:13:06,500 --> 00:13:09,300
main issue is the complexity of
distilling, the reports.

239
00:13:09,300 --> 00:13:13,200
And also some skewed data
stakeholders, get hard time,

240
00:13:13,200 --> 00:13:16,900
working with go4 due to
misattribution, especially mid

241
00:13:17,000 --> 00:13:20,100
small owners, and then they
start getting concerned on

242
00:13:20,100 --> 00:13:23,100
things.
Going with conversions, things

243
00:13:23,100 --> 00:13:26,500
that are going with convergence
and we have Ashton Clark,

244
00:13:26,500 --> 00:13:29,000
joining the conversation and
even though he's laid, I do love

245
00:13:29,000 --> 00:13:30,500
his answer.
So I'm still going to go back to

246
00:13:30,500 --> 00:13:33,600
his answer to question.
One, where he goes, yes, G-Force

247
00:13:33,600 --> 00:13:36,200
been running from most of our
clients since July twenty

248
00:13:36,200 --> 00:13:39,600
twenty-two, because we wanted to
have year-on-year data when the

249
00:13:39,600 --> 00:13:42,100
switch from you a happens.
Absolutely.

250
00:13:42,100 --> 00:13:45,300
What I was saying earlier on,
Google analytics set up,

251
00:13:45,300 --> 00:13:48,400
maintenance isn't included in
our paid media Scopes so we

252
00:13:48,400 --> 00:13:52,500
mostly helped by providing
context and And documentation

253
00:13:52,800 --> 00:13:57,400
and it continues GA for creating
a ga for property.

254
00:13:57,400 --> 00:14:00,200
IE deployment, wasn't
particularly difficult.

255
00:14:00,300 --> 00:14:03,500
But data collection setting up
conversions, discrepancies

256
00:14:03,700 --> 00:14:07,800
between platforms, including
between different views or

257
00:14:07,800 --> 00:14:11,100
reports within GA and recreating
Legacy.

258
00:14:11,100 --> 00:14:16,400
You a reports has been more of a
struggle, we then going on to

259
00:14:16,400 --> 00:14:20,200
question. 3, Julie asks, have
you found the third party tool?

260
00:14:20,600 --> 00:14:24,200
Also That helps you use GA for
more effectively.

261
00:14:24,300 --> 00:14:26,500
Not a lot of answers for this
Diner.

262
00:14:26,500 --> 00:14:28,900
Linear response.
Not yes, curious what others are

263
00:14:28,900 --> 00:14:30,900
answering.
Maybe I find something good to

264
00:14:30,900 --> 00:14:35,300
look into Guild and respond
saying I'm testing pyrrhic so pi

265
00:14:35,300 --> 00:14:41,200
wik as a possible alternative
but it would be very difficult

266
00:14:41,200 --> 00:14:44,100
to convince our larger clients
to migrate data away from what

267
00:14:44,100 --> 00:14:46,400
they've been using for 20 plus
years.

268
00:14:46,700 --> 00:14:50,600
Other than that data studio all
the way only Band-Aid with found

269
00:14:50,600 --> 00:14:54,100
that, Makes it better.
Govind respond saying not trust.

270
00:14:54,100 --> 00:14:57,400
Use GA for effectively by in
order to get simple reports.

271
00:14:57,400 --> 00:15:02,400
I use statcounter stat counter.
It has been recommended there

272
00:15:02,800 --> 00:15:05,800
and the ideal egos I have a GF
will resources page on the PPC

273
00:15:05,800 --> 00:15:09,200
chat website will absolutely
linked or include any resources,

274
00:15:09,200 --> 00:15:12,700
you all come up with.
So yeah, go to official PPC,

275
00:15:12,700 --> 00:15:17,300
chat.com, forward slash, Google
hyphen analytics, Hyphen for

276
00:15:17,500 --> 00:15:21,000
hyphen G, A for hyphen
resources, so yeah.

277
00:15:21,100 --> 00:15:25,300
Go to analytics.
Official PPC, chat.com, forward,

278
00:15:25,300 --> 00:15:30,400
slash, Google analytics for GA
for resources, put in a hyphen

279
00:15:30,400 --> 00:15:33,700
between all those words there,
Ashton clock response to

280
00:15:33,700 --> 00:15:36,500
question 2 saying, yes, it's
been hit-or-miss.

281
00:15:36,800 --> 00:15:39,900
It's been difficult to recreate.
You a reports like Behavior

282
00:15:39,900 --> 00:15:42,100
flow.
It's also been fine for simpler.

283
00:15:42,100 --> 00:15:44,400
Reporting like adding
conversions.

284
00:15:44,400 --> 00:15:49,400
Tables to our looker Studio
Google data Studio reports, but

285
00:15:49,400 --> 00:15:53,300
the recent quarter limit is a
Major Payne now and we have

286
00:15:53,300 --> 00:15:56,100
Julie herself responding to
question three saying, I have

287
00:15:56,100 --> 00:15:59,900
not found a third party tool
that can make GA For Better Or

288
00:15:59,900 --> 00:16:03,700
easier to work in but I really
really want one.

289
00:16:03,800 --> 00:16:07,700
Yeah it's a goes me too.
We have John Keegan response and

290
00:16:07,700 --> 00:16:13,600
I found that analytics Mania by
feather row vicious so that's Fe

291
00:16:13,600 --> 00:16:19,700
d 0 R 0 V IC i-- us and that's
handle to have the best

292
00:16:19,700 --> 00:16:22,500
information out right?
But To love greater usage.

293
00:16:22,500 --> 00:16:26,200
Open to any and all suggestions
please.

294
00:16:26,500 --> 00:16:29,000
Why not web responsive since
look at isn't considered

295
00:16:29,000 --> 00:16:32,400
third-party no, we haven't yet.
Found any other third party tool

296
00:16:32,400 --> 00:16:35,600
that makes it easier to install
the framework and definitions

297
00:16:35,600 --> 00:16:38,200
have to exist within GA for
itself.

298
00:16:38,200 --> 00:16:40,200
First actor, response.
Question, 3.

299
00:16:40,200 --> 00:16:43,600
Seen in quest of something that
is easy accurate and working

300
00:16:43,800 --> 00:16:47,000
like a charm charm.
Meanwhile assertive of some

301
00:16:47,000 --> 00:16:50,200
options Plus first-party data, a
data scientist reports.

302
00:16:50,400 --> 00:16:53,100
Then she ask have you guys
worked with automations or

303
00:16:53,100 --> 00:16:57,400
something else to pull back and
data and manual upload to Google

304
00:16:57,500 --> 00:16:59,700
ads.
Yeah, that would be an

305
00:16:59,700 --> 00:17:03,000
interesting use case for that.
And we have Ashton Clark

306
00:17:03,000 --> 00:17:04,700
responding to question 3 c, not
really.

307
00:17:04,700 --> 00:17:07,900
We use Lucas studio for
reporting, which helps a little,

308
00:17:07,900 --> 00:17:11,400
but quota limits, and seemingly
random restrictions on which

309
00:17:11,400 --> 00:17:14,400
filters, or Dimensions or
excetera can be applied to a

310
00:17:14,400 --> 00:17:16,800
table or graph has made this
approach.

311
00:17:16,900 --> 00:17:20,900
Less helpful in recent months,
and Julie takes us on to

312
00:17:21,099 --> 00:17:25,400
Forcing, are you looking for at
alternative analytics tools?

313
00:17:25,400 --> 00:17:30,100
If so, which ones have you
checked out thoughts and actor

314
00:17:30,100 --> 00:17:32,000
goes?
I might tweak this to what their

315
00:17:32,000 --> 00:17:34,800
party tool can replace go4
without breaking the bank.

316
00:17:35,200 --> 00:17:38,500
Angela goes fair question.
The market is a ripe right now

317
00:17:38,500 --> 00:17:41,900
for an affordable alternative to
Google analytics, not an

318
00:17:41,900 --> 00:17:45,500
Enterprise level solution, but
want that lots of businesses

319
00:17:45,700 --> 00:17:50,500
will pay a monthly fee to use.
I would sell this idea of a $50

320
00:17:50,500 --> 00:17:52,900
per month.
'The final latex Gil respond

321
00:17:52,900 --> 00:17:54,700
saying.
I am looking at any tool that

322
00:17:54,700 --> 00:17:58,900
doesn't have data Vis like this
mess and he's yeah shows an

323
00:17:58,900 --> 00:18:02,400
image of a Google data Studio
since I think.

324
00:18:02,400 --> 00:18:05,800
I'm not sure Ivan response to
question for say not really GA

325
00:18:05,800 --> 00:18:08,100
for lacks in reporting
capabilities for now.

326
00:18:08,100 --> 00:18:12,000
They will fix it sooner or later
but ga4 is better in some ways

327
00:18:12,300 --> 00:18:15,700
event-based bottom line.
I don't think it's worth the

328
00:18:15,700 --> 00:18:19,900
time and effort for most Google
ads managers to look elsewhere.

329
00:18:19,900 --> 00:18:23,100
Well it depends.
On, if a solution good solution,

330
00:18:23,100 --> 00:18:26,000
alternative solution comes
about, Chanel response,

331
00:18:26,000 --> 00:18:27,400
question, forcing, I haven't
yet.

332
00:18:27,400 --> 00:18:30,700
I have wished or expected
Microsoft, or someone to just

333
00:18:30,700 --> 00:18:32,800
recreate, you a or similar
product.

334
00:18:33,000 --> 00:18:36,900
Imagine the instant adoption you
would get absolutely right.

335
00:18:36,900 --> 00:18:40,000
Julia, Vice go sign me up.
Go go and response.

336
00:18:40,000 --> 00:18:43,800
I would love being analytics.
Microsoft Clarity is awesome.

337
00:18:44,000 --> 00:18:48,800
I don't know why, be a wouldn't
be too, and Microsoft Clarity

338
00:18:49,100 --> 00:18:52,700
gives a big eye to this.
This and they are Go-Go's, hey

339
00:18:52,700 --> 00:18:57,800
clippings, Microsoft Clarity
coming, and so that's yet.

340
00:18:58,500 --> 00:19:02,800
Clipping KP gift that has been
shown by Microsoft Clarity.

341
00:19:03,200 --> 00:19:05,900
Who am I?
Cursed of clarity, free

342
00:19:05,900 --> 00:19:10,000
easy-to-use tool, captures.
New real people use your side

343
00:19:10,000 --> 00:19:11,900
captures.
How real people use your site

344
00:19:11,900 --> 00:19:15,300
session recordings using
integration heat Maps.

345
00:19:15,600 --> 00:19:18,900
Yeah, I think it's a little, is
it, are they a Microsoft

346
00:19:18,900 --> 00:19:20,600
company?
They've got to bank to be using

347
00:19:20,600 --> 00:19:21,600
Microsoft.
As a bright.

348
00:19:21,800 --> 00:19:25,400
Anyway, I digress delivers
response to question for saying

349
00:19:25,400 --> 00:19:27,600
yes.
Brand lift studies numerous

350
00:19:27,600 --> 00:19:32,000
reports third-party research.
There are Rumblings about Adobe

351
00:19:32,000 --> 00:19:35,400
but their products are pricey
and very complicated to use as

352
00:19:35,400 --> 00:19:38,300
well from all the clients who
have come to me about Adobe

353
00:19:38,800 --> 00:19:40,400
Ashton clock response to
question, forcing.

354
00:19:40,400 --> 00:19:42,900
We haven't really looked for
Alternatives at this point, but

355
00:19:42,900 --> 00:19:46,700
I would definitely be interested
to see what's out there and

356
00:19:46,700 --> 00:19:50,200
always open to try something new
Julia.

357
00:19:50,200 --> 00:19:53,400
Why Stan come Sorry, Jeannie
Jeannie continues with our

358
00:19:53,400 --> 00:19:56,400
response to Ashton because I'm
thinking of trying some on the

359
00:19:56,400 --> 00:19:58,900
PPC chat site.
So I can report back by want to

360
00:19:58,900 --> 00:20:02,100
do any that are super expensive
yet.

361
00:20:02,100 --> 00:20:05,000
Don't spend all the money in the
bank for that Genie actor

362
00:20:05,000 --> 00:20:09,100
response to question forcing not
yet yet looking for one for now,

363
00:20:09,100 --> 00:20:11,800
assertive assumptions, Plus
first-party data Plus data

364
00:20:11,800 --> 00:20:16,100
scientist back and reports Tim
hollering response to question

365
00:20:16,100 --> 00:20:18,300
forcing.
I've had clients use a few

366
00:20:18,300 --> 00:20:20,900
different ones in the past which
is where I've got.

367
00:20:21,000 --> 00:20:24,800
The most exposure outside of GA.
Most of them are suited for

368
00:20:24,800 --> 00:20:27,900
specific Industries, e-comm SAS,
Healthcare Etc.

369
00:20:27,900 --> 00:20:30,200
But I'm open to getting some
records.

370
00:20:30,200 --> 00:20:33,800
Definitely want to learn more.
John Keegan response to

371
00:20:33,800 --> 00:20:35,100
question.
Forcing yes.

372
00:20:35,100 --> 00:20:37,700
Adobe is borderline compliant
for hip-hop.

373
00:20:37,700 --> 00:20:42,300
So HIPAA but expensive there is
another one called periodic

374
00:20:42,300 --> 00:20:47,600
which someone mentioned earlier
so Pi wik that is gaining steam

375
00:20:47,700 --> 00:20:50,800
but nothing quite as intuitive
as ga-eun.

376
00:20:51,000 --> 00:20:54,400
You a and delivers go so
expensive and then Jam cake.

377
00:20:54,400 --> 00:20:57,200
And yeah, well with the Canadian
conversion rate system.

378
00:20:57,200 --> 00:21:00,800
I think you have to pay three
moose and a loony every other

379
00:21:00,800 --> 00:21:03,900
month for its ha ha that's
hilarious.

380
00:21:04,500 --> 00:21:06,200
I'm shocked.
I'm imagine all the audience

381
00:21:06,200 --> 00:21:09,000
will get that reference so if
you look in response to question

382
00:21:09,000 --> 00:21:12,500
3 saying I can't say that I've
come across anything to help but

383
00:21:12,500 --> 00:21:15,300
would be interested to hear of
any which people have found

384
00:21:15,600 --> 00:21:19,500
beneficial.
And then yeah, Julie takes us on

385
00:21:19,500 --> 00:21:22,900
to question five now that we've
Sufficiently annoyed that we are

386
00:21:22,900 --> 00:21:27,100
all sufficiently annoyed talking
about GA for she asked what is

387
00:21:27,100 --> 00:21:29,300
on your ga4 wish list where it
is?

388
00:21:29,300 --> 00:21:32,100
The only Google analytics
running date for this is

389
00:21:32,100 --> 00:21:35,800
currently July. 22, 23 Gil,
Golden Rose.

390
00:21:35,800 --> 00:21:39,800
Please give me more than three
grass, visualization options.

391
00:21:39,800 --> 00:21:44,400
When making a custom report, a
pile of toothpicks is not going

392
00:21:44,400 --> 00:21:47,200
to cut it.
Also some more Integrations with

393
00:21:47,200 --> 00:21:50,600
popular e-commerce platforms,
would be useful as well, Dino

394
00:21:50,600 --> 00:21:52,300
linear.
Goes as I've stated in previous

395
00:21:52,300 --> 00:21:56,400
tweet, it would be lovely, being
possible to segment data by

396
00:21:56,400 --> 00:21:59,800
Source or medium having more
reliable accurate data.

397
00:21:59,800 --> 00:22:03,400
These I think are the most
important, many things can be

398
00:22:03,400 --> 00:22:06,600
improved, and it would be
awesome to access things with

399
00:22:06,600 --> 00:22:10,600
lesser clicks kill response.
Question 5 seeing proper landing

400
00:22:10,600 --> 00:22:14,500
page reporting, out-of-the-box.
Exclude excluding query strings,

401
00:22:14,800 --> 00:22:18,000
and give the advertising tab,
something, it's particularly

402
00:22:18,000 --> 00:22:20,400
empty for me.
And we have Sophie Logan

403
00:22:20,400 --> 00:22:23,200
responded to Enforcing our
clients are happy with what they

404
00:22:23,200 --> 00:22:27,800
get through j4 and CRM.
So painful service is service is

405
00:22:27,800 --> 00:22:30,400
not something they'd be very
willing to do, which is

406
00:22:30,400 --> 00:22:33,700
understandable as they have what
they need for their day-to-day

407
00:22:33,700 --> 00:22:36,400
work.
But it's not always there for

408
00:22:36,400 --> 00:22:39,200
the marketing side.
We have, why not Webb responded

409
00:22:39,200 --> 00:22:42,200
to question for saying we have
gone as far as documenting the

410
00:22:42,200 --> 00:22:44,900
pricing of the other options for
our clients.

411
00:22:44,900 --> 00:22:49,200
Most of them are angry over the
costs but still considering do

412
00:22:49,200 --> 00:22:55,000
to man hours for MJ for that may
be inferior in the end and

413
00:22:55,000 --> 00:22:57,800
generally response to question
five saying usability in all

414
00:22:57,800 --> 00:23:00,200
caps, more better, default
reports.

415
00:23:00,200 --> 00:23:03,700
This should be fairly easy.
As I don't think they can get

416
00:23:03,700 --> 00:23:07,400
more much worse.
Did a human that uses the

417
00:23:07,400 --> 00:23:11,100
internet design?
Ga4, because I have my doubt, I

418
00:23:11,100 --> 00:23:14,000
wonder whether it actually meets
accessibility laws.

419
00:23:14,000 --> 00:23:17,000
I remember my friend earlier
this evening Rejoice, or Jack,

420
00:23:17,000 --> 00:23:20,200
who was saying about how
Beyonce's website because it was

421
00:23:20,200 --> 00:23:24,300
not accessible All to disabled
people people who are need to

422
00:23:24,300 --> 00:23:27,400
use alt text to, you know, read
through a page.

423
00:23:27,600 --> 00:23:32,000
Yeah, she got sued by that the
accessibility of a company that

424
00:23:32,100 --> 00:23:34,000
makes sure that sites are
accessible.

425
00:23:34,000 --> 00:23:36,900
So yeah, IGA for messing around
with that.

426
00:23:36,900 --> 00:23:37,800
Huh?
Interesting.

427
00:23:37,800 --> 00:23:38,900
Maybe that's one of the
lawsuits.

428
00:23:38,900 --> 00:23:43,800
Again, that's what one of the
losses lawsuits against them is

429
00:23:43,800 --> 00:23:46,300
about.
And then we have a delivers

430
00:23:46,300 --> 00:23:48,800
responded question facing
besides just simplifying.

431
00:23:48,800 --> 00:23:50,800
I want audiences to be easier to
pass.

432
00:23:50,900 --> 00:23:54,600
Pass pass back and understand
Google audience insights

433
00:23:54,600 --> 00:23:58,600
first-party audience insights
New Opportunities based on

434
00:23:58,600 --> 00:24:01,700
conversion data and then we have
John Keegan responding to

435
00:24:01,700 --> 00:24:03,900
question.
Five, same redesigned dashboard

436
00:24:03,900 --> 00:24:08,800
especially navigation to be more
intuitive like GA you a a

437
00:24:08,800 --> 00:24:12,900
clearly defined, a clearly
defined list of what is not

438
00:24:12,900 --> 00:24:15,500
being carried over from UA and
what is new?

439
00:24:15,900 --> 00:24:18,900
A better you a import system
net, net, net.

440
00:24:19,100 --> 00:24:24,600
Just be ga A yeah, and jelly.
Jelly responsive want to know a

441
00:24:24,608 --> 00:24:27,100
secret.
Think they think j4 is easier to

442
00:24:27,100 --> 00:24:30,800
navigate than you a?
Yeah, and don't John King cozy.

443
00:24:30,800 --> 00:24:32,800
I sorry, I just stopped by
coffee.

444
00:24:32,800 --> 00:24:35,300
Yeah, no definitely.
Not easy, Julie.

445
00:24:35,300 --> 00:24:37,900
Dan gives her wish list saying,
where to start in response to

446
00:24:37,900 --> 00:24:41,700
question five.
Yeah, make the UI easier for non

447
00:24:41,700 --> 00:24:43,800
deaths to use.
Take a look at the reports in

448
00:24:43,800 --> 00:24:47,000
Universal analytics and recreate
them dashboards.

449
00:24:47,300 --> 00:24:50,700
I'd even settle for a report
wizard at this point to let me

450
00:24:50,900 --> 00:24:54,200
Me tell it what I want and it
would build it.

451
00:24:54,200 --> 00:24:55,700
Imagine that.
That would be great.

452
00:24:56,000 --> 00:25:00,500
Sean McGinnis, I want to get it
making it McGinnis even I'm

453
00:25:00,500 --> 00:25:03,000
close here.
Our response are go back to

454
00:25:03,000 --> 00:25:06,400
allowing Channel level
customizations Channel, level

455
00:25:06,400 --> 00:25:09,500
customizations, Tim Holloman
respond saying I'll Echo the

456
00:25:09,500 --> 00:25:12,000
usability comment in response to
question five.

457
00:25:12,100 --> 00:25:15,500
It feels like it was made by
someone who has never used you a

458
00:25:15,500 --> 00:25:19,400
before reminds me of a mobile
app that decided to add a

459
00:25:19,400 --> 00:25:22,900
desktop functionality As an
afterthought to be honest.

460
00:25:23,000 --> 00:25:27,200
So usability 100% Ashton clock
response to question.

461
00:25:27,200 --> 00:25:30,200
Five saying, bring back the you
a behavior flow reports.

462
00:25:30,500 --> 00:25:34,000
I know that they are ways to
recreate it in GTA 4 but I

463
00:25:34,008 --> 00:25:38,200
haven't had success with that
yet and it's not as intuitive as

464
00:25:38,200 --> 00:25:42,500
you a, to me at least Julie then
goes your last question of the

465
00:25:42,500 --> 00:25:44,300
day.
Have you found any resources

466
00:25:44,600 --> 00:25:48,200
that have helped you in your
quest to actually use ga4?

467
00:25:49,000 --> 00:25:50,700
Yeah, before we get into that,
why?

468
00:25:50,900 --> 00:25:52,200
Why not?
Grab goes in response to

469
00:25:52,200 --> 00:25:54,900
question five saying?
Yeah, I'm thinking they need a

470
00:25:54,900 --> 00:25:59,000
lot more wizard for the
non-technical folks, which is

471
00:25:59,000 --> 00:26:02,200
minimum 50% of the end users of
GA for everyone.

472
00:26:02,500 --> 00:26:05,600
One of me, we have three to four
other users.

473
00:26:05,900 --> 00:26:07,600
There are Thomas, just gives a
comment about GA.

474
00:26:07,600 --> 00:26:11,600
Forcing my biggest thoughts on
G4 is that it was never meant as

475
00:26:11,600 --> 00:26:16,700
a replacement, but an evolution
of you a /, urchin, the entire

476
00:26:16,700 --> 00:26:20,700
concept is that you track KP is
not data.

477
00:26:21,000 --> 00:26:24,800
He continues like which like
wolf that's talked, all ask and

478
00:26:24,800 --> 00:26:27,700
unfair cetera but it's far more
intriguing than I had this

479
00:26:27,700 --> 00:26:28,800
report.
Where is it?

480
00:26:29,200 --> 00:26:31,800
And he continued to.
I just find it so funny when

481
00:26:31,800 --> 00:26:35,500
you, a was announced and UTM
wasn't passed in the Claire.

482
00:26:35,800 --> 00:26:38,800
There was a ton of Chicken
Little thing about it.

483
00:26:38,800 --> 00:26:43,500
Also, same story with every
update ever Riverbanks of goes,

484
00:26:43,500 --> 00:26:45,400
but the kpi still need to be
accurate.

485
00:26:45,400 --> 00:26:47,200
Know that goes.
Yeah, for sure.

486
00:26:47,200 --> 00:26:49,900
I'm not seeing huge differences
in event tracking, but maybe

487
00:26:49,900 --> 00:26:52,500
that's my limit.
Experience like I'm not working

488
00:26:52,500 --> 00:26:56,500
or thousand came monthly sites.
I'm working largely with small

489
00:26:56,500 --> 00:27:00,500
businesses so maybe great for
small businesses but yeah, not

490
00:27:00,500 --> 00:27:04,100
so great for the bigger ones and
we have Ashton clock responding

491
00:27:04,100 --> 00:27:06,000
to question.
Five saying, bring back the you

492
00:27:06,000 --> 00:27:09,300
a behavior flow report.
I know there are ways to

493
00:27:09,300 --> 00:27:12,600
recreate it in GA for by.
I haven't had success with that

494
00:27:12,600 --> 00:27:17,600
yet and it's not as intuitive as
you a, to me, at least.

495
00:27:17,900 --> 00:27:20,500
And then, yeah, we've got Julie,
green last question of the day.

496
00:27:20,500 --> 00:27:22,700
Have you?
Found any resources that have

497
00:27:22,700 --> 00:27:26,900
helped you in your quest to
actually use ga4, you're gonna

498
00:27:26,900 --> 00:27:29,800
respond saying lots of helpful
resources, lots of helpful

499
00:27:29,800 --> 00:27:33,900
resources, but only gets you to
the limits of ga4 at some point.

500
00:27:33,900 --> 00:27:36,300
It's not the resources that are
the problem.

501
00:27:36,300 --> 00:27:39,400
It's the tool itself beating a
dead horse at this point, but I

502
00:27:39,400 --> 00:27:43,900
don't think I'm exaggerating.
When I say G 4G a for is just a

503
00:27:43,900 --> 00:27:48,900
bad solution and why not website
in this vein, I don't find it to

504
00:27:48,900 --> 00:27:52,200
be a solution at all.
It does not solve any kind of

505
00:27:52,208 --> 00:27:54,300
pain points.
It is only adding to them.

506
00:27:54,300 --> 00:27:58,300
So we are just at deciding if
it's a necessary evil or not.

507
00:27:58,600 --> 00:28:00,600
Anjali goes.
Yeah, we need a non-enterprise

508
00:28:00,600 --> 00:28:04,500
priced alternative to put forth.
No, I would do it in a

509
00:28:04,500 --> 00:28:07,400
heartbeat, so yes, Bing anyone
else.

510
00:28:07,500 --> 00:28:10,800
Come on, give us an alternative
Diana Lena response saying they

511
00:28:10,800 --> 00:28:15,000
were YouTube channels of loves
data and analytics Mania, so

512
00:28:15,000 --> 00:28:19,800
loves data and analytics Mania
and even workshops from Google.

513
00:28:19,800 --> 00:28:25,700
I also follow Charles Farina.
So, Charles Farina on Twitter

514
00:28:25,700 --> 00:28:29,100
for this scope.
So, as mentioned earlier on the

515
00:28:29,100 --> 00:28:33,000
actually go, see, I have a page
on the PPC, chat site, where I'm

516
00:28:33,000 --> 00:28:36,600
collecting GA for resources.
I'll add any, you all share

517
00:28:36,600 --> 00:28:38,600
today.
To the page, in addition, to the

518
00:28:38,600 --> 00:28:41,400
recap.
Post-show Nelly response saying

519
00:28:41,400 --> 00:28:43,300
that.
Yeah, I have read some eBooks

520
00:28:43,300 --> 00:28:46,600
and did Bri, eat at Bri
underscore t on the school

521
00:28:46,600 --> 00:28:50,700
Anderson's course those are were
helpful, but definitely just

522
00:28:50,800 --> 00:28:52,900
Need to start getting my hands
dirty.

523
00:28:52,900 --> 00:28:56,100
There's nothing like just
getting the work done.

524
00:28:56,300 --> 00:28:58,500
Julie goes.
I did Breeze cause as well she's

525
00:28:58,500 --> 00:29:02,500
on the resources page.
So yeah, later people mentioning

526
00:29:02,500 --> 00:29:05,600
the resources and so if you look
in response to question five

527
00:29:05,600 --> 00:29:08,000
saying agreeing with a lot of
comments here, improved

528
00:29:08,000 --> 00:29:10,000
usability.
Everything just feels off

529
00:29:10,300 --> 00:29:12,400
unfinished and misplaced at the
moment.

530
00:29:12,400 --> 00:29:15,600
I know we will learn and adapt
but you would have make more

531
00:29:15,600 --> 00:29:19,600
sense for them to improve based
on all this feedback, they must

532
00:29:19,600 --> 00:29:23,100
be getting here.
Body listening to the feedback,

533
00:29:23,100 --> 00:29:26,800
that's the question, right?
We have Christian responding to

534
00:29:26,800 --> 00:29:30,400
question five saying, I wish to
return to you a and give us the

535
00:29:30,400 --> 00:29:33,500
option to use both.
Well, you can do that right now.

536
00:29:33,500 --> 00:29:36,700
So maybe for the future, Ashton
clock response saying in our

537
00:29:36,700 --> 00:29:39,100
teens, first effort to
understand and Implement you a

538
00:29:39,100 --> 00:29:43,300
for we all attended a webinar
and used resources from Krista

539
00:29:43,300 --> 00:29:47,300
sidon.
So that's Krista SE idn and

540
00:29:47,300 --> 00:29:52,800
that's how handle was helpful
and would and so yeah, great

541
00:29:52,800 --> 00:29:56,400
resources mentioned there, so
Bree e and distance of Bree

542
00:29:56,400 --> 00:29:59,400
underscore t on this call
Anderson and Krista side in

543
00:29:59,700 --> 00:30:03,000
there to people that you
definitely be following about

544
00:30:03,000 --> 00:30:06,400
anything ga4.
So yeah, we come to the end of

545
00:30:06,400 --> 00:30:09,300
that chat.
And it's definitely been an

546
00:30:09,300 --> 00:30:12,100
interesting one about our
frustrations with GA for what we

547
00:30:12,100 --> 00:30:16,100
wish for and resources that we
can use to help but someone like

548
00:30:16,100 --> 00:30:19,200
Guild mentioned, what really
struck out to me is the fact

549
00:30:19,200 --> 00:30:22,900
that no matter what the
resources Is sometimes you just

550
00:30:22,900 --> 00:30:25,600
come to the limitations.
It's the limitations of the

551
00:30:25,600 --> 00:30:27,200
tools.
That is the biggest problem.

552
00:30:27,500 --> 00:30:30,800
Not the fact that you do not
know necessarily what you are

553
00:30:30,800 --> 00:30:32,900
doing.
So, yeah, I hope you found that

554
00:30:32,900 --> 00:30:33,800
useful.
I hope again.

555
00:30:33,800 --> 00:30:35,800
This was one of those chats that
makes you feel like.

556
00:30:35,800 --> 00:30:38,700
Yes, I'm not alone with my
frustrations with ga4, I needed

557
00:30:38,700 --> 00:30:40,300
to be better.
Am I the only one?

558
00:30:40,600 --> 00:30:43,900
No, you are not the only one, if
you want to continue chatting

559
00:30:43,900 --> 00:30:46,500
about your frustrations with GA
for, please join us on,

560
00:30:46,500 --> 00:30:49,600
Thursday, on Twitter spaces.
I'm sure Julie will be leading a

561
00:30:49,600 --> 00:30:53,800
chat and very Entertaining.
I'm sure and vibrant chat about

562
00:30:53,800 --> 00:30:56,200
ga4 and our frustrations about
it.

563
00:30:56,400 --> 00:30:59,300
I hope you found this tutorial
useful, and yeah, if you want to

564
00:30:59,900 --> 00:31:03,500
take any, if you want to make
any corrections about it,

565
00:31:03,500 --> 00:31:07,100
anything that you want to say
about anything that I've said,

566
00:31:07,300 --> 00:31:08,800
please get in touch with me on
my Twitter.

567
00:31:08,800 --> 00:31:12,400
My DM's are open on my handle,
at the marketing, a new or

568
00:31:12,400 --> 00:31:14,300
joining on LinkedIn.
Check me out on LinkedIn.

569
00:31:14,300 --> 00:31:17,200
We have a PPC, chat Roundup
group up on there.

570
00:31:17,200 --> 00:31:20,500
And we'd love for you to join
and share your thoughts.

571
00:31:20,800 --> 00:31:23,800
It would also Be great to all
long-standing and brand new

572
00:31:23,800 --> 00:31:26,400
listeners to give the podcast a
review.

573
00:31:26,400 --> 00:31:29,600
It really helps with the growth
strategy of the podcast.

574
00:31:29,600 --> 00:31:32,400
You can do that on Spotify.
Yeah.

575
00:31:32,400 --> 00:31:36,900
By leaving a rating or leaving a
review on Apple as well,

576
00:31:36,900 --> 00:31:40,000
purchased it and more projects
and more if you just go to the

577
00:31:40,008 --> 00:31:45,900
link tree.com.
So, link2sd re e.com, /p P c--

578
00:31:45,900 --> 00:31:49,800
chat on the score round up, you
will be taken to their also,

579
00:31:49,800 --> 00:31:53,800
reminder.
We've got people PC live, UK the

580
00:31:53,800 --> 00:31:57,700
second event of our year of the
Year happening in March next

581
00:31:57,700 --> 00:32:00,100
month on the 30th.
We've got early bird tickets

582
00:32:00,300 --> 00:32:03,000
prices right now.
It's going to increase next

583
00:32:03,000 --> 00:32:04,300
week.
I'm going to give to the end of

584
00:32:04,300 --> 00:32:07,100
this week because I'm going on
holiday to holiday tomorrow.

585
00:32:07,100 --> 00:32:09,700
So I'm not going to settle that
up just yet.

586
00:32:09,800 --> 00:32:11,600
But yeah they're going to be
early bird.

587
00:32:11,600 --> 00:32:14,300
Tickets is going to the deadline
for that is going to be this

588
00:32:14,300 --> 00:32:17,200
way.
So buy your ticket before that

589
00:32:17,200 --> 00:32:21,900
price goes up next week.
Finally remember for your

590
00:32:21,900 --> 00:32:24,100
campaigns and businesses to
Glide smoothly.

591
00:32:24,100 --> 00:32:27,100
There's a lot of hard work
needed beneath the surface so

592
00:32:27,300 --> 00:32:29,800
keep this one's kicking by and
speak to you next week.