EP218 - Google Analytics 4 - Dealing with the Inevitable

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

2
00:00:03,800 --> 00:00:07,400
around up.
In today's episode, we have Judy

3
00:00:07,400 --> 00:00:12,200
taken us on a rollercoaster of a
topic on which is titled Google

4
00:00:12,200 --> 00:00:16,800
analytics for so ga for dealing
with the inevitable.

5
00:00:16,800 --> 00:00:19,700
So yeah, buckle up definitely.
She says buckle up.

6
00:00:19,700 --> 00:00:22,900
But yeah, I added the roller
coaster ride because we're all

7
00:00:22,900 --> 00:00:25,700
back and forth as to whether we
get it whether we understand it

8
00:00:25,700 --> 00:00:28,100
whether we set it up right,
whether we need to have set it

9
00:00:28,100 --> 00:00:32,500
up now or later, As as Google
announced earlier this year,

10
00:00:32,500 --> 00:00:36,500
it's going to be the usual, you
know, form of analytics.

11
00:00:36,500 --> 00:00:40,800
The universal added analytics is
going to be fully sunsetted by

12
00:00:40,800 --> 00:00:46,600
this time next year.
So about July 20, 23 and advice

13
00:00:46,600 --> 00:00:50,800
on the street, the word on the
street is that you should have

14
00:00:50,800 --> 00:00:55,600
already navigating an upgraded
to ga4 because you want to be

15
00:00:55,600 --> 00:00:58,500
able to see you and your data.
You want to be able to do that

16
00:00:58,500 --> 00:01:02,300
on an analysis.
Properly have you are running as

17
00:01:02,300 --> 00:01:07,700
well as ga4 so that you know,
you are confidently setup.

18
00:01:07,700 --> 00:01:11,200
And the right things are coming
through by the time you can't

19
00:01:11,200 --> 00:01:14,300
see any of the data that's being
pulled through in new a.

20
00:01:14,300 --> 00:01:17,600
So yeah, let's talk about that
and hope you enjoy.

21
00:01:26,500 --> 00:01:30,100
Hello and a warm, welcome to
this episode of the PTC, chat

22
00:01:30,100 --> 00:01:33,600
round up a podcast where I round
up the Twitter discussion that

23
00:01:33,600 --> 00:01:36,300
happens on Tuesdays at 5 p.m.
BST.

24
00:01:36,300 --> 00:01:40,100
So that's British summer time or
at 12 p.m. eastern time.

25
00:01:40,500 --> 00:01:43,200
I'm your host Anna on recording
here from my studio.

26
00:01:43,200 --> 00:01:48,700
Back in London, UK, if you were
here with me last week, I was in

27
00:01:48,700 --> 00:01:52,700
the The countryside of the UK
and a place called Woodford, a

28
00:01:52,700 --> 00:01:54,400
couple of hours outside of
London.

29
00:01:54,400 --> 00:01:58,200
But I am back in my comfortable,
London space, overlooking my

30
00:01:58,200 --> 00:02:02,000
garden, which I absolutely love.
And yeah, I use this platform to

31
00:02:02,000 --> 00:02:05,100
share, not just expert but also
my ideas and considered best

32
00:02:05,100 --> 00:02:07,900
practices about paid media and
the direction, the digital

33
00:02:07,900 --> 00:02:10,600
industry is going in.
So we want to keep up to date

34
00:02:10,600 --> 00:02:13,300
with my tips and tricks in the
industry, and get the latest on

35
00:02:13,300 --> 00:02:16,600
the podcast that has been called
your go to if you don't make it

36
00:02:16,600 --> 00:02:20,800
to the PPC chat live discussions
and Even if you do then, like,

37
00:02:20,800 --> 00:02:22,700
follow share and retweet on.
That's right.

38
00:02:22,700 --> 00:02:26,500
Twitter with my handle the
marketing, a new or join us on

39
00:02:26,500 --> 00:02:29,700
our LinkedIn group.
The PPC chat Roundup podcast.

40
00:02:29,800 --> 00:02:31,600
Yeah.
Just ask make a request to join

41
00:02:31,600 --> 00:02:34,300
and we'd love to have you there,
or if you're on Instagram.

42
00:02:34,300 --> 00:02:37,300
Why don't you check us out at
PPC, chat on the school, Round

43
00:02:37,300 --> 00:02:40,800
Up to get quotes, and Snippets
from our previous episodes.

44
00:02:41,200 --> 00:02:44,200
So we have Julie taking us on a
great topic.

45
00:02:44,200 --> 00:02:47,100
Again, talking about GTA4.
And this is one topic that I

46
00:02:47,108 --> 00:02:48,700
feel that we cannot be
discussed.

47
00:02:48,800 --> 00:02:52,500
Is enough because it's one of
those areas again that with as

48
00:02:52,500 --> 00:02:56,200
Google has been doing with us
this week, that keeps evolving

49
00:02:56,200 --> 00:02:59,800
again and again, and we have
quite a bit of time.

50
00:02:59,800 --> 00:03:02,100
I'd for this one time that I
would be saying very grateful

51
00:03:02,100 --> 00:03:07,200
for Google, giving us over a
year to prepare for the slap in

52
00:03:07,200 --> 00:03:10,400
the face.
Absolute sun set of universal

53
00:03:10,400 --> 00:03:15,100
analytics and a total switch to
ga4 and actually seeing some

54
00:03:15,100 --> 00:03:18,700
talk on the twittersphere and
just around the community about

55
00:03:18,900 --> 00:03:22,600
People are now thinking, what's
an option finally takes from,

56
00:03:22,600 --> 00:03:24,800
you know, Google analytics all
together and people are

57
00:03:24,800 --> 00:03:28,100
thinking, maybe we can use a
solution other than Google,

58
00:03:28,100 --> 00:03:31,600
Calendars analytics, but I don't
know how Bible that is.

59
00:03:32,500 --> 00:03:34,200
Anyway, we've got Julie going
on.

60
00:03:34,200 --> 00:03:36,600
Yeah, saying thank you for
joining me today.

61
00:03:36,600 --> 00:03:39,900
We are going to be talking about
GA for Google analytics for.

62
00:03:39,900 --> 00:03:41,800
I'm going to be saying, ga4
alone.

63
00:03:42,000 --> 00:03:44,000
Yeah.
And dealing with the inevitable.

64
00:03:44,000 --> 00:03:46,800
So buckle up cause it's sure to
be a lively one.

65
00:03:46,800 --> 00:03:48,400
But yeah.
First how are we doing?

66
00:03:48,400 --> 00:03:49,800
So yeah.
Yeah, nice little roll call.

67
00:03:49,800 --> 00:03:52,600
Again, we got Robert Brady
joining us saying, hey people

68
00:03:52,600 --> 00:03:55,100
see chat, I'll be mostly lucky
today, but it's a beautiful

69
00:03:55,100 --> 00:03:59,200
summer day in Idaho and I'm glad
to see you all here today.

70
00:03:59,500 --> 00:04:02,900
I'm Ali goes, I just yelled
potatoes when I saw your tweet,

71
00:04:03,000 --> 00:04:05,700
that is Idaho know what
potatoes.

72
00:04:05,700 --> 00:04:09,800
So that tells you how much I
know about Idaho, we do grow the

73
00:04:09,808 --> 00:04:11,700
best potatoes, very proud of
that.

74
00:04:11,700 --> 00:04:14,900
But there's a lot more going on
to, it's a big state without a

75
00:04:14,900 --> 00:04:17,700
lot of people.
So most people just haven't

76
00:04:17,700 --> 00:04:21,200
experienced it.
Unknown People from Idaho.

77
00:04:21,200 --> 00:04:24,900
Sorry, when I hear potato, I
think of the Irish and I'm not

78
00:04:25,100 --> 00:04:28,900
going to do the accent that I've
usually do around a very

79
00:04:29,200 --> 00:04:31,300
comfortable.
Irish friend of mine, who won't

80
00:04:31,300 --> 00:04:35,100
slap me by saying potato in the
Irish accent.

81
00:04:35,400 --> 00:04:37,300
So yeah, let's just leave it at
that, then.

