Meeting Title: Phoenix Event Tracking Plan Discussion Date: 2026-02-10 Meeting participants: Greg Stoutenburg, Nandika Jhunjhunwala, Mustafa Raja, Caitlyn Vaughn
WEBVTT
1 00:00:44.980 ⇒ 00:00:45.940 Greg Stoutenburg: Hey, y’all.
2 00:00:45.940 ⇒ 00:00:46.830 Nandika Jhunjhunwala: Whoa.
3 00:00:51.230 ⇒ 00:00:52.029 Greg Stoutenburg: There we go.
4 00:00:52.630 ⇒ 00:00:53.970 Greg Stoutenburg: Caitlin will be joining us.
5 00:00:54.690 ⇒ 00:00:55.290 Nandika Jhunjhunwala: Yes.
6 00:00:57.460 ⇒ 00:00:58.729 Greg Stoutenburg: How’s your week so far?
7 00:00:59.640 ⇒ 00:01:01.389 Nandika Jhunjhunwala: Oh, it’s good. What about you?
8 00:01:01.960 ⇒ 00:01:04.109 Greg Stoutenburg: Very good, it’s warming up a little bit here.
9 00:01:04.110 ⇒ 00:01:05.450 Nandika Jhunjhunwala: Nice, same here.
10 00:01:05.450 ⇒ 00:01:16.670 Greg Stoutenburg: Which is, I don’t know, I have mixed feelings. I got to skate on, Frozen Pond several times last week, and that’s fun, so… but if it’s gonna hit 40, can’t do that for long.
11 00:01:28.290 ⇒ 00:01:30.230 Nandika Jhunjhunwala: I will thank you, M.
12 00:01:50.440 ⇒ 00:02:00.559 Greg Stoutenburg: Earlier today, when you messaged me, or maybe yesterday evening, when you messaged me about best practices for naming conventions, I sent you an amplitude guide. Hey Caitlin, how’s it going today?
13 00:02:02.650 ⇒ 00:02:05.969 Caitlyn Vaughn: Sorry, my… I don’t press the button. Hi, good, how are you guys?
14 00:02:05.970 ⇒ 00:02:08.280 Greg Stoutenburg: I’m doing pretty well.
15 00:02:08.460 ⇒ 00:02:27.749 Greg Stoutenburg: Yeah, not… I sent you an Amplitude link, Nandika, but there’s also, there’s also a section of Post Hog’s docs that I actually just found a little later that mentions some. I think the only thing I would say, the only place where I would, like, depart from Post Hogs and side with Amplitude’s recommendation is that PostHog just says.
16 00:02:27.750 ⇒ 00:02:48.520 Greg Stoutenburg: put everything in lowercase, and my opinion is that, at least when it comes to event names and other people, because you want other people to eventually be building these charts, it is just more natural to read, you know, that object-action pattern with an initial capital, and then lowercase, then an initial capital, and then lowercase. Other than that, all good, all the same stuff.
17 00:02:49.520 ⇒ 00:02:50.200 Greg Stoutenburg: Yeah.
18 00:02:51.910 ⇒ 00:02:54.330 Greg Stoutenburg: Cool. So…
19 00:02:54.460 ⇒ 00:03:06.780 Greg Stoutenburg: Yes, there it is. Yep, with the space. I’ve also seen people, you know, say camel case, but there’s, like, no spaces, so then it would be… Yep. But then that’s also…
20 00:03:07.760 ⇒ 00:03:08.919 Greg Stoutenburg: Weird looking.
21 00:03:09.560 ⇒ 00:03:11.180 Caitlyn Vaughn: That’s, like, real camel casing, though.
22 00:03:11.180 ⇒ 00:03:11.700 Greg Stoutenburg: Yeah.
23 00:03:11.700 ⇒ 00:03:12.380 Caitlyn Vaughn: Yeah.
24 00:03:12.530 ⇒ 00:03:13.900 Greg Stoutenburg: Yeah, yeah, yep.
25 00:03:15.870 ⇒ 00:03:26.449 Greg Stoutenburg: Yeah, thank goodness someone thought of that name. This is like a camel. Okay. So, cool. Well…
26 00:03:26.630 ⇒ 00:03:42.659 Greg Stoutenburg: Welcome back, Caitlin, and, wanted to just sort of talk through what we have so far for an event tracking plan, you know, with where Phoenix is at now. Nanika, I think you had, something to sort of tee off our intro.
27 00:03:43.100 ⇒ 00:03:43.620 Nandika Jhunjhunwala: Yeah.
28 00:03:43.620 ⇒ 00:03:44.960 Greg Stoutenburg: We should just start there.
29 00:03:45.500 ⇒ 00:03:56.970 Nandika Jhunjhunwala: Yeah, for sure. What I wanted to show mostly was, like, the current version of PNX that I have access to for instrumentation, and what that looks like in terms of what I can actually instrument.
30 00:03:56.970 ⇒ 00:03:57.550 Greg Stoutenburg: Okay.
31 00:03:57.550 ⇒ 00:04:03.540 Nandika Jhunjhunwala: Because I think, like, the product is, like, very much a work in progress, so…
32 00:04:04.090 ⇒ 00:04:10.919 Nandika Jhunjhunwala: I can start off sharing that, and then if you guys have questions, I’ll just… yeah, give me a second.
33 00:04:11.090 ⇒ 00:04:11.800 Greg Stoutenburg: Yeah.
34 00:04:15.540 ⇒ 00:04:16.690 Nandika Jhunjhunwala: A…
35 00:04:26.690 ⇒ 00:04:39.340 Nandika Jhunjhunwala: Because I looked at the current version of Phoenix, and then our tracking plan, and I was like, what can I start tracking now? Yeah. And there was, like, not super overlap there, so, just something to think about.
36 00:04:39.340 ⇒ 00:04:40.000 Greg Stoutenburg: Yeah.
37 00:04:40.000 ⇒ 00:04:41.010 Nandika Jhunjhunwala: Listen.
38 00:04:41.670 ⇒ 00:04:57.190 Nandika Jhunjhunwala: This is the app… sorry, there’s a post hoc, running around here, but besides that, this is, like, the… I think the OI screen, like, divisions and, like, the query bar will come on later. And then we have tables and scheduling.
39 00:04:57.300 ⇒ 00:04:58.659 Nandika Jhunjhunwala: And then settings.
40 00:04:59.060 ⇒ 00:05:05.299 Nandika Jhunjhunwala: And then the data pipeline and the launcher here don’t do anything. I think this is for testing purposes, and this is, like…
41 00:05:05.440 ⇒ 00:05:07.050 Nandika Jhunjhunwala: Adding a placeholder for now.
42 00:05:07.200 ⇒ 00:05:12.670 Nandika Jhunjhunwala: And then when I click into tables, this is what it looks like, and then…
43 00:05:12.880 ⇒ 00:05:15.390 Nandika Jhunjhunwala: I wanted to instrument it,
44 00:05:15.850 ⇒ 00:05:22.470 Nandika Jhunjhunwala: you know, postdoc will detect all the elements and stuff. So that’s pretty easy and simple to do.
45 00:05:22.860 ⇒ 00:05:27.500 Nandika Jhunjhunwala: But besides that, if there were, like, other things.
46 00:05:28.090 ⇒ 00:05:30.859 Nandika Jhunjhunwala: that you wanted to instrument, there’s, like, custom…
47 00:05:31.260 ⇒ 00:05:33.090 Nandika Jhunjhunwala: Come back so that we can…
48 00:05:33.630 ⇒ 00:05:38.849 Nandika Jhunjhunwala: sort of spin up to, like, all people, companies, like, Collins, and, like…
49 00:05:39.650 ⇒ 00:05:46.600 Nandika Jhunjhunwala: these buttons are all that work for me. This is, like, the front end that I have access to, so I can’t just upload a CSV and see what happens.
50 00:05:46.720 ⇒ 00:05:53.069 Nandika Jhunjhunwala: Yet, like, tabs on top, and, like, sync changes, and share, and, like, those kind of buttons.
51 00:05:53.460 ⇒ 00:05:54.620 Greg Stoutenburg: Okay.
52 00:05:54.620 ⇒ 00:06:01.750 Nandika Jhunjhunwala: I can, like, toggle with different views, and… It’s like… yeah.
53 00:06:02.840 ⇒ 00:06:06.760 Nandika Jhunjhunwala: And scheduling is what it looks like.
54 00:06:10.200 ⇒ 00:06:12.299 Nandika Jhunjhunwala: So what I have access to is, like.
55 00:06:12.450 ⇒ 00:06:15.530 Nandika Jhunjhunwala: a front-end, like, skeleton, and yep.
56 00:06:15.900 ⇒ 00:06:20.440 Nandika Jhunjhunwala: within this, like, there are definitely, like, events we can start instrumenting. Yeah.
57 00:06:20.440 ⇒ 00:06:20.840 Greg Stoutenburg: Cool.
58 00:06:20.840 ⇒ 00:06:25.049 Nandika Jhunjhunwala: But that’s… that’s the extent of what I have access to so far.
59 00:06:25.050 ⇒ 00:06:25.400 Greg Stoutenburg: Okay.
60 00:06:25.400 ⇒ 00:06:26.380 Nandika Jhunjhunwala: Yes.
61 00:06:26.850 ⇒ 00:06:28.279 Greg Stoutenburg: Cool. Looks good.
62 00:06:28.480 ⇒ 00:06:38.210 Greg Stoutenburg: That’s great. Yeah, exciting. So, as far as, as far as workflows, so in what you have so far, when you open tables.
63 00:06:38.210 ⇒ 00:06:38.670 Nandika Jhunjhunwala: Yeah.
64 00:06:38.670 ⇒ 00:06:45.239 Greg Stoutenburg: the user be doing with tables there? So they click this, what are they… what’s their goal when they come here?
65 00:06:45.900 ⇒ 00:07:00.689 Caitlyn Vaughn: I can take over here if it’s easier. Yeah. So there’s, like, a few things that a user might do. The first is you basically import a list, right? So you can either do that from your CRM, or you should be able to upload a CSV soon.
66 00:07:00.690 ⇒ 00:07:13.480 Caitlyn Vaughn: Or you can pull from your, basically, like, default backend database. But for all intents and purposes of, like, pretending like we’re a new user, you’re basically either gonna pull from your CRM, or you’re gonna upload a CSV.
67 00:07:13.630 ⇒ 00:07:21.720 Caitlyn Vaughn: Now, once you have that data, you can basically go through and turn it into a view, you can edit it, you can,
68 00:07:22.090 ⇒ 00:07:39.720 Caitlyn Vaughn: basically use all of our data sources to enrich any missing data, you can update, you know, existing data fields, that kind of stuff, and then you will eventually be able to either push it back into your CRM or update your, backend database.
69 00:07:39.770 ⇒ 00:07:42.929 Caitlyn Vaughn: It’s basically, like, like a clay… thing.
70 00:07:42.930 ⇒ 00:07:55.120 Greg Stoutenburg: Yeah, okay, okay, great. Okay, so this is just where you’re gonna collect and maintain those records, and then you decide what you want to do with them after. Push them to some other source, or reference them somewhere. Okay, great.
71 00:07:55.120 ⇒ 00:07:56.020 Caitlyn Vaughn: Exactly.
72 00:07:56.020 ⇒ 00:08:05.280 Greg Stoutenburg: Okay, cool. That’s helpful. Okay, and then for the scheduler, I think that was…
73 00:08:05.750 ⇒ 00:08:11.010 Greg Stoutenburg: That was pretty clear, right? I mean, that’s… it’s for scheduling meetings. Senior meetings, assigning.
74 00:08:11.430 ⇒ 00:08:15.699 Greg Stoutenburg: Meetings, tracking your meetings, booking them. Okay, cool.
75 00:08:15.870 ⇒ 00:08:27.369 Greg Stoutenburg: Okay, yeah, that sounds good. We can, we can dive in and start with those things. Any other comments or thoughts or anything? And then I’ll sort of show what I have in place so far.
76 00:08:29.930 ⇒ 00:08:34.930 Nandika Jhunjhunwala: I think my only thought is I’m gonna… I’m gonna sync with, like, engineering and see, like.
77 00:08:35.260 ⇒ 00:08:38.930 Nandika Jhunjhunwala: what else I can have access to, but I’m assuming, like.
78 00:08:39.070 ⇒ 00:08:47.160 Nandika Jhunjhunwala: they’re all working on their own branches, and it’s not much to main, and since I’m, like, off of, like, the main branch, this is, like, what’s, like, final and done.
79 00:08:47.270 ⇒ 00:08:50.320 Nandika Jhunjhunwala: So as soon as I have access to, like, more things, like.
80 00:08:50.450 ⇒ 00:09:01.629 Nandika Jhunjhunwala: I can, like, screen share or, like, record or whatever’s easier. I can share, like, what the UI looks at that point, and then continue to keep you guys in the loop, so we can update our tracking plan accordingly.
81 00:09:02.010 ⇒ 00:09:03.869 Nandika Jhunjhunwala: And stay on top of that.
82 00:09:04.140 ⇒ 00:09:04.640 Nandika Jhunjhunwala: That…
83 00:09:04.640 ⇒ 00:09:05.210 Greg Stoutenburg: Yeah.
84 00:09:05.210 ⇒ 00:09:05.820 Nandika Jhunjhunwala: time.
85 00:09:05.960 ⇒ 00:09:18.430 Greg Stoutenburg: Yeah, yeah, that sounds good, and so, yeah, let’s just, you know, stay in touch, Sin Mustafa as well, because we can… so it’s pretty awesome that PostHog will auto-capture, like, a lot of stuff, and that you can do things like click a button.
86 00:09:18.430 ⇒ 00:09:19.040 Nandika Jhunjhunwala: Yeah.
87 00:09:19.040 ⇒ 00:09:28.809 Greg Stoutenburg: But that won’t necessarily, like, because… because our goal is, like, looking to a future where you all, and then, you know, eventually you’ll onboard others to be able to engage with these analytics, we want to make.
88 00:09:28.810 ⇒ 00:09:29.590 Nandika Jhunjhunwala: Make sure that everything’s.
89 00:09:29.590 ⇒ 00:09:47.860 Greg Stoutenburg: everything is, like, really easy to onboard to. So, so we want to make sure that, like, we’ve really grabbed onto the right event, and that we’re able to build charts that will, you know, that are sensible to anyone who’s putting them together. So, we can, AutoCapture will grab
90 00:09:48.340 ⇒ 00:09:54.940 Greg Stoutenburg: Tons of cool stuff, and let me… Just give some examples,
91 00:09:56.090 ⇒ 00:09:58.849 Greg Stoutenburg: But we’ll want to sort of manually map out
92 00:09:58.960 ⇒ 00:10:15.809 Greg Stoutenburg: the rest, when it comes to these, like, key workflows, we don’t… when it comes to the tracking plan, we don’t have to put everything in the tracking plan, right? But what we do want to include in the tracking plan is, like, those core interactions, those things that are part of some workflow that we think is important to measure, things like that.
93 00:10:15.810 ⇒ 00:10:16.330 Nandika Jhunjhunwala: Yeah.
94 00:10:16.700 ⇒ 00:10:25.880 Greg Stoutenburg: So in post-hog, anything that is an auto-capture event gets a dollar sign in front of it. And, so for interaction events, we can pretty much…
95 00:10:25.880 ⇒ 00:10:27.850 Nandika Jhunjhunwala: So, unless there are other…
96 00:10:27.850 ⇒ 00:10:36.420 Greg Stoutenburg: events that are parts of interactions in default that are really important to track, we can actually just rely on auto-capture, like, for the whole category. So any click
97 00:10:36.420 ⇒ 00:10:50.189 Greg Stoutenburg: or tap of the mouse, or a rage click, where it looks like someone’s just clicking the same spot multiple times with that change, or a dead click, where that’s where a user clicks a page and nothing happens. Those will just be tracked by default, and you can go in and do things like watch session replays and stuff like that.
98 00:10:50.790 ⇒ 00:10:54.170 Greg Stoutenburg: Similarly for navigation type.
99 00:10:54.400 ⇒ 00:11:00.019 Greg Stoutenburg: events, like page views and page leaves and things like that, posthoc is just… is just gonna track them.
100 00:11:00.810 ⇒ 00:11:16.290 Greg Stoutenburg: Now, for, yeah, so that’s… that’s that. So, if it’s alright, I’d like to show you what I wrote out so far for events that I think we should manually instrument, and this is… this is something that would require that front-end touch, then.
101 00:11:16.580 ⇒ 00:11:17.280 Nandika Jhunjhunwala: Yeah.
102 00:11:17.280 ⇒ 00:11:18.500 Greg Stoutenburg: With what you just showed.
103 00:11:18.500 ⇒ 00:11:18.870 Nandika Jhunjhunwala: Sorry.
104 00:11:18.870 ⇒ 00:11:19.670 Greg Stoutenburg: Yeah, good.
105 00:11:19.670 ⇒ 00:11:25.930 Nandika Jhunjhunwala: As a quick note, any manual events, I have a local instance of, Phoenix.
106 00:11:26.130 ⇒ 00:11:30.759 Nandika Jhunjhunwala: And I can… I can also add those in manually.
107 00:11:31.480 ⇒ 00:11:37.190 Nandika Jhunjhunwala: So, yeah, I think that should also, like, move quickly, hopefully, if I… I think I can figure it out, yeah.
108 00:11:37.390 ⇒ 00:11:46.640 Greg Stoutenburg: Yeah, that sounds good. Yeah, we’ll just coordinate on that and, and sort of make sure that we’re tracking, like, what’s going in and when, and make sure that we have a record of it.
109 00:11:46.920 ⇒ 00:11:50.600 Greg Stoutenburg: So for, so for Default OS,
110 00:11:51.070 ⇒ 00:12:07.199 Greg Stoutenburg: what you already showed me is gonna require some change to this, but when I was looking at all the things that it looks like a user could do, at least in the Figma designs, is basically you can query Default OS, meaning type something into the field and hit enter, select a result from what pops up.
111 00:12:07.630 ⇒ 00:12:16.239 Greg Stoutenburg: Again, this was in the designs, so we couldn’t instrument these yet. Modify a widget, so add a widget, change it, or move it.
112 00:12:16.660 ⇒ 00:12:19.250 Greg Stoutenburg: And then… switch workspaces.
113 00:12:19.500 ⇒ 00:12:22.779 Greg Stoutenburg: Which, I guess that’ll be coming down the line.
114 00:12:23.420 ⇒ 00:12:26.909 Greg Stoutenburg: For these two events.
115 00:12:27.590 ⇒ 00:12:32.550 Greg Stoutenburg: I think the properties we’d want to track there, like, for result selected, would be the type of result.
116 00:12:33.470 ⇒ 00:12:36.940 Greg Stoutenburg: And… That would be, as far as I can tell.
117 00:12:37.460 ⇒ 00:12:41.250 Greg Stoutenburg: The things that you’ll be able to select will be… a widget.
118 00:12:41.530 ⇒ 00:12:46.910 Greg Stoutenburg: And then the value of that would be whatever all the widgets are that a person could possibly select there.
119 00:12:47.630 ⇒ 00:13:04.910 Greg Stoutenburg: or in action. They take an action, you know, they tape something in, and it’s like, you know, add this record to my CRM, something like that, right? Or book a new meeting for 30 minutes, or something like that, right? So they’re gonna take some action, and then whatever the actions are that a user can take from there, we can list those off as the values of
120 00:13:05.220 ⇒ 00:13:07.460 Greg Stoutenburg: The result selected was a quick action.
121 00:13:09.010 ⇒ 00:13:11.970 Greg Stoutenburg: Does that make sense, what we’d be trying to set up there?
122 00:13:12.520 ⇒ 00:13:13.350 Greg Stoutenburg: Okay.
123 00:13:13.430 ⇒ 00:13:14.340 Nandika Jhunjhunwala: Yep. Cool.
124 00:13:14.340 ⇒ 00:13:18.050 Greg Stoutenburg: For widget modified, same kind of thing, you know,
125 00:13:18.610 ⇒ 00:13:30.470 Greg Stoutenburg: Property name, we have the property of action, also the property of widget type. Widget type, already covered that. Action would just be things like widget added, widget removed, widget moved, widget settings changed.
126 00:13:32.320 ⇒ 00:13:33.180 Greg Stoutenburg: Okay.
127 00:13:33.880 ⇒ 00:13:35.770 Greg Stoutenburg: Cool.
128 00:13:36.090 ⇒ 00:13:44.689 Greg Stoutenburg: Moving along then, so I won’t just, like, read through all these, but just to kind of give an overview. For the queue creation screen,
129 00:13:45.030 ⇒ 00:13:51.259 Greg Stoutenburg: we… the designs for those are final as well, that we have in Figma. It’ll… it’ll get stood up that way eventually.
130 00:13:51.970 ⇒ 00:13:53.359 Greg Stoutenburg: Yeah? Okay.
131 00:13:53.500 ⇒ 00:13:55.049 Greg Stoutenburg: Cool. So it looked like…
132 00:13:55.280 ⇒ 00:14:07.570 Greg Stoutenburg: I selected all these events, they all look like they are critical to using the queue. I mean, it’s to, you know, click the button to create a queue, you name it, you give it an ID, you give it a use case.
133 00:14:07.870 ⇒ 00:14:12.620 Greg Stoutenburg: And those use cases are, assignments, meetings, or meetings and assignments.
134 00:14:13.450 ⇒ 00:14:20.109 Greg Stoutenburg: Choose each of distribution strategy, Tiebreaker strategy, fairness strategy, and slot strategy, and then add members.
135 00:14:22.530 ⇒ 00:14:27.319 Greg Stoutenburg: So, that’s what I saw there. We’ll give properties for each of those, like what the use case is.
136 00:14:27.530 ⇒ 00:14:29.550 Greg Stoutenburg: As the user’s going through the flow.
137 00:14:29.670 ⇒ 00:14:38.709 Greg Stoutenburg: We want to include information like, as they select a distribution strategy, they select it for a particular named and identified queue.
138 00:14:39.360 ⇒ 00:14:41.520 Greg Stoutenburg: This’ll give us information on things like
139 00:14:41.990 ⇒ 00:14:46.049 Greg Stoutenburg: Which distribution strategy is chosen?
140 00:14:46.490 ⇒ 00:14:48.210 Greg Stoutenburg: Right, we’ll be able to get that kind of view.
141 00:14:50.120 ⇒ 00:15:03.910 Greg Stoutenburg: Yeah. Okay, so those are the… it looked like… those are the workflows that it seemed like were closest to being done. With what you showed me, we can add to the tracking plan more about those interactions that you just highlighted at the beginning of this call.
142 00:15:07.830 ⇒ 00:15:08.730 Greg Stoutenburg: Okay.
143 00:15:09.410 ⇒ 00:15:15.839 Greg Stoutenburg: Alright, so I think, maybe from here, the next steps are going to be…
144 00:15:15.840 ⇒ 00:15:34.100 Greg Stoutenburg: getting clear on what user properties we want to make sure to be tracking, and that’s going to be basically anything that would go into a customer table, but also you’ve got this concept of a workspace and also of an organization. So, those are going to be properties that apply to, they’re going to apply to users
145 00:15:34.100 ⇒ 00:15:43.080 Greg Stoutenburg: in their groups. So that’s… that’s something we’ll want to make sure to include. Are there any other, as far as you can think of, any other…
146 00:15:43.460 ⇒ 00:15:47.210 Greg Stoutenburg: Characteristics of users that will be very important to track.
147 00:15:47.590 ⇒ 00:15:49.570 Greg Stoutenburg: In default, other than, you know.
148 00:15:50.300 ⇒ 00:15:57.720 Greg Stoutenburg: I don’t know what to say, normal stuff, right? Like, when did they sign up? You know, where are they? Did they come in on a UTM? Things like that.
149 00:15:58.940 ⇒ 00:16:05.159 Nandika Jhunjhunwala: I think, I think the referral source adopt me one. I think we have that now, too, as far as I know.
150 00:16:05.440 ⇒ 00:16:16.270 Nandika Jhunjhunwala: And then… I don’t know if, Caitlin, you want to make the distinction between PLG and, like, sales user? Like, if they came from, like, a PLG source tester versus, like.
151 00:16:16.740 ⇒ 00:16:30.620 Nandika Jhunjhunwala: if they signed up via, like, a sales motion. I’m not sure what we’re tracking, like, in the customer database on the back end, but I’ve asked Victor to, like, put that in Post Talk so we can access that information, hopefully soon.
152 00:16:30.780 ⇒ 00:16:31.460 Nandika Jhunjhunwala: Yep.
153 00:16:31.460 ⇒ 00:16:46.589 Caitlyn Vaughn: Yeah, I’m wondering if we track that here, or how we would, but I think you’re talking about what I’m thinking, which is, like, attribution. Like, where did the sign-up come from, and it was, like, AOB, or marketing, or organic, or whatever.
154 00:16:48.050 ⇒ 00:16:50.950 Greg Stoutenburg: Yeah. For attribution, though.
155 00:16:51.510 ⇒ 00:17:00.859 Nandika Jhunjhunwala: leads that come from, like, a LinkedIn paid ad have a UTM, and then leads that come from, like, organic, like, wouldn’t have a UTM, and then…
156 00:17:01.030 ⇒ 00:17:09.830 Nandika Jhunjhunwala: For email, though, I think tracking attribution is more tricky, because, it makes it just land on the page. There isn’t, like, a tracking link in the email.
157 00:17:09.970 ⇒ 00:17:10.319 Caitlyn Vaughn: Yeah.
158 00:17:10.329 ⇒ 00:17:16.759 Nandika Jhunjhunwala: But I think we could definitely track to some extent, like, if they came from, like, an influencer, like LinkedIn ads, or…
159 00:17:16.959 ⇒ 00:17:20.899 Nandika Jhunjhunwala: Other paid ads, or they came, like, organically.
160 00:17:20.899 ⇒ 00:17:24.809 Caitlyn Vaughn: Yeah, we could probably also make some deductions of, like.
161 00:17:24.939 ⇒ 00:17:28.949 Caitlyn Vaughn: This person we sent an email to, they opened it, and then 5 minutes later, they signed up.
162 00:17:28.950 ⇒ 00:17:29.510 Nandika Jhunjhunwala: Like.
163 00:17:29.510 ⇒ 00:17:33.539 Caitlyn Vaughn: She could probably piece that together, but I don’t know if it’s something that we would track in here.
164 00:17:33.540 ⇒ 00:17:34.110 Nandika Jhunjhunwala: Yeah.
165 00:17:34.690 ⇒ 00:17:38.980 Greg Stoutenburg: Yeah, you can also embed code into the link that’s going out in an email.
166 00:17:38.980 ⇒ 00:17:39.880 Nandika Jhunjhunwala: Yeah, that…
167 00:17:39.880 ⇒ 00:17:40.560 Greg Stoutenburg: arrives.
168 00:17:41.040 ⇒ 00:17:48.109 Nandika Jhunjhunwala: that impacts how… where the email lands in the user’s inbox. So we refrain from doing that, but that’s definitely… Oh, I see. Yeah.
169 00:17:48.110 ⇒ 00:17:48.770 Greg Stoutenburg: Okay.
170 00:17:48.970 ⇒ 00:17:52.409 Greg Stoutenburg: Yeah, so,
171 00:17:52.410 ⇒ 00:18:15.310 Greg Stoutenburg: Yeah, okay, that sounds good, though. So, knowing that you’re interested in those sources is helpful, as well as the origin of the signups, and sometimes you make an inference, probably, like, if someone shows up on, on an enterprise plan, then they’re a sales lead, but not necessarily, right? Because insofar as you’re measuring PLG success, one of the things I’m sure you’ll want to know is, like, who goes in on the middle tier, and then they’re on a team for, you know.
172 00:18:15.450 ⇒ 00:18:17.780 Greg Stoutenburg: 3 months, and they…
173 00:18:17.920 ⇒ 00:18:26.840 Greg Stoutenburg: you know, use it a lot, and then eventually they’re in a sales call, right? So we’ll work on making sure we’ve got the right understanding of
174 00:18:27.080 ⇒ 00:18:29.289 Greg Stoutenburg: How to measure who’s coming in where.
175 00:18:29.290 ⇒ 00:18:30.470 Caitlyn Vaughn: Okay, cool.
176 00:18:30.640 ⇒ 00:18:34.660 Greg Stoutenburg: Sounds good. Okay. That’s helpful, and then,
177 00:18:34.830 ⇒ 00:18:42.009 Greg Stoutenburg: So, something that would be helpful for me to know is, as far as the relationship between workspace and organization.
178 00:18:42.310 ⇒ 00:18:46.630 Greg Stoutenburg: Can one and the same… okay. Can a user in one company
179 00:18:46.950 ⇒ 00:18:51.670 Greg Stoutenburg: And a different user in a different company be in the same workspace.
180 00:18:53.240 ⇒ 00:18:54.629 Caitlyn Vaughn: Wait, can you ask that again?
181 00:18:54.900 ⇒ 00:19:02.539 Greg Stoutenburg: Yeah, so can… so can two… can… this is a clearer way… can two different people in two different companies be in the same workspace?
182 00:19:02.860 ⇒ 00:19:03.880 Caitlyn Vaughn: Yes.
183 00:19:04.160 ⇒ 00:19:08.420 Greg Stoutenburg: Okay, alright, so you can, yeah, you can invite someone from elsewhere, and they can be in.
184 00:19:08.420 ⇒ 00:19:12.110 Caitlyn Vaughn: Yeah, we’re, attaching things to Workspace ID.
185 00:19:12.110 ⇒ 00:19:16.140 Greg Stoutenburg: Okay. So people can exist in multiple orgs, and…
186 00:19:16.230 ⇒ 00:19:20.060 Caitlyn Vaughn: multiple domains can be added to the same workspace ID.
187 00:19:20.060 ⇒ 00:19:26.999 Greg Stoutenburg: Okay, that’s helpful. Cool. Okay, great. So, we have that. Do you have,
188 00:19:27.460 ⇒ 00:19:31.099 Greg Stoutenburg: Are you able to share with me even, like, table schema?
189 00:19:31.240 ⇒ 00:19:44.020 Greg Stoutenburg: of things that you are already going to be, recording for users, because we can make sure that those things… and so, the ones you’re interested in, anyway, we can make sure that those data points are coming into post hoc as well.
190 00:19:44.870 ⇒ 00:19:50.869 Caitlyn Vaughn: When you say table schema, you mean, like, all of the backend tables, for our product data?
191 00:19:51.010 ⇒ 00:19:58.700 Greg Stoutenburg: Yeah, so like you just mentioned, like, Workspace ID. Like, so if you’ve already got Workspace ID that’s on the backend, we can send that into Post Hog.
192 00:19:58.810 ⇒ 00:20:06.919 Greg Stoutenburg: And use that… map that to what says workspace ID in postdoc. Yep, I can definitely do that. Those are at least created.
193 00:20:07.470 ⇒ 00:20:15.270 Greg Stoutenburg: Yeah, okay. I just realized that whole time I was just showing the same table. Okay. That, that’s great. So…
194 00:20:15.930 ⇒ 00:20:21.310 Greg Stoutenburg: I think… Oh yeah, I think my only other questions are…
195 00:20:22.220 ⇒ 00:20:31.579 Greg Stoutenburg: when you can, can you list off all of the available widgets that will be in Default OS, and all of the actions that someone can perform from Default OS?
196 00:20:32.180 ⇒ 00:20:35.090 Greg Stoutenburg: Not an emergency,
197 00:20:35.330 ⇒ 00:20:46.199 Greg Stoutenburg: it’s… and we can continue instrumenting and building charts as we go, but that is something that we’ll want to make sure that we have, because it’s, you know, just critical user actions in Default OS.
198 00:20:46.650 ⇒ 00:20:48.730 Caitlyn Vaughn: It’s a good… a good question, for sure.
199 00:20:48.730 ⇒ 00:20:49.280 Greg Stoutenburg: Cool.
200 00:20:50.270 ⇒ 00:20:51.790 Greg Stoutenburg: There’ll be a list somewhere.
201 00:21:03.360 ⇒ 00:21:04.280 Greg Stoutenburg: Okay.
202 00:21:05.470 ⇒ 00:21:14.009 Nandika Jhunjhunwala: So, like, what I was struggling with, Craig, when I was trying to instrument, like, my current instance of Phoenix is…
203 00:21:14.540 ⇒ 00:21:18.970 Nandika Jhunjhunwala: how do I… if I do start instrumenting those elements, like.
204 00:21:19.280 ⇒ 00:21:24.730 Nandika Jhunjhunwala: what can I infer from that? And is it, like, valuable to set up, like.
205 00:21:24.980 ⇒ 00:21:34.579 Nandika Jhunjhunwala: insights or charts based on, like, those click buttons and stuff like that. So if you have any, like, recommendations there, if you’d like me to share my screen again for more context.
206 00:21:34.580 ⇒ 00:21:49.539 Greg Stoutenburg: Yeah. Yeah. No, yeah, that’s a good question, and that’s… that’s sort of why we’re… why we’re approaching it this way. So, in a tracking plan, you could… if you just let autocomplete, or sorry, auto-track fill in your event tracking plan, it would just be… it would just go on forever, right?
207 00:21:49.540 ⇒ 00:21:50.000 Nandika Jhunjhunwala: Yeah.
208 00:21:50.000 ⇒ 00:22:03.459 Greg Stoutenburg: So what the things that we want to record in the tracking plan are going to be those actions and properties of actions that are directly tied to some important workflow, or some important KPI. So.
209 00:22:03.460 ⇒ 00:22:10.450 Greg Stoutenburg: it, you know, if… say you define an activated user as a user… I’m just making this up… as a user who,
210 00:22:10.680 ⇒ 00:22:16.579 Greg Stoutenburg: creates a queue, and completes a table, just for example, right?
211 00:22:17.030 ⇒ 00:22:25.799 Greg Stoutenburg: then you would need to track everything a user would do that’s directly tied to one of those things. So that’s gonna be things like
212 00:22:26.090 ⇒ 00:22:27.320 Greg Stoutenburg: Sign up.
213 00:22:27.630 ⇒ 00:22:35.570 Greg Stoutenburg: log in. How do they log in, right? Do they come in through, you know, GitHub, Google Auth, whatever, username and password? do they,
214 00:22:36.180 ⇒ 00:22:49.579 Greg Stoutenburg: you know, go through your onboarding screens. So it’s gonna be… it’s gonna be those things. And then we use auto-tracking for the rest of it. Auto-tracking will tell you things like, you know, we’ll look at the funnel, and we’ll see who dropped off between.
215 00:22:49.870 ⇒ 00:22:58.149 Greg Stoutenburg: creating an event and actually inviting someone. And then we go in, you know, and we look at, like, session replays and things like that, and go, alright, well.
216 00:22:58.340 ⇒ 00:23:15.179 Greg Stoutenburg: Was there something that distracted them? Whatever. So, all that to say, as we’re instrumenting these things, the tracking plan is going to help us just focus on just those core actions that a user takes to get to some ideal state. And we don’t have to write everything else down in there.
217 00:23:16.540 ⇒ 00:23:17.500 Caitlyn Vaughn: Okay, cool.
218 00:23:17.500 ⇒ 00:23:18.050 Greg Stoutenburg: Yeah.
219 00:23:18.240 ⇒ 00:23:18.870 Greg Stoutenburg: Yep.
220 00:23:18.870 ⇒ 00:23:22.640 Caitlyn Vaughn: Do you want us to write it down, like, in the doc that you already created?
221 00:23:22.960 ⇒ 00:23:32.449 Greg Stoutenburg: I mean, yeah, I mean, happy to… it’s a… it’s a collaborative doc, so if we’ve… if there’s… if there are events in here that you already know, you want to make sure to be tracking,
222 00:23:32.810 ⇒ 00:23:43.180 Greg Stoutenburg: you can just go ahead and put it in there. My only ask would just be, you know, flag the things that are in there that you’re adding, just because, we want to just sort of keep it tight.
223 00:23:43.180 ⇒ 00:23:46.600 Caitlyn Vaughn: Okay, cool. Yep. Yeah, that makes sense.
224 00:23:47.320 ⇒ 00:23:53.099 Greg Stoutenburg: Or even, and also, you know, I’m building this out for you, so if you’re like, hey, here’s this workflow that they just stood up.
225 00:23:53.330 ⇒ 00:23:56.859 Greg Stoutenburg: Please track this, these are all important. I go, okay, I’ll find the right events.
226 00:23:56.860 ⇒ 00:23:59.240 Caitlyn Vaughn: We can just send it over to you!
227 00:23:59.240 ⇒ 00:24:02.360 Greg Stoutenburg: Just send it over. Hand it over. Yep, that’s what we’re here for.
228 00:24:02.590 ⇒ 00:24:10.990 Greg Stoutenburg: Yep. Amazing to my ears. Okay, great. Yeah, yes, you do not, that’s, that’s the partnership. You do not have to do this work.
229 00:24:10.990 ⇒ 00:24:14.860 Caitlyn Vaughn: Amazing. Yeah, we can just pay you to do it, that’s even better.
230 00:24:14.860 ⇒ 00:24:17.900 Greg Stoutenburg: That’s, yeah, exactly. That’s, that’s the goal.
231 00:24:18.940 ⇒ 00:24:35.749 Greg Stoutenburg: Cool. Okay, great. So, is there anything… well, no, so you already have that. I’ll go back through this recording, and I’ll look at some of the flows that you just showed, Nandica, and make sure that we’re tracking the right things in here.
232 00:24:36.090 ⇒ 00:24:37.730 Nandika Jhunjhunwala: I can send you a loom, too.
233 00:24:37.890 ⇒ 00:24:38.710 Greg Stoutenburg: If you want… Yeah, great.
234 00:24:38.710 ⇒ 00:24:39.230 Nandika Jhunjhunwala: F.
235 00:24:39.460 ⇒ 00:24:40.539 Greg Stoutenburg: Love a loom.
236 00:24:41.090 ⇒ 00:24:46.460 Greg Stoutenburg: Yep, and then I’ll… thanks for clarifying as well, the relationship between organization ID and workspace ID.
237 00:24:47.280 ⇒ 00:24:59.359 Greg Stoutenburg: So then, yeah, so then my asks were anything that’s in those tables of user data that you already have records of, that we’ll want to send in to postdoc. If you can share that with me, that would be great. And I think…
238 00:24:59.490 ⇒ 00:25:04.059 Greg Stoutenburg: It’s just a matter of beginning to do some instrumentation and getting some charts set up, then.
239 00:25:04.550 ⇒ 00:25:07.930 Nandika Jhunjhunwala: Nice. So that’s… that’s, like, my next question, like.
240 00:25:08.200 ⇒ 00:25:15.989 Nandika Jhunjhunwala: I guess maybe we can think after this call, like, what do you think we should start instrumenting with, like, based off of these conversations and, like.
241 00:25:15.990 ⇒ 00:25:16.320 Greg Stoutenburg: Yep.
242 00:25:16.320 ⇒ 00:25:22.049 Nandika Jhunjhunwala: Tying it back to, like, if any of those elements on the front end tie back to, like, a metric or a critical workflow.
243 00:25:22.050 ⇒ 00:25:25.010 Greg Stoutenburg: Yep. Or an activation point for our users, yep.
244 00:25:25.010 ⇒ 00:25:35.090 Nandika Jhunjhunwala: I haven’t… I’ve been, like, just trying to, like, wrap my head around, like, instrumenting, so I haven’t thought through, like, a strategic lens, like, too much, so that… that… that would be super helpful.
245 00:25:35.090 ⇒ 00:25:35.920 Greg Stoutenburg: Yeah, great.
246 00:25:35.920 ⇒ 00:25:43.599 Nandika Jhunjhunwala: And then the other thing I wanted to mention was, I shared the fake jam board with Caitlin, and then she had some, like.
247 00:25:43.740 ⇒ 00:25:48.879 Nandika Jhunjhunwala: insights into, like, customer milestones, so I think we added some sticky notes and stuff like that.
248 00:25:48.880 ⇒ 00:25:49.239 Greg Stoutenburg: Oh, great.
249 00:25:49.240 ⇒ 00:25:51.619 Nandika Jhunjhunwala: So maybe we can also discuss,
250 00:25:51.910 ⇒ 00:25:55.870 Nandika Jhunjhunwala: That… I can go back to that and… Yep.
251 00:25:56.130 ⇒ 00:25:58.240 Greg Stoutenburg: You better do that now, or set up some time separately?
252 00:25:58.970 ⇒ 00:26:08.569 Caitlyn Vaughn: I have to jump in a few minutes, so if you guys want to do that now, that’s fine. But looking at the Figma board, I think one of my initial, like.
253 00:26:08.590 ⇒ 00:26:19.260 Caitlyn Vaughn: reaction to it is, I mean, firstly, it’s great that you’re thinking about tracking all the right things, like, things that I actually care about, too. Some of those things, if you’ve looked at the pricing and packaging sheet.
254 00:26:19.360 ⇒ 00:26:26.540 Caitlyn Vaughn: On Notion, a lot of those won’t even be available in the PLG, like, sign-up, though.
255 00:26:26.540 ⇒ 00:26:46.510 Caitlyn Vaughn: For example, we are gating, purchasing extra credits, pages, routing, scheduling, a handful of other things, so there’s, like, no world in which somebody would just, like, sign up and then, you know, start doing… start using routing and scheduling. Like, they would have to talk to us first, at the very least.
256 00:26:46.510 ⇒ 00:26:47.300 Greg Stoutenburg: Family.
257 00:26:47.300 ⇒ 00:26:50.030 Caitlyn Vaughn: So things like that, and then…
258 00:26:50.260 ⇒ 00:27:00.469 Caitlyn Vaughn: we are actually gonna roll out PLG in, like, a month, probably, after releasing the product, because I still need to build out, like, billing and onboarding.
259 00:27:00.860 ⇒ 00:27:14.620 Caitlyn Vaughn: So after those two things are done, then we’ll actually release PLG, but for now, we’re gonna start migrating customers, so we’ll have a handful of, like, existing users that are now gonna be using the new product, along with some, like, net new sales.
260 00:27:14.920 ⇒ 00:27:15.480 Greg Stoutenburg: Okay.
261 00:27:16.610 ⇒ 00:27:24.009 Greg Stoutenburg: Okay, great. Yeah, that’s great. So for, yeah, I started mop… mapping out a lot of this before, you know,
262 00:27:24.690 ⇒ 00:27:31.200 Greg Stoutenburg: A lot was shipped, so, for the… Routing and scheduling…
263 00:27:31.860 ⇒ 00:27:37.230 Greg Stoutenburg: Did I put this in here? I intended to go, alright, user ends at a CTA for this.
264 00:27:37.720 ⇒ 00:27:40.330 Greg Stoutenburg: Will they be able to see that?
265 00:27:40.490 ⇒ 00:27:47.289 Greg Stoutenburg: Will the first group of users be able to see that they got… they clicked a CTA because they were interested in talking to sales about routing?
266 00:27:47.570 ⇒ 00:28:00.329 Caitlyn Vaughn: Yes? Okay. I mean, all of the, like, first users will probably have routing and scheduling access, since most of our current users, that’s, like, that’s our use case right now, is, like, routing and scheduling, right?
267 00:28:00.330 ⇒ 00:28:00.989 Greg Stoutenburg: Yeah, yeah.
268 00:28:00.990 ⇒ 00:28:15.320 Caitlyn Vaughn: But with the new product, it’s just a fraction of what we have, but, you know, as we’re porting everybody over, it’s probably gonna map kind of one-to-one for now. So they will be able to see, like, once we launch PLG, the, like, grayed out, like, talk to sales button.
269 00:28:15.320 ⇒ 00:28:29.350 Greg Stoutenburg: But they won’t be able to just purchase seats on their own. Okay, yeah. Okay, that’s good. Yeah, so that can go in the tracking plan, but then that’s something that we just won’t be instrumenting right away, because it’s not there. Okay, great.
270 00:28:30.040 ⇒ 00:28:45.070 Greg Stoutenburg: That sounds good. So, Nandika, I can set up some time separately for us to look at some of those, you know, like, strategically, some of those workflows. The ones on the FigJam that I put a pause by, those are ones that I know are still in development, so I just went, okay, like…
271 00:28:45.150 ⇒ 00:28:59.360 Greg Stoutenburg: These… I won’t put these in the tracking plan yet. The ones with the checkmark are the ones that I already did, and then… yeah, so we can just, do the tracking plan, and then look at those things that we can start instrumenting, sort of, now rather than later.
272 00:29:00.080 ⇒ 00:29:02.440 Nandika Jhunjhunwala: Sounds good, yeah, that sounds great.
273 00:29:03.120 ⇒ 00:29:10.680 Caitlyn Vaughn: Okay, perfect. I gotta jump to my next call, but it’s great, y’all. I can tell how much work you’re putting into this, I so appreciate you guys owning it, and…
274 00:29:10.680 ⇒ 00:29:11.240 Greg Stoutenburg: Owen.
275 00:29:11.240 ⇒ 00:29:13.060 Caitlyn Vaughn: I’ll see you on Thursday.
276 00:29:13.060 ⇒ 00:29:13.969 Greg Stoutenburg: Alright, see y’all.
277 00:29:13.970 ⇒ 00:29:14.990 Nandika Jhunjhunwala: Thank you so much.
278 00:29:14.990 ⇒ 00:29:15.550 Greg Stoutenburg: Like…
279 00:29:15.550 ⇒ 00:29:16.100 Nandika Jhunjhunwala: Bye.