Meeting Title: Default App Data Deduplication Sync Date: 2025-09-11 Meeting participants: vishalag, Henry Zhao, Shreya Chowdhury


WEBVTT

1 00:01:00.050 00:01:01.810 Henry Zhao: Hey Vishal, how’s it going?

2 00:01:05.650 00:01:07.510 vishalag: Doing good. How’s it going on your end?

3 00:01:08.190 00:01:13.029 Henry Zhao: Good, thank you. I think I invited one more person from the team, so that you can meet,

4 00:01:13.370 00:01:14.710 Henry Zhao: He’ll be helping me out.

5 00:01:17.120 00:01:17.760 vishalag: Okay.

6 00:01:19.570 00:01:20.970 Henry Zhao: We’ll just see if she’s coming.

7 00:01:25.380 00:01:29.100 vishalag: I added the insert ID, I mean, it’s still duplicating, so I think it sounds

8 00:01:30.200 00:01:32.670 vishalag: Yep, I think it’s something… I don’t know.

9 00:01:32.670 00:01:34.100 Henry Zhao: Let me see that.

10 00:01:34.700 00:01:37.429 Henry Zhao: Let me see the second part of the instructions.

11 00:01:39.100 00:01:43.400 vishalag: No, I think I have a strong feeling that it’s from Segment, because…

12 00:01:43.590 00:01:46.110 vishalag: If you look at the event properties.

13 00:01:46.290 00:01:49.740 vishalag: The event ID is different, all the data is same.

14 00:01:50.610 00:01:52.449 vishalag: I can show you quickly.

15 00:01:52.450 00:01:55.820 Henry Zhao: We should be able to deduplicate it, because of the event ID.

16 00:01:57.540 00:02:00.309 vishalag: Yeah, just let me know if you can see my screen.

17 00:02:01.160 00:02:05.230 vishalag: So you see this? This is, like, I just pushed the…

18 00:02:05.590 00:02:07.850 vishalag: Inside ID thing, I think, like.

19 00:02:08.500 00:02:12.580 vishalag: 45 minutes ago or something. So, here is the insert ID.

20 00:02:12.670 00:02:13.919 Henry Zhao: Okay,

21 00:02:14.350 00:02:16.140 vishalag: This, and this are same.

22 00:02:16.620 00:02:17.310 vishalag: Okay?

23 00:02:18.160 00:02:19.080 vishalag: Make a good suit.

24 00:02:19.080 00:02:23.320 Henry Zhao: Why is an amplitude smart enough to know to deduplicate those? You know?

25 00:02:24.040 00:02:36.159 vishalag: I don’t know, I mean, you told me instead of day, I was not aware of it, and then… but you see, event add is different for both of them, so I have a gut feeling, because in segment, segment creates event, you know, like, in the code base.

26 00:02:36.740 00:02:40.839 vishalag: Like, the segment event, which is, like, a property from their end.

27 00:02:41.440 00:02:44.130 vishalag: So, TLDR, I think.

28 00:02:44.430 00:02:53.150 vishalag: segment, event, event ID. This is segment, events, event ID, okay? So I think you have to do some changes on segment side. I have a very strong feeling, because, see.

29 00:02:53.380 00:03:04.580 vishalag: before we fixed the default analytics thing, see, earlier also we were having twice, input was twice, default analytics was twice, so I think it’s strongly, I feel that it’s from segment side.

30 00:03:05.140 00:03:11.740 vishalag: So… Or, I don’t know, man, like, honestly, I’m not a power user of either segment or amplitude.

31 00:03:12.380 00:03:13.490 vishalag: You are the expert.

32 00:03:14.110 00:03:14.650 vishalag: Sweet.

33 00:03:20.050 00:03:23.089 Henry Zhao: But that’s, that’s the thing, though, the, the,

34 00:03:23.320 00:03:35.229 Henry Zhao: the help article from Amplitude says, if two identical events fire within the same second, we count only one. So they have the same insert ID, and the same event, and the same second, so it should only count one, even though the event ID is different.

35 00:03:36.430 00:03:37.969 vishalag: So let me…