82
00:04:37,300 --> 00:04:39,200
Gradually advice.
Yeah, joining us as well as a

83
00:04:39,200 --> 00:04:40,400
morning.
All not bad.

84
00:04:40,400 --> 00:04:42,900
Sonny with Cool Breeze.
Here on the island today.

85
00:04:43,200 --> 00:04:45,900
I'm a lie, of course, joins us.
And I'm feeling good today,

86
00:04:45,900 --> 00:04:49,300
wrapped up here, one of my
business reconnected With an old

87
00:04:49,300 --> 00:04:52,300
friend, got some audits to
finish and school starts.

88
00:04:52,300 --> 00:04:56,400
Soon, that sounds like an
exciting and and Lively trip

89
00:04:56,400 --> 00:04:58,400
there.
Yeah, before we get into the

90
00:04:58,400 --> 00:05:01,600
questions, I would also read out
Julie's, sa of sorts.

91
00:05:01,600 --> 00:05:04,800
She's goes.
This chat is intended for PPC,

92
00:05:04,800 --> 00:05:08,100
Professionals of all levels
especially when it comes to GA

93
00:05:08,100 --> 00:05:10,700
Force because no matter how new
you are, it's one of those

94
00:05:10,700 --> 00:05:15,300
things where I love it that we
spoke about this a few weeks ago

95
00:05:15,300 --> 00:05:19,600
about what really balances the
filled out for, That right now

96
00:05:19,600 --> 00:05:22,300
where the state of whether
you've been doing this for 12

97
00:05:22,300 --> 00:05:24,000
years or whether you've been
doing this for a couple of

98
00:05:24,000 --> 00:05:28,300
years, this is one area to you.
For that makes you go, we're all

99
00:05:28,300 --> 00:05:30,900
learning this together, you
know, that big whether you want

100
00:05:30,900 --> 00:05:33,000
to be doing paid search for a
few years, you could know

101
00:05:33,000 --> 00:05:36,200
something a lot better than
someone who's been doing this

102
00:05:36,200 --> 00:05:40,600
for 10, 20 years, kind of thing.
So, yeah, this is definitely one

103
00:05:40,600 --> 00:05:43,900
of those conversations that is
for PPC, Professionals of all

104
00:05:43,900 --> 00:05:45,400
levels.
She continues.

105
00:05:45,400 --> 00:05:48,100
If you have something you want
to share, please do we are a

106
00:05:48,100 --> 00:05:49,800
friendly and supportive.
Supportive Community.

107
00:05:49,800 --> 00:05:51,800
Please don't be afraid to
participate.

108
00:05:52,100 --> 00:05:55,900
Lurkers and are of course,
always welcome to.

109
00:05:56,800 --> 00:06:00,700
And yeah, she reminds us that we
have a handy PC acronyms page as

110
00:06:00,700 --> 00:06:03,600
I already have mentioned.
I'll be saying ga4 or lot in

111
00:06:03,600 --> 00:06:07,800
reference to Google analytics
for so yeah go check out

112
00:06:07,900 --> 00:06:11,900
official.
PPC chat.com /p p c hyphen

113
00:06:12,500 --> 00:06:17,100
acronym said the oh God not the
vertical one.

114
00:06:17,100 --> 00:06:19,600
This horizontal one that goes.
The middle so I'm not the

115
00:06:19,600 --> 00:06:22,900
underscore one.
The middle of course you can

116
00:06:22,900 --> 00:06:27,500
find out what people are talking
about and no one needs to know

117
00:06:27,700 --> 00:06:30,800
you looked it up.
So yeah, so you can order your

118
00:06:31,100 --> 00:06:34,200
homework, then doing.
Ron also joins us as well.

119
00:06:34,300 --> 00:06:35,800
Anyway, let's get into
questions.

120
00:06:36,300 --> 00:06:38,100
Julie takes us on with question
one going.

121
00:06:38,100 --> 00:06:40,600
Let's get started.
And this first question is, to

122
00:06:40,600 --> 00:06:43,500
get an idea of how many of us
are working on in GA for.

123
00:06:43,600 --> 00:06:47,400
Have you been working or trying
to work in Google analytics for

124
00:06:47,700 --> 00:06:49,300
GA for yet?
So, that's That's why I didn't

125
00:06:49,300 --> 00:06:52,900
really join live.
I looked a lot because not

126
00:06:52,900 --> 00:06:56,500
really whipping working on GTA4.
I of course I work at Marin

127
00:06:56,500 --> 00:06:59,600
software we have our own
platforms on our way of doing

128
00:06:59,600 --> 00:07:01,300
things.
Their we're trying to support a

129
00:07:01,300 --> 00:07:05,100
few clients who use Google
analytics by job is not in terms

130
00:07:05,100 --> 00:07:09,300
of analytics, is about the whole
paid search management as it

131
00:07:09,300 --> 00:07:11,700
were.
Daniel body responds to

132
00:07:11,700 --> 00:07:14,600
question, one saying we have
been working with our clients to

133
00:07:14,600 --> 00:07:17,100
on board to ga4.
They know it's something they

134
00:07:17,100 --> 00:07:20,600
have to do with which is half.
Battle Gear goes, it's harder to

135
00:07:20,600 --> 00:07:24,900
deploy than Universal analytics,
not sure how the new Google, one

136
00:07:24,900 --> 00:07:29,000
tag to rule them all is going to
play into this either.

137
00:07:29,300 --> 00:07:32,100
And yeah, we've got the
wonderful Genie who loves to

138
00:07:32,200 --> 00:07:34,600
join some of these chats and
really listens to us when we

139
00:07:34,600 --> 00:07:37,400
have bits of ranch.
She goes wanted to clarify.

140
00:07:37,400 --> 00:07:41,900
The nothing is changing as a
result of G stag dot JS,

141
00:07:41,900 --> 00:07:46,100
becoming the Google tag.
If you've got G stag in dot Js,

142
00:07:46,400 --> 00:07:48,600
Js installed.
There's no action to take.

143
00:07:48,700 --> 00:07:52,800
Take it's the same tag but
offers added functionality more

144
00:07:53,100 --> 00:07:57,000
hair and she gives a link which
I'll add to the recap.

145
00:07:57,300 --> 00:07:59,000
There are Thomas.
Also goes, is it?

146
00:07:59,000 --> 00:08:02,100
I feel so silly and thinking
that it's the same old thing.

147
00:08:02,100 --> 00:08:05,700
So yeah.
So is it going with was to Julie

148
00:08:05,700 --> 00:08:07,700
going?
It's harder to deploy, not sure.

149
00:08:07,700 --> 00:08:11,700
The Google one tag to rule them
all is going to play and that's

150
00:08:11,700 --> 00:08:13,800
Doug, our Thomas responding to
that going, is it?

151
00:08:13,800 --> 00:08:16,600
I feel so silly thinking.
That's the same thing that it's

152
00:08:16,600 --> 00:08:19,100
the same thing and the events
are so, Much more

153
00:08:19,100 --> 00:08:20,700
straightforward in their
language.

154
00:08:20,700 --> 00:08:23,900
No more trying to explain the
difference between a category

155
00:08:23,900 --> 00:08:28,000
tag and action.
Now that I'm on board, with

156
00:08:28,000 --> 00:08:31,000
Julia voice goes.
They'll Goods is funny because I

157
00:08:31,000 --> 00:08:34,700
find category and or tags so
Universal a taxonomy structure

158
00:08:34,700 --> 00:08:36,500
and yet.
So difficult for the average

159
00:08:36,500 --> 00:08:41,700
person to wrap their head around
CF, literally any WordPress site

160
00:08:42,000 --> 00:08:45,200
delivers goes think about it.
This way, conversational flow,

161
00:08:45,400 --> 00:08:48,600
has its own syntax and it's
usually pretty informal.

162
00:08:48,700 --> 00:08:51,500
Intuitive and contextual formal
language.

163
00:08:51,500 --> 00:08:54,700
Like instructions or programs
are the opposite so people can

164
00:08:54,700 --> 00:08:58,100
get it, but it's work instead of
intuition.

165
00:08:58,900 --> 00:09:01,000
Yep, I don't, I don't get that
either.

