Meeting Title: Brainforge x Eden Health Project Sync Date: 2025-08-08 Meeting participants: Henry Zhao, Robert Tseng
WEBVTT
1 00:03:24.750 ⇒ 00:03:25.720 Robert Tseng: Hey, Henry.
2 00:03:29.700 ⇒ 00:03:31.070 Henry Zhao: Hey, Robert, how’s it going.
3 00:03:31.430 ⇒ 00:03:33.250 Robert Tseng: Good! How are you? You back.
4 00:03:33.500 ⇒ 00:03:34.279 Henry Zhao: Yeah, yeah.
5 00:03:34.900 ⇒ 00:03:35.730 Robert Tseng: Nice.
6 00:03:35.840 ⇒ 00:03:37.389 Henry Zhao: Do you want to talk about that first.st
7 00:03:38.647 ⇒ 00:03:46.962 Robert Tseng: Yeah. So I know you sent some messages, and I haven’t read through everything in too much detail yet. So yeah, I mean, I I guess.
8 00:03:47.400 ⇒ 00:03:59.310 Robert Tseng: I mean, I I could take my time and read through things and respond, but I I guess we’re yeah. I I literally just jumped in with very little context. So I I’m not not fully prepared from my side.
9 00:03:59.780 ⇒ 00:04:19.100 Henry Zhao: Yeah, I’d rather just talk to you in person. So I did a lot of reflecting this week. And obviously, 1st of all, thank you for your feedback. Secondly, I don’t think it was a surprise to me at all. I think starting Tuesday, I was already like mentally thinking about how I wanted to talk to you about you know how I wasn’t happy with you know what I’ve delivered so far yet, yet, either.
10 00:04:19.824 ⇒ 00:04:25.070 Henry Zhao: And I think the main thing that I wanted to point out is that I don’t think it actually had anything to do with the travel delays
11 00:04:25.518 ⇒ 00:04:30.679 Henry Zhao: like, that might be 5% of it. I would say 95% of it after reflecting, is.
12 00:04:31.470 ⇒ 00:04:38.299 Henry Zhao: I think I’m just still kind of ramping up and getting used to kind of the way things are run running at Brainforge. Yeah.
13 00:04:38.540 ⇒ 00:04:55.840 Henry Zhao: I think when I 1st joined, my expectation was that I would be helping with the Cdp. I would be helping with reporting those types of things. But then in week 2, I, you know, kind of got an idea of the business and learned from you that I would be eventually taking ownership and
14 00:04:55.980 ⇒ 00:05:15.449 Henry Zhao: so that’s when I started shifting gears towards that. And I think I’m pretty much prepared for that as of next week. But to get there, I think what happened was I was about to go out, so I thought you brought on Andrew to help out and away was our data engineer. So I thought, you know, let me rely on them to just kind of get my back while I’m out.
15 00:05:15.840 ⇒ 00:05:29.160 Henry Zhao: My expectation was that when I got back on Tuesday, what or Monday was that North Beam server side would at least be integrated either in segment or Etl some some Api code that he would use.
16 00:05:29.450 ⇒ 00:05:34.570 Henry Zhao: and that I would just make sure that everything was working fine, and I was hoping that Andrew would have implemented pinterest
17 00:05:35.100 ⇒ 00:05:44.710 Henry Zhao: Cappy and all that stuff, and I would just be vetting it. But that wasn’t the case, and I didn’t find out until I had a meeting with a wish on Tuesday, which was the 1st time he was available.
18 00:05:45.020 ⇒ 00:05:48.969 Henry Zhao: So by then I was like, now I need to do kind of like.
19 00:05:49.770 ⇒ 00:05:54.469 Henry Zhao: do some control and make sure that this doesn’t get dropped. So by then that’s Wednesday, right?
20 00:05:55.500 ⇒ 00:06:13.759 Henry Zhao: But by Wednesday I was like, there’s some knowledge gap here. I need to like, do some research on what’s the best way to to send data into North Beam as well as the customer. I/O stuff, follow up on this SMS consent stuff like there was just a lot going on, and I also had to watch things on missed meetings and then the default stuff. So now, by the time that’s done, it’s like Thursday, right?
21 00:06:13.760 ⇒ 00:06:32.270 Henry Zhao: Yeah. And then I missed our meeting because of the delay. So it sounds like I’m not communicating, but I think the main thing is just. I need to be more proactive. I needed to spend more time this week which I was able to do last night. And so, since I was able to spend a lot more time last night like doing research getting those linear tickets in a in a row, and like being
22 00:06:32.656 ⇒ 00:06:42.389 Henry Zhao: understood of, like the progress that was made last week when I was gone. What went wrong last week? I think I’m in a much better spot now to be able to take ownership moving forward and.
23 00:06:42.390 ⇒ 00:06:42.950 Robert Tseng: Okay.
24 00:06:42.950 ⇒ 00:06:48.150 Henry Zhao: Be able to meet deadlines or communicate them better if deadlines are being missed.
25 00:06:48.610 ⇒ 00:07:01.790 Henry Zhao: I also learned this week that linear is internal, and so we need to. And Amber told me we need to be communicating that to the client. If deadlines are gonna be missed which I haven’t been doing, because, 1st of all, I didn’t know what to say, because I was still catching up, and secondly.
26 00:07:02.580 ⇒ 00:07:16.180 Henry Zhao: I didn’t want to say the wrong thing, so I think it was a combination of those things, so I don’t think it was really related to the travel. I think it was the fact that I went out for a week in my onboarding, and while I’m still kind of understanding
27 00:07:16.420 ⇒ 00:07:19.589 Henry Zhao: what the role of Oasius, what the role of Andrew was, and.
28 00:07:19.590 ⇒ 00:07:20.070 Robert Tseng: Yeah.
29 00:07:20.070 ⇒ 00:07:21.779 Henry Zhao: You doing in terms of taking ownership.
30 00:07:22.370 ⇒ 00:07:23.020 Robert Tseng: Yeah.
31 00:07:23.280 ⇒ 00:07:37.100 Robert Tseng: okay, no. I think I appreciate the the self reflection. And yeah, I think that that makes sense. I think just to kind of add on to some of the things that you’re saying, and just to kind of add more color there. So yeah, I mean on the Andrew side. I think
32 00:07:38.360 ⇒ 00:07:49.189 Robert Tseng: I don’t think he was exactly what I expected, either, like I think, like you said it was like when you stepped out. I was expecting him in a wish to just be able to. I wasn’t, I mean, I knew that things would slow down, but like
33 00:07:49.330 ⇒ 00:07:54.339 Robert Tseng: I mean, we didn’t do anything other than Meta. So like, yeah, I think
34 00:07:54.460 ⇒ 00:08:05.809 Robert Tseng: there, I I do think that Andrew’s more of a specialist, and like not, he’s not owning any projects like. I think he’s made that clear. Whether, he said explicitly or not, he just
35 00:08:06.461 ⇒ 00:08:11.750 Robert Tseng: he’ll he’ll manage the communications which I think he’s good at, for whatever he does like. The
36 00:08:11.880 ⇒ 00:08:33.889 Robert Tseng: the clients are fine with the messages he sends. But it’s just like this talk like I think I don’t really think he’s like, really clear on what needs to be done. And so I do think he needs like a pro like a product owner, or like a someone that he’s reporting to, which was kind of me. For like, while you’re out, which was fine, we did have to make some adjustments to the the model. So that’s why the Meta thing got delayed.
37 00:08:34.134 ⇒ 00:08:55.869 Robert Tseng: Because what we had scoped out before you left we we push that that went live where we looked at that together, and then, you know, that was from Cutters direction. Then Mattesh looks at it, and he’s like, no, I don’t want that. I want something else. So there was like they were not clear what they wanted either. So we did need to have like a bit of more time to make the adjustment. I think the meta pixels are working perfectly fine now. So that’s okay.
38 00:08:56.281 ⇒ 00:08:58.908 Robert Tseng: But yeah, for a wish, like a wish is
39 00:08:59.730 ⇒ 00:09:06.359 Robert Tseng: because, like, yeah, I don’t. I don’t think he’s an expert in this stuff, either, like he can go. I do think
40 00:09:06.810 ⇒ 00:09:09.278 Robert Tseng: I do think he’s our most
41 00:09:11.090 ⇒ 00:09:17.510 Robert Tseng: self serviceable engineer like he can go and figure out anything is kind of how I’ve
42 00:09:17.680 ⇒ 00:09:35.679 Robert Tseng: deployed him on projects, whereas, like I feel like every other engineer, only stays within like a very limited scope, like a we’ll figure it out, but he may not. He may not know it, and he’s not good at asking for help. So like, I think that’s another another thing. So we kind of have to like, make the decision for him of like
43 00:09:36.260 ⇒ 00:09:48.819 Robert Tseng: what like I need you to look at at this and get to an answer like kind of make. Make it very clear for him, and if he doesn’t figure it out, then he’ll come back, and he’ll say he couldn’t figure it out. But he’s not gonna
44 00:09:49.300 ⇒ 00:10:08.999 Robert Tseng: which is like an opposite problem, I guess in a more precise way is to describe it is, I feel like of the other engineers. They’re like default. No, it’s like, Oh, I’ve never seen that before. I don’t know what to do. I’m not gonna take it on oasis like default. He’ll do anything, but he won’t tell you if he doesn’t know what he’s doing and so like, it’s kind of a balance like I
45 00:10:09.310 ⇒ 00:10:23.829 Robert Tseng: I I do want more people like a wish, but I also want a wish to better like escalate when he needs support, which I think he’s getting better at but I would rather deal with his situation than the other engineers, who default to saying No! To everything.
46 00:10:24.210 ⇒ 00:10:31.355 Henry Zhao: I’m kind of the opposite of a wish, right in the terms of. We talked about this before I left. It was that in the beginning. I like to be a little bit more cautious.
47 00:10:32.450 ⇒ 00:10:43.110 Henry Zhao: working Gtm. Or or segment, because I don’t want to break anything or so. That’s what I want to talk to you about today, I think, can work well with a wish, and that we kind of balance each other out a little bit.
48 00:10:43.110 ⇒ 00:10:43.765 Robert Tseng: Yeah.
49 00:10:44.629 ⇒ 00:11:01.779 Henry Zhao: What I want to do is just hold them a little bit more accountable of like. Let’s communicate more often. Let me know if there’s something you don’t know how to do, and let’s figure it out together and then, in the meantime, I want to just confirm some things with you today before moving forward, just to make sure I’m not breaking anything, and that I understand the client needs. Then I will be sure to communicate with the client
50 00:11:02.482 ⇒ 00:11:05.540 Henry Zhao: more clearly and more timely starting next week.
51 00:11:05.830 ⇒ 00:11:10.300 Robert Tseng: Okay, yeah. I mean, that sounds good. I’m sure. You know, week is what it is like. We’ll we’ll be able to
52 00:11:10.590 ⇒ 00:11:37.199 Robert Tseng: kind of have a better start next week. But yeah, everyone on that client like Annie Damalade. A wish like I mean, they’re all full time with us. So like I, don’t they? If you need them for anything they should. They should be able to find time with you like. It’s not like we’re having hours cap on them, like I do with like Andrew and other people. So yeah, like, I, I just want you to feel like you never have to like. Ask if you can get their time, like I think you know, if you’re
53 00:11:37.350 ⇒ 00:11:56.570 Robert Tseng: maybe it’ll come up to me at some point if they’re like, hey, Henry’s like bothering me too much, but like maybe I won’t hear that, for, like, you know, a week or 2 weeks but I would rather I would rather deal with that from them if they bring it up. But I don’t think that’s what would actually happen. So I just, you know, especially as you’re still getting familiar with things like.
54 00:11:56.660 ⇒ 00:12:25.080 Robert Tseng: Yeah, I think everyone is there to try to be helpful for you. And I think we kind of just in this remote setting. People don’t respond to anything unless you tag them directly like it is like a very the direct communicator gets rewarded more, and getting in having their way, which is not always the best, because not everyone is like that personality wise on our team. But yeah, I guess that’s that’s maybe like a cultural adjustment. You you might have to make along the way.
55 00:12:25.080 ⇒ 00:12:32.149 Henry Zhao: Exactly. So. I think just this week I’m culturally getting used to kind of what await does and what Andrew is go was supposed to do
56 00:12:32.579 ⇒ 00:12:37.049 Henry Zhao: so that I I didn’t really communicate much, because I didn’t want Eden to kind of.
57 00:12:37.460 ⇒ 00:12:41.410 Henry Zhao: I didn’t want it to seem like we didn’t know what was going on, or altogether
58 00:12:42.380 ⇒ 00:12:54.459 Henry Zhao: be a little bit more quiet and mysterious. And how I said, re- responded in that that group chat before. I think I’ll just take a little bit more hands on approach on things that maybe a waste doesn’t have the bandwidth or knowledge to do.
59 00:12:54.680 ⇒ 00:12:55.220 Robert Tseng: Yeah.
60 00:12:55.220 ⇒ 00:13:12.529 Henry Zhao: Some of that stuff I need to learn also. So I’m just using Chat, Gpt or Youtube to kind of learn these things. So like yesterday I was able to catch up on the tier 11 and edge layer stuff that Stuart had mentioned. So I was wondering, do you think we should use. So because for the north beam stuff, I want to get that done asap. But.
61 00:13:12.530 ⇒ 00:13:12.860 Robert Tseng: Yeah.
62 00:13:12.860 ⇒ 00:13:17.300 Henry Zhao: Keep telling me that there’s no way to do it via Api, or segment, or polytomic.
63 00:13:17.520 ⇒ 00:13:22.730 Henry Zhao: So Stuart’s recommendation was to use something like the edge layers, and
64 00:13:23.260 ⇒ 00:13:27.950 Henry Zhao: could I schedule a demo for rainforge to see if that solves our our issue?
65 00:13:28.530 ⇒ 00:13:31.139 Robert Tseng: Yeah, well, so I guess I I
66 00:13:31.730 ⇒ 00:13:33.479 Robert Tseng: I kind of view it as.
67 00:13:34.060 ⇒ 00:13:51.639 Robert Tseng: We could still do. Server to server without like stuff is like, my understanding is that you’re basically just using like cloudflare, or like setting up some other. You know, external dns thing before the
68 00:13:51.980 ⇒ 00:13:59.070 Robert Tseng: before, like the typical front end, like pixel fires. And so you’re able to capture more events upfront.
69 00:13:59.350 ⇒ 00:14:24.619 Robert Tseng: I I think that we can probably still do like I think we could roll it out in phases. I don’t think the edge layer thing is the 1st thing that we should jump to. I think there’s a more basic like North Beam server to server like approach which I tried to announce to the, to the team that that’s what we were. We were. Gonna go with that. I I feel like that’s still like the easier thing to go after first, st and then we can incrementally build from there. But I feel like.
70 00:14:24.980 ⇒ 00:14:47.570 Robert Tseng: because I feel like Stuart is just. You know, he’s just chat, gpt, and stuff as well, and he’s like, Oh, cool! This is like a random tech thing that I’ve never heard of before. You guys should do this. So I I would take whatever he says with a great salt like I. It may not actually be the right way to implement it, because that might be super slow for us, like there’s probably something intermediary that we could deliver. That’s better than what they have right now, but, like, maybe we can put that on our roadmap, for later.
71 00:14:47.730 ⇒ 00:15:00.589 Henry Zhao: I think I’d like to do both simultaneously. I’d like to get get a little bit more info on blot out just to see what that does. Yeah. So I want to do a demo on that. But they asked for a website. Do you think I should put brainforce.ai or Eden health
72 00:15:00.800 ⇒ 00:15:01.850 Henry Zhao: for the demo call.
73 00:15:02.360 ⇒ 00:15:04.781 Robert Tseng: Oh, yeah, we should do eaten health. Yeah.
74 00:15:05.200 ⇒ 00:15:08.753 Robert Tseng: Yeah. Or it’s I think it’s just called tryudin.com is kind of the
75 00:15:09.280 ⇒ 00:15:12.669 Robert Tseng: I didn’t know if it was okay for me to put their website on there on behalf of the client.
76 00:15:12.960 ⇒ 00:15:13.530 Robert Tseng: Oh, yeah.
77 00:15:13.530 ⇒ 00:15:20.020 Henry Zhao: For them to do research on like our needs. So I want to do that spontaneously while we figure out the other stuff. And maybe
78 00:15:20.440 ⇒ 00:15:24.509 Henry Zhao: Stuart know that there’s gonna be a few more weeks, that where we can get this rolled out.
79 00:15:24.790 ⇒ 00:15:26.640 Robert Tseng: Yeah, okay.
80 00:15:26.640 ⇒ 00:15:29.149 Henry Zhao: It sounds like it sounds like it’s so urgent. But
81 00:15:31.350 ⇒ 00:15:33.480 Henry Zhao: I don’t think there’s something we can get done like in a week.
82 00:15:33.740 ⇒ 00:15:41.289 Robert Tseng: Yeah, I mean, I’m hoping that there’s something north beam wise that we could patch for them for next week, like, I don’t know. My understanding is that
83 00:15:41.460 ⇒ 00:15:56.279 Robert Tseng: they feel like North theme is completely unreliable. It’s not working for whatever reason. So I I haven’t looked. I haven’t looked detail into it, but I will next week, because I don’t feel like we’ve made much progress there, but between that and I think
84 00:15:56.790 ⇒ 00:16:24.799 Robert Tseng: so we’ll I may also be around, so we’ll tag team on that like anything I can help with the Northeas stuff. But the the customer, I/OI think, is the big is is a big priority, just making sure that we have the cost kind of controlled there and then. Obviously, the SMS consent thing is is urgent for them, because they’re kind of out of compliance right now. So I think that’s that’s something that we need to, which I think is a good forcing function for pushing data from our customer data model into customer. I/O.
85 00:16:24.880 ⇒ 00:16:41.809 Robert Tseng: We may not have a bobby right now to run a campaign off of the model, but we’re able to at least show that, like the the right SMS consent, field is being pushed in. So like I kind of, I feel like it’s just a continuation of something that we were trying to do before. But we just didn’t have the right reason to do it. Then.
86 00:16:42.620 ⇒ 00:16:54.560 Henry Zhao: Okay, so real quick clarification question for customer. I/O, like us, put it pulling, putting in SMS consent as well as oasis profile data does that go into all these destinations, or just order, completed or just the reverse? Etl ones.
87 00:16:55.670 ⇒ 00:16:57.929 Robert Tseng: I think that’s just for for customer. I/O.
88 00:16:58.440 ⇒ 00:16:59.050 Henry Zhao: Yeah.
89 00:16:59.450 ⇒ 00:17:05.490 Robert Tseng: Yeah. Well, the customer, I currently
90 00:17:05.940 ⇒ 00:17:11.405 Robert Tseng: well, yeah, it would. It’s it would be reverse Etl into customer. I/O, right? So
91 00:17:12.561 ⇒ 00:17:33.339 Robert Tseng: we’ve. We’ve kind of briefly talked about like what the customer I/O’s current customer data model is like they’ve built something that’s in there. I’ve wanted. We’re basically trying to replace it with what what we have in bigquery with that was built out. So, yeah, and that will have SMS consent. It’ll be a lot leaner than what customer I/O has in customer. I’ll have something with.
92 00:17:33.460 ⇒ 00:17:39.630 Robert Tseng: you know, like 200 300 fields or whatever. And yeah, we we’re just we’re just trying to replace that.
93 00:17:39.630 ⇒ 00:17:42.049 Henry Zhao: So is that a new destination, in addition to these
94 00:17:43.550 ⇒ 00:17:45.189 Henry Zhao: of one of these existing ones.
95 00:17:45.360 ⇒ 00:17:55.199 Robert Tseng: I haven’t looked at the destination into customer I/O. In a while, so I don’t. I don’t really know what’s what we’re sending in there. I think we would just assume that.
96 00:17:55.500 ⇒ 00:18:00.309 Robert Tseng: Yeah, we we probably have to figure out like we’re replacing it or adding something new. I don’t know the question.
97 00:18:00.310 ⇒ 00:18:04.270 Henry Zhao: I don’t know what these are actually being used for. It was just Bobby that was using customer. I/O right.
98 00:18:04.270 ⇒ 00:18:05.179 Robert Tseng: Correct. Yeah.
99 00:18:05.790 ⇒ 00:18:06.890 Henry Zhao: So
100 00:18:07.460 ⇒ 00:18:16.009 Henry Zhao: okay, so I can look at this stuff and just say, like, if it doesn’t make sense to me, maybe we can remove it. Do I need to get one’s approval to like make suggestions or.
101 00:18:16.260 ⇒ 00:18:25.299 Robert Tseng: No, yeah. I mean, I think, just by default, it’s probably easier to just push something new. And then we can always delete later, because that way we don’t really break anything. He’s been used. Yeah. So maybe that’s.
102 00:18:25.300 ⇒ 00:18:28.849 Henry Zhao: Then, maybe in the future, we talk about like cutting away some of these.
103 00:18:30.160 ⇒ 00:18:33.509 Henry Zhao: Yeah, that’s gonna get rid of the usage over overages right.
104 00:18:34.395 ⇒ 00:18:51.659 Henry Zhao: which brings us to the next topic, which is the. So I’m just gonna go ahead and do this. I told you last time I didn’t want to break anything. But I’m just gonna go ahead and do it. Okay. But that leads us to the discussion of the mix panel overages. So what is the team actually using mixed panel for right now. So I under. So I try to understand what I’m not supposed to not break.
105 00:18:52.020 ⇒ 00:18:56.980 Robert Tseng: Yeah, I’ll show you quickly on mixed panel side.
106 00:19:03.560 ⇒ 00:19:04.660 Robert Tseng: room.
107 00:19:08.470 ⇒ 00:19:09.180 Robert Tseng: Hmm.
108 00:19:11.580 ⇒ 00:19:17.239 Robert Tseng: Sorry I have like a bunch of mixed panel accounts for different clients have to like log out log in.
109 00:19:17.240 ⇒ 00:19:20.550 Henry Zhao: While. Yeah, while you do that, let me organize the other things I need to talk to you about today.
110 00:19:21.410 ⇒ 00:19:22.639 Henry Zhao: 400 topics.
111 00:19:23.870 ⇒ 00:19:25.130 Robert Tseng: No worries.
112 00:19:25.130 ⇒ 00:19:26.369 Henry Zhao: Okay. Robert. Uten.
113 00:19:27.398 ⇒ 00:19:29.849 Robert Tseng: Okay, so I’ll share my screen.
114 00:19:35.300 ⇒ 00:19:36.820 Robert Tseng: Okay, so
115 00:19:39.000 ⇒ 00:19:56.700 Robert Tseng: this is their mixed panel environment. Yeah. So they have 2 projects. They’ve eaten and new Eden. Don’t use new Eden. Just use Eden. You know, this is all stuff that’s just coming straight from segment, you know. Web flow data. So all the page views. So I set up a few boards for them. One is like
116 00:19:56.700 ⇒ 00:20:09.970 Robert Tseng: website intake. So this is what the brand team uses. They get to. Just look at. You know, site conversion trends and stuff like that, you know, who’s going like what blogs like, you know, it’s just like your web analytics. This is like Google analytics pretty much
117 00:20:10.321 ⇒ 00:20:14.120 Robert Tseng: but just like with more granularity that they could do in in Ga 4
118 00:20:14.967 ⇒ 00:20:18.850 Robert Tseng: and then I think overview wise.
119 00:20:19.240 ⇒ 00:20:46.810 Robert Tseng: This is what they used to use like. This was the only report they had before I came. And like, before, we built out the data warehousing or everything. So yeah, before the like. Adam the CEO. He was the one who brought mixed panel in. He was very gung ho! About mixed panel, and they only had mixed panel segment. So like they were just using this to basically run their business like, just understand like orders. And obviously, this is just not reliable, this all this is just data that comes off of the
120 00:20:46.950 ⇒ 00:21:04.279 Robert Tseng: you know, the the Gtm stuff that goes on web flow that goes from segment, and a lot of it doesn’t have the same checks that we do in our warehouse. So their orders are over, reported the sign ups are overported. There’s, I think, just overall. Transactional data is not reliable in in mixed out.
121 00:21:04.280 ⇒ 00:21:09.180 Henry Zhao: Okay, so is the plan for all to get rid of mixed panel and just build these in data studio. For example.
122 00:21:11.000 ⇒ 00:21:29.219 Robert Tseng: I mean we could, but I think Adam’s pretty like insistent that he wants to keep mixed panel, and he wants to. You make it more useful. I think they’re paying a lot for mixed panel, for the fact that nobody uses it other than the brand team, which is not really a revenue generating like part of the company. So yeah, I think.
123 00:21:30.040 ⇒ 00:21:53.740 Robert Tseng: But I think what we have now like, I I would trust, like the web traffic data and everything. And there, there’s some more tracking that we need to do. I’ve built tracking plans before, and we can do some of the telemetry to add additional events. But yeah, I think the directive is really just to get mixed panel into a usable place. I do think that like what I saw from like
124 00:21:54.180 ⇒ 00:21:58.639 Robert Tseng: the billing and everything like it just concern me.
125 00:21:59.090 ⇒ 00:22:04.992 Robert Tseng: Yeah, it concerned me because it’s built on Mtus or no. It’s no, it’s built on events. Tracks
126 00:22:05.480 ⇒ 00:22:11.150 Robert Tseng: already scaled back some of this stuff, but like, because before they.
127 00:22:11.150 ⇒ 00:22:11.639 Henry Zhao: What do you want me.
128 00:22:11.640 ⇒ 00:22:16.350 Robert Tseng: Even like page scroll events and stuff into there. So I already deleted some of it.
129 00:22:17.070 ⇒ 00:22:17.930 Henry Zhao: So you don’t sorry.
130 00:22:17.930 ⇒ 00:22:20.090 Henry Zhao: The events that are not in the dashboards.
131 00:22:21.200 ⇒ 00:22:37.299 Robert Tseng: Yeah, well, I I think we just. We have to let them know, like what is mixed panel. For what can they actually reliably report there. What should they go to tableau for? And like, I don’t think we’ve really communicated that well across across the team. So
132 00:22:38.320 ⇒ 00:22:50.550 Henry Zhao: So my next step maybe be to ask the team. You can tell me who to ask but W. What is being used in mixed panel right now, and I should just get rid of the events that are not being used in any of these used charts.
133 00:22:51.590 ⇒ 00:22:53.680 Robert Tseng: Yeah, I
134 00:22:53.830 ⇒ 00:23:00.790 Robert Tseng: I don’t think anybody would tell you the answer, because most people, if you look at the usage data, no one’s really doing anything in here?
135 00:23:02.750 ⇒ 00:23:06.149 Henry Zhao: So no, no, we just team. And for Adam.
136 00:23:07.480 ⇒ 00:23:25.409 Robert Tseng: Yeah. Well, me, Adam’s vision is that the marketing team can answer a lot of their own questions if they just came into mixed panel and built it out themselves like he has this, like the self service kind of vision, or whatever. I don’t know how realistic that is. Cause I don’t. I don’t really know. Like
137 00:23:25.990 ⇒ 00:23:27.350 Robert Tseng: what we would.
138 00:23:27.520 ⇒ 00:23:29.380 Robert Tseng: I mean. I I
139 00:23:29.990 ⇒ 00:23:44.859 Robert Tseng: it’s been a while since I’ve come back to mix. I mean we we I’ve written out like a mixed panel, data strategy and kind of like what the phase rollout would be and everything. But I think that’s kind of that’s a bit stale like I feel like it needs to be adapted to what? What could we reasonably do now?
140 00:23:45.090 ⇒ 00:24:02.669 Robert Tseng: I I I just think that our customer data is good. Now, I want that model to be accessible in mixed panel, and if you do that, then you can. You can look at a lot of the you get have a lot of more interesting customer segmentation that’s easier to do in in mixed panel. So
141 00:24:02.790 ⇒ 00:24:14.367 Robert Tseng: I I feel like if we just get oasis model into mixed panel. I think that would help us create a lot of interesting segments, and that that would that would make some of this reporting
142 00:24:14.920 ⇒ 00:24:23.239 Robert Tseng: more, more valuable for for the team rather than just looking at it, you know, generic or like general, like traffic trends, or whatever.
143 00:24:23.800 ⇒ 00:24:29.579 Henry Zhao: Well, that’s separate, right? So that’s separate from the task that says, reduce overage cost, optimize sentiment data routing to mix panel.
144 00:24:30.060 ⇒ 00:24:40.360 Robert Tseng: Yeah, so yeah, right now, it’s like, well, if there’s anything that we can cut out like we should cut it out. And then we can kind of build it back up from there. So I think that’s kind of that that makes sense to me.
145 00:24:40.520 ⇒ 00:24:48.460 Henry Zhao: Okay. So for now I don’t need to talk to Adam or anything. I just need to go into the events that are being sent to Mixpanel and just get rid of things like the page scroll.
146 00:24:48.750 ⇒ 00:24:51.600 Henry Zhao: or things that are not in dashboards here, but are maybe in bigquery.
147 00:24:51.600 ⇒ 00:25:01.669 Robert Tseng: They scroll already took out so. But there’s like a bunch of I don’t know. There seems like there’s probably events I don’t know, so a lot of email events, I think that’s like, kind of a like a big
148 00:25:02.620 ⇒ 00:25:10.290 Robert Tseng: if you have, you just look through it. A lot of it is, it’s mostly email events. So then we’re firing a lot of repeat, identify events. There’s like.
149 00:25:11.360 ⇒ 00:25:13.967 Robert Tseng: probably 3 identified events per user, like.
150 00:25:14.340 ⇒ 00:25:17.499 Henry Zhao: I don’t think identifies build as an event right?
151 00:25:17.750 ⇒ 00:25:23.680 Robert Tseng: Oh, it’s not okay, cool? Well, then, yeah, I think the email events are the most common. So
152 00:25:24.380 ⇒ 00:25:30.049 Robert Tseng: it’s. And it’s like, Do we really need email events in a mixed panel. If we have that in customer, I already.
153 00:25:30.270 ⇒ 00:25:31.639 Henry Zhao: Okay. Understood.
154 00:25:31.970 ⇒ 00:25:32.610 Robert Tseng: Yeah.
155 00:25:32.860 ⇒ 00:25:38.830 Henry Zhao: Okay, I might just ask message you in slack after this, just to make sure that my, what I’m gonna do next is
156 00:25:39.320 ⇒ 00:25:42.899 Henry Zhao: right way. Okay? And then just the last thing is.
157 00:25:43.200 ⇒ 00:25:46.539 Henry Zhao: I just asked you if Checkout started is failing in segment.
158 00:25:47.786 ⇒ 00:25:51.653 Henry Zhao: So nobody is using that one hook for reporting right. I just don’t want.
159 00:25:51.930 ⇒ 00:25:52.819 Robert Tseng: No one’s using it.
160 00:25:53.690 ⇒ 00:25:58.639 Henry Zhao: Okay, so let me just ignore that for now and then, maybe future. When we do like a segment
161 00:26:00.380 ⇒ 00:26:04.479 Henry Zhao: the audit, we can figure out what are the web hooks that are not working, and if we even need them.
162 00:26:04.880 ⇒ 00:26:29.159 Robert Tseng: Yeah, I mean, honestly, we’re just talking through this. I feel like that’s an easy way for mixed panels, just like cut the customer. I/O events, we already do email kind of like reporting in customer. I/O, so anything with like lifecycle and email, just keep that a customer, I/O and don’t let the same events go into mixed panel that would cut the mix panel bill, and that would make it very clear like what like where to split people off into yeah.
163 00:26:29.510 ⇒ 00:26:37.822 Henry Zhao: What I’ll probably do is I’ll have that list my recommendation, and then just run it by you real quick, and then see like, should I talk to Adam and say, this is our recommendation, or what? The next step is just
164 00:26:38.400 ⇒ 00:26:39.220 Henry Zhao: okay.
165 00:26:39.550 ⇒ 00:26:48.799 Henry Zhao: And then the last thing we have 2 more minutes is just finalizing our discussion on kind of the feedback from this week it’s just since I was contracted at 20 HA week.
166 00:26:49.100 ⇒ 00:26:49.530 Robert Tseng: Oh, yeah.
167 00:26:49.530 ⇒ 00:26:54.096 Henry Zhao: Heads up that I won’t be able to make like every meeting in the next 2 months.
168 00:26:54.350 ⇒ 00:26:55.060 Robert Tseng: Yeah.
169 00:26:55.060 ⇒ 00:27:07.450 Henry Zhao: Because there were plans that I’d made, you know, before even, you know, even meeting you in New York. But I will be sure to communicate that with you, and also my calendar is always up to date. I’ve already blocked the next few weeks, just to make sure that
170 00:27:07.978 ⇒ 00:27:10.719 Henry Zhao: and I’ve declined the meetings that I won’t be able to attend.
171 00:27:10.930 ⇒ 00:27:15.463 Robert Tseng: Okay, yeah, that’s that’s fine. I don’t mind you decline meetings. Yeah, I mean, I guess.
172 00:27:16.140 ⇒ 00:27:17.580 Robert Tseng: yeah. Obviously.
173 00:27:18.020 ⇒ 00:27:31.730 Robert Tseng: Well, I was hoping to make the decision of like, Oh, do we want to, you know, increase your hours, and I I don’t know what kind of you know. Expand your capacity. But maybe you let us know when you want to have that conversation, then if you want to stay.
174 00:27:31.730 ⇒ 00:27:34.639 Henry Zhao: Next week. See if things are improved, and I think they will be. I think.
175 00:27:34.640 ⇒ 00:27:36.010 Robert Tseng: Okay. Yeah.
176 00:27:36.010 ⇒ 00:27:39.877 Henry Zhao: Then you know the normal me you were talking about is so.
177 00:27:40.200 ⇒ 00:27:43.179 Robert Tseng: Okay? Alright. Well, yeah. Then we can. We can save that conversation. Yeah.
178 00:27:43.180 ⇒ 00:27:46.619 Henry Zhao: Yeah, I just need these few days to catch up. I think next week you’ll see the difference.
179 00:27:46.880 ⇒ 00:27:47.989 Robert Tseng: Okay. Cool.
180 00:27:48.190 ⇒ 00:27:49.179 Robert Tseng: Sounds good.
181 00:27:49.310 ⇒ 00:27:53.346 Henry Zhao: All right. I just need to catch up on you. Didn’t know I was focused a lot on default yesterday and today.
182 00:27:53.730 ⇒ 00:27:54.450 Robert Tseng: Okay.
183 00:27:54.660 ⇒ 00:27:56.110 Henry Zhao: On Eden. And yeah.
184 00:27:56.720 ⇒ 00:27:58.899 Robert Tseng: Alright, thanks, Henry, appreciate it.