Meeting Title: Brainforge User Properties and Workflows Sync Date: 2026-02-26 Meeting participants: Nandika Jhunjhunwala, Greg Stoutenburg


WEBVTT

1 00:01:39.330 00:01:40.480 Greg Stoutenburg: Hey, Nautica!

2 00:01:41.880 00:01:42.830 Nandika Jhunjhunwala: Hello?

3 00:01:43.000 00:01:44.400 Greg Stoutenburg: Hello!

4 00:01:44.840 00:01:45.640 Greg Stoutenburg: How’s your week?

5 00:01:46.510 00:01:53.160 Nandika Jhunjhunwala: Good! Hectic, confusing in startup world, so… the usual. Yeah, what about you?

6 00:01:53.160 00:02:12.390 Greg Stoutenburg: Fantastic, yeah, similar. Yeah. One second… Yeah, yeah, yeah, a lot going on, and it’s like, it seems like maybe the way it’s going over there is, like, wait, wait, wait, wait, wait, no! Right? Like, everything, everything’s ready now, do it now.

7 00:02:13.800 00:02:14.510 Greg Stoutenburg: Yep.

8 00:02:14.510 00:02:15.369 Nandika Jhunjhunwala: For sure, yeah.

9 00:02:15.370 00:02:16.019 Greg Stoutenburg: Very good.

10 00:02:18.510 00:02:21.059 Greg Stoutenburg: Cool. Alright,

11 00:02:21.650 00:02:28.780 Greg Stoutenburg: So, on my end, I kind of wanted to show off the user properties that I had in mind, and we could talk about instrumentation for that.

12 00:02:28.780 00:02:29.160 Nandika Jhunjhunwala: Fair.

13 00:02:29.160 00:02:39.989 Greg Stoutenburg: And, and then maybe you can show me what workflows are in place now, and we can talk about some mapping for that, and then anything else that’s remaining. Does that sound good?

14 00:02:39.990 00:02:41.069 Nandika Jhunjhunwala: Yeah, sounds great.

15 00:02:41.070 00:02:51.560 Greg Stoutenburg: Cool, alright. So, before I share my screen, I had a conversation with Caitlin today about onboarding, and we kind of talked about, like, different journeys that different types of users might take in

16 00:02:51.560 00:03:07.969 Greg Stoutenburg: I mean, the suggestion of distinguishing from an account, like, an account creator from an admin, because some users might create an account, but then really, to have the permissions to do things like connect their data source or set up a calendar, they might need, you know, roles that they don’t have, so…

17 00:03:08.190 00:03:26.030 Greg Stoutenburg: So we need, like, a concept of a creator and an owner, and then, like, a member might be someone who just comes in and they’re added to a team, and they’ll do things like schedule or receive appointments, but they won’t be, like, connecting sources and calendars and things like that. So, I… I haven’t…

18 00:03:26.030 00:03:32.860 Greg Stoutenburg: I think I anticipated that in the tracking plan, but that’s something to keep in mind as we look at this.

19 00:03:35.630 00:03:39.649 Greg Stoutenburg: Where’s the delete button? Okay, there we go. So… alright.

20 00:03:42.790 00:03:51.040 Greg Stoutenburg: All right, so for user properties, so all the events, I haven’t added any events since last time that we talked about them. So…

21 00:03:51.660 00:04:08.649 Greg Stoutenburg: A group property for Post Hog will be any property that’s… it’s not a property of an individual, it’s a property of an organization, and so the organization has the property regardless of other properties that users have who are a part of the organization.

22 00:04:08.650 00:04:09.160 Nandika Jhunjhunwala: Great.

23 00:04:09.160 00:04:16.909 Greg Stoutenburg: Now, sometimes the fact that a group has a property means that the user who’s in the group will inherit the property.

24 00:04:16.910 00:04:17.300 Nandika Jhunjhunwala: Right.

25 00:04:17.300 00:04:30.969 Greg Stoutenburg: for example, plan, right? Like, if, if, you know, if Brainforge has, is on the, you know, the pro plan, then everyone who’s a member of the Brainforge team is thereby on the pro plan.

26 00:04:31.440 00:04:41.710 Greg Stoutenburg: But that doesn’t apply to everything, right? Like, company size, the fact that my company has, you know, 11 to 50 members doesn’t mean that I have 11 to 50 members.

27 00:04:42.020 00:04:46.889 Greg Stoutenburg: Okay. So, the only group properties that

28 00:04:47.120 00:04:59.100 Greg Stoutenburg: I think are gonna be relevant to us off the top of my head, and if others come to mind, like, you know, please say so, we’ll add them right now, are company size and, like, org region. So, tier.

29 00:04:59.460 00:05:01.090 Greg Stoutenburg: Size, region.

30 00:05:01.580 00:05:06.289 Greg Stoutenburg: Is there anything else that immediately comes to mind that… We want to…

31 00:05:06.550 00:05:16.819 Nandika Jhunjhunwala: maybe just a workspace ID as a group property, I’m not sure, because I know we talked about users being into workspaces.

32 00:05:16.820 00:05:17.490 Greg Stoutenburg: Yep.

33 00:05:17.730 00:05:21.750 Nandika Jhunjhunwala: That’s, like, the only one I can think of off the top of my head.

34 00:05:21.870 00:05:30.499 Nandika Jhunjhunwala: But I think that those should be good, and I’m assuming group properties are different from cohorts, user cohorts will create, that we’ll create it, so…

35 00:05:30.500 00:05:31.220 Greg Stoutenburg: Yes.

36 00:05:31.220 00:05:32.050 Nandika Jhunjhunwala: Okay.

37 00:05:32.050 00:05:43.079 Greg Stoutenburg: What did I do? What… what did I do? Come back. All right. So, group property, right, so this would be, like, like, workspace…

38 00:05:44.350 00:05:48.860 Greg Stoutenburg: Yeah, so this would be all of the workspaces that are associated with a team, right?

39 00:05:49.010 00:05:49.390 Nandika Jhunjhunwala: Yes.

40 00:05:49.390 00:05:51.189 Greg Stoutenburg: Good.

41 00:05:52.060 00:06:00.870 Greg Stoutenburg: Maybe we just do workspace ID, and that can just be all of the workspace IDs that users are associated with.

42 00:06:01.050 00:06:03.250 Greg Stoutenburg: Well, wait a second, wait, let’s think about this.

43 00:06:04.550 00:06:10.480 Greg Stoutenburg: Right, these will be distinct, because a user could be a part of multiple workspaces, including ones

44 00:06:11.080 00:06:15.250 Greg Stoutenburg: I think, including ones that are not a part of their own organization. Is that the case?