166
00:09:01,000 --> 00:09:04,000
I feel like I need to pose from
actually reading out that tweet

167
00:09:04,000 --> 00:09:06,100
and actually try to assimilate
that tweet.

168
00:09:06,200 --> 00:09:09,800
Probably I'll come back to that
later and then we have down

169
00:09:09,800 --> 00:09:11,100
Patterson responding to
question.

170
00:09:11,100 --> 00:09:14,300
One saying, I've dabbled in it
here and there not a fan

171
00:09:14,300 --> 00:09:17,400
personally, but I recognize that
I'm going to have to spend time

172
00:09:17,400 --> 00:09:20,600
getting used to it.
Either way Judy goes, yes, I

173
00:09:20,600 --> 00:09:24,300
have finally gotten all clients
to deploy Google analytics for

174
00:09:24,500 --> 00:09:26,800
on their site.
And I am trying to get better at

175
00:09:26,800 --> 00:09:31,700
working in it and malygos I have
to question ones in on like with

176
00:09:31,700 --> 00:09:34,600
most things that Google pushes
through this one.

177
00:09:34,600 --> 00:09:36,900
I'm probably considered an early
adopter.

178
00:09:36,900 --> 00:09:40,500
Well done in Mario for being
early on that one and then we

179
00:09:40,500 --> 00:09:42,100
got Julia voice responding
saying yes.

180
00:09:42,100 --> 00:09:45,400
Kind of one of my clients has it
installed by it's pretty in

181
00:09:45,400 --> 00:09:49,400
unintuitive and it's not a great
time of year to to put aside

182
00:09:49,400 --> 00:09:51,700
hours to dive in a little busy
time.

183
00:09:51,700 --> 00:09:55,000
Jennifer respond saying yes, I
am struggling with some aspects

184
00:09:55,000 --> 00:09:58,100
of the reporting capabilities,
not doing what I need them to

185
00:09:58,100 --> 00:10:00,200
do, the things.
I'm really moves me about all

186
00:10:00,208 --> 00:10:01,900
these answers.
You got all the people that

187
00:10:01,900 --> 00:10:04,900
finding it difficult like, you
know, Julie trying to get the

188
00:10:04,900 --> 00:10:09,500
better work at it and Julia by
saying that prion unintuitive

189
00:10:09,600 --> 00:10:11,300
Jennifer going that she's
struggling with it.

190
00:10:11,300 --> 00:10:14,200
Those are the ones getting the
most likes and me for me, that

191
00:10:14,200 --> 00:10:16,700
indicates, there's loads of
people who are struggling with

192
00:10:16,700 --> 00:10:21,600
it, finding it on So yeah, ga4
do something about that or

193
00:10:21,600 --> 00:10:23,300
rather Google do something about
that.

194
00:10:23,700 --> 00:10:26,300
Show Nelly has will respond
saying, yes, have it setup and

195
00:10:26,300 --> 00:10:28,000
tracking conversions.
For all clients.

196
00:10:28,000 --> 00:10:31,400
I try to spend at least a little
time there every day.

197
00:10:31,400 --> 00:10:34,800
If I don't have to find a quick
answer and I'm slowly getting

198
00:10:34,800 --> 00:10:36,800
more comfortable.
Well done, Sean.

199
00:10:37,200 --> 00:10:39,900
We have Julie them responding to
giving question to seen if you

200
00:10:39,900 --> 00:10:44,100
have been working in GTA 4, how
has it been going for you

201
00:10:44,300 --> 00:10:47,900
generally and Melissa drugs
respond to question one saying

202
00:10:47,900 --> 00:10:52,100
I'm only Working with one client
who uses GA and they are still

203
00:10:52,100 --> 00:10:55,600
on you a, I'll be lurking.
So I can learn more about GA for

204
00:10:55,800 --> 00:10:56,700
Shane.
Let's plug.

205
00:10:56,700 --> 00:11:01,400
Marco has a whole series on GA
for latest installment hair.

206
00:11:01,400 --> 00:11:05,000
And that is a search engine know
Michael itself article and we

207
00:11:05,000 --> 00:11:08,700
will be sharing that I'll be
sharing that in tomorrow's paid

208
00:11:08,700 --> 00:11:12,300
search Association daily links.
So if you're subscribed you'll

209
00:11:12,300 --> 00:11:15,300
be seeing what that article is
Lauren's Chasers.

210
00:11:15,300 --> 00:11:17,500
Well response to question one
saying yes, being pushing

211
00:11:17,500 --> 00:11:20,300
clients to get it in.
Told and attached to their at

212
00:11:20,300 --> 00:11:23,300
accounts.
Reporting companies are making

213
00:11:23,300 --> 00:11:25,600
money.
Trying to get data for clients

214
00:11:25,600 --> 00:11:28,600
though, because it's very
different from Universal and

215
00:11:28,600 --> 00:11:32,600
things are hard to find or just
are not there as you can clock

216
00:11:32,600 --> 00:11:35,400
as well response to question one
saying, yes, we had most of our

217
00:11:35,400 --> 00:11:39,500
clients set up before July so
that they would be able to take

218
00:11:39,500 --> 00:11:41,200
advantage of year-over-year
data.

219
00:11:41,200 --> 00:11:44,400
When the switch is made it next
year, definitely has a learning

220
00:11:44,400 --> 00:11:48,500
curve but slowly getting more
comfortable down, Patterson.

221
00:11:48,600 --> 00:11:49,900
Vaughn's to question one as
well, saying.

222
00:11:49,900 --> 00:11:51,400
I see it.
As one of those.

223
00:11:51,400 --> 00:11:54,600
It's what we're going to be left
with so we better get used to

224
00:11:54,600 --> 00:11:56,400
it.
Kind of things everyone that

225
00:11:56,400 --> 00:12:01,600
uses GA should, at least get it
installed collecting data ASAP.

226
00:12:02,200 --> 00:12:04,700
Sean anything response to
question 2 saying it's bit

227
00:12:04,700 --> 00:12:08,300
frustrating and exciting.
It is pretty clunky but you can

228
00:12:08,300 --> 00:12:12,100
do a lot more customization and
create nicer-looking reports and

229
00:12:12,100 --> 00:12:15,300
graphs, no better feeling.
When you finally figure out how

230
00:12:15,300 --> 00:12:18,500
to get the data you want in the
right spot, but it can take

231
00:12:18,700 --> 00:12:22,300
While we have Julie responding
to question 2, saying I have

232
00:12:22,300 --> 00:12:24,900
found working in ga4 to be very
difficult.

233
00:12:25,300 --> 00:12:29,100
I'm trying to keep pushing as it
will be the only option before

234
00:12:29,100 --> 00:12:33,200
we know it but it's a struggle
and we have Julie advises.

235
00:12:33,200 --> 00:12:35,900
Well, responding to question 2
saying not.

236
00:12:35,900 --> 00:12:40,100
Well honestly, I'm so glad we
have an analytics, a team to

237
00:12:40,100 --> 00:12:43,400
support because the learning
curve for this thing is quite

238
00:12:43,400 --> 00:12:45,500
something.
It's going to take a Time

239
00:12:45,800 --> 00:12:48,500
investment to get going, not
really a plug.

240
00:12:48,600 --> 00:12:51,500
And play Vibe.
And then, we have Tim Halloran

241
00:12:51,500 --> 00:12:54,900
responding to question.
One saying, yes, switching to it

242
00:12:54,900 --> 00:12:58,500
on and off making sure goals are
tagged, and it's populating for

243
00:12:58,500 --> 00:13:00,900
clients.
So it's ready to question two.

244
00:13:00,900 --> 00:13:04,300
He goes URI is different, but I
don't have a positive or

245
00:13:04,300 --> 00:13:08,400
negative opinion of it yet.
I have Google on how to do

246
00:13:08,400 --> 00:13:09,700
things.
Whenever I'm looking for

247
00:13:09,700 --> 00:13:13,600
something specific Miley follow
goes, I wouldn't say I'm working

248
00:13:13,600 --> 00:13:17,700
in so much as exploring.
I was in a, you a five times

249
00:13:17,700 --> 00:13:21,600
yesterday for ODed and GA 40 of
those times.