36 00:03:39.710 00:03:48.520 Henry Zhao: Let me do talk to a person and just continue the investigation. I’ll do it with segment and amplitude, because I’ve already checked segment, I couldn’t figure out why it’s duplicating. Hi, Shreya.

37 00:03:48.880 00:03:51.119 Henry Zhao: So I’m gonna need some help from their supports.

38 00:03:53.140 00:03:56.880 vishalag: Yeah, I mean, it’s pretty weird. I mean, I strongly feel that

39 00:03:57.010 00:04:03.310 vishalag: It’s from segment side, because as I told you, the event ID is segment’s event ID, right? So…

40 00:04:03.680 00:04:05.280 vishalag: I think segment…

41 00:04:05.450 00:04:14.069 vishalag: on the spot, it’s sending two times or something, I don’t know, honestly. Like, you guys know Segment or Amplitude way better, but I kind of feel that

42 00:04:14.300 00:04:19.079 vishalag: Amplitude will say that The event height is different, right?

43 00:04:23.039 00:04:28.739 Henry Zhao: Okay, let me work on that and let you know what I find. In the meantime, I will continue to monitor

44 00:04:30.199 00:04:33.709 Henry Zhao: Let me show you what my amplitude looks like.

45 00:04:34.620 00:04:35.230 vishalag: Yeah.

46 00:04:35.970 00:04:37.960 Henry Zhao: I think it looks a little different from yours, I don’t know why.

47 00:04:38.910 00:04:42.400 vishalag: No, I think you must be looking in the different space,

48 00:04:42.700 00:04:46.780 vishalag: I mean, I generally go to the home section and data, that’s it.

49 00:04:47.490 00:04:48.960 vishalag: Or live events.

50 00:04:50.800 00:04:52.280 Henry Zhao: Yes, I go to events.

51 00:04:54.570 00:04:58.140 Henry Zhao: And then, clicking on Meeting Booked…

52 00:05:00.510 00:05:01.170 vishalag: Hmm.

53 00:05:02.700 00:05:04.490 Henry Zhao: Do I close this without clicking?

54 00:05:04.770 00:05:11.779 Henry Zhao: It looks like it’s getting better now after you made it live. The… but see, my insert ID is also unexpected, and I can’t make it expected.

55 00:05:13.490 00:05:14.210 Henry Zhao: You see that?

56 00:05:14.760 00:05:16.759 Henry Zhao: Like, there’s nothing I can click.

57 00:05:17.690 00:05:21.049 vishalag: Click on the… click on the left side of… inside of the checkbox.

58 00:05:23.130 00:05:26.210 vishalag: Yeah, and then click on Add Property, top right.

59 00:05:27.050 00:05:27.900 Henry Zhao: Okay.

60 00:05:29.900 00:05:34.659 vishalag: No, I remember doing this somewhere, and I’d close it out.

61 00:05:36.230 00:05:42.980 vishalag: I mean, it’s basically coming because previously lots of events were not having this, right? Now it’s there.

62 00:05:43.740 00:05:44.440 vishalag: So…

63 00:05:44.440 00:05:46.019 Henry Zhao: just creating a certain ID like this.

64 00:05:53.120 00:05:55.149 vishalag: I don’t know, dude. I mean…

65 00:05:56.230 00:06:01.969 vishalag: like, what does it say, the exclamation mark? It says 54.

66 00:06:01.970 00:06:04.230 Henry Zhao: What’s unexpected property.

67 00:06:08.310 00:06:13.030 vishalag: Because I did this, I remember doing this. I fixed it for one of the events.

68 00:06:14.260 00:06:16.499 Henry Zhao: Why is it different from mine and yours?

69 00:06:17.020 00:06:18.700 vishalag: I think it should be the same.

70 00:06:20.110 00:06:23.019 vishalag: It can’t be different. We gave you full access.

71 00:06:24.330 00:06:36.630 Henry Zhao: Can you… because this didn’t even show up until you made it expected this morning. So when you added lead ID, this entry didn’t show on a few days ago, right? So you created Lead ID a few days ago, and all I was seeing was this.

72 00:06:36.780 00:06:43.869 Henry Zhao: So, to me, it looks like Vishal didn’t do anything, but then when you made it expected this morning, I think that’s when this appeared for me.