45 00:06:15.900 00:06:19.520 Nandika Jhunjhunwala: I think in future, in the future, it could be a possibility, yeah.

46 00:06:19.520 00:06:22.840 Greg Stoutenburg: Okay, okay. Because, like, for example, in Slack.

47 00:06:23.350 00:06:27.870 Greg Stoutenburg: I’m in Brainforges Slack, but I’m in several other Slacks, right? So if someone wants to know, like.

48 00:06:28.030 00:06:32.990 Greg Stoutenburg: Brainforge can have, you know, its list of members, but that’s… that’s not exhaustive of

49 00:06:33.180 00:06:36.810 Greg Stoutenburg: the memberships of the users. Okay, so that’s good.

50 00:06:47.560 00:06:48.330 Greg Stoutenburg: Cool.

51 00:06:50.520 00:06:51.340 Greg Stoutenburg: Good.

52 00:06:54.060 00:06:55.040 Greg Stoutenburg: Okay.

53 00:06:56.310 00:07:00.180 Nandika Jhunjhunwala: And those should be… those should match. Maybe I’ll just put in a note.

54 00:07:07.390 00:07:09.679 Greg Stoutenburg: Okay. Good. Alright.

55 00:07:10.040 00:07:16.230 Greg Stoutenburg: If any of this come to mind, we’ll, we can record them. For user properties.

56 00:07:16.520 00:07:30.749 Greg Stoutenburg: I put internal user, so this can just be helpful in analytics, like, to filter out testing, so any user who’s internal to default, or otherwise not a normal user, so, like, that would include, like, anyone at Brainforge, for example. Company name.

57 00:07:31.790 00:07:39.240 Greg Stoutenburg: company ID, workspace, we just talked about this, user ID, which is just assigned by post hoc by default.

58 00:07:39.570 00:07:41.420 Greg Stoutenburg: Any acquisition channel?

59 00:07:41.780 00:07:47.420 Greg Stoutenburg: And I suggested here at least a way to get started. Organic invited paid referral, username.

60 00:07:48.180 00:07:56.370 Greg Stoutenburg: Couple of UTMs, right? Source parameters like Google, LinkedIn, Medium, campaign…

61 00:07:57.270 00:08:03.990 Greg Stoutenburg: Marketing will eventually want that, even if they don’t want it now. First visit domain.

62 00:08:04.920 00:08:06.880 Greg Stoutenburg: sign-up method. I think…

63 00:08:07.380 00:08:14.119 Greg Stoutenburg: So, I know right now at least email and Google were in the designs that Caitlin showed me today.

64 00:08:14.910 00:08:18.569 Greg Stoutenburg: I’m sure SAML will be necessary for Enterprise?

65 00:08:19.190 00:08:28.330 Greg Stoutenburg: And then, you know, anything else that comes up, like, you know, GitHub, for example. First name, last name, email, country, city, you know, basic stuff.

66 00:08:28.750 00:08:32.580 Greg Stoutenburg: user created at… email verification.

67 00:08:33.340 00:08:40.290 Greg Stoutenburg: I put industry name… no, I know this is being worked on right now, so this is something that, like, I think we shouldn’t instrument for sure at this time.

68 00:08:40.299 00:08:40.649 Nandika Jhunjhunwala: Because…

69 00:08:40.650 00:08:42.749 Greg Stoutenburg: This onboarding is being worked on, but…

70 00:08:42.750 00:08:43.340 Nandika Jhunjhunwala: Right.

71 00:08:43.340 00:08:49.049 Greg Stoutenburg: We can include here things that are… things that we learn about the user as they go through the journey.

72 00:08:49.200 00:08:54.919 Greg Stoutenburg: And then, like, you know, role, and then subscription status.

73 00:08:56.240 00:08:57.810 Nandika Jhunjhunwala: Yeah,

74 00:08:58.240 00:09:06.209 Nandika Jhunjhunwala: for some of these properties, I’m thinking about how we would get them in post hoc, like, for acquisition channel, like.

75 00:09:06.380 00:09:11.290 Nandika Jhunjhunwala: Because that’s not front-end data, I can add in code.

76 00:09:12.680 00:09:15.990 Nandika Jhunjhunwala: Yeah, I’m not super sure how we would…

77 00:09:17.370 00:09:20.799 Nandika Jhunjhunwala: That would be an interesting field to solve for.

78 00:09:20.800 00:09:21.430 Greg Stoutenburg: Yep.

79 00:09:22.800 00:09:26.940 Nandika Jhunjhunwala: like, this is, like, why I was asking, like, our CTO for product data.

80 00:09:29.490 00:09:37.340 Nandika Jhunjhunwala: Yeah, I’ll think about that one, because it’s definitely, like, an important one. I think that data currently lives in…

81 00:09:37.810 00:09:39.810 Nandika Jhunjhunwala: Our forms in default.

82 00:09:39.810 00:09:40.730 Greg Stoutenburg: Hmm.

83 00:09:40.730 00:09:42.119 Nandika Jhunjhunwala: Where they ask, like.

84 00:09:42.800 00:09:48.979 Nandika Jhunjhunwala: So, like, if a lead comes in purely inbound, it says inbound lead, and then it comes via, like.

85 00:09:48.980 00:09:53.529 Greg Stoutenburg: an outbound, it, like, then get, like, says outbound lead. Yeah. So…

86 00:09:53.840 00:09:57.820 Nandika Jhunjhunwala: I’m not sure how we would do this, like, with PLG.

87 00:09:58.780 00:10:08.180 Greg Stoutenburg: Well, I mean, for one thing, we might not instrument this right away, but also marketers would probably have some suggestions here about how to code this.

88 00:10:08.180 00:10:08.910 Nandika Jhunjhunwala: No.

89 00:10:09.430 00:10:25.449 Greg Stoutenburg: And it might be that this is, like, derivative of some of these other things, right? Like, because if you show up here, then, you know, you are… you’re gonna be, like, you know, paid or referral, for example. So, yeah.

90 00:10:25.450 00:10:37.110 Nandika Jhunjhunwala: The only problem with that is, like, someone might come off as purely, like, organic, but there would… there could be, like, activity in, like, Salesforce that we logged, or, like.

91 00:10:37.110 00:10:37.440 Greg Stoutenburg: Yeah.

92 00:10:37.440 00:10:50.129 Nandika Jhunjhunwala: marketing platform that we wouldn’t account for in this case, because it could say, like, source direct, but then they definitely got some sort of marketing email that didn’t contain a UTM or, like, an email, like, just a pure email.

93 00:10:50.130 00:10:50.530 Greg Stoutenburg: Yep.

94 00:10:50.530 00:10:51.420 Nandika Jhunjhunwala: Oh…