250
00:13:21,600 --> 00:13:25,000
Oh, Molly should have tested.
Whether what you were seeing you

251
00:13:25,000 --> 00:13:26,800
as same as what you have seen in
do for the.

252
00:13:26,800 --> 00:13:29,000
Hey, maybe it's not, that's not
how it works.

253
00:13:29,200 --> 00:13:30,700
Doing Brown response to question
one.

254
00:13:30,700 --> 00:13:36,500
Seen a bit but nowhere near
enough at that needs to change a

255
00:13:36,500 --> 00:13:40,300
bit but nowhere near enough and
that needs to change.

256
00:13:40,400 --> 00:13:44,000
I dabble inside it at Best.
Damn Patterson goes, I still

257
00:13:44,000 --> 00:13:47,400
don't use it for actual
reporting thinking of making

258
00:13:47,400 --> 00:13:51,000
that switch in.
Re 2023, I need to spend more

259
00:13:51,000 --> 00:13:54,000
time with it.
I'm still very lost in there.

260
00:13:54,400 --> 00:13:56,800
Laurens Chase response to a
question to saying it has been

261
00:13:56,800 --> 00:13:59,700
going slow.
I have not been able to devote

262
00:13:59,700 --> 00:14:03,500
too much time to learn in beyond
the initial class I took with

263
00:14:03,500 --> 00:14:05,900
Bree and Orson Bree underscore t
on this.

264
00:14:05,900 --> 00:14:09,900
Call Anderson is the handle due
to a lot of client work working

265
00:14:09,900 --> 00:14:11,800
with.
I with analytics experts to

266
00:14:11,800 --> 00:14:16,500
develop reports with clients are
not having to slow down in

267
00:14:16,500 --> 00:14:19,000
response to a question to a
stolen car goes, it's Tough to

268
00:14:19,000 --> 00:14:21,700
be honest.
A lot of the reports / metrics

269
00:14:21,700 --> 00:14:25,900
Etc that we used in the you a
have been renamed changed or

270
00:14:25,900 --> 00:14:29,500
removed all together.
Any answer to question 2.

271
00:14:29,500 --> 00:14:32,500
So now, so yeah, we have Julie
taken us on to question 3,

272
00:14:32,500 --> 00:14:35,900
saying, let's get more specific.
What is, or are your biggest

273
00:14:35,900 --> 00:14:40,200
frustrations in working in
Google analytics, GA for even

274
00:14:40,200 --> 00:14:43,100
shontella response team.
It's not user friendly at all,

275
00:14:43,500 --> 00:14:46,500
and it seems like they wanted
the sidebar to look cleaner.

276
00:14:46,500 --> 00:14:50,600
So, they just shoved a bunch of
Ports on each page than

277
00:14:50,600 --> 00:14:53,800
Patterson respond saying recent
annoyance was instead of setting

278
00:14:53,800 --> 00:14:56,300
up a advanced segments to act
like a filter.

279
00:14:56,700 --> 00:15:00,700
I had to set up audiences that
start collecting from that point

280
00:15:00,700 --> 00:15:03,900
on really annoying.
I hope they are other ways to do

281
00:15:03,900 --> 00:15:06,500
it, but it's not intuitive at
all.

282
00:15:07,000 --> 00:15:10,400
Julie goes to question 3, where
to start everything is just

283
00:15:10,400 --> 00:15:12,800
harder and I have worked in
analytics.

284
00:15:12,800 --> 00:15:16,900
Since before Google purchased
urgent, which is now GA, it's

285
00:15:16,900 --> 00:15:22,800
built for Deb's, not Don devs.
Reporting's are a major PTA Pi t

286
00:15:22,800 --> 00:15:25,500
a pain in the ass.
I imagine, it's what she means

287
00:15:25,800 --> 00:15:28,300
to configure if you can find
them.

288
00:15:28,600 --> 00:15:31,500
As you continue setting up.
A conversion action is really

289
00:15:31,500 --> 00:15:34,100
not easy.
Sharing reports still can figure

290
00:15:34,100 --> 00:15:36,500
that out.
Creating dashboards for clients

291
00:15:36,500 --> 00:15:38,700
have.
No, it has a lot of

292
00:15:38,700 --> 00:15:43,300
customization capability but not
enough ready to go stuff and

293
00:15:43,300 --> 00:15:45,500
Glenn response to that.
Well Force wants to question.

294
00:15:45,500 --> 00:15:47,700
Three, same, yeah.
Point on sharing.

295
00:15:47,700 --> 00:15:50,600
I don't think go.
Well designed it so reports and

296
00:15:50,600 --> 00:15:53,100
annotations could have cross
user access.

297
00:15:53,100 --> 00:15:56,400
I think they are coaxing people
towards data studio.

298
00:15:56,400 --> 00:16:00,400
For this, televised goes and
data studio is unsupported.

299
00:16:00,400 --> 00:16:04,200
Get ready for snake-haired?
Julia because these unsupported

300
00:16:04,200 --> 00:16:08,500
but required conky tools.
Make my eyes burn like Angry

301
00:16:08,500 --> 00:16:12,200
Superman, who you do not want
angry Superman and yeah Julie

302
00:16:12,200 --> 00:16:13,600
goes.
Don't get me started on data

303
00:16:13,600 --> 00:16:15,700
Studio.
It's like a coding class project

304
00:16:15,700 --> 00:16:19,500
that got released as a finished
product by T gazillion dollar

305
00:16:19,500 --> 00:16:22,500
International cooperation?
Oh, wait, it's not like that.

306
00:16:22,700 --> 00:16:26,100
It is that.
Yeah, Melissa goes, very true.

307
00:16:26,100 --> 00:16:28,600
Something that you really need
some quite a bit of coding

308
00:16:28,600 --> 00:16:30,500
knowledge.
Actually figure out Jennifer

309
00:16:30,500 --> 00:16:32,300
response to question three
saying, the reporting

310
00:16:32,300 --> 00:16:35,900
capabilities are different and
challenging for what my client

311
00:16:35,900 --> 00:16:38,800
needs of /.
Has asked for not a fan of these

312
00:16:38,800 --> 00:16:41,700
reports trying to find a
solution with the new GA for

313
00:16:41,700 --> 00:16:44,900
capabilities for what they want
to see.

314
00:16:45,100 --> 00:16:47,900
Lawrence response to question 3
saying the lack of usability

315
00:16:47,900 --> 00:16:51,900
versus the Old platform, making
changes to something people have

316
00:16:51,900 --> 00:16:55,000
Decades of user experience with
has drastically.

317
00:16:55,000 --> 00:16:58,800
As they did was less than ideal
show Nelly response.

318
00:16:58,800 --> 00:17:00,400
This is exactly what I was
thinking.

319
00:17:00,400 --> 00:17:04,800
Could they not have kept some of
the reports that we all use to

320
00:17:04,800 --> 00:17:08,000
and then add customization
pieces to make the transition

321
00:17:08,000 --> 00:17:11,200
easier than goes feel like they
decided to rebuild it from the

322
00:17:11,200 --> 00:17:16,099
ground up, but I'm not clear on
why they felt that was necessary

323
00:17:16,400 --> 00:17:19,099
to Milan.
Ringo's pmags ga4, Integration

324
00:17:19,099 --> 00:17:24,000
of cookies or legal polarization
of user data in the name of

325
00:17:24,000 --> 00:17:27,400
privacy push to replace first
party via enhanced conversion

326
00:17:27,400 --> 00:17:32,500
modeled conversion data who let
conspiracy Tim out.

327
00:17:33,000 --> 00:17:36,000
Yeah, there's goes a Google is
probably using it for their own

328
00:17:36,000 --> 00:17:38,500
benefit as well.
I still have my tinfoil hat

329
00:17:38,500 --> 00:17:42,100
somewhere hair.
Yeah it's all about them

330
00:17:42,100 --> 00:17:44,900
profiting from this really
Google is a business.

331
00:17:44,900 --> 00:17:49,000
They're trying to do things to
embrace entertain a Two things.

332
00:17:49,200 --> 00:17:51,100
Melissa goes.
Y'all are scaring me.

333
00:17:51,200 --> 00:17:52,800
Haha.
Yeah, be afraid.