73 00:06:47.430 00:06:51.780 Henry Zhao: Whereas other events, like, if they’re unexpected, I can click and add it very easily.

74 00:06:53.450 00:06:58.959 Henry Zhao: new properties for some reason. To me, they’re showing as having issues, but for you, it’s okay.

75 00:07:03.850 00:07:05.380 vishalag: Seriously.

76 00:07:05.380 00:07:08.830 Henry Zhao: Weird, right? But it looks like it’s fixed. The red is gone now, right? So…

77 00:07:11.250 00:07:11.930 vishalag: Yeah, I mean.

78 00:07:11.930 00:07:12.290 Henry Zhao: So I work.

79 00:07:12.290 00:07:12.860 vishalag: Or what?

80 00:07:12.860 00:07:15.309 Henry Zhao: If I left the meeting booked, I wonder if it drops off.

81 00:07:16.390 00:07:22.779 vishalag: I guess the overtime it will get fixed, right? Like, if you look at the 14-day window, it will get fixed, because…

82 00:07:23.030 00:07:27.590 vishalag: Amplitude must feel that it’s a different kind of data coming in or something.

83 00:07:28.090 00:07:31.780 vishalag: Like, they are unexpectedly getting some key-value pairs.

84 00:07:33.010 00:07:35.639 Henry Zhao: Why am I not even able to find a meeting booked anymore?

85 00:07:40.240 00:07:41.910 Henry Zhao: What’s going on?

86 00:07:42.460 00:07:44.319 vishalag: I think you have to do any event, right?

87 00:07:44.500 00:07:46.290 vishalag: First, you have to select event type.

88 00:07:48.450 00:07:49.870 vishalag: Select an event.

89 00:08:02.220 00:08:04.160 Henry Zhao: supposed to show up here when I do a meeting.

90 00:08:05.050 00:08:06.830 Henry Zhao: Am I in some, like, different…

91 00:08:08.400 00:08:11.630 Henry Zhao: Are you… are we maybe in dev, actually?

92 00:08:12.310 00:08:16.560 vishalag: Doesn’t really matter, I mean, it’s a standard amplitude dashboard, I think.

93 00:08:16.830 00:08:19.930 vishalag: I don’t know, you might have to reach out to Amplitude.

94 00:08:20.140 00:08:21.819 Henry Zhao: Or I don’t know how to…

95 00:08:23.590 00:08:24.849 vishalag: It’s pretty weird, dude.

96 00:08:26.110 00:08:27.220 Henry Zhao: Very weird, right?

97 00:08:27.500 00:08:29.890 Henry Zhao: Let me add content here, new chart.

98 00:08:31.820 00:08:34.650 Henry Zhao: Now it’s here, like, what just happened?

99 00:08:35.530 00:08:36.840 Henry Zhao: The meeting booked.

100 00:08:37.669 00:08:39.660 Henry Zhao: I want to count distinct…

101 00:08:43.080 00:08:45.609 Henry Zhao: Property values for user…

102 00:08:48.250 00:08:51.069 Henry Zhao: I don’t know, this is grouped by a lead ID for now, just see if it works.

103 00:08:57.380 00:09:02.540 Henry Zhao: So it works, there’s not, like, a complete drop-off in these days when it was red, so I guess it’s okay, right?

104 00:09:02.960 00:09:06.310 vishalag: I think that red was just saying the lead ID was unexpected for my end.

105 00:09:06.330 00:09:08.210 Henry Zhao: But the meeting booked looks like it’s…

106 00:09:09.240 00:09:09.940 vishalag: Yep.

107 00:09:10.890 00:09:13.660 Henry Zhao: I mean… Stop grouping by.

108 00:09:17.280 00:09:17.990 Henry Zhao: That’s weird.

109 00:09:31.910 00:09:33.110 Henry Zhao: Event totals.

110 00:09:35.210 00:09:39.999 Henry Zhao: This probably dropped off because of weekend, so I think that’s okay. So yeah, it looks fine to me.

111 00:09:40.340 00:09:42.709 Henry Zhao: Form submission, let me just double check.

112 00:09:42.830 00:09:46.249 Henry Zhao: Form submitted, right? Or is it form submission? Form submission?