95 00:10:52.600 00:11:08.969 Greg Stoutenburg: Yeah, and it’s funny you mention that, because just today, I was talking to Caitlin about how something that I’ve seen before is, especially in, you know, B2B SaaS, where if there’s a free tier, someone from a company might go in and, like, evaluate it, like, just, like, scope it out for free.

96 00:11:08.970 00:11:20.330 Greg Stoutenburg: And then, they might use their Gmail for this, and I know that you’ll only accept business emails, so you’ll avoid that, right? But then they’ll write, like, a recommendation or a report for someone else, and then pass that along, and then they… then that other person contacts sales.

97 00:11:20.420 00:11:28.759 Greg Stoutenburg: So this looks like they just came out of nowhere, but really, they actually, you know, they had some previous experience. Similarly,

98 00:11:29.130 00:11:39.139 Greg Stoutenburg: someone might have some experience with the channel, but they show up as organic, so… yeah. Yeah, and then maybe we find a way to update that from Salesforce or something.

99 00:11:39.420 00:11:53.259 Nandika Jhunjhunwala: Yeah, like, that makes me wonder, because a lot of this data does live in Salesforce, like, for that particular, like, user, or account, at the account level, for short, at the company level,

100 00:11:54.500 00:12:00.209 Nandika Jhunjhunwala: So, I’m not super sure, but I can tell you what properties are in…

101 00:12:01.860 00:12:05.959 Nandika Jhunjhunwala: in post-hoc and, like, the ones that I can instrument today, I’ll add them in.

102 00:12:05.960 00:12:06.760 Greg Stoutenburg: Okay.

103 00:12:06.760 00:12:09.200 Nandika Jhunjhunwala: So let me…

104 00:12:13.010 00:12:14.940 Nandika Jhunjhunwala: I’ll just log in and see.

105 00:12:20.880 00:12:29.670 Greg Stoutenburg: Yeah, and it’s okay, like, we don’t have to be able to… we already know, because this is the tracking plane we’re building out, we already know that we can’t instrument all this today anyway, so,

106 00:12:29.800 00:12:31.410 Greg Stoutenburg: The question is more…

107 00:12:31.960 00:12:39.600 Greg Stoutenburg: Are these all the things we want to make sure that we will be able to track? And if not, you know, let’s cut them, or let’s add what we need to add.

108 00:12:40.690 00:12:41.369 Nandika Jhunjhunwala: For sure.

109 00:12:41.370 00:12:42.090 Greg Stoutenburg: Nope.

110 00:12:49.040 00:12:52.869 Nandika Jhunjhunwala: Yeah, and some of these events have gone live into our main branch, so it’s kind of nice…

111 00:12:52.870 00:12:53.440 Greg Stoutenburg: Awesome.

112 00:12:54.170 00:12:58.450 Nandika Jhunjhunwala: Other people’s events also being tagged with those custom names that we created.

113 00:12:58.450 00:12:59.629 Greg Stoutenburg: Awesome. Great.

114 00:13:06.190 00:13:08.620 Nandika Jhunjhunwala: Yeah, I’m not seeing a ton, but…

115 00:13:09.230 00:13:18.079 Nandika Jhunjhunwala: I’m seeing, like, dock icon clicked, and… Organizations which clicked, and… Stuff like that.

116 00:13:19.610 00:13:20.520 Nandika Jhunjhunwala: Nice.

117 00:13:21.630 00:13:27.960 Nandika Jhunjhunwala: Okay, sorry, I’m sorry to interrupt you, like, do you have more… to share?

118 00:13:27.960 00:13:31.740 Greg Stoutenburg: Oh, I was just saying that, like, these are, like, ideal right now.

119 00:13:31.740 00:13:32.520 Nandika Jhunjhunwala: So, yeah.

120 00:13:32.520 00:13:39.559 Greg Stoutenburg: We already know that we can’t instrument all of these, you know, in the current state, so the question is more.

121 00:13:40.590 00:13:54.370 Greg Stoutenburg: are there any things that you can think of, I can’t, that’s why I’m, you know, suggesting this list, that default would want to be able to see in analytics down the line that’s not represented here, or anything here that you already know is, like, not relevant?

122 00:13:55.650 00:13:59.439 Nandika Jhunjhunwala: No, I think they look great,

123 00:13:59.560 00:14:04.550 Nandika Jhunjhunwala: Like, user subscription data, industry, like, later on, and like…

124 00:14:04.550 00:14:05.170 Greg Stoutenburg: Yeah.

125 00:14:05.510 00:14:07.779 Nandika Jhunjhunwala: I think all of those are super…

126 00:14:08.530 00:14:14.820 Nandika Jhunjhunwala: Super important and, like, important for us to join that data for… From different sources.

127 00:14:15.490 00:14:17.829 Greg Stoutenburg: Good, good. Yep. Okay, cool.

128 00:14:18.200 00:14:20.200 Greg Stoutenburg: Alright.

129 00:14:21.320 00:14:25.389 Greg Stoutenburg: So, that’s… that’s these then, and then.

130 00:14:26.270 00:14:28.899 Nandika Jhunjhunwala: Want to go over to…

131 00:14:28.900 00:14:32.470 Greg Stoutenburg: Here, Tracking implementation?

132 00:14:32.830 00:14:33.550 Nandika Jhunjhunwala: Yeah.

133 00:14:34.420 00:14:37.249 Greg Stoutenburg: So these are all the things that you’ve set up already, right?

134 00:14:37.700 00:14:38.470 Nandika Jhunjhunwala: Correct.

135 00:14:38.470 00:14:39.230 Greg Stoutenburg: Okay.

136 00:14:40.820 00:14:43.719 Nandika Jhunjhunwala: Some of them are live in Maine, some of them are not, but.

137 00:14:43.840 00:14:44.430 Greg Stoutenburg: That’s cool.

138 00:14:44.680 00:14:47.909 Nandika Jhunjhunwala: By end of day tomorrow, they’ll all be live in Maine.

139 00:14:47.910 00:14:49.120 Greg Stoutenburg: Okay, sweet.

140 00:14:49.580 00:14:52.190 Greg Stoutenburg: Sweet, sweet. Now,

141 00:14:52.510 00:14:59.050 Greg Stoutenburg: Right, and these are all from tables and enrichment, okay. So, I think I can use the A column

142 00:14:59.260 00:15:02.510 Greg Stoutenburg: As a way to figure out what workflow these are a part of.

143 00:15:03.570 00:15:08.239 Greg Stoutenburg: So I think what I’d like to add is, you know, thinking about this as, like, user journeys.

144 00:15:09.830 00:15:15.480 Greg Stoutenburg: Someone who’s working through onboarding, for example, starts it, they go through some step.