334
00:17:52,800 --> 00:17:56,800
Be very afraid of dentists and
goes and then some hollering

335
00:17:56,800 --> 00:17:59,700
response to question 3 saying I
did the tutorial prompts a

336
00:17:59,700 --> 00:18:03,100
couple times and assumed it
would teach GA fall to me as a

337
00:18:03,100 --> 00:18:06,100
you a user, but instead it
explained things to me.

338
00:18:06,100 --> 00:18:09,400
Like I was a high school student
and the terminology /.

339
00:18:09,400 --> 00:18:13,100
Definition used were different
than you a no correlations.

340
00:18:13,100 --> 00:18:15,800
Besides that Notch.
Besides that.

341
00:18:16,100 --> 00:18:18,200
Not sure yet.
Gosh.

342
00:18:18,600 --> 00:18:22,100
They're training system, not
great Ashton, Clark response to

343
00:18:22,100 --> 00:18:24,900
question 3 saying I didn't
secondary Dimensions to reports

344
00:18:24,900 --> 00:18:28,700
leads to some of the data being
hidden which limits are insights

345
00:18:28,900 --> 00:18:32,400
example, main Dimensions equals
two sessions Source or medium

346
00:18:32,700 --> 00:18:35,700
conversions because to 20.
But when you add in a session

347
00:18:35,700 --> 00:18:40,100
campaign, Dimension will only
show 15 conversions.

348
00:18:40,300 --> 00:18:42,100
How does that help Google
really?

349
00:18:42,600 --> 00:18:44,200
Tom Patterson response to
question three.

350
00:18:44,200 --> 00:18:47,200
Saying it also seems to take
forever for a change on a report

351
00:18:47,200 --> 00:18:48,400
to load.
So I start one.

352
00:18:48,500 --> 00:18:51,200
During if it froze.
But nope, it's just slow.

353
00:18:51,300 --> 00:18:53,300
I'm impatient.
Julia voice goes.

354
00:18:53,300 --> 00:18:55,000
I just don't know where to
begin.

355
00:18:55,000 --> 00:18:57,200
That's the main thing for
clients.

356
00:18:57,200 --> 00:18:59,900
Where it is installed.
I don't know, what the best

357
00:18:59,900 --> 00:19:05,300
five-step best first step is how
to map our goals over.

358
00:19:05,600 --> 00:19:08,500
Everything is a search and a
weird problem to solve.

359
00:19:08,500 --> 00:19:11,800
It's great for hourly billing, I
guess Miley response.

360
00:19:11,800 --> 00:19:15,700
It feels like a whole new
software and not an iteration of

361
00:19:15,700 --> 00:19:19,300
an existing platform.
Therefore I feel like Learning a

362
00:19:19,300 --> 00:19:22,700
whole new skill set.
My biggest frustration is not

363
00:19:22,700 --> 00:19:27,500
being able to intuitively find
my reports anymore.

364
00:19:27,600 --> 00:19:30,300
Lord, dr.
Thomas response to question.

365
00:19:30,300 --> 00:19:32,000
One.
Same been using J for four

366
00:19:32,000 --> 00:19:34,000
years.
It's been out for a long time.

367
00:19:34,200 --> 00:19:37,600
Lots to chew on with, has it
been around for years?

368
00:19:38,500 --> 00:19:41,500
Yeah.
And our toes dogs do in response

369
00:19:41,500 --> 00:19:44,800
to a question to same mindset,
shift are hard and I think the

370
00:19:44,808 --> 00:19:47,600
reporting being so different was
a major roadblock for everyone,

371
00:19:47,600 --> 00:19:51,000
but I think it's The right way
forward for lots of reasons.

372
00:19:51,600 --> 00:19:54,400
Even based of solve, some of
dogs answers from last week.

373
00:19:54,400 --> 00:19:56,600
I'm starting to think is he
getting paid by Google?

374
00:19:57,300 --> 00:20:00,300
This is do saying a lot of
things that Google like done pop

375
00:20:00,300 --> 00:20:01,600
singers.
I'm curious to hear your

376
00:20:01,600 --> 00:20:04,200
thoughts on why.
It's the right way forward care

377
00:20:04,200 --> 00:20:07,200
to elaborate.
If he did elaborate it was not

378
00:20:07,200 --> 00:20:09,500
in this thread.
I decide that he actually did

379
00:20:09,700 --> 00:20:13,700
elaborate on that and then we
have the actually giving an

380
00:20:13,700 --> 00:20:16,000
answer to question. 3.
Another answers question 3

381
00:20:16,000 --> 00:20:19,400
saying, I think there is a major
mismatch between Actual users of

382
00:20:19,400 --> 00:20:23,000
the platform and who the
platform was built for most PCS

383
00:20:23,000 --> 00:20:26,100
or business owners of marketing
or marketing.

384
00:20:26,100 --> 00:20:29,200
People have no interest in
things like bigquery, yes, I

385
00:20:29,200 --> 00:20:33,600
included we want easy to find
and configure reports to the

386
00:20:33,600 --> 00:20:37,400
advice goes well and for those
of us who do use bigquery, it's

387
00:20:37,400 --> 00:20:41,000
still just a data Lake.
There's a lot of work that goes

388
00:20:41,000 --> 00:20:44,600
into making sense of it all and
it's pricey Julie goes.

389
00:20:44,600 --> 00:20:48,300
Yes, that is part of my point to
bigquery is not accessible.

390
00:20:48,400 --> 00:20:52,400
Isabel equally to all.
So have it be put forward as

391
00:20:52,400 --> 00:20:57,400
just exported to be q and do X
is not satisfactory and then

392
00:20:57,400 --> 00:21:00,100
yeah we've got down passes and
goes I'm recognizing I'm going

393
00:21:00,100 --> 00:21:02,700
to have to get good with
bigquery because it's the only

394
00:21:02,700 --> 00:21:06,300
way I found to be able to still
access the old GA data.

395
00:21:06,300 --> 00:21:09,400
Once they shut it all down that
part and learn is probably my

396
00:21:09,400 --> 00:21:12,900
biggest annoyance with it or
Universe goes hard agree, and

397
00:21:12,900 --> 00:21:16,400
its exports to this pricey thing
and hire a team to analyze it,

398
00:21:16,400 --> 00:21:20,000
but don't worry.
It's your data. 80 then goes, I

399
00:21:20,000 --> 00:21:23,000
won't argue with that.
Bigquery is oriented for devs.

400
00:21:23,200 --> 00:21:26,900
I won't argue with you that
bigquery is oriented for devs,

401
00:21:26,900 --> 00:21:29,400
but let's remember that.
Google Deb's, largely interact,

402
00:21:29,400 --> 00:21:32,900
only with other Google devs.
They aren't marketers.

403
00:21:32,900 --> 00:21:36,100
Absolutely not, they'll our
Thomas response to question.

404
00:21:36,100 --> 00:21:38,900
Three, same, the biggest
frustration is moving everything

405
00:21:38,900 --> 00:21:43,200
around because we all had our go
to reports on diagnosis tools

406
00:21:43,200 --> 00:21:46,400
and they genuinely all changed
with GA for without a map.

407
00:21:46,400 --> 00:21:50,300
To say here's where the spur is.
There's where this report that

408
00:21:50,300 --> 00:21:53,300
you.
Yeah, you worked all day on.

409
00:21:53,500 --> 00:21:54,300
Did it goes?
Yeah.

410
00:21:54,400 --> 00:21:56,100
Yes, to this.
I was trying to find those

411
00:21:56,100 --> 00:22:00,500
things to create little cheat
sheets to post on PBC chat site

412
00:22:00,500 --> 00:22:03,200
and I got so mad.
I went on a tweeting rant.

413
00:22:03,200 --> 00:22:04,900
I love it with England's Glenn
goes.

414
00:22:04,900 --> 00:22:06,400
That's what we love about you
Julie.

415
00:22:06,400 --> 00:22:08,700
Yeah, we're right.
I'll just say, but I love it

416
00:22:08,700 --> 00:22:11,600
tweeting rods and down.
Goes this makes me want to laugh

417
00:22:11,600 --> 00:22:13,000
/ crying.
Yeah.