113 00:09:46.670 00:09:47.850 vishalag: problems removed from that.

114 00:09:50.620 00:09:52.810 Henry Zhao: So you’re saying form submission and…

115 00:09:53.620 00:09:57.569 Henry Zhao: Meeting booked are both a lead being created for default.

116 00:10:00.680 00:10:03.170 vishalag: not lead-created, I mean, like…

117 00:10:03.500 00:10:17.260 vishalag: See, form submission definitely creates a lead, and that lead can be used for booking a meeting, but there is a use case where a meeting can be directly booked, and on the spot, a new lead can also be generated.

118 00:10:17.690 00:10:36.870 vishalag: So let’s say, like, I can share you a Calendly link, right? So default also supports sharing direct scheduler link. In that, also, Henry will be treated as a new lead. But if, let’s say, I ask you to fill a form, and then our workflow engine basically over, let’s say, as per the node, shows you a

119 00:10:36.980 00:10:54.320 vishalag: a scheduler, then as per the config, if we use the previous lead ID, so then a form submission lead ID will be reused. So, to answer your question, form submission will definitely create a new lead ID, display… like, the scheduler meeting booked may or may not use the existing lead ID.

120 00:10:55.920 00:10:59.209 Henry Zhao: So, if I want to know the total leads created.

121 00:10:59.460 00:11:05.030 Henry Zhao: Do I look at the distinct lead IDs from form submission and meeting booked, or just one of those?

122 00:11:05.250 00:11:05.800 vishalag: Both, right?

123 00:11:05.800 00:11:06.330 Henry Zhao: Okay.

124 00:11:08.420 00:11:13.810 Henry Zhao: So yeah, just combine those two events and count the distinct lead IDs, and I should have the number of new leads.

125 00:11:14.420 00:11:15.990 vishalag: Correct. Exactly.

126 00:11:16.470 00:11:17.110 Henry Zhao: Okay.

127 00:11:17.780 00:11:23.560 Henry Zhao: Okay, so far that’s clear, and these events look good now. So… I have lead ID, I’ll figure out the insert ID part.

128 00:11:24.570 00:11:27.799 Henry Zhao: Yeah, I mean, security is being added, so, like…

129 00:11:27.800 00:11:32.310 vishalag: an hour ago, so, I mean, you can check it out, and

130 00:11:32.810 00:11:38.279 vishalag: I, like, overall, whatever discussion you have with the Amplitude team, my gut feeling says it’s from segments.

131 00:11:38.550 00:11:39.919 vishalag: Issue. Okay.

132 00:11:40.040 00:11:43.020 vishalag: Because it was pre-existing also, right?

133 00:11:43.760 00:11:44.370 Henry Zhao: Yeah.

134 00:11:44.750 00:11:47.560 vishalag: The same data, timestamp, everything.

135 00:11:48.020 00:11:51.980 vishalag: So yeah, you can check it out. Let me know if I can help in any way.

136 00:11:53.240 00:12:02.740 Henry Zhao: Yeah, I’m sure that it is coming from segment, but I was hoping that Amplitude had a way to deduplicate it by ignoring the event ID, like, by just looking at the other three, which are enough to say this is the same thing.

137 00:12:03.150 00:12:04.830 Henry Zhao: That’s what I’m trying to figure out from Amplitude.

138 00:12:05.290 00:12:05.880 Henry Zhao: Yeah.

139 00:12:05.880 00:12:09.419 vishalag: And we will most probably tell you that the event guide is different.

140 00:12:10.070 00:12:10.890 Henry Zhao: Like…

141 00:12:11.180 00:12:12.660 vishalag: They will tell you that.

142 00:12:12.660 00:12:16.649 Henry Zhao: Like, in the code, just not grouped by that, right? Like, it’s so simple.

143 00:12:18.000 00:12:23.310 vishalag: Yeah, but then you have to do it manually for all of them, right? Like, it will be too much of effort for you, I guess.

144 00:12:25.330 00:12:26.820 Henry Zhao: Yeah, okay.

145 00:12:27.200 00:12:29.639 Henry Zhao: Shreya, did you have any questions for Vishal?