145 00:15:15.590 00:15:26.620 Greg Stoutenburg: they complete it, or they skip a step, right? And we’ll add more as we get onboarding sorted out, but, you know, those are, like, pieces of it. So,

146 00:15:27.440 00:15:30.960 Greg Stoutenburg: My question then is, can I…

147 00:15:31.390 00:15:37.330 Greg Stoutenburg: Tie each of these events to some distinct workflow that a user might be involved in.

148 00:15:39.170 00:15:45.109 Nandika Jhunjhunwala: Yeah, for sure. That and the other thing that, I’ve been thinking about is…

149 00:15:45.210 00:15:49.940 Nandika Jhunjhunwala: I need to update this, but most of the properties have, like.

150 00:15:50.460 00:15:53.610 Nandika Jhunjhunwala: Most of the events have a property called appName.

151 00:15:53.610 00:15:54.360 Greg Stoutenburg: Yep.

152 00:15:55.030 00:16:02.949 Nandika Jhunjhunwala: So… For, like, we can also, like, group by app name and app name tables.

153 00:16:02.950 00:16:06.160 Greg Stoutenburg: And then we can group by user as well and see, like.

154 00:16:06.510 00:16:13.900 Nandika Jhunjhunwala: events related to tables that the user interacted with as, like, sort of, like, a generic overview of, like.

155 00:16:14.470 00:16:17.149 Nandika Jhunjhunwala: Where their activities are concentrated.

156 00:16:18.570 00:16:36.379 Nandika Jhunjhunwala: So if we had, like, if you grouped by app name, and then we saw, like, for workflows, these aren’t that many events associated with, like, workflows, these many with, like, tables, these many with, like, this particular section of, like, settings, or, like, routing, or whatever.

157 00:16:36.380 00:16:37.290 Greg Stoutenburg: Yeah.

158 00:16:37.290 00:16:40.790 Nandika Jhunjhunwala: I don’t know if that’s, like, super useful, or, like, if you have any thoughts there.

159 00:16:40.790 00:16:45.849 Greg Stoutenburg: Yeah, no, I’m just trying to think about it. So, like, we have something that PostHog gives for free.

160 00:16:46.050 00:16:51.200 Greg Stoutenburg: I mean, not free, but, like, just includes, is any page view event?

161 00:16:51.200 00:16:51.660 Nandika Jhunjhunwala: Yeah.

162 00:16:51.660 00:16:52.860 Greg Stoutenburg: Any clicks?

163 00:16:53.130 00:17:04.170 Greg Stoutenburg: So, probably some of these, like… like, these will just… these will be captured even if you don’t ask Post Hog to do it. Like, it’ll just come in.

164 00:17:05.250 00:17:09.299 Greg Stoutenburg: So… but I do like this app name.

165 00:17:09.750 00:17:11.869 Greg Stoutenburg: As a property of…

166 00:17:12.390 00:17:20.520 Greg Stoutenburg: any click, right? Like, where they’re clicking. So, you know, this is… this is actually… this is gonna be a follow-up. This will be a follow-up for me.

167 00:17:21.200 00:17:27.329 Greg Stoutenburg: When a user click something, and PostHog registers that using AutoCapture.

168 00:17:27.470 00:17:34.950 Greg Stoutenburg: The click is AutoCapture. Is the app name also going to be auto-capture, or do we have to, like, configure

169 00:17:35.420 00:17:36.890 Greg Stoutenburg: The click to do that.

170 00:17:37.980 00:17:39.170 Greg Stoutenburg: I’m not sure.

171 00:17:39.560 00:17:47.290 Nandika Jhunjhunwala: So, if I’m looking at, like, a page view, I see a bunch of properties, and one of those properties are, like.

172 00:17:47.630 00:17:51.079 Nandika Jhunjhunwala: path name, I think, which tells you what path

173 00:17:51.570 00:17:54.419 Nandika Jhunjhunwala: It was, but it’s like… I’ll let me share my screen, actually.

174 00:17:54.420 00:17:55.150 Greg Stoutenburg: Yeah.

175 00:17:55.580 00:17:56.070 Greg Stoutenburg: Yep.

176 00:17:56.280 00:17:57.909 Greg Stoutenburg: We’ll stop mine.

177 00:17:59.710 00:18:00.820 Nandika Jhunjhunwala: So…

178 00:18:04.660 00:18:05.890 Nandika Jhunjhunwala: Do you see my screen?

179 00:18:07.870 00:18:08.550 Greg Stoutenburg: Yep.

180 00:18:08.760 00:18:12.919 Nandika Jhunjhunwala: Okay, so, as you can see, page view…

181 00:18:12.920 00:18:14.320 Greg Stoutenburg: Page view.

182 00:18:14.590 00:18:18.690 Nandika Jhunjhunwala: So it has referral, URL, title, it clicks out, and contact.

183 00:18:19.120 00:18:21.980 Nandika Jhunjhunwala: The current URL, you can see that.

184 00:18:21.980 00:18:22.720 Greg Stoutenburg: Okay.

185 00:18:22.720 00:18:23.680 Nandika Jhunjhunwala: Yeah.

186 00:18:25.280 00:18:28.260 Nandika Jhunjhunwala: So that’s one, and then if I look at…

187 00:18:29.940 00:18:33.889 Nandika Jhunjhunwala: This is an organization twitched, dogged by conflict.

188 00:18:34.100 00:18:38.540 Nandika Jhunjhunwala: Again, it has all those auto-capture properties, and then at the end, it has the…

189 00:18:39.000 00:18:40.570 Nandika Jhunjhunwala: app name tables, it’s just, like.

190 00:18:40.570 00:18:41.320 Greg Stoutenburg: Okay.

191 00:18:41.320 00:18:42.200 Nandika Jhunjhunwala: Dude?

192 00:18:42.200 00:18:45.320 Greg Stoutenburg: Okay. Now, did you have to configure that, or was that there already?

193 00:18:45.320 00:18:46.710 Nandika Jhunjhunwala: No, I configured that.

194 00:18:46.930 00:18:50.190 Greg Stoutenburg: Okay, nice. Good. Okay.

195 00:18:50.190 00:18:57.829 Nandika Jhunjhunwala: And then I have an organization ID here, too. And then I can also show you what user properties we already have.

196 00:18:59.400 00:19:02.510 Nandika Jhunjhunwala: I was gonna see that, where was it?

197 00:19:04.510 00:19:06.690 Greg Stoutenburg: So I’m gonna write down app name.

198 00:19:07.190 00:19:12.900 Greg Stoutenburg: And app title, just in the interaction events, since we know that that’s there.

199 00:19:13.530 00:19:24.009 Nandika Jhunjhunwala: Yeah, so in that sheet, like, the tab, there’s, like… I’ve listed out all properties for each event, so it was to make it simple for us to…