418
00:22:13,000 --> 00:22:15,100
Considering if Julie can't find
a solution.

419
00:22:15,800 --> 00:22:19,500
God help the rest of us.
Yeah, I've long Begged went down

420
00:22:19,500 --> 00:22:23,400
partisan goes on long ago.
He did give a response that he

421
00:22:23,400 --> 00:22:25,700
did.
Did an elaboration went down,

422
00:22:25,700 --> 00:22:28,200
Patterson goes and curious to
hear your thoughts on.

423
00:22:28,200 --> 00:22:30,600
What's the right way forward
care to elaborate dog are

424
00:22:30,600 --> 00:22:31,300
Thomas.
Good.

425
00:22:31,300 --> 00:22:35,100
I have long begged for a reason
to divorce our website and

426
00:22:35,100 --> 00:22:39,300
Analysis from the session and a
mythical visitor the data in

427
00:22:39,300 --> 00:22:41,500
you.
A has been so polluted that I

428
00:22:41,500 --> 00:22:44,400
think we underestimated the
amount of errors in the in

429
00:22:44,400 --> 00:22:49,100
analysis caused by it.
So he goes, so my thinking is

430
00:22:49,100 --> 00:22:52,700
that moving only to a meaningful
events model versus a traffic

431
00:22:52,800 --> 00:22:55,000
focused.
Model means that we can do what

432
00:22:55,000 --> 00:22:58,400
the platforms are.
Well, trying to do at least in

433
00:22:58,400 --> 00:23:01,400
their Comm Strat to optimize
towards the goal.

434
00:23:01,400 --> 00:23:05,900
Not the intermediate step 2.
Can't be succinctly, ever so

435
00:23:05,900 --> 00:23:08,900
many times.
I think we are trying to chase

436
00:23:08,900 --> 00:23:12,800
ghosts in the data looking for
trends that aren't really there

437
00:23:13,100 --> 00:23:16,000
in order to make it sound.
Like we are data-driven instead

438
00:23:16,000 --> 00:23:17,300
of Simply measuring.
What?

439
00:23:17,500 --> 00:23:22,000
Really they're 3y him just go in
there?

440
00:23:22,300 --> 00:23:24,200
Yes he's going on a raft, turn
around.

441
00:23:24,200 --> 00:23:28,300
So that's sweet, three of five
any so he continues.

442
00:23:28,300 --> 00:23:32,400
So, so to trying to tie this up
into things, I focus on, it's a

443
00:23:32,400 --> 00:23:36,100
lot easier to say well, we lose
a percentage of conversions

444
00:23:36,100 --> 00:23:40,500
tracked by users who don't agree
to tracking versus well, we lost

445
00:23:40,500 --> 00:23:44,200
a ton of traffic month, over
month because we implemented a

446
00:23:44,208 --> 00:23:49,600
basic consent pop-up for Earth.
And then he goes to 5 out of 5.

447
00:23:49,600 --> 00:23:53,900
So when I talk about the right
way, it's on doing so much work,

448
00:23:53,900 --> 00:23:57,000
that we've learnt and taught our
clients to care about.

449
00:23:57,000 --> 00:24:00,200
But I think it's more accurate
with better, focus on what

450
00:24:00,200 --> 00:24:05,000
really matters to businesses and
with less junk filling the data.

451
00:24:05,400 --> 00:24:08,100
Yes, I think that maybe biggest
issues that it's going to be a

452
00:24:08,108 --> 00:24:11,900
learning curve, but the data
could be used for the end of the

453
00:24:11,908 --> 00:24:14,200
day.
We need to be measuring events

454
00:24:14,200 --> 00:24:16,700
right events where everybody's
like with data driven, the data

455
00:24:16,700 --> 00:24:19,600
driven, Actually at the end of
the day you should be, it should

456
00:24:19,600 --> 00:24:22,200
be about informing what the
customer is doing.

457
00:24:22,500 --> 00:24:26,000
We say that it data-driven so
much.

458
00:24:26,000 --> 00:24:29,600
Like if we're not talking about
customers, I get that we all

459
00:24:29,600 --> 00:24:34,700
looking at data but communities
arse nearly especially

460
00:24:34,700 --> 00:24:37,200
communities and knowing your
audience is going to be the

461
00:24:37,200 --> 00:24:41,000
backbone of the future.
Is the backbone of current state

462
00:24:41,000 --> 00:24:46,000
of affairs, even so even more.
So in the future, Glenn respond

463
00:24:46,000 --> 00:24:50,100
saying, love dogs phrase, better
focus on what really matters to

464
00:24:50,100 --> 00:24:51,500
businesses.
Absolutely.

465
00:24:51,500 --> 00:24:55,800
Yes, this is a wrenching change
for us, but we can use it to

466
00:24:55,800 --> 00:24:59,500
remold perceptions of what
analytical data gives us.

467
00:24:59,800 --> 00:25:03,400
Not pretty useful.
So yeah, it's not a pretty is

468
00:25:03,400 --> 00:25:06,000
about useful.
How Google is doing it is

469
00:25:06,000 --> 00:25:09,600
annoying but I think they are
doing the right thing.

470
00:25:09,800 --> 00:25:12,600
God don't quote me on that,
although it's now recorded, I

471
00:25:12,608 --> 00:25:17,300
might edit this out, who knows.
We have freezer Andrews, who

472
00:25:17,300 --> 00:25:18,900
goes?
Yeah, hey gang a little late to

473
00:25:18,900 --> 00:25:20,500
the party boy in response to
question.

474
00:25:20,500 --> 00:25:24,800
Three, he goes, I think just
like the large shift in UI is

475
00:25:24,800 --> 00:25:27,500
the shock for me.
Everything seems to just be

476
00:25:27,500 --> 00:25:30,400
stripped back and we'll take a
while to get used to.

477
00:25:30,400 --> 00:25:33,000
Yeah, I think, is that taking a
while and learning new stuff is

478
00:25:33,000 --> 00:25:36,900
what we annoyed with Julie goes.
It's kind of wild to that in UA

479
00:25:37,400 --> 00:25:40,300
G am in you a.
It had gotten to the point of

480
00:25:40,300 --> 00:25:42,000
asking.
It's a question in the natural

481
00:25:42,000 --> 00:25:45,800
language and it showed you data
or Repose j4 does Even have

482
00:25:45,800 --> 00:25:49,200
categories that feel logical to
Universal GA users.

483
00:25:49,200 --> 00:25:53,300
Even power users, Dan goes
definitely feels like a step

484
00:25:53,300 --> 00:25:56,500
back in this regard.
So yeah, it's the whole process

485
00:25:56,500 --> 00:25:59,900
of how things are can be done as
very much annoying.

486
00:25:59,900 --> 00:26:01,800
That's what I feel like I'm
getting here anyway.

487
00:26:02,300 --> 00:26:04,800
Julie Denver's gives us question
for going.

488
00:26:04,800 --> 00:26:07,700
Keep feel free to keep sharing
frustrations but let's look at

489
00:26:07,700 --> 00:26:10,100
the flipside.
To is there anything col?

490
00:26:10,100 --> 00:26:12,700
You found it in Google analytics
for and I think.

491
00:26:12,700 --> 00:26:14,700
Yeah.
Doug shouldn't answer this one.

492
00:26:14,700 --> 00:26:19,300
He's when his five-part answer
to it in terms of what how you

493
00:26:19,300 --> 00:26:22,300
why he thinks it is beneficial.
It's a good step forward.

494
00:26:22,600 --> 00:26:24,300
Glenn response, question,
forcing.

495
00:26:24,300 --> 00:26:26,900
I cannot say there is something
in the ga for you.

496
00:26:26,900 --> 00:26:30,400
I, I like but to be honest,
looking at the wider GA for

497
00:26:30,400 --> 00:26:35,000
platform accessible via bigquery
and data Studio.

498
00:26:35,000 --> 00:26:38,500
I like its ability to handle the
complexity of modern B2B

499
00:26:38,500 --> 00:26:43,300
marketing Stacks free response
saying the actual automatically

500
00:26:43,300 --> 00:26:47,500
creative predictive Dance has
been imported into your Google