146 00:12:30.650 00:12:45.450 Shreya Chowdhury: No, I didn’t have any questions. Sorry, I’m coming in from not a whole lot of context into the data, I just onboarded onto this, like, last week, and got a ticket for it yesterday that Henry has been helping out with.

147 00:12:45.540 00:12:55.329 Shreya Chowdhury: Yeah, so we’re just hoping to make some progress on that ticket. He was telling me a little bit about, deduplicating the data yesterday, so… yeah.

148 00:12:55.930 00:13:12.900 Henry Zhao: Yeah, and then the next thing we want from Vishal is to implement, like, activity inside the default app, right? So any of the tabs being clicked, so that we can have active usage counts in the app. Because I think what Caitlin wants to know is how many people are actually using it, and right now we don’t know, because we only have

149 00:13:13.000 00:13:16.559 Henry Zhao: Meeting booked, form submission, just, like, a few of the events.

150 00:13:17.340 00:13:29.099 Henry Zhao: So we want to know, like, the person that’s actually using default, how many active events are they doing? Like, what are… are they clicking dashboards? Are they creating meeting types? Like, what are they actually doing? Because for them to use the platform.

151 00:13:29.600 00:13:30.350 Shreya Chowdhury: Okay.

152 00:13:31.080 00:13:34.449 Shreya Chowdhury: Okay, cool. I think it would be really useful if…

153 00:13:34.450 00:13:52.310 Shreya Chowdhury: I’m going to probably have a chat with Utem about it later, but yeah, if you… if you could send me, like, a quick update on, like, the main, like, couple of things that we’re working on, and if we have any blockers, and, like, just a very rough timeline of, like, when we think we’d have that done, that would be really helpful for me.

154 00:13:52.970 00:13:56.840 Henry Zhao: Yeah, Michelle, if you can give us a timeline on getting the new onboarding events.

155 00:13:57.580 00:14:03.240 Henry Zhao: As well, like, just have new onboarding completed, and the tab clicks inside default.

156 00:14:04.220 00:14:06.760 vishalag: what’s the onboarding completion part? I mean, I know.

157 00:14:06.760 00:14:08.000 Henry Zhao: Oh, there was one more thing.

158 00:14:08.220 00:14:11.500 Henry Zhao: Wait, we already… you say… we are… do we already have the onboarding event?

159 00:14:12.510 00:14:15.940 vishalag: It used to be, I remember it being there, but, like.

160 00:14:16.380 00:14:17.539 Henry Zhao: Yeah, it was,

161 00:14:18.760 00:14:28.090 Henry Zhao: So, by the way, Sriya, just as context for you, any of the things that are live are events that Vishal and I have already looked at and kind of, approved.

162 00:14:28.370 00:14:35.729 Henry Zhao: So yeah, we do have new user onboarded, so sorry, I said it wrong. We have new users onboarded, but now we want some session data. So…

163 00:14:37.810 00:14:42.530 Henry Zhao: I wonder if we can use web session and web session start? I don’t know if that’s correct.

164 00:14:43.040 00:14:44.890 Henry Zhao: But basically…

165 00:14:45.110 00:14:55.249 Henry Zhao: somebody asked, like, who are the most user… who are the ones using the app the most, like, for the longest amount of time? So for that, we’re gonna need session data. So, like, how long is each session?

166 00:14:55.730 00:15:01.699 Henry Zhao: And I think I sent you amplitude session data.

167 00:15:05.960 00:15:10.169 Henry Zhao: Yeah, we just need, like, a session ID. Right now, I think they’re all negative 1.

168 00:15:13.020 00:15:20.260 vishalag: Yeah, I mean, because all of these are being sent from the backend side, not just coming from, like, the UI. So for session, you will need…

169 00:15:20.400 00:15:23.189 vishalag: like, UI, right? Integration.

170 00:15:25.620 00:15:27.210 Henry Zhao: I don’t, I don’t know what we…

171 00:15:27.930 00:15:32.040 vishalag: basically, like, who is using the tabs and everything, right? Like, you need to know.

172 00:15:32.500 00:15:38.319 vishalag: So, all of that, we need someone who can work on it. So, I will have to pull in someone else.