200 00:19:24.390 00:19:28.500 Nandika Jhunjhunwala: create dashboards off of that, hopefully.

201 00:19:29.140 00:19:29.880 Nandika Jhunjhunwala: Let me look.

202 00:19:29.880 00:19:37.669 Greg Stoutenburg: Yeah, so just for, like, sort of framing, like, the tab that says Tracking Plan, the goal of it is

203 00:19:37.820 00:19:48.040 Greg Stoutenburg: like, this is… these are all the things that we intend to be tracking, and this is what they do, and this is what they’re for. So if… as we, like, you know, turn events on and off.

204 00:19:48.150 00:20:03.680 Greg Stoutenburg: we should remove things from there. So the reason I wanted to add app name and app title to the interaction events area is just so we know anytime someone’s using click tab, rage click, dead click, app name and app title will be included in that.

205 00:20:05.020 00:20:05.950 Nandika Jhunjhunwala: Yeah. Yep.

206 00:20:06.960 00:20:12.359 Nandika Jhunjhunwala: So currently we have, like, Their host.

207 00:20:13.000 00:20:16.430 Nandika Jhunjhunwala: Yeah, so they have, like, UTM source and…

208 00:20:16.790 00:20:21.159 Nandika Jhunjhunwala: all those fields, I think, like, automatically configured from PostDog.

209 00:20:21.360 00:20:25.550 Nandika Jhunjhunwala: It’s obviously not here because they’re just internal users.

210 00:20:25.550 00:20:26.010 Greg Stoutenburg: Yep.

211 00:20:26.010 00:20:30.300 Nandika Jhunjhunwala: Country… And then…

212 00:20:30.580 00:20:31.260 Greg Stoutenburg: Yep.

213 00:20:31.380 00:20:34.680 Nandika Jhunjhunwala: I don’t know what these things are. I don’t know what some of those things are, yeah.

214 00:20:35.300 00:20:38.780 Nandika Jhunjhunwala: Yeah, cool. Yeah, there’s the latest UTM source, too.

215 00:20:39.370 00:20:42.189 Nandika Jhunjhunwala: So all of that is useful.

216 00:20:42.470 00:20:48.140 Nandika Jhunjhunwala: I did see, like, so there, they have an organization ID right here, so one of the group properties already…

217 00:20:48.390 00:20:49.980 Nandika Jhunjhunwala: There, which is great.

218 00:20:49.980 00:20:51.180 Greg Stoutenburg: Good.

219 00:20:51.340 00:20:54.710 Nandika Jhunjhunwala: I think this one, like, RCTO Victor added.

220 00:20:55.180 00:20:58.239 Nandika Jhunjhunwala: Which… the organization ID.

221 00:20:58.240 00:20:58.740 Greg Stoutenburg: Okay.

222 00:20:58.740 00:21:02.509 Nandika Jhunjhunwala: But my… I might be wrong. So the referring domain to…

223 00:21:02.510 00:21:03.120 Greg Stoutenburg: Good.

224 00:21:03.290 00:21:10.779 Nandika Jhunjhunwala: Yeah, so there are some properties we talked about already there, and then…

225 00:21:10.990 00:21:11.440 Greg Stoutenburg: Yup.

226 00:21:11.440 00:21:14.919 Nandika Jhunjhunwala: Yeah, I can look more into, like, configuring additional properties.

227 00:21:15.070 00:21:19.290 Nandika Jhunjhunwala: Because I would want to add them right here and not create a separate, like, event.

228 00:21:19.440 00:21:21.139 Greg Stoutenburg: Yeah, yeah, yeah, definitely.

229 00:21:21.670 00:21:23.400 Nandika Jhunjhunwala: I’ll look into that, though.

230 00:21:23.880 00:21:24.460 Greg Stoutenburg: Yep.

231 00:21:24.790 00:21:25.610 Greg Stoutenburg: Cool.

232 00:21:26.510 00:21:28.630 Greg Stoutenburg: Okay then,

233 00:21:28.960 00:21:37.109 Greg Stoutenburg: Want to take a look at… has it… have any new designs or anything come up in the last little bit that we haven’t had a chance to review?

234 00:21:37.400 00:21:46.310 Nandika Jhunjhunwala: Yeah, so your Vercel should be updated with the latest developments. The Vercel instance you have is ahead of the main, so it’s…

235 00:21:46.550 00:21:54.619 Nandika Jhunjhunwala: More stuff that’s experimental and, like, really reviewed as well, so that one gets, like, updated quicker than.

236 00:21:54.620 00:21:55.830 Greg Stoutenburg: Edit. Yup.

237 00:21:58.270 00:22:02.100 Greg Stoutenburg: Yeah, alright, that looks the same.

238 00:22:03.280 00:22:06.100 Nandika Jhunjhunwala: You should see some more, like, icons and stuff come in.

239 00:22:07.460 00:22:10.190 Greg Stoutenburg: Maybe if I hit the launcher, no, the launcher still doesn’t do anything.

240 00:22:10.910 00:22:13.899 Nandika Jhunjhunwala: Let me share my screen.

241 00:22:14.150 00:22:15.210 Greg Stoutenburg: Yeah, okay.

242 00:22:19.140 00:22:27.019 Nandika Jhunjhunwala: Okay… Yeah, you may have the… the different… different reversal deployment, I don’t know.

243 00:22:27.020 00:22:28.130 Greg Stoutenburg: Okay.

244 00:22:29.280 00:22:31.640 Nandika Jhunjhunwala: So many result of violence.

245 00:22:31.640 00:22:32.659 Greg Stoutenburg: Yeah, I’m sure.

246 00:22:33.390 00:22:35.359 Nandika Jhunjhunwala: Is this what you see as well?

247 00:22:37.120 00:22:44.550 Greg Stoutenburg: Let me close my apps and see if that’s what that looks like. Yep, default dev engineering, there’s the time, there’s…

248 00:22:44.930 00:22:47.580 Greg Stoutenburg: the same, I don’t have workflows in my.

249 00:22:47.580 00:22:52.309 Nandika Jhunjhunwala: Oh, okay. So this is new. Okay. Foreclosed…

250 00:22:52.460 00:22:55.950 Nandika Jhunjhunwala: They have some, like, skeletal templates here.

251 00:22:55.950 00:22:57.910 Greg Stoutenburg: Look at that, looking nice.

252 00:22:57.910 00:22:58.880 Nandika Jhunjhunwala: Yeah.

253 00:22:59.100 00:23:06.610 Nandika Jhunjhunwala: It’s all, again, still very bare bones, like folder, start workflow… And then…

254 00:23:06.610 00:23:07.280 Greg Stoutenburg: Cool.