501
00:26:47,500 --> 00:26:52,300
ads account. 7-Day.
Likely Turner's, your better get

502
00:26:52,300 --> 00:26:55,700
ready for wind back campaign.
That sounds cool.

503
00:26:57,000 --> 00:26:59,800
And we have some very short and
straightforward answers.

504
00:26:59,800 --> 00:27:02,500
It's a question form here.
We've got GTA Vice going.

505
00:27:03,000 --> 00:27:06,600
Quick hits from me but that's
due to not enough time to spend

506
00:27:06,600 --> 00:27:10,000
in other thing and Yahoo and
phrases.

507
00:27:10,000 --> 00:27:12,600
Put a main bear.
Damn, Patterson straight to the

508
00:27:12,600 --> 00:27:14,500
point.
Not yet Laurens Chase.

509
00:27:14,500 --> 00:27:18,500
Even straighter to the point?
No we've got John Eddie, give it

510
00:27:18,500 --> 00:27:21,500
a more detailed answer and I
have been able to create some

511
00:27:21,500 --> 00:27:26,400
cool custom reports that either
wouldn't have looked good or may

512
00:27:26,400 --> 00:27:30,800
have Been impossible in you a
but 99.9% of the time, I can

513
00:27:30,800 --> 00:27:35,000
find better or faster.
Answers in you a, Judy goes

514
00:27:35,000 --> 00:27:37,800
question for saying, I have not
yet uncovered, something really

515
00:27:37,800 --> 00:27:40,100
cooling.
J4, I hope to find something,

516
00:27:40,400 --> 00:27:43,900
but it is going to be a while,
until I can do what I've done in

517
00:27:43,900 --> 00:27:48,200
Universal analytics simply and
easily to have time to try other

518
00:27:48,200 --> 00:27:50,900
functions will report back when
/.

519
00:27:50,900 --> 00:27:54,800
If I find stuff though and she
continues to that saying, once I

520
00:27:54,800 --> 00:27:58,400
wrapped wrap my head around,
Customizing reports, I think

521
00:27:58,600 --> 00:28:01,000
there will probably be some cool
things in there.

522
00:28:01,000 --> 00:28:04,900
It's just a slog to get reports
that I used to just exist,

523
00:28:05,200 --> 00:28:08,200
Ashton Clark response to
question 14 overall, not really,

524
00:28:08,200 --> 00:28:12,100
really well that said, I am
interested in what Explorations

525
00:28:12,100 --> 00:28:15,700
and more customized reporting
might have to offer, just

526
00:28:15,700 --> 00:28:21,300
haven't had time to play around
with it in depth yet and we have

527
00:28:21,300 --> 00:28:24,800
Dylan online coming in late
winter, but I'll give you a few

528
00:28:24,800 --> 00:28:28,400
of his Hogs has started.
Question 1, he said being been

529
00:28:28,400 --> 00:28:30,900
working in, j4 lot more.
Recent people kind of wish I

530
00:28:30,900 --> 00:28:34,600
started earlier feel like I've
left it pretty late but the case

531
00:28:34,700 --> 00:28:38,200
ease of finding the information
I need has kept me on UEFA most

532
00:28:38,200 --> 00:28:41,900
of the part we have Fraser going
to answer a question.

533
00:28:41,900 --> 00:28:43,600
Forcing following the crowd hair
with a?

534
00:28:43,608 --> 00:28:47,800
No, I'm interested to see how it
develops over time, but it again

535
00:28:47,800 --> 00:28:52,000
feels like it's been rushed out
rather than educating users.

536
00:28:52,000 --> 00:28:55,500
First televised goes, I mean, if
you were a product manager for

537
00:28:55,500 --> 00:28:58,300
this, wouldn't you?
You tease some cool features and

538
00:28:58,300 --> 00:29:00,900
show how to build them with
tutorials.

539
00:29:01,100 --> 00:29:03,400
Make some buzz and lay out a
road map.

540
00:29:03,400 --> 00:29:07,900
I don't get it it's a cool tool
with a rollout made for us to

541
00:29:07,900 --> 00:29:10,100
hate.
Julie goes a lot of Dhaka the

542
00:29:10,100 --> 00:29:12,900
documentation as soon as you
have coding experience or that

543
00:29:12,900 --> 00:29:16,000
you mind works like a death to
phrase.

544
00:29:16,000 --> 00:29:18,200
It goes yes.
And even though we should know a

545
00:29:18,200 --> 00:29:22,300
little Korean B, it doesn't hurt
to know the basics.

546
00:29:22,400 --> 00:29:25,200
As much as my dad doesn't
believe it.

547
00:29:25,200 --> 00:29:28,400
We don't build websites.
So make it easy for the users

548
00:29:28,400 --> 00:29:30,200
guys.
Yes, I don't build websites and

549
00:29:30,208 --> 00:29:35,300
you know, I don't know how to
build websites so dr.

550
00:29:35,300 --> 00:29:37,700
Thomas time, response to
question forcing, I found the

551
00:29:37,700 --> 00:29:40,900
focus of conversions and revenue
really good in the and the

552
00:29:40,900 --> 00:29:44,800
default dashboards super useful
for clients who just want to log

553
00:29:44,800 --> 00:29:48,300
in and look really quickly.
I kind of love the concept of

554
00:29:48,300 --> 00:29:52,000
the report Builder, much less
need to pop something down to

555
00:29:52,000 --> 00:29:54,300
excel.
Okay, I am convinced dog is

556
00:29:54,300 --> 00:29:56,500
working for Google now, she's
someone check his LinkedIn.

557
00:29:56,600 --> 00:30:00,100
Mmm.
And then we have Judy going on

558
00:30:00,100 --> 00:30:03,000
to question, five, which is the
last question of today.

559
00:30:03,000 --> 00:30:05,900
Another short sweet set of
questions, although more than

560
00:30:05,900 --> 00:30:08,700
three more info.
But she goes, if you could

561
00:30:08,700 --> 00:30:12,600
provide direct feedback to the
Google analytics just last year,

562
00:30:12,600 --> 00:30:18,900
14, what would you say or share?
And I'm sure a lot today keeps

563
00:30:18,900 --> 00:30:20,500
going.
That is a reply to this tweet

564
00:30:20,500 --> 00:30:24,300
and then I click into it and I
don't see any replies Twitter,

565
00:30:24,300 --> 00:30:25,900
what's going on?
I was it tweetdeck, there's

566
00:30:25,900 --> 00:30:28,600
glitching on me.
We then have dug our Thomas

567
00:30:28,600 --> 00:30:29,900
responding to question five
years.

568
00:30:29,900 --> 00:30:34,400
And I think the biggest thing is
to solidify, what ga4 really

569
00:30:34,400 --> 00:30:36,200
means.
I've been trying to read between

570
00:30:36,200 --> 00:30:39,900
the lines to get to my thoughts.
But someone outright said the

571
00:30:39,900 --> 00:30:44,000
way I've been asked, how Shake
taught it is over, would go

572
00:30:44,000 --> 00:30:48,100
super far to me interesting.
The other thing is to really

573
00:30:48,100 --> 00:30:51,000
focus on how to content make it
seem.

574
00:30:51,000 --> 00:30:55,800
Like this isn't even a lateral
move show off the power of ga4

575
00:30:55,900 --> 00:31:00,200
get an Avinash.
Kaushik of ga4, to explain the

576
00:31:00,200 --> 00:31:03,600
basics and higher strategy.
Now, who is Avinash?

577
00:31:03,800 --> 00:31:07,700
Kaushik, I made to Google that
later during Bond response to

578
00:31:07,708 --> 00:31:09,400
question Tuesday.
And it's like learning a new

579
00:31:09,400 --> 00:31:12,000
sport, a lot of things I don't
know, or yet.

580
00:31:12,000 --> 00:31:14,700
Understand.
And I'm just someone who doesn't

581
00:31:14,700 --> 00:31:17,600
necessarily like sports.
So how about us dealing with

582
00:31:17,600 --> 00:31:19,500
that?
And it during pain response to

583
00:31:19,508 --> 00:31:22,300
question three saying, right
now, I don't love how different

584
00:31:22,300 --> 00:31:25,400
is but I'm sure that will pass
once I get used to the ends of

