Meeting Title: EMH Clients Amplitude Kickoff Call Date: 2025-08-15 Meeting participants: acromie, Adam Kittleson, Robert Tseng
WEBVTT
1 00:01:08.330 ⇒ 00:01:09.510 acromie: Hey, Adam.
2 00:01:11.280 ⇒ 00:01:12.200 Adam Kittleson: Hello, Lou?
3 00:01:17.630 ⇒ 00:01:19.750 acromie: Oops, that’s not what I wanted.
4 00:01:21.230 ⇒ 00:01:24.350 Adam Kittleson: Pulling receipts, always fun.
5 00:01:26.900 ⇒ 00:01:27.540 acromie: Yeah.
6 00:01:27.540 ⇒ 00:01:30.530 Adam Kittleson: to do that for SEM Russia all year?
7 00:01:30.530 ⇒ 00:01:32.470 acromie: I will soon, I’m sure.
8 00:01:32.700 ⇒ 00:01:35.710 Adam Kittleson: Okay. Might see if it’s just ready now, then.
9 00:01:35.710 ⇒ 00:01:37.560 acromie: Yeah, if you’ve got it, send it over.
10 00:01:44.970 ⇒ 00:01:47.349 acromie: Yeah, it hasn’t hit yet, so….
11 00:01:47.350 ⇒ 00:01:47.950 Adam Kittleson: Got it.
12 00:01:48.400 ⇒ 00:01:49.929 acromie: But I bet it will soon.
13 00:01:50.220 ⇒ 00:01:50.840 Adam Kittleson: Yeah.
14 00:01:52.580 ⇒ 00:01:53.890 Robert Tseng: Yeah, awesome. Hey, Adam.
15 00:01:54.190 ⇒ 00:01:55.530 acromie: Hey!
16 00:01:56.900 ⇒ 00:01:58.260 acromie: How’s it going?
17 00:01:59.310 ⇒ 00:02:02.539 Robert Tseng: We just, we put on, like, a…
18 00:02:03.020 ⇒ 00:02:05.960 Robert Tseng: Hot yoga event with some brands here.
19 00:02:05.960 ⇒ 00:02:07.110 acromie: Oh, cool!
20 00:02:07.110 ⇒ 00:02:09.750 Robert Tseng: And, I thought there would be a…
21 00:02:10.289 ⇒ 00:02:17.620 Robert Tseng: like, a room for me to take this call afterwards, and there wasn’t, so I was, like, scrambling to get to… Oh, no! Yeah.
22 00:02:17.990 ⇒ 00:02:21.719 acromie: Will this work okay? I mean, do you want to move it, or.
23 00:02:21.720 ⇒ 00:02:28.809 Robert Tseng: No, no, this’ll work. I mean, the connection’s fine, and the weather’s nice out in New York, so I’m good. Alright. Yeah.
24 00:02:29.580 ⇒ 00:02:32.579 Robert Tseng: Apologies for all the mixed up, I thought I could make it work.
25 00:02:32.820 ⇒ 00:02:40.240 acromie: No, no worries. Again, we’re happy to move it if we need to, but we’ll get started and see how it goes. Sure.
26 00:02:43.700 ⇒ 00:02:44.900 acromie: Awesome.
27 00:02:47.290 ⇒ 00:02:49.500 acromie: Well, how do we want to get started?
28 00:02:50.730 ⇒ 00:03:03.460 Robert Tseng: Yeah, well, I mean, I guess, you know, this being the kind of kickoff call, I mean, maybe things have changed since the last time we kind of, like, chatted. We chatted pretty high level. I didn’t, like, built into any of your systems or anything, so….
29 00:03:04.500 ⇒ 00:03:08.360 Robert Tseng: Yeah, I guess it would be good to just know, kind of, like, what
30 00:03:08.380 ⇒ 00:03:11.819 Robert Tseng: I mean, I like to plan, like, the first… first week, two weeks out, so…
31 00:03:11.840 ⇒ 00:03:29.740 Robert Tseng: I know we had some things we wanted to review on the Amplit side. You wanted to evaluate capabilities, because you already have some set up, want to see if the CDP product is feasible for kind of what you’re trying to use it for. So, obviously, getting access to real estate is kind of a given after this call, but, I was hoping that we can kind of talk through
32 00:03:29.770 ⇒ 00:03:37.400 Robert Tseng: Kind of from your perspective, what the priorities are. I mean, I have, like, this typical, like, audit structure that I… I read through.
33 00:03:37.400 ⇒ 00:03:37.950 acromie: Everybody happy.
34 00:03:37.950 ⇒ 00:03:42.360 Robert Tseng: to adapt it to… based on, like, what you think is, the most important.
35 00:03:42.380 ⇒ 00:04:00.880 acromie: I mean, well, yes, I think there’s, like, a whole… when I think of the priority, one of the things that is, like, super high priority for us is getting either the and or the, Google ad, the GA4 flow running.
36 00:04:01.070 ⇒ 00:04:12.379 acromie: And then being able to connect to the ad… Google ad accounts and send conversion data, so in both places, right? Because, like.
37 00:04:13.070 ⇒ 00:04:31.899 acromie: we… I think we… we’re… we’re waffling between, do we just send it all to GA4, like everybody is used to, and then we connect everybody’s ad accounts through GA4 to grab the conversion events, or does it make sense to just do the direct connection from Amplitude to the Google Ad accounts?
38 00:04:31.950 ⇒ 00:04:39.350 acromie: Both… in both areas, we’re getting those errors where it just does not want to send the data.
39 00:04:39.350 ⇒ 00:05:00.660 acromie: And I think you’re right, it’s probably just how the data is and needs to be transformed and sent over correctly. So those are a big one that are impacting our system and everybody’s ads account, like, right now. So, like, that’s a huge… that would be a huge win for us if there’s a way to, like, look at that
40 00:05:00.660 ⇒ 00:05:02.529 acromie: Earlier in the process.
41 00:05:02.730 ⇒ 00:05:09.650 acromie: But also, if there’s things that have to happen first in order to get to that place, that’s definitely the next step.
42 00:05:09.940 ⇒ 00:05:10.500 acromie: So….
43 00:05:10.500 ⇒ 00:05:11.070 Robert Tseng: Okay.
44 00:05:11.340 ⇒ 00:05:20.329 Robert Tseng: That sounds good. I mean, from there, I mean, the amplitude, J4, kind of access, and then I guess for me to investigate, a couple of the questions would be.
45 00:05:20.540 ⇒ 00:05:23.459 Robert Tseng: Well, I guess, for the, like.
46 00:05:23.680 ⇒ 00:05:40.060 Robert Tseng: They gave more events already, going to the ad accounts. Seems like you feel like you don’t trust them, I don’t know, I mean, usually you feel like they’re under-reporting, so I think just kind of getting a sense of, like, you know, how… what… how much of the error is from, kind of.
47 00:05:40.190 ⇒ 00:05:54.869 Robert Tseng: like, the current… the current setup, yeah, so I think kind of getting the magnitude of it, I think, would be helpful, because there’s multiple reasons why, you know, ad tagging tracking is off, like, even if you do send it through… Yeah.
48 00:05:54.870 ⇒ 00:06:06.710 acromie: We just literally aren’t getting the data we want to see in there, so it’s… yeah, like, it… I think there are some errors in the console when you look that up, but…
49 00:06:06.860 ⇒ 00:06:13.030 acromie: One of them is a naming error, for… that’s the GA4 one, right, Adam?
50 00:06:13.900 ⇒ 00:06:23.939 Adam Kittleson: Yeah, that’s, related to sending session events. Basically, everything that I’ve found on that is that they want us to send
51 00:06:24.070 ⇒ 00:06:27.109 Adam Kittleson: Sessions as a specific event, rather than how.
52 00:06:27.110 ⇒ 00:06:27.460 Robert Tseng: Yep.
53 00:06:27.460 ⇒ 00:06:34.730 Adam Kittleson: Analytics structures it, so we can actually break it down by source and channel and all that. So that’s kind of the one naming one.
54 00:06:34.730 ⇒ 00:06:35.170 acromie: Yep.
55 00:06:35.170 ⇒ 00:06:35.870 Robert Tseng: Yeah.
56 00:06:35.870 ⇒ 00:07:00.160 acromie: Perfect. Okay, good. Oh, good, I’m glad you’re on the right track. And by the way, Robert, this is Adam. Adam is my marketing web analytics specialist. He’s just our data guy here, from a reporting standpoint, and so he’s the one who’s using Amplitude, the most from our team and putting together a lot of the reporting, so he’ll be highly involved, and
57 00:07:00.160 ⇒ 00:07:01.000 acromie: …
58 00:07:01.000 ⇒ 00:07:14.769 acromie: Adam, this is Robert, who is an amplitude expert, and kind of knows all of the issues we’re experiencing due to working with other clients on exactly the same thing, it sounds like, so….
59 00:07:15.000 ⇒ 00:07:16.450 Adam Kittleson: Awesome, yeah, nice to meet you.
60 00:07:16.670 ⇒ 00:07:24.930 Robert Tseng: Yeah, good to meet you, Adam. I guess, like, as far as communications go, I know Rico sent over kind of a Slack. I don’t know if you guys work in Slack, or….
61 00:07:24.930 ⇒ 00:07:37.550 acromie: I got… we don’t normally work in Slack, so I was able to get in. Adam had some troubles, but I think I just need to… Adam, I think you and I just need to screen share, and I’ll show you what I did to get in, because we don’t have, like, a…
62 00:07:38.010 ⇒ 00:07:48.819 acromie: paid account in there or anything, so I think you just have to create a workspace, and then it’ll connect you, and I think it gives you, like, a 30-day, 90-day trial, or something like that, anyway.
63 00:07:48.820 ⇒ 00:07:49.850 Robert Tseng: Okay.
64 00:07:50.250 ⇒ 00:07:51.849 Robert Tseng: What do you, what do you use internally?
65 00:07:51.850 ⇒ 00:07:54.259 acromie: We use Teams, so… Okay.
66 00:07:54.260 ⇒ 00:07:56.609 Robert Tseng: We could do Teams instead, if that’s better.
67 00:07:56.620 ⇒ 00:08:02.440 acromie: Can… can you cross… Can we… communicate over Teams, cross.
68 00:08:02.440 ⇒ 00:08:04.739 Robert Tseng: You can’t do cross-domain, yeah.
69 00:08:04.740 ⇒ 00:08:05.329 acromie: we’re after.
70 00:08:05.330 ⇒ 00:08:05.750 Robert Tseng: yeah.
71 00:08:05.750 ⇒ 00:08:16.390 acromie: Yeah. So, I mean, like, we can… we can figure this out. I think it just… the cross comp… the way you guys have it set it up wanted us to have a… a
72 00:08:16.690 ⇒ 00:08:25.249 acromie: a plan, which I can also look at if we need to. I don’t think it’s going to be that expensive for the duration of what we’re working on, but….
73 00:08:25.250 ⇒ 00:08:34.359 Robert Tseng: If it’s a single, connection, a single channel, it’s free, but that must mean that maybe someone else in your organization’s already, kind of.
74 00:08:34.610 ⇒ 00:08:44.970 acromie: It’s entirely possible. Yeah, like, I know there’s a Slack for, like, our franchisees that I accidentally entered the other day.
75 00:08:46.280 ⇒ 00:08:46.669 Robert Tseng: Oh, okay.
76 00:08:46.670 ⇒ 00:08:55.119 acromie: But, I didn’t… there was an invite, I was like, oh, what’s this? And then I got in there and was like, oh, this is all franchisees. I do not want to be in here.
77 00:08:56.150 ⇒ 00:09:02.319 acromie: But, either way, like, I mean, we can…
78 00:09:03.220 ⇒ 00:09:08.670 acromie: we can figure something out. … Yeah.
79 00:09:09.580 ⇒ 00:09:13.539 acromie: Trying to think what else besides Slack. I mean…
80 00:09:13.740 ⇒ 00:09:18.409 acromie: Yeah, I think Slack will be the easiest thing to figure out, because we’re already in another…
81 00:09:18.640 ⇒ 00:09:23.490 acromie: Slack workspace for, Amplitude. Actually, Amplitude has a Slack workspace.
82 00:09:23.490 ⇒ 00:09:24.130 Robert Tseng: Yeah.
83 00:09:24.490 ⇒ 00:09:28.240 acromie: So we’re in there, in our cohort. …
84 00:09:28.370 ⇒ 00:09:35.629 acromie: But, so, it’s not like we don’t have Slack, but yeah, we just don’t have it for us in general, but….
85 00:09:35.630 ⇒ 00:09:36.280 Robert Tseng: Okay.
86 00:09:36.280 ⇒ 00:09:38.019 acromie: I’ll figure that out on our side.
87 00:09:38.600 ⇒ 00:09:39.590 Robert Tseng: Okay, maybe fair.
88 00:09:39.590 ⇒ 00:09:41.680 acromie: Adam gets in there.
89 00:09:42.140 ⇒ 00:09:42.740 Robert Tseng: Yeah.
90 00:09:44.270 ⇒ 00:09:56.189 Robert Tseng: Okay, that sounds good. So, we’ll use that. I’ll definitely root cause kind of what’s going on the ad side, just making sure the… yeah, I mean, I think it’d be good to even do, like, a…
91 00:09:56.280 ⇒ 00:10:07.020 Robert Tseng: more zoomed-out walkthrough, like, kind of going through that journey, and kind of seeing the conversion event, when you expect it to fire, because, I think that would probably be helpful to….
92 00:10:07.020 ⇒ 00:10:07.540 acromie: Hmm.
93 00:10:07.540 ⇒ 00:10:26.429 Robert Tseng: To get a sense of. Yeah, obviously seeing it from the user perspective, and then from a systems perspective, like, what… I mean, you’re logging the event and showing up in amplitude, but kind of, like, knowing, like, how that event is being tracked right now, because there is going to be some,
94 00:10:27.530 ⇒ 00:10:36.400 Robert Tseng: like, lag between the event being tracked at Amplitude and then sending it from Amplitude. I think that’s just something to expect, like, we can manage it.
95 00:10:36.400 ⇒ 00:10:55.069 acromie: Yeah, and we’re… yeah, that’s absolutely correct, and there’s gonna be cases where we’re getting the data at a later time anyway, so that’s… yeah. I think as long as we know what those potential delays are, we’ll be… nothing is… needs to be real time, like, that’s not a huge priority, so….
96 00:10:55.460 ⇒ 00:10:56.040 Robert Tseng: Yeah.
97 00:10:56.460 ⇒ 00:11:06.869 Robert Tseng: Okay. Yeah, I know Google Ads has the window, you can… I don’t know what you set your custom window at, so there are certain, like, configurations about ads that I probably want to know as well.
98 00:11:06.870 ⇒ 00:11:08.030 acromie: Right. ….
99 00:11:08.030 ⇒ 00:11:10.429 Robert Tseng: Yeah, so I think that… that’s…
100 00:11:10.570 ⇒ 00:11:16.340 Robert Tseng: much as we can kind of cover on… I mean, I can write up, send you over, like, more of, like, a questionnaire format, we can.
101 00:11:16.340 ⇒ 00:11:17.690 acromie: Perfect, yeah, that would be great.
102 00:11:17.690 ⇒ 00:11:18.250 Robert Tseng: as well.
103 00:11:18.590 ⇒ 00:11:27.680 acromie: Yep, awesome. Okay. And then as far as adding you into Amplitude, is it just you, or is there anyone else on your team that needs access?
104 00:11:27.970 ⇒ 00:11:37.340 Robert Tseng: I’m thinking, after this call, I was hoping to get a better sense of, like, who I want to add. I was thinking, coming in, maybe, like, 2 or 3 people from my side.
105 00:11:37.340 ⇒ 00:11:49.020 Robert Tseng: Including myself. So, I think it sounds like, because of the Google Ads focus, like, I have a, like, a tackling and tagging specialist, his name is Oren, I’ll probably bring him in.
106 00:11:49.140 ⇒ 00:11:55.390 Robert Tseng: And then, I don’t know, I guess I’ll kind of have to see what else we’re working with here to see what else I want to tap.
107 00:11:55.600 ⇒ 00:11:59.160 acromie: Okay, perfect, yeah, just, yeah, send those over, and we’ll get them in right away.
108 00:11:59.410 ⇒ 00:12:00.000 Robert Tseng: Okay.
109 00:12:02.290 ⇒ 00:12:16.709 Robert Tseng: Okay, cool. I mean, do you want to do a quick overview of you kind of just clicking around in Amplitude, or just get to get a tour? I mean, I’m happy to kind of jump in there myself afterwards, but yeah, just kind of want to…
110 00:12:17.440 ⇒ 00:12:18.960 Robert Tseng: See what we have so far.
111 00:12:18.960 ⇒ 00:12:19.570 acromie: Yeah?
112 00:12:19.710 ⇒ 00:12:23.269 acromie: Yeah, let me, get into the main…
113 00:12:24.130 ⇒ 00:12:29.450 acromie: space here, maybe… there we go, home, okay. All right.
114 00:12:29.900 ⇒ 00:12:33.600 acromie: And Adam, feel free to jump in if I need to.
115 00:12:35.200 ⇒ 00:12:38.809 acromie: Hold on, which desktop am I… what? Oh.
116 00:12:39.120 ⇒ 00:12:40.470 acromie: Weird, okay.
117 00:12:41.800 ⇒ 00:12:45.279 acromie: My numbers are not in order of where…
118 00:12:45.670 ⇒ 00:12:49.859 acromie: Where they are on my desk. Okay, can you see amplitude?
119 00:12:51.350 ⇒ 00:12:52.870 Robert Tseng: Yes, I can.
120 00:12:52.870 ⇒ 00:12:55.510 acromie: Okay, great. Oh, of course.
121 00:12:55.880 ⇒ 00:13:08.130 acromie: Let’s try that again. Okay, so, the big thing to note is that we have… our main project is EMH clients. This is what the majority of our stuff is coming in through.
122 00:13:08.130 ⇒ 00:13:25.150 acromie: We do have a testing and development project for any, like, major efforts before we do it in the, you know, production, and then this was one that was for another connection that we created. So, just the EMH clients is where most of what we’re working in is.
123 00:13:25.150 ⇒ 00:13:32.419 acromie: Let’s see what else? So, we are receiving… hold on…
124 00:13:32.490 ⇒ 00:13:37.310 acromie: It makes sense to go by… And….
125 00:13:37.310 ⇒ 00:13:40.750 Adam Kittleson: My end, it’s showing a LSM doc.
126 00:13:40.750 ⇒ 00:13:41.720 acromie: Is it?
127 00:13:41.720 ⇒ 00:13:42.490 Adam Kittleson: Yeah.
128 00:13:43.150 ⇒ 00:13:45.860 acromie: No, that’s weird. Okay, hold on.
129 00:13:53.140 ⇒ 00:13:55.699 acromie: I don’t even have one up on my screen. Oh!
130 00:13:56.760 ⇒ 00:13:58.270 acromie: Unless, no.
131 00:13:59.410 ⇒ 00:14:01.930 acromie: Hold on, let me find out what wears.
132 00:14:02.440 ⇒ 00:14:03.790 acromie: sharing here.
133 00:14:06.970 ⇒ 00:14:16.650 acromie: Desktop 3… Share. And then… Defined my… Nope, that’s not it.
134 00:14:16.840 ⇒ 00:14:17.660 acromie: Hold on….
135 00:14:20.070 ⇒ 00:14:21.390 Robert Tseng: I see it, kind of.
136 00:14:21.560 ⇒ 00:14:22.300 acromie: Yeah. Do you?
137 00:14:22.760 ⇒ 00:14:24.610 Adam Kittleson: It’s a small window right now.
138 00:14:24.830 ⇒ 00:14:28.769 acromie: Thank you. Oh my gosh, yes, thank you. It just got small. Okay.
139 00:14:28.770 ⇒ 00:14:29.219 Adam Kittleson: There we go.
140 00:14:29.600 ⇒ 00:14:30.100 Robert Tseng: Yeah.
141 00:14:30.100 ⇒ 00:14:40.200 acromie: Holy moly, okay. So, again, EMH clients is our main… in case you weren’t seeing that before, these two are both the kind of testing…
142 00:14:40.320 ⇒ 00:14:49.180 acromie: this is our primary testing and development, and this was for a specific connection that was being made in the past. We could probably remove that at this point, but….
143 00:14:49.180 ⇒ 00:14:52.959 Robert Tseng: Do you use Healthy, or is that just Healthfully, it’s just like a….
144 00:14:52.960 ⇒ 00:14:56.679 acromie: We do use Healthfully, yep. Are you familiar with them?
145 00:14:56.680 ⇒ 00:14:57.250 Robert Tseng: Yeah, yeah.
146 00:14:57.250 ⇒ 00:15:08.669 acromie: Okay, cool. Yeah, no, we just launched online scheduling. In fact, our last, group is going live on Monday into the system, so….
147 00:15:08.670 ⇒ 00:15:09.570 Robert Tseng: Oh, no way.
148 00:15:09.570 ⇒ 00:15:14.720 acromie: Yeah. Yeah, yeah, yeah. So, we’re working on… they’re sending us data, but also, like.
149 00:15:15.840 ⇒ 00:15:24.459 acromie: they didn’t send the data the way I asked them to send the data, so… and I have to do a new statement of work with them in order for them to fix it.
150 00:15:25.430 ⇒ 00:15:26.130 Robert Tseng: Yeah.
151 00:15:26.580 ⇒ 00:15:28.370 acromie: Whole long story. Anyway….
152 00:15:28.370 ⇒ 00:15:33.480 Robert Tseng: We’ve worked with a client that’s… that was on Health Reinforce, so that’s why I asked. It’s not, like, a very….
153 00:15:33.480 ⇒ 00:15:36.560 acromie: not that well-known in the industry, I think, so I was just surprised to see it.
154 00:15:36.700 ⇒ 00:15:45.769 acromie: Yeah. So they, so they’re sending us conversion data from our online scheduling, … here…
155 00:15:46.210 ⇒ 00:15:50.000 acromie: And so, a lot of what we’re getting from them… oh, here.
156 00:15:50.230 ⇒ 00:15:51.470 acromie: Oh, wait.
157 00:15:51.610 ⇒ 00:16:11.139 acromie: I was just looking at them. So, besides… so these are the ones we’re getting from them. There’s actually, I think, one more in the system. But, basically everything comes over as events. There’s no, like, they’re not send… they’re only sending device ID over as a user property, so that it can sync with the…
158 00:16:11.320 ⇒ 00:16:18.760 acromie: And create our known users, that’s kind of our field we’re using primarily.
159 00:16:19.120 ⇒ 00:16:28.440 acromie: And so, everything else is, you know, your typical… You know, analytics sessions, …
160 00:16:28.920 ⇒ 00:16:43.489 acromie: we did go through and labeled, like, a ton of stuff in here. Adam went through and labeled, like, every button and whatnot, so we do have the ability to pull those in when necessary. …
161 00:16:43.590 ⇒ 00:16:49.159 acromie: We also have in here, one thing we’re doing is we have, …
162 00:16:49.320 ⇒ 00:16:52.000 acromie: What we’re calling compliant key events.
163 00:16:52.160 ⇒ 00:17:08.279 acromie: So, like, we have a key somewhere that tells me, like, Irvin Yalum is actually a click on a specific button, or a scheduled call, or something like that, to kind of mask the names from Google, so we’re not saying, this person filled out a form.
164 00:17:08.280 ⇒ 00:17:13.249 acromie: You know, kind of thing, to kind of help with that compliance piece.
165 00:17:13.339 ⇒ 00:17:20.759 acromie: … And so, that’s how those are in here, and those are just copies of the primary
166 00:17:21.010 ⇒ 00:17:24.999 acromie: you know, conversion event in here. …
167 00:17:25.960 ⇒ 00:17:35.440 acromie: Let’s see, what else? Right now, we’re getting… Okay, let’s see… event properties…
168 00:17:36.270 ⇒ 00:17:41.870 acromie: So, one thing Healthfully did was they sent us everything instead of, the…
169 00:17:42.720 ⇒ 00:17:50.869 acromie: dialed-down list I wanted, so we have in here, a lot of information.
170 00:17:50.970 ⇒ 00:17:59.319 acromie: I’m hoping I can get them to at least remove some of these, because they go into a lot more PHI than I want in the system. …
171 00:17:59.480 ⇒ 00:18:00.670 acromie: But…
172 00:18:01.460 ⇒ 00:18:14.740 acromie: so we have a lot of event properties. Now, some of these, I’d really like to be user properties, because, for example, if they come in and, like, this is their appointment location.
173 00:18:14.740 ⇒ 00:18:21.670 acromie: Here’s… the other thing they did was they sent us IDs instead of the text, so some of these things are…
174 00:18:22.080 ⇒ 00:18:35.609 acromie: useless. But, let’s just say this was the right one. If this was the appointment location, we would want to know that that user is visiting, is part of that location, and so I kind of want it to be
175 00:18:35.660 ⇒ 00:18:49.970 acromie: a user property in the end, you know, unless they change locations, at which point that would change in our data warehouse. We haven’t finished that data warehouse connection to amplitude, that’s a big thing that we need to… to button up.
176 00:18:50.130 ⇒ 00:18:51.450 acromie: ….
177 00:18:51.720 ⇒ 00:18:58.809 Robert Tseng: That’s in Azure, and somebody’s… Yeah, that’s the Azure stuff that I think we’re gonna walk through as well. Okay.
178 00:18:59.040 ⇒ 00:19:09.670 acromie: And so, the hope is that we would then send up, like, when that appointment location changed in the database, it would change their user, you know.
179 00:19:10.000 ⇒ 00:19:23.130 acromie: event or property up in the system here. Because we might have, in the future, we might want to send, yeah, that one. Fix it. Did you fix it? Thank you.
180 00:19:23.170 ⇒ 00:19:32.599 acromie: Yeah. Because it’s locked on the other side. Is it locked on the other side? It’s got a key, it’s got a key locked. Did someone come in from the other door or something? Because someone opened that, but there was nobody here.
181 00:19:33.500 ⇒ 00:19:37.550 acromie: No, I’m not… I saw it close. I’m sorry, hold on a second.
182 00:19:37.550 ⇒ 00:19:38.240 Robert Tseng: No worries.
183 00:19:38.240 ⇒ 00:19:49.839 acromie: It ain’t happening no more. Okay, cool, thank you. I know, like, Ray, I know, it’s creeped me out. There’s a bunch of kids playing over there, so… yeah, maybe. Thank you.
184 00:19:50.030 ⇒ 00:20:00.810 acromie: I’m here alone at the office, and the door that goes to our sublet office, which is a school, so there’s a bunch of kids on the other side, all of a sudden, it, like, opened, and then, like, slowly shut, and I… I moved out to, like.
185 00:20:01.220 ⇒ 00:20:10.869 acromie: someone had come in, and I was like, but I saw the door, like, shut, but I was like, there’s nobody here, there’s nobody in the office, like, what is going on? And so, I….
186 00:20:10.870 ⇒ 00:20:12.419 Robert Tseng: That’s really creepy.
187 00:20:12.420 ⇒ 00:20:20.730 acromie: And Aaron’s like, it’s locked, there’s nobody getting in there. I’m like, I’m like, I don’t know how it happened, but that door opened, I will tell you.
188 00:20:20.960 ⇒ 00:20:21.300 Robert Tseng: ….
189 00:20:23.370 ⇒ 00:20:25.439 acromie: Anyway, sorry about that.
190 00:20:25.440 ⇒ 00:20:26.150 Robert Tseng: your hips.
191 00:20:26.300 ⇒ 00:20:35.039 acromie: Okay, so, … yeah, so just, we need to figure out, like, what does that user look like? Because we don’t have, you know, aside from…
192 00:20:35.770 ⇒ 00:20:53.349 acromie: more of, like, the web properties. We don’t have a lot of user properties in here yet, because I don’t know how to turn them into, like, if there’s a way to go, like, if this event happens, take this property and add it to, you know, or update the user field, right?
193 00:20:53.530 ⇒ 00:20:54.060 Robert Tseng: Yeah.
194 00:20:54.060 ⇒ 00:21:00.669 acromie: So that’s kind of what I’m looking to do there. … What else? We…
195 00:21:01.650 ⇒ 00:21:10.499 acromie: have been trying… these are the Google Ads. This is the one we’re… we’re trying to… we’ve been working with. He’s been trying to work with it, too, the Z at this location.
196 00:21:10.730 ⇒ 00:21:11.050 Robert Tseng: Yep.
197 00:21:11.050 ⇒ 00:21:22.399 acromie: figure out, same with our national account, you can see we had some test ones. This is our GA4 compliant feed, and if you go to the… -oh.
198 00:21:22.920 ⇒ 00:21:25.059 acromie: It might… did it stop because it…
199 00:21:26.630 ⇒ 00:21:31.190 acromie: Oh, it’s delivering everything now. Adam, have you looked at it recently?
200 00:21:31.350 ⇒ 00:21:35.520 acromie: Oh, delivering, it’s just not… we’re not getting the session data, right?
201 00:21:35.520 ⇒ 00:21:38.640 Adam Kittleson: Yeah, it’s delivering it as an event.
202 00:21:39.360 ⇒ 00:21:40.440 Adam Kittleson: Instead of….
203 00:21:40.440 ⇒ 00:21:42.649 acromie: Okay, so we might just need to….
204 00:21:42.650 ⇒ 00:21:46.989 Adam Kittleson: It flips back and forth. It… sometimes it’ll, …
205 00:21:47.230 ⇒ 00:21:50.839 Adam Kittleson: then show an error, and sometimes it doesn’t, so I….
206 00:21:51.080 ⇒ 00:21:51.859 acromie: Oh, okay.
207 00:21:53.630 ⇒ 00:21:54.340 acromie: Huh.
208 00:21:55.360 ⇒ 00:21:59.360 acromie: So yeah, so we might have to take a look at that. …
209 00:22:00.700 ⇒ 00:22:04.680 acromie: But yeah, I mean, we’ve got it filtered down to the events we want.
210 00:22:05.110 ⇒ 00:22:07.880 acromie: And the user data that we want.
211 00:22:08.310 ⇒ 00:22:18.199 acromie: … And then the ads account… see, is it gonna show us anything when it’s not on? Probably not.
212 00:22:18.880 ⇒ 00:22:21.370 acromie: We test the connection…
213 00:22:26.860 ⇒ 00:22:36.049 acromie: Ugh, failed computing credential metadata, okay, I don’t know what that means, but I think that’s different than what we were looking at before, so maybe…
214 00:22:36.250 ⇒ 00:22:38.990 acromie: he changed his password or something, I don’t know.
215 00:22:39.170 ⇒ 00:22:42.470 acromie: Or something happened with our… our app.
216 00:22:43.320 ⇒ 00:22:44.770 acromie: ….
217 00:22:47.390 ⇒ 00:22:53.519 Robert Tseng: Yeah, I would say that generally, the, error messaging in, CDPs is not very helpful.
218 00:22:53.520 ⇒ 00:22:55.179 acromie: Yeah, right? Yeah.
219 00:22:55.180 ⇒ 00:23:13.090 Robert Tseng: I think even though it’ll look like it’s a success from one side, it may not have actually been received on the other side. So, I think typically what I would do is I would just take the test payload from receiving key that you’re sending from, and then I would just go send it in directly to me, if it’s an API, that’s easier to get a physical
220 00:23:13.090 ⇒ 00:23:17.390 Robert Tseng: your endpoint, and you get their full error log, and I’d be able to figure it out from there.
221 00:23:17.540 ⇒ 00:23:18.510 Robert Tseng: Yeah.
222 00:23:18.850 ⇒ 00:23:30.509 acromie: And just to bring us back, like, amplitude for us is both analytics and CDP, so everything is being collected and stored here.
223 00:23:31.270 ⇒ 00:23:34.450 acromie: And, let’s see…
224 00:23:35.700 ⇒ 00:23:41.239 acromie: the other thing we’re going to want to do is start ingesting, but we’re not there yet. We started the, …
225 00:23:41.760 ⇒ 00:23:49.559 acromie: an HT… you know, an API for the data warehouse, but it’s not… oh, this is interesting. What is this sending? Because it says it’s active.
226 00:23:50.360 ⇒ 00:23:53.230 acromie: Did Etherin get farther on this than I thought?
227 00:23:54.450 ⇒ 00:23:55.680 acromie: I don’t know.
228 00:23:55.910 ⇒ 00:23:58.179 Adam Kittleson: Well, that might have been Lauren and Ivan, too.
229 00:23:58.180 ⇒ 00:24:04.470 acromie: Oh, maybe. Maybe they’re working on it. So that’s… yeah, that’s another thing. I have a group of, …
230 00:24:04.890 ⇒ 00:24:11.899 acromie: engineers who are working in Power BI stuff that might be pulling some data, so I should connect with them on that, but…
231 00:24:11.920 ⇒ 00:24:29.210 acromie: We can kind of… we can bring them in at that point, too, when we need, because they… they are really, like, the data warehouse folks in our group. Okay. So, they’ll be able to answer any questions about Azure and how that’s set up, and get… get you in there, you know, when we need to.
232 00:24:29.250 ⇒ 00:24:37.870 acromie: When it comes to… reporting. Adam, I’m gonna lean on you in this place, like…
233 00:24:38.130 ⇒ 00:24:51.670 acromie: Are there… in fact, do you want to share your screen and just show any, like, any things we’ve run into about reporting that felt like we were trying to figure out how to show data, but, like.
234 00:24:51.890 ⇒ 00:24:55.369 acromie: Kinda had to change how we looked at it, or…
235 00:24:55.760 ⇒ 00:24:58.309 acromie: Versus what we’re used to in analytics.
236 00:24:58.530 ⇒ 00:25:08.390 Adam Kittleson: Yeah, I think for the most part, that area’s in a solid spot. The one thing that…
237 00:25:09.170 ⇒ 00:25:10.870 Adam Kittleson: I think we really…
238 00:25:11.120 ⇒ 00:25:18.740 Adam Kittleson: have struggled with is, and forgive me for trying to do this on the fly here, … Which….
239 00:25:19.420 ⇒ 00:25:21.390 acromie: Oh, it’s that button to the….
240 00:25:22.540 ⇒ 00:25:28.660 Adam Kittleson: … Yeah, it’s the… Where’s the actual form submit?
241 00:25:31.110 ⇒ 00:25:37.410 Adam Kittleson: Not that one… all form leads, so…
242 00:25:38.950 ⇒ 00:25:43.529 Adam Kittleson: The issue here that we’ve run into is, …
243 00:25:43.940 ⇒ 00:25:52.969 Adam Kittleson: and maybe this… actually, I don’t think it would be solved by online scheduling, but either way, our lead form is…
244 00:25:53.530 ⇒ 00:26:05.319 Adam Kittleson: technically on a separate domain, we use JotForm for those. So Analytics was still able to actually track the leads and attribute them to the page that they
245 00:26:05.500 ⇒ 00:26:16.529 Adam Kittleson: started… that they got to the form from. With Amplitude, we’ve run into some issues where it… since they’re leaving the site, technically, to fill out the form, it then…
246 00:26:16.880 ⇒ 00:26:25.139 Adam Kittleson: We’ll just attribute the lead to the thank you page, because they… it’s fired on the page view of that page, …
247 00:26:25.780 ⇒ 00:26:40.509 Adam Kittleson: But since there’s no page on our site immediately before it in the funnel, something with that kind of breaks it. So yeah, everything just gets attributed to the thank you page, even if we do, like.
248 00:26:42.370 ⇒ 00:26:51.269 Adam Kittleson: prefer… or referring domain, yeah, then we’ll just pin it on JobForm instead of the actual
249 00:26:51.490 ⇒ 00:26:57.500 Adam Kittleson: Page they came from. … So I would say that’s…
250 00:26:58.100 ⇒ 00:27:03.039 Adam Kittleson: the big one there that we’re still kind of having with reporting.
251 00:27:03.040 ⇒ 00:27:12.660 acromie: But, but, let’s, let’s not bank on this too much, because as of Monday, I mean, and the end of the month, JotForm will no longer be the thing.
252 00:27:12.660 ⇒ 00:27:13.050 Adam Kittleson: Yeah.
253 00:27:13.050 ⇒ 00:27:18.070 acromie: So, I think That, while this has been an issue, it might not be something for us to…
254 00:27:18.350 ⇒ 00:27:19.570 acromie: really dig into.
255 00:27:19.570 ⇒ 00:27:30.249 Adam Kittleson: Yeah. But… does play into… The online scheduling issue, though, and this is really more of…
256 00:27:30.550 ⇒ 00:27:41.800 Adam Kittleson: I guess, how healthfully is sending the data, for a lot of our reports that we use for this, let’s just go to…
257 00:27:42.870 ⇒ 00:27:49.930 Adam Kittleson: like, insurance… scheduled. So we still have to group it by…
258 00:27:50.990 ⇒ 00:27:57.669 Adam Kittleson: referring location page rather than the location they actually scheduled at. …
259 00:27:58.100 ⇒ 00:28:04.779 Adam Kittleson: Which is not… for some of these events, like, insurance scheduled here, we really just want to see what…
260 00:28:05.350 ⇒ 00:28:09.990 Adam Kittleson: insurance they actually scheduled an appointment at, and at which location, not…
261 00:28:10.150 ⇒ 00:28:13.199 Adam Kittleson: which page they came from. ….
262 00:28:13.750 ⇒ 00:28:14.969 acromie: That’s interesting that you’re not.
263 00:28:14.970 ⇒ 00:28:15.610 Adam Kittleson: Bye.
264 00:28:15.610 ⇒ 00:28:26.460 acromie: Because it should be… maybe it’s not part of the… What event is that… Piece of data from….
265 00:28:27.060 ⇒ 00:28:30.789 Adam Kittleson: Like, is that in the appointment scheduled?
266 00:28:30.970 ⇒ 00:28:36.240 acromie: event properties… the insurance… Scheduled.
267 00:28:36.240 ⇒ 00:28:40.890 Adam Kittleson: I think so, … Yeah, cause I….
268 00:28:40.890 ⇒ 00:28:46.320 acromie: The location they scheduled at should be in that same event.
269 00:28:46.940 ⇒ 00:28:51.219 Adam Kittleson: Yeah, like, the provider appointment, maybe this isn’t the best.
270 00:28:51.220 ⇒ 00:29:04.029 acromie: I think another… a good example, Adam, is that, like, for example, when we pull a funnel, that shows what they’re doing in online scheduling, we also want to see, like, what page, like.
271 00:29:04.430 ⇒ 00:29:06.939 acromie: The people who clicked on…
272 00:29:07.060 ⇒ 00:29:19.170 acromie: that online scheduling button, right? So I want to see someone clicked on an online scheduling button on the website, they went into HealthFully, and now here’s their… their path through Healthfully.
273 00:29:19.330 ⇒ 00:29:20.170 acromie: And…
274 00:29:20.600 ⇒ 00:29:40.050 acromie: But when we try to put those two… the events from Healthfully next to the event from the website, it doesn’t… there’s no connection, there’s no… … we get a… here, yeah, pull it in, and… and… because I think what happens is we get a, …
275 00:29:41.250 ⇒ 00:29:54.599 acromie: like, everything will be under Schedule Appointment, like, you’ll have online schedule… schedule an appointment button clicked, and then zeros across all of the conversion points in… from Healthfully.
276 00:29:54.910 ⇒ 00:30:04.179 acromie: Or you’ll have all of the healthfully, you know, conversion data in a zero in the schedule on line button clicked. So they’re not, like…
277 00:30:04.490 ⇒ 00:30:08.180 acromie: It’s not able to connect that
278 00:30:08.380 ⇒ 00:30:11.679 acromie: Event with these events over here?
279 00:30:12.560 ⇒ 00:30:16.430 acromie: … It’s better if you do the funnel.
280 00:30:16.430 ⇒ 00:30:20.929 Robert Tseng: I think I get it. It’s not stitching, … It’s not stitching it.
281 00:30:20.930 ⇒ 00:30:21.710 acromie: together.
282 00:30:21.710 ⇒ 00:30:26.600 Robert Tseng: Yeah, the same user, yeah, in two different systems. And the device ID is….
283 00:30:26.600 ⇒ 00:30:32.470 acromie: flowing over, so I don’t know why it’s not. There’s that connecting value.
284 00:30:33.770 ⇒ 00:30:35.030 acromie: …
285 00:30:36.250 ⇒ 00:30:43.240 acromie: But yeah, if you do that, and then, add in online scheduling button click… oh, there you go.
286 00:30:43.240 ⇒ 00:30:48.650 Adam Kittleson: Well, yeah, now it… see, then it only counts the people that went all the way through the process.
287 00:30:49.320 ⇒ 00:30:50.290 Adam Kittleson: Instead of….
288 00:30:50.290 ⇒ 00:30:51.799 Robert Tseng: Yeah, you’re not seeing drop-off.
289 00:30:51.800 ⇒ 00:30:54.709 acromie: Right, right. That’s what we want to see.
290 00:30:55.020 ⇒ 00:30:55.570 Robert Tseng: Yeah.
291 00:30:56.660 ⇒ 00:31:10.260 acromie: So, like, that’s a good example of a report that we could help, you know, like, that… I think that’s a good example that shows, like, there’s some sort of disconnect in the data, or we’re not thinking about it right to pull the report together.
292 00:31:10.400 ⇒ 00:31:13.250 acromie: … Yeah.
293 00:31:13.380 ⇒ 00:31:15.420 acromie: Because I want to be able to see…
294 00:31:15.600 ⇒ 00:31:29.839 acromie: you know, eventually, we’re gonna start pulling up from Azure, you know, whether or not they actually attended the appointment. So now I want… I just want to be able to see the whole user journey from beginning to end, you know, as long as I have that connect… connected data.
295 00:31:29.840 ⇒ 00:31:40.629 acromie: I want to know, like, what did they do on the website before they got to the location? Did they look at multiple locations? And then, did that person end up scheduling? And then, you know, that kind of thing.
296 00:31:42.360 ⇒ 00:31:46.260 acromie: But right now, we definitely have this, like, drop between the two.
297 00:31:46.490 ⇒ 00:31:47.760 acromie: two places.
298 00:31:48.270 ⇒ 00:31:52.080 Robert Tseng: What are you going to be using for intakes moving forward, and …
299 00:31:52.380 ⇒ 00:31:54.400 Robert Tseng: Yeah, when we said that’s next week?
300 00:31:54.780 ⇒ 00:31:56.080 acromie: I’m sorry, what was that?
301 00:31:56.370 ⇒ 00:32:02.189 Robert Tseng: what are you using for, I guess, well, scheduling intake? I guess the flow is…
302 00:32:02.380 ⇒ 00:32:07.480 Robert Tseng: Yeah, I’m trying to, like, visualize the user flow, I don’t know if we have, like, documents, but, like, ….
303 00:32:07.480 ⇒ 00:32:09.889 acromie: I might have something I can send you.
304 00:32:09.890 ⇒ 00:32:10.510 Robert Tseng: Draw.
305 00:32:10.510 ⇒ 00:32:11.220 acromie: See if I finished it.
306 00:32:11.220 ⇒ 00:32:20.299 Robert Tseng: But it’s like, you schedule an appointment first, there’s no intake or anything that they fill out first, like, what’s the drop-off that you’re trying to see in the scheduling view in an ideal situation?
307 00:32:20.300 ⇒ 00:32:29.649 acromie: Yeah, Adam, do you want to just quick click through to online scheduling and show? Yeah. So, what happens is they go from our website over to Healthfully.
308 00:32:29.830 ⇒ 00:32:40.809 acromie: This is a location that’s not live yet. And then they click over to… yeah, go to a location that’s live, because then you’ll see all the data that’s being…
309 00:32:40.970 ⇒ 00:32:42.550 acromie: transmitted over.
310 00:32:42.880 ⇒ 00:32:44.980 acromie: And pulled in by Healthfully.
311 00:32:47.050 ⇒ 00:32:50.000 acromie: Lee’s Summit is a good one.
312 00:32:50.470 ⇒ 00:32:53.400 acromie: I think all the Colorados are alive already.
313 00:32:55.660 ⇒ 00:32:57.759 acromie: Lake Worth, yeah, that’s another one.
314 00:32:57.990 ⇒ 00:32:59.490 Adam Kittleson: Forever to load here.
315 00:33:05.400 ⇒ 00:33:09.150 Adam Kittleson: Okay, so they come to the page, then schedule online.
316 00:33:10.330 ⇒ 00:33:16.360 Adam Kittleson: And then, yeah, they can search by… primarily what…
317 00:33:16.650 ⇒ 00:33:19.269 Adam Kittleson: Kind of condition they’re trying to treat.
318 00:33:20.480 ⇒ 00:33:24.010 Adam Kittleson: … oh, yeah, I gotta add….
319 00:33:27.400 ⇒ 00:33:36.080 acromie: So basically, yeah, they’re doing searches, right? So we know they came from a specific location, because that gets appended to the, to the link.
320 00:33:36.660 ⇒ 00:33:55.359 acromie: There’s both the zip code for searching, and then we have referring location page. Then they go through this process of searching. Then, if they click in on someone’s schedule to look at, it or look at the bio, this is another event. So now we know that they’re actually looking at someone’s availability.
321 00:33:55.580 ⇒ 00:34:14.550 acromie: And then the next event is in the scheduling process. Once… I think it’s once they’ve clicked next on this, we now know who they are, that they’re start… they’re getting basically searched in the system to make sure they’re not an existing client, because right now only new clients can schedule through the form… through the website.
322 00:34:14.760 ⇒ 00:34:27.620 acromie: And then the final two events are that the patient was created in the EHR, and that the appointment was scheduled in the EHR. So, those are always generally even numbers.
323 00:34:27.940 ⇒ 00:34:31.310 acromie: … Unless there’s an error.
324 00:34:31.739 ⇒ 00:34:33.599 Adam Kittleson: Yeah, that’s these ones here.
325 00:34:35.659 ⇒ 00:34:41.570 acromie: So that’s kind of the flow. So we want to know, like, who’s dropping off in the form, are they…
326 00:34:41.639 ⇒ 00:34:59.400 acromie: Are people dropping off from this, you know, people are coming in through this page, and they’re dropping off more at this space, or these people from… that come in from this page are looking for these insurances, because we do get their search information and what they’re putting into the forms when they do that search.
327 00:35:01.200 ⇒ 00:35:01.780 Robert Tseng: Yeah.
328 00:35:04.080 ⇒ 00:35:05.590 Robert Tseng: Okay, …
329 00:35:06.260 ⇒ 00:35:10.990 Robert Tseng: Maybe the last question for now would be, so, from, like, yeah, I mean, I want to kind of…
330 00:35:12.430 ⇒ 00:35:18.659 Robert Tseng: build out some of these initial reports, too. It sounds like there’s already… it looks like there’s already some stuff there, so…
331 00:35:18.830 ⇒ 00:35:24.990 Robert Tseng: Wondering, like, what would be a good starting point. Like, I think we’ll start… I think we build as well, but,
332 00:35:25.320 ⇒ 00:35:27.720 Robert Tseng: Like, if you could just share, like.
333 00:35:28.890 ⇒ 00:35:37.660 Robert Tseng: I mean, I won’t edit anything directly, I’ll duplicate it and, like, kind of work on my own staging environment, I guess. But, yeah, I think that would be helpful, too.
334 00:35:39.170 ⇒ 00:35:42.430 Robert Tseng: Yeah, I think along the way, I’ll audit all the events.
335 00:35:42.490 ⇒ 00:35:49.889 Robert Tseng: Doesn’t look like there are that many events, you just have a lot of properties, and … so, I mean, yeah, figuring out what properties will save
336 00:35:49.940 ⇒ 00:36:03.250 Robert Tseng: event properties, what should persist as user properties, like, I can give you a point of view on that. Is there a tracking plan already, by the way? If not, I can also… I mean, I think that could be part of the exercise that I do.
337 00:36:03.990 ⇒ 00:36:09.119 acromie: Yeah, I think… I think we should probably set one up. I don’t know that we have anything fully…
338 00:36:09.260 ⇒ 00:36:10.720 acromie: documented.
339 00:36:10.910 ⇒ 00:36:11.820 Adam Kittleson: Nose.
340 00:36:11.820 ⇒ 00:36:15.659 Robert Tseng: Okay, that’s fine. That’ll be part of the, the audit process that I go through.
341 00:36:15.950 ⇒ 00:36:16.660 Robert Tseng: Yeah.
342 00:36:16.660 ⇒ 00:36:19.109 acromie: Awesome. So we’ll create one of ours.
343 00:36:21.630 ⇒ 00:36:28.470 Robert Tseng: Yeah, I think that sounds… Good for… to start. I’ve taken some notes here.
344 00:36:28.690 ⇒ 00:36:32.859 Robert Tseng: Yeah, so I guess once we kind of get both of you in Slack and
345 00:36:33.210 ⇒ 00:36:48.050 Robert Tseng: I mean, I’ll probably bring… I’ll bring Zora on for sure, and I’ll decide if I want to bring someone else in right now, but, yeah, I think I’ll just… I’ll give you, like, a questionnaire of any other questions that, you know, you can answer, and… Perfect. We’ll kind of just…
346 00:36:48.520 ⇒ 00:36:52.279 Robert Tseng: Gonna get access to some of the tools, and we can get started early.
347 00:36:52.760 ⇒ 00:36:53.410 acromie: Sounds good.
348 00:36:53.410 ⇒ 00:36:54.229 Robert Tseng: on Monday.
349 00:36:54.450 ⇒ 00:37:14.149 acromie: Great, awesome. And then, yeah, like, I think I would just love to have, like, a… as we get into this, like, what’s the timeline look like? Like, what are we… you know, just so I know, like, when are we… do we think we’ll get to the point where we’re getting those ad accounts figured out, or even if it’s a… a general idea?
350 00:37:14.310 ⇒ 00:37:15.180 acromie: ….
351 00:37:15.180 ⇒ 00:37:32.790 Robert Tseng: Yeah, that’s, like, the first thing I probably want to go after, because that seems pretty urgent. So, I mean, I think I could… we could get it done within a week. And then, yeah, I think, like, usually the kind of, like, slow amplitude audit, kind of tracking plan, like, event data design process, like, I would say 2 weeks is typically what I work with, so…
352 00:37:32.790 ⇒ 00:37:35.610 Robert Tseng: Yep. Yeah, so I think that’s, you know.
353 00:37:35.700 ⇒ 00:37:40.269 Robert Tseng: as far as rough estimates, that’s what we could expect. I think we could get a lot done in 2 weeks.
354 00:37:40.460 ⇒ 00:37:55.029 acromie: Awesome. Great. Love it. Yeah. Okay, well, great. Well, I’ll work with Adam to get him in Slack, and we will, look forward to getting started. Let me know if we need to jump on… if we need to plan any meetings, just because my schedule gets a little crazy real quick, so…
355 00:37:55.030 ⇒ 00:38:01.560 acromie: Want to get anything we need on the calendar? Otherwise, I know you’ve got auditing to do anyway, so….
356 00:38:01.560 ⇒ 00:38:09.870 Robert Tseng: Sure, yeah, I mean, we can tentatively just set something for the middle of the week next week, and just as a checkpoint, if we want to do that, while we’re sort of tall.
357 00:38:10.160 ⇒ 00:38:12.940 Robert Tseng: My calendar pulled up.
358 00:38:13.690 ⇒ 00:38:20.059 Robert Tseng: maybe Wednesday? I feel like we could probably have a good amount to talk about by Wednesday. Yeah.
359 00:38:20.060 ⇒ 00:38:21.310 acromie: What name do you want to look at?
360 00:38:22.260 ⇒ 00:38:26.420 Robert Tseng: Yeah, would you be able to do… I mean, I have, like.
361 00:38:27.410 ⇒ 00:38:38.200 Robert Tseng: I guess I’m Eastern. I mean, 12 to 12.30 Eastern is ideal, but I could also do, like, 1… 1.30 to 3 Eastern.
362 00:38:39.110 ⇒ 00:38:47.450 acromie: Let’s see, we have… let’s see… 1.30 is 12.30 our time.
363 00:38:47.980 ⇒ 00:38:50.150 acromie: How long do you want to put on? A half hour?
364 00:38:51.580 ⇒ 00:38:53.319 Robert Tseng: Yeah, and 30 minutes is good.
365 00:38:53.630 ⇒ 00:38:58.200 acromie: Could we do, 1.30 to 2 your time?
366 00:38:58.420 ⇒ 00:38:59.739 acromie: 12… does that work for you?
367 00:38:59.740 ⇒ 00:39:00.360 Robert Tseng: Okay.
368 00:39:01.400 ⇒ 00:39:01.980 Adam Kittleson: Yeah, thanks.
369 00:39:01.980 ⇒ 00:39:06.429 acromie: Schedule. So that’s 12… 1230 to 1 on ours, right before our other meeting.
370 00:39:07.830 ⇒ 00:39:08.850 Adam Kittleson: Yeah, that works.
371 00:39:09.320 ⇒ 00:39:16.030 Robert Tseng: Okay, cool. Well, I guess I’ll, I’ll just put a hold on that for now on my own calendar, and I’ll, …
372 00:39:16.570 ⇒ 00:39:19.060 Robert Tseng: I’ll add both, please.
373 00:39:20.920 ⇒ 00:39:27.229 Robert Tseng: Yeah, I don’t think I’m able to auto-populate it yet, so I’ll just… I’ll, like, add… actually add you to it, after this call.
374 00:39:27.230 ⇒ 00:39:28.090 acromie: Sounds good.
375 00:39:28.090 ⇒ 00:39:28.670 Robert Tseng: Yeah.
376 00:39:28.940 ⇒ 00:39:29.870 acromie: Awesome.
377 00:39:30.370 ⇒ 00:39:30.990 Robert Tseng: Okay.
378 00:39:31.240 ⇒ 00:39:34.239 acromie: Alright, well, exciting! We’re excited!
379 00:39:34.710 ⇒ 00:39:40.529 Robert Tseng: Yeah, I’m excited to get started. Yeah, good to meet both of you, and I’m sure we’ll be in touch soon.
380 00:39:40.530 ⇒ 00:39:41.990 acromie: You too. Alright, sounds good.
381 00:39:41.990 ⇒ 00:39:43.399 Adam Kittleson: Have a good weekend.