255 00:23:08.020 00:23:09.280 Nandika Jhunjhunwala: New, all these…

256 00:23:09.280 00:23:10.449 Greg Stoutenburg: Oh, look at that. Yeah, nice.

257 00:23:10.450 00:23:11.010 Nandika Jhunjhunwala: So…

258 00:23:11.010 00:23:11.690 Greg Stoutenburg: Yeah.

259 00:23:12.100 00:23:15.300 Nandika Jhunjhunwala: I guess it doesn’t do anything so far, you can just click on them.

260 00:23:15.300 00:23:15.950 Greg Stoutenburg: Yeah.

261 00:23:16.230 00:23:19.669 Nandika Jhunjhunwala: It’s not fully live, but we can definitely start instrumenting these.

262 00:23:19.900 00:23:22.550 Nandika Jhunjhunwala: Once they’re in Maine.

263 00:23:22.750 00:23:26.569 Nandika Jhunjhunwala: Because these are still, not fully approved by the NGO.

264 00:23:27.070 00:23:27.660 Greg Stoutenburg: Yeah.

265 00:23:27.660 00:23:29.709 Nandika Jhunjhunwala: So, I would not want to instrument them, because I.

266 00:23:29.710 00:23:30.100 Greg Stoutenburg: window.

267 00:23:30.100 00:23:31.739 Nandika Jhunjhunwala: Very much subject to change.

268 00:23:31.740 00:23:34.919 Greg Stoutenburg: Yeah, it would just be a waste of time, and there’s so many buttons.

269 00:23:34.920 00:23:35.720 Nandika Jhunjhunwala: Yeah.

270 00:23:35.720 00:23:36.330 Greg Stoutenburg: Yeah.

271 00:23:36.330 00:23:40.910 Nandika Jhunjhunwala: And then there’s… Scheduling, this is also new.

272 00:23:42.700 00:23:45.090 Nandika Jhunjhunwala: Not scheduling, sorry, routing is new.

273 00:23:46.440 00:23:50.780 Nandika Jhunjhunwala: Yeah, so… Toggling it on and off.

274 00:23:51.110 00:23:51.830 Greg Stoutenburg: Cool.

275 00:23:52.800 00:23:58.590 Greg Stoutenburg: So, do you see this, or no? I do see it, yep. I have routing, I just don’t have pipelines.

276 00:23:58.880 00:24:01.380 Nandika Jhunjhunwala: Oh, pipeline is for internal testing.

277 00:24:01.880 00:24:03.340 Greg Stoutenburg: Okay, got it.

278 00:24:03.340 00:24:05.160 Nandika Jhunjhunwala: Do you have workflows, or…

279 00:24:05.450 00:24:07.560 Greg Stoutenburg: I have,

280 00:24:08.310 00:24:14.169 Greg Stoutenburg: No, I’m sorry. That’s what I meant to say. I don’t have workflows. I… I do have pipeline.

281 00:24:15.140 00:24:17.090 Nandika Jhunjhunwala: Oh, and do you have routing?

282 00:24:17.470 00:24:20.850 Greg Stoutenburg: I’m routing. The only thing I don’t have is the lightning bolt there.

283 00:24:21.000 00:24:22.120 Nandika Jhunjhunwala: Oh, okay, got it.

284 00:24:22.370 00:24:23.080 Greg Stoutenburg: Yep.

285 00:24:23.080 00:24:29.880 Nandika Jhunjhunwala: Totally okay, I can start planning. I don’t even know what branch this is on, because

286 00:24:30.850 00:24:33.999 Nandika Jhunjhunwala: I just got this Vercel deployment, okay.

287 00:24:34.410 00:24:37.579 Nandika Jhunjhunwala: So they call it, like, the nightly, because this is not…

288 00:24:37.580 00:24:38.170 Greg Stoutenburg: Okay.

289 00:24:38.170 00:24:38.500 Nandika Jhunjhunwala: Beautiful.

290 00:24:38.500 00:24:43.350 Greg Stoutenburg: This is anything that, that, was pushed to today, I guess?

291 00:24:43.470 00:24:44.380 Greg Stoutenburg: Or yesterday.

292 00:24:44.380 00:24:48.490 Nandika Jhunjhunwala: Workflows has been life for a while, like, this has been life for a while, so…

293 00:24:48.490 00:24:49.120 Greg Stoutenburg: Okay.

294 00:24:49.120 00:24:52.169 Nandika Jhunjhunwala: Yeah, could you share your versatile deployment link so I can check?

295 00:24:52.370 00:24:54.039 Greg Stoutenburg: Yeah, I have.

296 00:24:54.370 00:24:56.269 Greg Stoutenburg: Well, let me close the app again.

297 00:25:40.720 00:25:41.760 Nandika Jhunjhunwala: Yay!

298 00:25:42.540 00:25:51.439 Nandika Jhunjhunwala: Oh… Anything that is the… the main branch.

299 00:25:51.550 00:25:53.060 Nandika Jhunjhunwala: I’m gonna check.

300 00:26:01.810 00:26:05.430 Nandika Jhunjhunwala: I see, okay. So you have the main branch.

301 00:26:05.430 00:26:06.130 Greg Stoutenburg: Okay.

302 00:26:06.810 00:26:15.050 Nandika Jhunjhunwala: This is the nightly branch, so I’ll… yeah. They’re not that much different. I think they should both catch up to each other soon.

303 00:26:15.230 00:26:16.889 Greg Stoutenburg: Okay. It might even be ready tomorrow.

304 00:26:16.890 00:26:17.540 Nandika Jhunjhunwala: No.

305 00:26:17.780 00:26:20.570 Nandika Jhunjhunwala: So, I guess what I wanted to ask you is, like.

306 00:26:20.950 00:26:24.790 Nandika Jhunjhunwala: Do you think I should be instrumenting every…

307 00:26:24.930 00:26:27.950 Nandika Jhunjhunwala: button here? Probably not, right? Like, if you’re…

308 00:26:28.060 00:26:32.620 Nandika Jhunjhunwala: No. Doing view setting, or, like, toggling, like, certain…

309 00:26:32.680 00:26:35.140 Greg Stoutenburg: Fields on and off, that’s not important.

310 00:26:35.290 00:26:44.079 Greg Stoutenburg: No, not really. So, there are so many buttons, and this is, like… it’s an app that just has a lot of things that you can configure, so we should…

311 00:26:44.080 00:26:56.370 Greg Stoutenburg: In order to avoid having, like, a really bloated tracking plan and just paying for tons of events that don’t help us understand anything, what we want to do is just rely on auto-capture for those individual clicks.

