Meeting Title: [HOLD] Ellie <> Brainforge Check-in Date: 2025-08-22 Meeting participants: Alison Cromie, Zoran Selinger, Adam Kittleson, Robert Tseng
WEBVTT
1 00:02:51.860 ⇒ 00:02:52.660 Zoran Selinger: Hello?
2 00:02:54.790 ⇒ 00:02:56.000 Alison Cromie: Hello!
3 00:02:56.630 ⇒ 00:02:58.320 Zoran Selinger: Hi, Alison, nice to meet you.
4 00:02:59.090 ⇒ 00:03:05.869 Alison Cromie: Nice to meet you, too, and I apologize, I ended up having to drive home after my last meeting, so I’m just, …
5 00:03:06.100 ⇒ 00:03:10.369 Alison Cromie: Just about to get there, and we’ll switch over to a computer as soon as I can here.
6 00:03:11.180 ⇒ 00:03:13.030 Zoran Selinger: Sure, that’s… that’s fine.
7 00:03:13.030 ⇒ 00:03:14.100 Alison Cromie: No problem.
8 00:03:14.630 ⇒ 00:03:28.880 Alison Cromie: I did forward the invitation to my coworker, Adam, because he will also be critical in these kind of check-ins, so… yeah, he should be joining as well. If he hasn’t already, I’m on driving mode right now, so I can’t tell.
9 00:03:28.880 ⇒ 00:03:31.779 Zoran Selinger: Yeah, okay, okay. That’s fine, that’s fine.
10 00:03:33.970 ⇒ 00:03:36.589 Zoran Selinger: So, are we gonna wait for Adam, then?
11 00:03:37.440 ⇒ 00:03:40.949 Alison Cromie: Yeah, I think so. I am surprised he’s not here yet, so….
12 00:03:41.150 ⇒ 00:03:43.590 Zoran Selinger: Yeah, no, no, no, not yet, not yet.
13 00:03:47.370 ⇒ 00:03:48.679 Zoran Selinger: I think he’s joining.
14 00:03:49.480 ⇒ 00:03:50.220 Alison Cromie: Oh, great.
15 00:03:51.820 ⇒ 00:03:52.590 Adam Kittleson: Hey!
16 00:03:53.680 ⇒ 00:03:55.009 Zoran Selinger: Hi, nice to meet you.
17 00:03:55.010 ⇒ 00:03:56.489 Adam Kittleson: Nice to meet you, how you doing?
18 00:03:56.860 ⇒ 00:03:58.150 Zoran Selinger: Yeah, good, good.
19 00:03:58.530 ⇒ 00:04:05.009 Zoran Selinger: Good. A bit of a full day. Yeah, I feel that. 8PM here. Yeah.
20 00:04:05.010 ⇒ 00:04:05.490 Adam Kittleson: Oh, wow.
21 00:04:05.490 ⇒ 00:04:06.330 Zoran Selinger: Nothing like a full….
22 00:04:06.330 ⇒ 00:04:07.280 Alison Cromie: Friday.
23 00:04:07.280 ⇒ 00:04:07.840 Zoran Selinger: Yeah.
24 00:04:08.600 ⇒ 00:04:11.959 Zoran Selinger: Yeah, but it’s fine, it’s fine. …
25 00:04:12.550 ⇒ 00:04:14.849 Zoran Selinger: I don’t know if Robert is…
26 00:04:15.010 ⇒ 00:04:17.209 Zoran Selinger: Looks like Robert is joining.
27 00:04:20.019 ⇒ 00:04:22.949 Robert Tseng: Hey, everyone. Sorry I’m late.
28 00:04:22.950 ⇒ 00:04:24.250 Adam Kittleson: Hey, no worries.
29 00:04:24.540 ⇒ 00:04:24.860 Robert Tseng: You’re like.
30 00:04:24.860 ⇒ 00:04:25.730 Alison Cromie: Hey, Robert.
31 00:04:26.620 ⇒ 00:04:36.469 Robert Tseng: Zoom is taking longer and longer to, get in. Like, I… I joined at 1.59 PM, and it just took, like, 3 minutes to actually get in. I don’t understand.
32 00:04:36.470 ⇒ 00:04:37.500 Alison Cromie: Oh, wow.
33 00:04:39.630 ⇒ 00:04:41.709 Robert Tseng: Maybe I’m missing an update or something.
34 00:04:43.400 ⇒ 00:04:46.150 Alison Cromie: It was really fast from my phone, so….
35 00:04:47.530 ⇒ 00:05:07.320 Alison Cromie: And Robert, I’ll let you know, too, I apologize, I… I was not expecting to have to drive home after my last meeting, but I forgot my keycards at the office, so I am… will be home in, like, 5 minutes, but I’m here, and I brought Adam in to help with anything, especially if we needed to do anything visually. And he’s critical for these meetings anyway, so….
36 00:05:07.610 ⇒ 00:05:20.850 Robert Tseng: Sure. Yeah, well, yeah, no worries. I guess you all have already got acquainted a little bit, but I’ll just kind of reiterate a bit on our side. So, yeah, I mean, Zoran here is… he’s…
37 00:05:21.090 ⇒ 00:05:36.379 Robert Tseng: tagging, tagging tracking expert. I’m kind of on the amplitude side, so the two of us together are gonna kind of get everything you need, done. Yeah, I thank you for being really responsive on the Notion doc and some of our initial questions.
38 00:05:36.380 ⇒ 00:05:41.950 Robert Tseng: So, I know I just kind of sent a message, like, a few hours ago, and I think, …
39 00:05:42.190 ⇒ 00:05:45.489 Robert Tseng: Yeah, that should probably unblock us for this next step. Our goal is really.
40 00:05:45.490 ⇒ 00:05:46.000 Alison Cromie: Perfect.
41 00:05:46.270 ⇒ 00:05:59.970 Robert Tseng: ads quickly back up and running as fast as possible, and then I think we have a plan forward for GA4. I’ll let, Zoran kind of just talk through, like, his recommendation, and then…
42 00:06:00.080 ⇒ 00:06:04.650 Robert Tseng: Yeah, I think that’s really the main thing we wanted to just be on the same page about from this golf.
43 00:06:04.650 ⇒ 00:06:05.330 Alison Cromie: Awesome.
44 00:06:05.480 ⇒ 00:06:06.080 Robert Tseng: Yeah.
45 00:06:07.010 ⇒ 00:06:08.359 Zoran Selinger: Yeah, yeah, so…
46 00:06:08.930 ⇒ 00:06:20.890 Zoran Selinger: I was looking… I was looking into… into the setup. I was actually a little bit surprised to see that the only source of… of data streaming into that GA4 property is amplitude.
47 00:06:20.890 ⇒ 00:06:40.490 Zoran Selinger: So that’s kind of… that… that is… is uncommon. And, obviously, I was… I was looking at, kind of some recommendations, I was reading up on it, and it’s… it’s really uncommon. Like, I… I see… I see this, I, I’ve… I’ve seen no other examples of this.
48 00:06:40.570 ⇒ 00:06:46.230 Zoran Selinger: And, I was looking into, into the data, and really, we do see
49 00:06:46.330 ⇒ 00:06:51.169 Zoran Selinger: Those custom events that you filtered in the connector, they are streaming in.
50 00:06:51.330 ⇒ 00:06:57.619 Zoran Selinger: But no event properties are visible. Literally none. So we hit this….
51 00:06:57.620 ⇒ 00:06:59.079 Alison Cromie: And that’s what we’re missing.
52 00:06:59.080 ⇒ 00:07:12.850 Zoran Selinger: Yeah, we see, we see, correct mapping, of device ID into the client ID, that’s correct. And obviously, we see the event name. And that’s, that’s it.
53 00:07:12.920 ⇒ 00:07:20.160 Zoran Selinger: So there… there is absolutely no stitching, there. …
54 00:07:21.010 ⇒ 00:07:24.240 Zoran Selinger: And this is because we do not have
55 00:07:24.460 ⇒ 00:07:31.400 Zoran Selinger: Kind of the key events that we need for, at least for the interface, to show…
56 00:07:31.760 ⇒ 00:07:40.489 Zoran Selinger: to show the data in the form that we want it to. If you have streaming of the data into BigQuery, you can do
57 00:07:40.610 ⇒ 00:07:55.750 Zoran Selinger: all that work manually, right? You can do a little bit of stitching yourself, but if you want to see it in the interface, we really need… we need basically two things, because this is happening with… the background of this is the measurement protocol.
58 00:07:55.890 ⇒ 00:08:04.719 Zoran Selinger: Right, GA4 measurement protocol. We need… so, when the data comes in, it’s going to try to search for the session
59 00:08:05.100 ⇒ 00:08:07.619 Zoran Selinger: For the session data that is already in there.
60 00:08:07.670 ⇒ 00:08:27.480 Zoran Selinger: We do not have the first visit and session part events in that property at all. It has nothing to stitch to, and naturally, it won’t show you the session level dimensions and metrics that we want to see. And that’s your UTMs, that’s your campaign names, that’s your channels, and all that, yeah. So…
61 00:08:28.750 ⇒ 00:08:34.899 Zoran Selinger: This setup is… I’m guessing this is very intentional, that you only want those events in.
62 00:08:36.429 ⇒ 00:08:37.130 Zoran Selinger: induction.
63 00:08:37.130 ⇒ 00:08:42.259 Alison Cromie: Well, so we definitely want to bring in the session data. I think…
64 00:08:42.580 ⇒ 00:08:56.189 Alison Cromie: that’s where we… I agree with you, we need that information in there. You know, our goal, we can’t have the Google Pixel on our website, because it just gathers too much data. So, you know, our goal is to stream it from Amplitude.
65 00:08:56.420 ⇒ 00:08:59.620 Alison Cromie: In a way that’s, you know, HIPAA compliant.
66 00:09:00.070 ⇒ 00:09:01.020 Alison Cromie: …
67 00:09:01.200 ⇒ 00:09:15.529 Alison Cromie: So that our outside agencies and partners who are working with our franchisees can still see what’s happening without needing access to something like Amplitude, where we do have a lot of PHI involved.
68 00:09:15.910 ⇒ 00:09:17.010 Alison Cromie: …
69 00:09:17.210 ⇒ 00:09:31.370 Alison Cromie: So, if there are recommendations, if there are other events we need to be sending over in order to make this work, we are 100% open to that, as long as we’re excluding any, you know, PII that Google could then turn into PHI.
70 00:09:33.010 ⇒ 00:09:42.680 Zoran Selinger: Yeah, so we can maybe try sending that first visit and session start events as events from Amplitude.
71 00:09:42.750 ⇒ 00:09:54.400 Zoran Selinger: What will probably be easier as it… when it comes to compliance, what about the… for example, the GTM server side?
72 00:09:55.010 ⇒ 00:09:57.179 Zoran Selinger: Have you looked into that?
73 00:09:57.180 ⇒ 00:09:57.740 Alison Cromie: Nope!
74 00:09:59.000 ⇒ 00:09:59.519 Zoran Selinger: Because we can….
75 00:09:59.520 ⇒ 00:10:01.180 Alison Cromie: I tried to, but I…
76 00:10:01.590 ⇒ 00:10:08.050 Alison Cromie: I don’t think we had someone on our team who understood it enough to understand how that would work.
77 00:10:10.090 ⇒ 00:10:22.050 Zoran Selinger: So, I mean, this is basically… it’s your server, if we… if you do… if we do custom domain setup correctly, it sits on your domain, you’re sending
78 00:10:22.120 ⇒ 00:10:38.169 Zoran Selinger: events… you’re sending requests to your… from one page to another one of your pages, and of course, in the backend, what’s sending the event is the actual API. But we have full functionality from the server-side GTM.
79 00:10:38.580 ⇒ 00:10:39.630 Zoran Selinger: … Right.
80 00:10:39.750 ⇒ 00:10:46.049 Zoran Selinger: Yeah, so that one, that one should work. In terms of just having it on the client side.
81 00:10:46.420 ⇒ 00:10:53.069 Zoran Selinger: So just straight-up Google Tag. So I see you do have other properties that are doing that.
82 00:10:53.940 ⇒ 00:11:11.600 Alison Cromie: Yes, and because we’re trying not to interrupt the current marketing flow, but our goal is to, you know, turn off any pixels that we need to once we kind of have everything flowing the way we want it to.
83 00:11:12.330 ⇒ 00:11:20.259 Alison Cromie: So we’re kind of walking in this space where we are very non-compliant right now, and trying to get compliant as fast as we can.
84 00:11:20.630 ⇒ 00:11:30.730 Alison Cromie: So you will see things on there that are, you know, tags. We do have a tag manager in place, so we can, you know, we can use that, …
85 00:11:32.050 ⇒ 00:11:43.900 Alison Cromie: Yeah, so I… we’re open. If there’s a better way to do this, I think we are 100% interested in hearing about it, and as long as we’re remaining compliant, that is, you know, that’s the goal.
86 00:11:44.430 ⇒ 00:11:45.110 Zoran Selinger: Meow.
87 00:11:45.230 ⇒ 00:11:50.619 Zoran Selinger: I think it’s gonna be important for us to understand what being compliant really means.
88 00:11:50.810 ⇒ 00:11:56.869 Alison Cromie: What I’m trying to get to, best case scenario right now, the simplest thing that we could do.
89 00:11:56.910 ⇒ 00:12:10.829 Zoran Selinger: is, if that’s allowable, would be, let’s just send a page view event and nothing else. So we just initiate the GTAG, and PageView is the only thing that we send via the pixel.
90 00:12:13.350 ⇒ 00:12:16.640 Zoran Selinger: So, how far is that from compliant.
91 00:12:16.640 ⇒ 00:12:17.290 Alison Cromie: Yay.
92 00:12:17.290 ⇒ 00:12:23.230 Zoran Selinger: He’s not… Would that be… Can we get to that place? Would that be…
93 00:12:24.560 ⇒ 00:12:40.769 Zoran Selinger: Okay? So, we’re only just sending the pager event, and absolutely nothing else, because that will allow us to get that initial… that initialized session, that first visit of session start events that we need for the stitching.
94 00:12:41.160 ⇒ 00:12:42.430 Zoran Selinger: And that would be….
95 00:12:42.430 ⇒ 00:12:44.339 Alison Cromie: do that from Amplitude.
96 00:12:47.100 ⇒ 00:12:59.970 Zoran Selinger: So it might be possible to do that from amplitude. We need to figure out what else we need to collect, so there’s absolutely going to be amplitude customization on the collection side as well.
97 00:13:00.820 ⇒ 00:13:01.430 Alison Cromie: Right.
98 00:13:02.150 ⇒ 00:13:04.600 Zoran Selinger: what’s… what’s interesting… I mean.
99 00:13:05.420 ⇒ 00:13:10.170 Zoran Selinger: the question that comes to mind, if we do that with amplitude, how is… I mean.
100 00:13:11.310 ⇒ 00:13:14.920 Zoran Selinger: we are basically then doing the same thing as GA, and GA.
101 00:13:14.920 ⇒ 00:13:32.530 Alison Cromie: We are, but with Amplitude, we have a BAA in place, which makes it compliant, and it becomes basically first-party collection, whereas Google won’t sign a BAA, so collect… sending them anything that… so, like, knowing that someone
102 00:13:32.600 ⇒ 00:13:51.919 Alison Cromie: hit our… a very specific… knowing that a specific person, because they usually have IPs and all of that tracked as well, hit a page about mental health in our location page. I have been led to believe by legal counsel constitutes that combination of PHI.
103 00:13:52.690 ⇒ 00:13:55.529 Zoran Selinger: Alright, so that’s enough to be PHI.
104 00:13:56.220 ⇒ 00:13:56.920 Alison Cromie: Yep.
105 00:13:56.920 ⇒ 00:14:01.430 Zoran Selinger: Okay, okay, so… so server-side GTM.
106 00:14:01.610 ⇒ 00:14:07.800 Zoran Selinger: then… so, the problem here is the third party, that we are sending requests to Google servers.
107 00:14:07.800 ⇒ 00:14:08.420 Alison Cromie: Correct.
108 00:14:09.020 ⇒ 00:14:15.599 Zoran Selinger: This is… if we do, basically, what server-side GTM, it’s an instance on your GCP account.
109 00:14:16.430 ⇒ 00:14:17.050 Alison Cromie: Yep.
110 00:14:17.310 ⇒ 00:14:19.280 Zoran Selinger: It’s an… it’s an instance there.
111 00:14:19.630 ⇒ 00:14:26.369 Zoran Selinger: So… Usually, the best way to do this, to be in a first-party context.
112 00:14:26.510 ⇒ 00:14:30.290 Zoran Selinger: Is to… to do a little bit of routing, and have…
113 00:14:30.440 ⇒ 00:14:33.940 Zoran Selinger: Just a subdirectory on your own… on your domain.
114 00:14:34.420 ⇒ 00:14:42.199 Zoran Selinger: And this is where your tracking goes. So instead of going to the google.com collects, etc, it goes to.
115 00:14:42.200 ⇒ 00:14:42.770 Alison Cromie: Huh.
116 00:14:42.950 ⇒ 00:14:59.189 Zoran Selinger: your domain slash collect, and then all the parameters that you want to collect. So this would keep you in the first-party context. It does not leave… the data doesn’t leave your properties at all. It doesn’t go to a third party.
117 00:15:00.200 ⇒ 00:15:00.870 Alison Cromie: Okay.
118 00:15:01.220 ⇒ 00:15:13.420 Zoran Selinger: Yeah, so… but obviously, if… if we need to be very careful, I cannot give legal advice, so we need to… we need to… you need to check this, if that is….
119 00:15:13.420 ⇒ 00:15:13.890 Alison Cromie: Yeah.
120 00:15:13.890 ⇒ 00:15:16.150 Zoran Selinger: Right? This is your server, right?
121 00:15:16.260 ⇒ 00:15:18.909 Zoran Selinger: This is under your own domain.
122 00:15:19.960 ⇒ 00:15:21.020 Alison Cromie: Right, and so.
123 00:15:21.020 ⇒ 00:15:22.690 Zoran Selinger: Functionality on the server side.
124 00:15:23.250 ⇒ 00:15:36.539 Alison Cromie: Yep, so right now, if we look at server-side from a, like, where our website is hosted, right now it is in a non-compliant space. So, we are in the process of migrating it.
125 00:15:36.710 ⇒ 00:15:38.920 Alison Cromie: into Azure.
126 00:15:39.340 ⇒ 00:15:44.600 Alison Cromie: So, that will be our next step. We’re just not there right now.
127 00:15:44.840 ⇒ 00:15:46.190 Alison Cromie: …
128 00:15:47.770 ⇒ 00:15:55.140 Alison Cromie: So, that could be a possibility. We are kicking off that project on September, like, 3rd or 4th, I think.
129 00:15:55.600 ⇒ 00:16:01.549 Zoran Selinger: Sure, … just… so server-side GTM can be also configured on Azure.
130 00:16:02.270 ⇒ 00:16:04.579 Zoran Selinger: It can be instanced anywhere.
131 00:16:04.580 ⇒ 00:16:05.140 Alison Cromie: Okay.
132 00:16:05.290 ⇒ 00:16:15.480 Zoran Selinger: So Azure is one of the ones that we can, we can absolutely configure. So that would give us, basically, full GTM functionality,
133 00:16:15.860 ⇒ 00:16:17.760 Zoran Selinger: There, right?
134 00:16:18.030 ⇒ 00:16:19.480 Alison Cromie: Okay, alright.
135 00:16:19.480 ⇒ 00:16:23.089 Zoran Selinger: So, basically, we would still have a GTM,
136 00:16:23.270 ⇒ 00:16:39.379 Zoran Selinger: and a tag, or it doesn’t have to be a GTM, it can be… it can be a custom implementation with an embedded tag that would send your requests, but not to Google, but to your Azure server then. And that will then…
137 00:16:39.510 ⇒ 00:16:48.360 Zoran Selinger: we will then… that Azure server will function, like, fully, almost fully like GTM, and it just, sends the data….
138 00:16:48.360 ⇒ 00:16:51.910 Alison Cromie: Nothing ever gets transmitted to Google unless we tell it to.
139 00:16:51.910 ⇒ 00:17:05.560 Zoran Selinger: Yeah, of course, yes, we have full control over everything. We get those HTTP requests with all the data fields, and we do and filter however we want. We can do… in that GTM, we can do a lot as well.
140 00:17:05.560 ⇒ 00:17:07.320 Alison Cromie: Right. Right.
141 00:17:08.050 ⇒ 00:17:08.900 Alison Cromie: Okay.
142 00:17:10.050 ⇒ 00:17:13.160 Zoran Selinger: So that would be, that would be… but…
143 00:17:13.400 ⇒ 00:17:17.530 Zoran Selinger: Yeah, let’s… let’s check what we can… what we can and can’t do.
144 00:17:18.260 ⇒ 00:17:18.790 Alison Cromie: Yeah.
145 00:17:21.760 ⇒ 00:17:25.190 Zoran Selinger: Yeah, so if we have to do that with amplitude.
146 00:17:25.670 ⇒ 00:17:34.810 Zoran Selinger: like, still, we, we do, we do, we do a lot of the same thing, then there, with a lot of additional effort.
147 00:17:34.810 ⇒ 00:17:36.740 Alison Cromie: Gotcha, okay, got it.
148 00:17:38.430 ⇒ 00:17:45.500 Alison Cromie: So it’s not quite as simple as just starting to send that other event, that session start event, or…?
149 00:17:46.770 ⇒ 00:17:54.049 Zoran Selinger: if… so, if you’re just… oh, no, no, I mean, we need to figure out what parameters we need to have for.
150 00:17:55.280 ⇒ 00:18:00.410 Zoran Selinger: If we just look at the BigQuery and the raw data, we would easily stitch that.
151 00:18:00.800 ⇒ 00:18:08.629 Zoran Selinger: you know, using a little bit of SQL and all that. But to have all the functionality that Google Analytics
152 00:18:08.750 ⇒ 00:18:14.659 Zoran Selinger: the interface, you know, the audiences that you can create for Google Ads and all that stuff.
153 00:18:14.660 ⇒ 00:18:15.280 Alison Cromie: right.
154 00:18:15.280 ⇒ 00:18:17.119 Zoran Selinger: We, we need, we need to…
155 00:18:17.470 ⇒ 00:18:20.320 Zoran Selinger: To be exactly aligned to what they need.
156 00:18:21.090 ⇒ 00:18:24.389 Alison Cromie: Yeah, okay, so we’ll have to talk through that, because…
157 00:18:24.500 ⇒ 00:18:33.989 Alison Cromie: like, we want to be able to send audiences from Amplitude into ad accounts, which… that’s part of connecting the ad accounts directly.
158 00:18:34.100 ⇒ 00:18:44.199 Alison Cromie: … And then, the reason why we want to maintain a GA4 account is so that our
159 00:18:44.200 ⇒ 00:19:01.169 Alison Cromie: marketing partners can go in and see things like traffic to a location page, right? Like, that’s one of the main things. Adam, what else was on that? Do they include on their reports? It’s where the session sources. So, where the traffic is coming from.
160 00:19:01.330 ⇒ 00:19:11.370 Alison Cromie: And then… it… right now, their Google Ad accounts are all streaming from our current analytics account.
161 00:19:11.410 ⇒ 00:19:24.219 Alison Cromie: However, if we’re gonna connect their ad accounts directly to Amplitude, we should also be able to send them the conversion points that way as well. So they might… we might need that piece of the connectivity.
162 00:19:24.270 ⇒ 00:19:25.330 Alison Cromie: …
163 00:19:25.450 ⇒ 00:19:43.890 Alison Cromie: we’re not using Google Analytics to do any, like, major, dashboarding and reporting, and our agencies are only, tapping into it to bring into their tools. So, like, DataBox and that kind of thing. So…
164 00:19:43.920 ⇒ 00:19:55.520 Alison Cromie: It could be that the… the amount of information we need in there is pretty simple. We don’t need the full, like, experience in there.
165 00:19:55.520 ⇒ 00:19:56.740 Zoran Selinger: Sure.
166 00:19:57.080 ⇒ 00:19:58.380 Alison Cromie: I mean, and…
167 00:19:58.850 ⇒ 00:20:10.909 Alison Cromie: Yeah, I mean, that’s the only reason we’re even maintaining it, is because some of these agencies have their own tools that don’t tap into amplitude, right? So, …
168 00:20:11.820 ⇒ 00:20:12.750 Alison Cromie: Yeah.
169 00:20:14.150 ⇒ 00:20:17.899 Zoran Selinger: Yeah, yeah, we’ll have to, we’ll have to figure that out.
170 00:20:17.930 ⇒ 00:20:31.060 Zoran Selinger: But I think, yeah, server-side GTM might be the simplest solution here for now. But yeah, let us explore that a little bit more, and we’ll get back to you.
171 00:20:31.060 ⇒ 00:20:38.429 Zoran Selinger: As for… for Google Ads, I mean, I don’t see a reason why, yeah, we don’t need to…
172 00:20:38.430 ⇒ 00:20:49.930 Zoran Selinger: include the GA4 into that at all at the moment. I think sticking to the native integration is great. I know the API
173 00:20:49.930 ⇒ 00:21:09.169 Zoran Selinger: in the background is actually very simple. We need two pieces of information for that integration to work, so I don’t expect them, for example, that integration to break, or… it literally just needs Google Click ID and a correct timestamp, and that’s going to work, and the matching rate is 100%, and it’s…
174 00:21:09.170 ⇒ 00:21:19.660 Zoran Selinger: And I see you are collecting Google Click IDs correctly, and its mapping is great, so we just need to figure out why the connection is failing.
175 00:21:19.660 ⇒ 00:21:20.500 Alison Cromie: Yeah.
176 00:21:21.380 ⇒ 00:21:30.599 Zoran Selinger: D… The connection page just says that there’s some credentials formatting that’s wrong, …
177 00:21:31.040 ⇒ 00:21:38.810 Zoran Selinger: failed computing credential metadata. So it might be just the format of the file, the….
178 00:21:38.810 ⇒ 00:21:39.430 Alison Cromie: Okay.
179 00:21:39.430 ⇒ 00:21:46.620 Zoran Selinger: the key file, so… Right. Yeah, we… do we have access to your… to your GCP, project?
180 00:21:46.620 ⇒ 00:21:48.259 Robert Tseng: Yeah, it gave us, ….
181 00:21:48.260 ⇒ 00:21:49.080 Alison Cromie: Yes.
182 00:21:52.490 ⇒ 00:21:58.780 Robert Tseng: Yeah, I was just gonna say, I think… I think they gave it to us a couple hours ago, but we… it’s in the most recent Slack messages, right?
183 00:21:59.170 ⇒ 00:21:59.850 Zoran Selinger: Yeah.
184 00:21:59.850 ⇒ 00:22:13.849 Alison Cromie: Yeah, it came yesterday, I added you in there, and I gave the owner access, so you should have… if you’re finding you’re missing something, though, let me know, and I’ll go poke around and figure that out, but….
185 00:22:15.880 ⇒ 00:22:18.569 Zoran Selinger: So we’ll, we’ll log in and, …
186 00:22:19.000 ⇒ 00:22:26.529 Zoran Selinger: try to generate new credentials, we’ll upload that, and see how we can get in.
187 00:22:27.170 ⇒ 00:22:31.300 Alison Cromie: Is… Adam, is there a specific ad account that we should test this with?
188 00:22:31.950 ⇒ 00:22:36.400 Adam Kittleson: I mean, Jamie said we could test with his, if we wanted.
189 00:22:36.400 ⇒ 00:22:44.269 Alison Cromie: Okay, do you wanna… do you wanna confirm that and just let him know, and then provide, Zoran with, what account number that is?
190 00:22:44.400 ⇒ 00:22:44.900 Adam Kittleson: Yes.
191 00:22:44.900 ⇒ 00:22:47.180 Zoran Selinger: But the Orlando one? I mean, I see the.
192 00:22:47.180 ⇒ 00:22:49.760 Alison Cromie: Yeah, yeah, the Orlando one.
193 00:22:53.570 ⇒ 00:22:59.739 Zoran Selinger: Okay, good, because I see, I see, that, conversion, actually is set up there.
194 00:23:00.030 ⇒ 00:23:00.790 Alison Cromie: Yep.
195 00:23:00.990 ⇒ 00:23:05.880 Zoran Selinger: Yeah, and the setup is good, I just see, ….
196 00:23:05.880 ⇒ 00:23:06.450 Alison Cromie: Yeah.
197 00:23:06.450 ⇒ 00:23:13.290 Zoran Selinger: Data was never streaming in, so it just says inactive, so it was probably never active.
198 00:23:13.380 ⇒ 00:23:32.060 Zoran Selinger: I see no conversions loaded ever there, so, it’s probably… it’s probably just the connection just is not working, but I’m sure we can get that done. It should be pretty simple, we just… we just need that, a new key file for the service account. We should be good.
199 00:23:33.980 ⇒ 00:23:38.200 Zoran Selinger: I’m really optimistic there. You should be up and running.
200 00:23:38.200 ⇒ 00:23:42.210 Alison Cromie: pretty quickly. I don’t see as a reason for it to fail.
201 00:23:43.860 ⇒ 00:23:44.350 Zoran Selinger: No.
202 00:23:44.350 ⇒ 00:23:45.250 Alison Cromie: That’s amazing.
203 00:23:46.090 ⇒ 00:23:47.230 Zoran Selinger: That’s a simple one.
204 00:23:47.750 ⇒ 00:23:48.460 Zoran Selinger: …
205 00:23:49.160 ⇒ 00:24:04.219 Zoran Selinger: And that event in question, so that Marshall Linehan, events, so you… the volume of that, you expect us to… to… for data to start streaming in immediately, basically. It’s… we have enough volume…
206 00:24:04.550 ⇒ 00:24:06.090 Zoran Selinger: That we should see. I think so.
207 00:24:06.270 ⇒ 00:24:10.090 Zoran Selinger: Numbers going in almost immediately, right?
208 00:24:10.860 ⇒ 00:24:16.800 Alison Cromie: Yeah, Adam, remind me, that’s the… the, scheduled, an appointment event, right?
209 00:24:17.060 ⇒ 00:24:21.649 Adam Kittleson: Yeah, I’m pulling it up exactly what that is right now, …
210 00:24:25.000 ⇒ 00:24:33.290 Adam Kittleson: … it took away my description, that’s not good. … Yeah, that’s the appointment create.
211 00:24:34.190 ⇒ 00:24:35.499 Adam Kittleson: So yeah, there should be….
212 00:24:35.500 ⇒ 00:24:39.069 Alison Cromie: Perfect. Yes, so that is the primary… that is our main event.
213 00:24:39.070 ⇒ 00:24:51.930 Zoran Selinger: Oh, of course, okay. So we should be seeing it within a day or… within a day. We should be… Okay. We should be seeing events coming in, once we confirm this connection.
214 00:24:52.490 ⇒ 00:24:59.279 Zoran Selinger: And, yeah, I mean, from my experience, really, Google Fake ID is the only thing we need there.
215 00:24:59.980 ⇒ 00:25:05.199 Zoran Selinger: That is one-to-one matching, 100% matching rate.
216 00:25:06.760 ⇒ 00:25:11.629 Zoran Selinger: That attribution and all of that will be perfect, from my experience.
217 00:25:11.940 ⇒ 00:25:16.159 Zoran Selinger: I’ve done integrations with that a lot, so….
218 00:25:16.890 ⇒ 00:25:17.580 Alison Cromie: Awesome.
219 00:25:17.580 ⇒ 00:25:23.179 Zoran Selinger: Excellent. As long as we’re collecting all click IDs diligently and correctly, we’re good to go.
220 00:25:23.840 ⇒ 00:25:24.420 Alison Cromie: Right.
221 00:25:26.410 ⇒ 00:25:31.679 Adam Kittleson: I just got confirmation from Jamie, too, that he is all for us testing with his account, so….
222 00:25:31.680 ⇒ 00:25:35.020 Alison Cromie: Figured as much. Yeah.
223 00:25:44.140 ⇒ 00:25:46.940 Zoran Selinger: Yeah, I think that’s… Got it.
224 00:25:46.940 ⇒ 00:25:47.360 Alison Cromie: Awesome.
225 00:25:47.650 ⇒ 00:25:51.159 Zoran Selinger: From my side, I don’t know, Robert, if you have anything.
226 00:25:51.820 ⇒ 00:26:07.179 Robert Tseng: Yeah, so just to summarize, just kind of from my understanding as well, just on what we’re agreeing on. So, yeah, we’ll use the GTM server-side approach, but we’ll use… I mean, eventually we’re gonna have transition to sending it to the Azure endpoint. That’s probably more for, like.
227 00:26:07.520 ⇒ 00:26:09.729 Robert Tseng: September, so we’re gonna do it when.
228 00:26:09.730 ⇒ 00:26:10.240 Alison Cromie: Yeah.
229 00:26:10.240 ⇒ 00:26:21.350 Robert Tseng: now, but then that… well, I guess that’s not… I mean, this… this is not the ad… the ads thing seems like you guys already talked about it, so I’m just talking specifically about this part. Yeah. I just want to know, like, from a timeline perspective.
230 00:26:21.630 ⇒ 00:26:31.759 Robert Tseng: Does that mean we’re trying to do something with what we have right now, with the current instance, and then we end up doing it again for Azure, or kind of like, how do we… how do we….
231 00:26:31.760 ⇒ 00:26:32.550 Alison Cromie: Honestly?
232 00:26:32.550 ⇒ 00:26:33.220 Robert Tseng: now.
233 00:26:33.220 ⇒ 00:26:52.219 Alison Cromie: If we can get ads connected, I am 100% okay telling the agency partners that they’re just gonna be a little blind to web traffic for a while, and we can say, hey, we’re gonna connect this, but in the meantime, we’re just gonna get your… your ad accounts connected directly.
234 00:26:52.220 ⇒ 00:26:52.610 Robert Tseng: Okay.
235 00:26:52.610 ⇒ 00:26:55.149 Alison Cromie: Cause they’ll be happy about that.
236 00:26:55.150 ⇒ 00:26:55.570 Robert Tseng: Okay.
237 00:26:56.260 ⇒ 00:26:56.980 Robert Tseng: Sure.
238 00:26:57.540 ⇒ 00:26:58.220 Alison Cromie: So…
239 00:26:58.440 ⇒ 00:27:05.179 Alison Cromie: Yeah, I’m okay waiting if you guys are okay waiting. I know that’s outside of our… our anticipated timeline, but…
240 00:27:05.370 ⇒ 00:27:07.640 Alison Cromie: … Yeah.
241 00:27:07.640 ⇒ 00:27:11.540 Robert Tseng: Yeah, well, let’s connect this, and then we’ll kind of… then we’ll see, …
242 00:27:11.700 ⇒ 00:27:29.229 Robert Tseng: Yeah, and then… I guess as far as, like, other things, this is more for, like, the Tuesday check-in. By then, like, I’ve already kind of gone through all the amplitude events and things, and I know that we wanted to make some adjustments to the reports, so I… I’ve been putting together, like, an event data design tracking plan, I’ll share those things on Tuesday.
243 00:27:29.230 ⇒ 00:27:29.660 Alison Cromie: on.
244 00:27:29.660 ⇒ 00:27:43.529 Robert Tseng: And then, like, some recommendations. Well, I’ll probably already pre… I’ll make some adjustments to the reports already by then, but also some, like, recommendations on what we could do after that. Yeah, so I think that’s kind of what you can expect coming Tuesday call. Yeah.
245 00:27:43.530 ⇒ 00:27:50.470 Alison Cromie: Great, and then, one thing I shared today in Slack, was a spreadsheet that has, kind of.
246 00:27:50.470 ⇒ 00:28:13.819 Alison Cromie: all of the events, or not events, the properties that are in the data warehouse, as well as those that are coming from Healthfully, and that’s marked as OLS, online scheduling as Healthfully. Yeah. And so there’s kind of some information about, like, what the source of each one is. We might need to map out, like, what’s changing where, and I’ll look… I might have started that process, I’ll look and see if I have it.
247 00:28:13.960 ⇒ 00:28:26.470 Alison Cromie: I would say the spreadsheet is not, like, 100%, so there might be some things missing, and let, like, we can talk through it, and I can kind of fill in the blanks as we go here, and I’ll try to get some time to take a look at it as well.
248 00:28:26.470 ⇒ 00:28:37.049 Alison Cromie: But just FYI, that’s… that’s kind of what we’ve been working off of internally, just to know, like, what is all the data we have, you know, availability to use.
249 00:28:37.050 ⇒ 00:28:46.620 Alison Cromie: What do we actually want to use? I think there’s quite a few things in there that I say no. You know, we’re not gonna pull it up, because it’s PHI we don’t need. And then…
250 00:28:46.690 ⇒ 00:28:49.040 Alison Cromie: Yeah, so… We can… Okay.
251 00:28:49.040 ⇒ 00:28:49.530 Robert Tseng: Yeah.
252 00:28:49.530 ⇒ 00:28:49.860 Alison Cromie: figure out.
253 00:28:49.860 ⇒ 00:28:56.810 Robert Tseng: I briefly scanned the list. There’s definitely more in Amplitude than just this list, so, ….
254 00:28:56.810 ⇒ 00:28:59.359 Alison Cromie: Yes, that’s because Healthfully is sending me more than….
255 00:28:59.360 ⇒ 00:29:00.890 Robert Tseng: Showing everything, right? Yeah.
256 00:29:00.890 ⇒ 00:29:08.850 Alison Cromie: And they haven’t shut it off like I’ve asked them to, so I’m like, you guys are sending me a lot of PHI right now that I really don’t want in here, but….
257 00:29:08.850 ⇒ 00:29:09.170 Robert Tseng: Yeah.
258 00:29:09.170 ⇒ 00:29:12.519 Alison Cromie: I mean, we’re okay because we have a BAA, but like….
259 00:29:15.330 ⇒ 00:29:17.769 Robert Tseng: Okay. Just, I’ll just give you an….
260 00:29:17.770 ⇒ 00:29:18.420 Alison Cromie: Anyway.
261 00:29:18.560 ⇒ 00:29:20.160 Robert Tseng: Yeah. Yeah, no, I….
262 00:29:20.160 ⇒ 00:29:22.510 Alison Cromie: Very aware of that one.
263 00:29:24.210 ⇒ 00:29:24.760 Robert Tseng: Cool.
264 00:29:24.920 ⇒ 00:29:28.780 Robert Tseng: Yeah, I know we’re trying to… one of the other deliverables at the end is, like, to
265 00:29:28.780 ⇒ 00:29:45.700 Robert Tseng: kind of give you… obviously, the event scope properties, a lot of these is not really showing up right now, but these are all tracked as the event scope properties, like, knowing what will persist and be stored as user properties, like, kind of building that, like, user profile model, that’s kind of, like, one of the other things that we want to get done with this.
266 00:29:45.700 ⇒ 00:29:56.239 Alison Cromie: I need to go look at that spreadsheet again a little closer, because I may have started a column to indicate, like, what’s a persistent, or I meant to, so I’ll.
267 00:29:56.240 ⇒ 00:29:56.650 Robert Tseng: Okay.
268 00:29:56.650 ⇒ 00:30:03.200 Alison Cromie: I’ll look at that, and if not, I’ll make an update and send a new copy. … But, …
269 00:30:03.500 ⇒ 00:30:13.990 Alison Cromie: Yeah, that’s, yeah, that 100%, we can go through and determine, like, what makes sense to be a user property that persists, or may, may change
270 00:30:14.230 ⇒ 00:30:16.850 Alison Cromie: very rarely, right? Yeah.
271 00:30:17.360 ⇒ 00:30:18.270 Alison Cromie: Yeah.
272 00:30:19.940 ⇒ 00:30:20.790 Robert Tseng: Cool.
273 00:30:21.380 ⇒ 00:30:22.250 Alison Cromie: Awesome.
274 00:30:23.310 ⇒ 00:30:36.039 Robert Tseng: Okay, yeah, I mean, that’s, that’s… I mean, we have our orders, we know what to do next. Yeah, I mean, I just hold 45 minutes in case we run over, but, like… I’m okay having time back in my day. Yeah.
275 00:30:38.640 ⇒ 00:30:39.230 Alison Cromie: Awesome.
276 00:30:39.230 ⇒ 00:30:40.159 Robert Tseng: Have a good weekend, everyone.
277 00:30:40.160 ⇒ 00:30:43.639 Alison Cromie: Really excited. Keep us in the loop on the ads connection.
278 00:30:44.810 ⇒ 00:30:46.339 Zoran Selinger: Milo. Milu.
279 00:30:46.340 ⇒ 00:30:47.080 Alison Cromie: Awesome.
280 00:30:47.080 ⇒ 00:30:49.489 Robert Tseng: Thank you. Have a great weekend.
281 00:30:49.490 ⇒ 00:30:50.260 Adam Kittleson: Yeah, too.
282 00:30:50.260 ⇒ 00:30:50.910 Zoran Selinger: Luma.