585
00:31:25,400 --> 00:31:28,500
interface, love that To attitude
during bound.

586
00:31:28,500 --> 00:31:31,300
Then continue the response to
question five saying make it

587
00:31:31,300 --> 00:31:35,400
easier to setup will be the big
things also don't make you a

588
00:31:35,400 --> 00:31:38,600
data disappear.
Yeah you know leave it there.

589
00:31:38,600 --> 00:31:43,000
Pause 2023 past 2024, I'd like
that Dylan online, response.

590
00:31:43,000 --> 00:31:46,100
Question forcing no.
But I've seen videos of other

591
00:31:46,100 --> 00:31:49,400
people doing cool things but
haven't implemented because they

592
00:31:49,400 --> 00:31:54,000
haven't applied to my clients.
And another interesting link GD.

593
00:31:54,000 --> 00:31:58,800
Shares is that there is a ga4
Certification program out.

594
00:31:58,900 --> 00:32:03,000
Now, Lord, I wonder what the
fill rate of that is.

595
00:32:03,000 --> 00:32:07,100
Obviously, we considering people
are finding this very hard still

596
00:32:07,100 --> 00:32:10,900
damn Patterson goes adding that
to my list to do this year,

597
00:32:10,900 --> 00:32:13,000
Robert Wilkins.
Yeah she has my emotion.

598
00:32:13,000 --> 00:32:16,100
I would fail miserably.
I need to learn it.

599
00:32:16,100 --> 00:32:18,800
Yeah I need to learn GA for the
first place before we can

600
00:32:18,800 --> 00:32:23,000
actually start doing
certifications about it.

601
00:32:23,100 --> 00:32:26,500
Yeah on that note I'll bring us
to the end of this.

602
00:32:26,700 --> 00:32:29,200
Chatter, do we have any
interesting?

603
00:32:29,200 --> 00:32:32,600
Post questions answers?
No, I think that is.

604
00:32:32,600 --> 00:32:35,700
Oh, John Keegan came in late.
But let's, let's give his answer

605
00:32:35,700 --> 00:32:37,600
to question five.
Whoever built.

606
00:32:37,600 --> 00:32:40,900
This clearly has no concept of
how marketers use the platform

607
00:32:40,900 --> 00:32:44,600
on a day-to-day basis.
It's lack, it lacks intuitive.

608
00:32:44,600 --> 00:32:47,100
NE sand is causing advertisers
to use.

609
00:32:47,100 --> 00:32:52,500
More time to find basic things
and yeah, Julie put in very nice

610
00:32:52,500 --> 00:32:55,700
gift going.
We're all in this together

611
00:32:55,700 --> 00:32:59,100
growing has said, you know, the
out flew by and everyone and

612
00:32:59,100 --> 00:33:02,300
thanking everyone for honest
views were all figuring this out

613
00:33:02,600 --> 00:33:05,600
and I got a cerebral workout
from it.

614
00:33:05,600 --> 00:33:08,900
Yeah, definitely cerebral work
out for me as well.

615
00:33:09,000 --> 00:33:12,200
Really interesting to see the
big sides of the pros and the

616
00:33:12,200 --> 00:33:16,900
cons because they are will be
Pros as much as we drag our feet

617
00:33:16,900 --> 00:33:20,500
in the ground thinking that they
would be no Pros, they are Pros.

618
00:33:20,500 --> 00:33:23,800
So yeah, I hope you enjoyed that
session of us to going through.

619
00:33:23,800 --> 00:33:28,000
Ga4, how are you finding it?
Yusei takes a new takeaways.

620
00:33:28,000 --> 00:33:29,800
They're all these things
familiar with you.

621
00:33:29,800 --> 00:33:33,300
Again, these kinds of, you know,
especially runs the the

622
00:33:33,300 --> 00:33:35,500
annoyances.
It's about remembering you're

623
00:33:35,500 --> 00:33:39,300
not alone in your frustrations.
And if you understood some of

624
00:33:39,300 --> 00:33:42,300
the things that we're struggling
with struggling with, why don't

625
00:33:42,300 --> 00:33:44,300
you share that with us,
especially when our Twitter

626
00:33:44,300 --> 00:33:47,700
spaces, chat on Thursday at 5:00
p.m.

627
00:33:47,700 --> 00:33:51,000
BST 12 p.m. eastern time.
So the kind of the same time

628
00:33:51,000 --> 00:33:54,300
that we have the live chat.
So, yeah, join us on Thursday,

629
00:33:54,300 --> 00:33:57,700
we've taken some great takeaways
and one To share that with us or

630
00:33:57,700 --> 00:34:01,000
just share a bit more of your
frustrations and a bit of the

631
00:34:01,000 --> 00:34:05,600
things that you wish that Google
had done better with a G8 for.

632
00:34:05,900 --> 00:34:08,199
So yeah, if you have any
feedback about the podcast and

633
00:34:08,199 --> 00:34:10,800
maybe even some corrections on
anything that has been shared,

634
00:34:10,800 --> 00:34:14,000
please get in touch with me on
Twitter, my DMs are open on my

635
00:34:14,000 --> 00:34:16,199
handle the marketing, a new, or
on LinkedIn.

636
00:34:16,199 --> 00:34:19,900
We have the PPC chat around up
group on there and we would love

637
00:34:19,900 --> 00:34:23,400
to have you join us on there, to
share your thoughts?

638
00:34:23,699 --> 00:34:26,300
It'll be great if you're a long
and stand long-standing member

639
00:34:26,300 --> 00:34:29,800
and Or a brand-new mr.
To give the podcast a rating or

640
00:34:29,800 --> 00:34:34,000
review is very easy to give a
rating on Spotify, just to go to

641
00:34:34,000 --> 00:34:39,900
L IM KT r .t e, /p p c--, chat
underscore Roundup, click on

642
00:34:39,900 --> 00:34:44,300
this, on the Spotify laying and
yo, yo yo get to my profile.

643
00:34:44,300 --> 00:34:47,000
And there's as literally, you
see the stars of how many people

644
00:34:47,000 --> 00:34:50,800
have rated so far and just add
yours love.

645
00:34:50,900 --> 00:34:54,300
That allow be a massive help to
give the indication to other

646
00:34:54,300 --> 00:34:56,300
people.
That this is a worthwhile.

647
00:34:56,500 --> 00:35:00,200
Podcast anyway, before I go I
just also want to do a little

648
00:35:00,200 --> 00:35:04,800
plug about the PPC live, UK
second event, that is happening

649
00:35:04,800 --> 00:35:09,600
on the 29th of September.
We have four amazing speakers,

650
00:35:09,900 --> 00:35:12,200
three, three speakers.
One is a first time speaker,

651
00:35:12,200 --> 00:35:15,400
another as a second time speaker
and we've got the amazing

652
00:35:15,400 --> 00:35:18,700
Crystal.
Carter who's ahead of SEO comes

653
00:35:18,800 --> 00:35:21,400
at wigs, but knows a lot about
PPC.

654
00:35:21,400 --> 00:35:25,400
So it would really be great to
get bridge that gap, between SEO

655
00:35:25,400 --> 00:35:28,400
and PPC.
And How let people understand

656
00:35:28,700 --> 00:35:32,900
how SEO can work understanding
SEO can really work well or paid

657
00:35:32,900 --> 00:35:36,900
search professional and the
headliner would be Rand fishkin.

658
00:35:36,900 --> 00:35:41,100
This amazing speaker, you know
Global founder he's found is

659
00:35:41,100 --> 00:35:44,400
parked or oh, that's an audience
research tool.

660
00:35:44,700 --> 00:35:48,800
So yeah September 29th, please
go get your tickets, just go to

661
00:35:48,800 --> 00:35:55,700
be it. .L y /p p c-- live at UK
cept scpt 22.

662
00:35:57,000 --> 00:35:59,900
So finally remember for your
campaigns and businesses to

663
00:35:59,900 --> 00:36:02,500
Glide smoothly, there's a lot of
hard work needed beneath the

664
00:36:02,500 --> 00:36:05,700
surface say, keep your swans
kicking by, and speak to you

665
00:36:05,700 --> 00:36:06,500
next week.