312 00:26:56.400 00:27:03.930 Greg Stoutenburg: and look at what a user might be attempting to do, and those are the things that we actually want to map out and instrument on our own. So…

313 00:27:04.310 00:27:14.540 Greg Stoutenburg: So for… yeah, I mean, for this area, what we want to think about then is probably anyone who’s just in the activity area is just…

314 00:27:14.900 00:27:19.149 Greg Stoutenburg: they’re… they’re just looking. They’re like, what have we… what have we done lately?

315 00:27:19.180 00:27:37.330 Greg Stoutenburg: Probably nothing to map out there. That’s not really a distinct workflow. But queues is, right? If I… if you go to queues, right, then this is someone who’s, like, setting something up. So here we would want to go, alright, user clicked queue, right, user clicked open, or user clicked create, and then follow those steps through there.

316 00:27:37.710 00:27:43.799 Greg Stoutenburg: And I think, actually, that is one that, in the tracking plan, using the Figma designs that I had available,

317 00:27:44.320 00:27:46.710 Greg Stoutenburg: I mapped out a version of that

318 00:27:47.080 00:27:55.640 Greg Stoutenburg: We’ll see if it’s what, you know, shows up here, but, like, from queue creation, to strategy selection and so on, to adding a member,

319 00:27:56.120 00:27:58.909 Greg Stoutenburg: That’s something that we would want to map out, yeah.

320 00:27:59.080 00:27:59.690 Nandika Jhunjhunwala: Sounds good.

321 00:27:59.690 00:28:00.380 Greg Stoutenburg: Yeah.

322 00:28:00.980 00:28:03.049 Nandika Jhunjhunwala: And then assignments, okay.

323 00:28:03.420 00:28:04.440 Nandika Jhunjhunwala: It’s not done yet.

324 00:28:04.440 00:28:05.700 Greg Stoutenburg: Okay, yeah, cool.

325 00:28:06.330 00:28:09.569 Nandika Jhunjhunwala: And this we would want to instrument, I’m assuming?

326 00:28:09.570 00:28:13.079 Greg Stoutenburg: Yeah, yeah, let’s do this. And that is… that is in the tracking plan already, actually.

327 00:28:13.080 00:28:16.680 Nandika Jhunjhunwala: Okay, so when you create a queue, queue identifier…

328 00:28:16.680 00:28:17.220 Greg Stoutenburg: Yep.

329 00:28:17.220 00:28:18.619 Nandika Jhunjhunwala: Meetings only, assignments only.

330 00:28:18.620 00:28:25.949 Greg Stoutenburg: One of those. Yep. Because this is someone really doing something, right? Rather than, you know, clicking a button or browsing or something.

331 00:28:25.950 00:28:26.400 Nandika Jhunjhunwala: Got it.

332 00:28:26.400 00:28:28.010 Greg Stoutenburg: Yeah, so we’ll want that in.

333 00:28:28.150 00:28:40.000 Greg Stoutenburg: And the reason why is that when we then go create those funnels to figure out what users are doing, where they might be getting stuck, it’s those sequences of activity that are gonna reveal that for us.

334 00:28:40.660 00:28:41.420 Nandika Jhunjhunwala: But…

335 00:28:41.420 00:28:42.020 Greg Stoutenburg: Yes.

336 00:28:44.910 00:28:46.140 Nandika Jhunjhunwala: Sounds good.

337 00:28:49.810 00:29:01.609 Greg Stoutenburg: I also wanted to ask you, I know that there was some… there were some events that were being collected in segment and sent to various destinations. Post Hog is not a destination.

338 00:29:01.650 00:29:16.460 Greg Stoutenburg: Amplitude is… there’s not a lot going from segment, really. I mean, it’s, you know, you’re on a relatively inexpensive plan and sending, like, 15% of the monthly allocation.

339 00:29:17.190 00:29:21.150 Greg Stoutenburg: So I… I wondered if…

340 00:29:22.160 00:29:45.829 Greg Stoutenburg: I wondered what the plan might be, and, you know, I mean, I have recommendations, but what the thoughts might be around what’s being collected in segment currently, and if you’d want to continue relying on that to send to different destinations, or just go, like, you know, we can just use anything that’s in post-hog, we’ll just treat that as the product analytics single source of truth, and then if we want to be sending data from post-hog elsewhere, then we can do that. For example.

341 00:29:46.230 00:29:46.580 Nandika Jhunjhunwala: No.

342 00:29:46.580 00:29:48.940 Greg Stoutenburg: You know, cohorts, or webhooks, or whatever.

343 00:29:50.470 00:30:02.489 Nandika Jhunjhunwala: No, I think that’s a great, great call-out. I haven’t thought about it too much. So, I don’t know what they were sending to Amplitude. I think it was really basic data, like user properties.

344 00:30:02.860 00:30:03.960 Nandika Jhunjhunwala: So…

345 00:30:03.960 00:30:05.570 Greg Stoutenburg: Yeah, the other thing’s even being collected.

346 00:30:05.570 00:30:06.020 Nandika Jhunjhunwala: Yeah.

347 00:30:06.020 00:30:13.470 Greg Stoutenburg: At all. So there’s… well, 50% of the events are just… they don’t even have a name, so we don’t know.

348 00:30:14.210 00:30:20.460 Greg Stoutenburg: Yeah, meeting mark, form submitted, logins, publishers, use.

349 00:30:21.040 00:30:25.749 Nandika Jhunjhunwala: I mean, most of these were instrumenting on the front end now, okay.

350 00:30:25.940 00:30:34.460 Nandika Jhunjhunwala: But I think a good call-up would be adding in posthog and then maybe sending in, like, customer data. Yeah. We could do that here, probably.

351 00:30:34.460 00:30:37.790 Greg Stoutenburg: Yeah. Yeah. Post hog is not in here. Amplitude is.

352 00:30:37.790 00:30:40.199 Nandika Jhunjhunwala: Yeah, this hasn’t been updated for a while.

353 00:30:40.760 00:30:47.100 Greg Stoutenburg: Okay, yeah. And then really, you know, I think something that might be worth it, like, you’re not spending

354 00:30:47.560 00:30:54.119 Greg Stoutenburg: kind of hardly any money on this right now, it’s like $100 a month. I just looked at it today, let’s see.

355 00:30:54.800 00:31:05.880 Greg Stoutenburg: Yeah, you’re spending, like, $120 a month, so, like, inconsequential, but also, you know, you don’t really want, like, cluttered data, so as I look at destinations… wait, sorry, let’s go back.

356 00:31:06.820 00:31:11.630 Greg Stoutenburg: For sources, there’s the app, and then there’s just this Node.js snippet.

357 00:31:11.630 00:31:12.130 Nandika Jhunjhunwala: Yeah.