173 00:15:38.320 00:15:41.320 Henry Zhao: Okay, we can talk about that tomorrow at the meeting with leadership.

174 00:15:41.770 00:15:42.360 vishalag: Yep.

175 00:15:42.550 00:15:43.089 vishalag: It’s glue.

176 00:15:43.090 00:15:46.289 Henry Zhao: Yeah, we’ll just say we need to pull in somebody else, we need session ID, we need…

177 00:15:46.480 00:15:49.650 Henry Zhao: The tab clicks, and that Vishal needs backup, basically.

178 00:15:51.530 00:15:56.810 Henry Zhao: Yeah, because I’ve already bothered you for a lot of different things, and I think, Sriya, you’ll get more context at the meeting tomorrow, because we’ll go over all the.

179 00:15:56.810 00:16:12.310 Shreya Chowdhury: Yeah, I just need an update to talk to the leads about, for where we’re at on default, and then also where we are on that ticket. Because if we’re not going to be able to complete those 3 things for Caitlin, I just want to make sure they know that, like, we’re actively working on it and what the timeline looks like.

180 00:16:13.570 00:16:17.999 Henry Zhao: Yeah, we’ll just talk to them about that tomorrow. Vishal, if you can have an estimate by tomorrow.

181 00:16:18.140 00:16:20.929 Henry Zhao: Because also, the timeline depends on if we can get extra help, right? So…

182 00:16:24.710 00:16:25.250 vishalag: Yep.

183 00:16:26.470 00:16:32.049 Henry Zhao: And then the one that Robert commented on, I can use new onboarding, maybe, to figure out if we can address that point.

184 00:16:32.780 00:16:34.780 Henry Zhao: And then deduplication we’re looking into.

185 00:16:35.470 00:16:41.999 Henry Zhao: hopefully it’s done by tomorrow, because I’m reaching out to support, but if they don’t respond to me, there’s nothing I can do, yeah.

186 00:16:44.220 00:16:45.370 Shreya Chowdhury: Yeah, that’s fair.

187 00:16:46.660 00:16:48.439 Henry Zhao: So that’s the update, basically.

188 00:16:48.440 00:16:49.030 Shreya Chowdhury: Yeah.

189 00:16:49.370 00:17:01.779 Shreya Chowdhury: Okay, cool. I think we can… I’m gonna go through the ticket, and probably just… maybe on the linear ticket, we’ll just add, like, what each of the blockers in progress for those things are, and then we can probably leave it at that state.

190 00:17:02.580 00:17:03.180 Henry Zhao: Okay.

191 00:17:03.550 00:17:04.079 Shreya Chowdhury: Yeah.

192 00:17:05.099 00:17:08.069 Henry Zhao: And I’ll be there tomorrow in the meeting to also mention these things.

193 00:17:08.660 00:17:10.519 Shreya Chowdhury: Okay, cool. Sounds good.

194 00:17:11.410 00:17:13.259 Henry Zhao: Okay, thanks, Vishal, again, for all of your help.

195 00:17:14.680 00:17:27.109 vishalag: Cool, no problem, man. I will be… I will… I’ve asked the team to get someone looped in for the UI. Let’s see if someone loops in, because it will be a purely different ballgame to get session replays.

196 00:17:27.310 00:17:34.739 vishalag: And, get to tap clicks, right? So, let’s see who’s available. I mean, honestly speaking, I think it’s really difficult to get someone in.

197 00:17:35.630 00:17:36.610 vishalag: Yeah.

198 00:17:36.950 00:17:38.950 Henry Zhao: They’ll have to understand that that’s gonna take a while.

199 00:17:39.190 00:17:39.900 Henry Zhao: Yeah.

200 00:17:41.870 00:17:42.420 vishalag: Cool.

201 00:17:42.910 00:17:47.799 Henry Zhao: So then they can figure out their priorities, right? Like, if this is a priority to them, they’ll need to find a way to loop somebody in.

202 00:17:48.390 00:17:49.869 vishalag: Yep, I guess so.

203 00:17:51.320 00:17:53.400 vishalag: Alright, cool.

204 00:17:54.170 00:17:55.360 Shreya Chowdhury: Bye. See you guys tomorrow.