358 00:31:12.130 00:31:15.879 Greg Stoutenburg: That’s on the page. For… here, this is the better visual.

359 00:31:16.510 00:31:21.669 Greg Stoutenburg: For connections, these are all of the connections.

360 00:31:22.470 00:31:25.940 Greg Stoutenburg: I wonder… I don’t know what all of them do, I don’t know what this does.

361 00:31:26.590 00:31:27.020 Nandika Jhunjhunwala: Yeah.

362 00:31:27.020 00:31:30.839 Greg Stoutenburg: That’s, you know, that’s Clearbit. I don’t know what this might be. Yeah.

363 00:31:31.560 00:31:33.410 Greg Stoutenburg: I don’t know to what degree intercom.

364 00:31:33.410 00:31:33.920 Nandika Jhunjhunwala: Hmm.

365 00:31:33.920 00:31:41.540 Greg Stoutenburg: SRIO or use Slack, that’s good. But also, like, I… it might be worth us just thinking about

366 00:31:41.640 00:31:44.679 Greg Stoutenburg: In the future, which one of these do you want to be using?

367 00:31:44.900 00:31:49.769 Greg Stoutenburg: And then, you know, I mean, consider turning segment off.

368 00:31:50.120 00:31:55.950 Greg Stoutenburg: Or just adding post hog and figuring out which of the events that are being collected should be sent over.

369 00:31:55.950 00:31:56.670 Nandika Jhunjhunwala: Yeah.

370 00:31:56.670 00:32:03.879 Greg Stoutenburg: And then, there might also be from… from Post Hog, I mean, I know PostHog connects to Slack and Customer I.O,

371 00:32:04.060 00:32:09.920 Greg Stoutenburg: and intercom. You know, so some of those connections can also just be direct from postdog.

372 00:32:09.920 00:32:11.260 Nandika Jhunjhunwala: Yeah. No, I think.

373 00:32:11.260 00:32:14.690 Greg Stoutenburg: Not something answered today, but just, you know…

374 00:32:14.690 00:32:21.240 Nandika Jhunjhunwala: I think it’s a great thing to be thinking about. I think we would need the engineering team involved here, and, like, right now, I’m sure, you know, like, there are.

375 00:32:21.240 00:32:22.399 Greg Stoutenburg: Sure. Yeah, they’re busy.

376 00:32:22.400 00:32:31.959 Nandika Jhunjhunwala: burdened with Phoenix, so once they have, like, bandwidth there, I think, we could send, like, website data here, like, because we’re getting a new marketing website, so probably, like.

377 00:32:31.960 00:32:34.749 Greg Stoutenburg: We can send in, like, DNN data.

378 00:32:34.750 00:32:35.900 Nandika Jhunjhunwala: Yeah.

379 00:32:36.020 00:32:48.369 Nandika Jhunjhunwala: identify them, like, logging in or, like, self-serve signing up, from segment, or I think, like, I don’t know, I think PostHog does that directly as well, so we could just put it on PostHog, and then… yeah.

380 00:32:48.370 00:32:48.990 Greg Stoutenburg: Yeah.

381 00:32:49.220 00:32:52.190 Nandika Jhunjhunwala: This is just, like, a conversation with engineering that I…

382 00:32:52.190 00:33:12.170 Greg Stoutenburg: Yeah, that sounds good. And, you know, so again, I don’t know what all of these destinations do, but given that the only source that’s actually being used is just the, you know, just the node snippet that’s in the app and on the website, like, PostHog actually does all that just by itself. So, like, segment isn’t really being used for anything.

383 00:33:12.660 00:33:20.380 Greg Stoutenburg: So, yeah, again, unless there’s some destination here that Posthog, as of right now, doesn’t connect to, but then, you know, there’s workarounds for that, too, so…

384 00:33:20.380 00:33:25.829 Nandika Jhunjhunwala: Yeah, no, for sure, yeah, you’re right. We probably don’t even need segment for post-hoc, because it has, like…

385 00:33:26.570 00:33:28.749 Nandika Jhunjhunwala: A good amount of connection, so…

386 00:33:28.750 00:33:33.790 Greg Stoutenburg: Yeah, yeah. Yeah, and then where I think, like, for PLG purposes,

387 00:33:34.270 00:33:52.490 Greg Stoutenburg: the kind of data that you’re getting in post hoc would be most useful would be, like, sending cohorts to Customer I.O. for engagement, or, like, you know, sending events to Customer I.O, so, you know, anytime someone clicked the upgrade button, you immediately hit them with, like, a, hey, we saw you were scoping out this plan, why don’t you, you know, whatever.

388 00:33:52.490 00:33:53.969 Nandika Jhunjhunwala: Those sorts of things.

389 00:33:54.210 00:33:55.169 Nandika Jhunjhunwala: That’s a… yeah.

390 00:33:56.640 00:33:57.670 Greg Stoutenburg: Alright.

391 00:33:58.090 00:34:10.259 Greg Stoutenburg: Okay, I think we’re in good shape for now, so I think our takeaways were, you’re gonna explore what user property implementation looks like in Post Hog. Yeah. And,

392 00:34:10.710 00:34:11.750 Greg Stoutenburg: And…

393 00:34:12.250 00:34:24.809 Greg Stoutenburg: Yeah, and then I guess the other one is… just take a look at what I’ve already jotted down for… in the tracking plan for the queue creation process. Yeah. Because now that that’s up, like.

394 00:34:25.080 00:34:28.679 Greg Stoutenburg: you know, you can see if I miss anything, or if there’s anything else that we should be collecting there.

395 00:34:29.070 00:34:31.939 Greg Stoutenburg: We can add that to the tracking plan, and then instrument that as well.

396 00:34:31.949 00:34:32.669 Nandika Jhunjhunwala: outfit.

397 00:34:32.830 00:34:33.639 Greg Stoutenburg: Boom.

398 00:34:34.100 00:34:34.900 Greg Stoutenburg: Cool.

399 00:34:35.139 00:34:38.289 Nandika Jhunjhunwala: Sure. Yeah, I’ll do all of that. Awesome.

400 00:34:39.049 00:34:45.229 Nandika Jhunjhunwala: I know, I think… I think you said the… the table workflow, like, user journey is live, right?

401 00:34:45.729 00:34:50.389 Nandika Jhunjhunwala: So, I guess after I have the queue events, we can also do the queue user journey? Yep.

402 00:34:51.100 00:34:54.750 Greg Stoutenburg: Yep, that sounds good. Cool. Awesome. Alright.

403 00:34:54.929 00:34:55.929 Nandika Jhunjhunwala: Thank you.

404 00:34:55.929 00:34:58.380 Greg Stoutenburg: Yep, talk soon. Alright. Bye.