Meeting Title: EdenOS x Brainforge Data Weekly Date: 2026-04-15 Meeting participants: Fireflies.ai Notetaker Chandra, gowtham, Greg Stoutenburg, Diego Makarausky, Zoran Selinger, Girish, Adam’s iPhone
WEBVTT
1 00:03:56.490 ⇒ 00:03:59.240 gowtham: to supply your dining. In supply danny, sir.
2 00:05:10.340 ⇒ 00:05:11.210 Diego Makarausky: Hey guys.
3 00:05:12.190 ⇒ 00:05:13.410 Greg Stoutenburg: Hey Diego, how’s it going?
4 00:05:16.240 ⇒ 00:05:18.739 Diego Makarausky: All good, all good. How about you?
5 00:05:19.750 ⇒ 00:05:20.700 Greg Stoutenburg: Doing well.
6 00:05:37.350 ⇒ 00:05:38.120 Greg Stoutenburg: Bye.
7 00:05:39.010 ⇒ 00:05:46.560 Greg Stoutenburg: to me with questions, which is awesome. Questions like, how are you selecting
8 00:05:47.790 ⇒ 00:05:51.720 Greg Stoutenburg: additional projects, you know, what’s the criteria? Like, like.
9 00:05:52.190 ⇒ 00:06:04.950 Greg Stoutenburg: good, thoughtful question, that I’m able to gather and engage with, which is awesome, especially because… this kind of rolls into our next topic, but…
10 00:06:06.200 ⇒ 00:06:21.939 Greg Stoutenburg: One particular… So it looks like we’re waiting for… They replied, like, 3 months. Sauron… I believe Adam was going to be on the call, but he didn’t mark yes. Robert won’t be on.
11 00:06:22.920 ⇒ 00:06:27.009 Greg Stoutenburg: So I do think we should wait for those remaining folks.
12 00:06:28.740 ⇒ 00:06:30.480 Greg Stoutenburg: Diego, where are you located?
13 00:06:31.120 ⇒ 00:06:35.729 Diego Makarausky: I am in Brazil right now. I mean, not just right now, I’m always in Brazil.
14 00:06:36.110 ⇒ 00:06:38.849 Greg Stoutenburg: Okay, okay, cool. We’re in Brazil?
15 00:06:39.650 ⇒ 00:06:40.679 Diego Makarausky: In Rio.
16 00:06:41.040 ⇒ 00:06:43.980 Greg Stoutenburg: Okay, nice. Alright.
17 00:06:43.980 ⇒ 00:06:44.980 Diego Makarausky: Yeah.
18 00:06:45.720 ⇒ 00:06:46.889 Greg Stoutenburg: So you’re not in Philadelph.
19 00:06:46.890 ⇒ 00:06:47.489 Diego Makarausky: How are you?
20 00:06:47.490 ⇒ 00:06:48.080 Greg Stoutenburg: today.
21 00:06:48.620 ⇒ 00:06:53.059 Greg Stoutenburg: Nope, I’m in York, Pennsylvania, so, you know, you get the right state.
22 00:06:54.810 ⇒ 00:06:57.020 Greg Stoutenburg: Do I appear to be super laggy on your end?
23 00:06:58.930 ⇒ 00:07:00.590 Greg Stoutenburg: From here, it looks like my video is struggling.
24 00:07:00.590 ⇒ 00:07:04.460 Diego Makarausky: Okay. No, I can see a freeze now and then, but…
25 00:07:04.460 ⇒ 00:07:10.099 Greg Stoutenburg: Yeah. Had a lot of Wi-Fi issues. Had to replace the router this morning. Hey, again, Zoran.
26 00:07:11.280 ⇒ 00:07:13.290 Greg Stoutenburg: So, I think we’re just waiting for Adam, then.
27 00:07:15.510 ⇒ 00:07:18.449 Diego Makarausky: Give it a minute, see if he’ll be able to join.
28 00:07:26.580 ⇒ 00:07:28.320 Greg Stoutenburg: I’ll ping him in the new channel.
29 00:07:42.270 ⇒ 00:07:50.179 Greg Stoutenburg: Yeah, I spent, I spent a week in Brazil one time. It was in, Santa Maria, down in the very southern portion, about…
30 00:07:50.180 ⇒ 00:07:51.000 Diego Makarausky: Oh, yeah.
31 00:07:51.000 ⇒ 00:07:54.150 Greg Stoutenburg: 4 hours or so from Porto Alegre by car.
32 00:07:55.250 ⇒ 00:07:56.060 Diego Makarausky: Nice.
33 00:07:56.320 ⇒ 00:08:04.619 Diego Makarausky: Was that wintertime? Because that gets really cold during wintertime. I mean, depends on your reference. If you’re…
34 00:08:04.620 ⇒ 00:08:05.010 Greg Stoutenburg: Oh, yeah.
35 00:08:05.010 ⇒ 00:08:06.410 Diego Makarausky: from Canada, that’s.
36 00:08:06.410 ⇒ 00:08:07.290 Greg Stoutenburg: Yeah, summer day.
37 00:08:07.290 ⇒ 00:08:10.650 Diego Makarausky: But for me, here in Rio, that’s really gold.
38 00:08:10.650 ⇒ 00:08:15.500 Greg Stoutenburg: Yeah, I’m from Michigan, and it was beautiful. I think it was, like, May. I think it was, like, April or May.
39 00:08:15.500 ⇒ 00:08:15.900 Diego Makarausky: Brilliant.
40 00:08:15.900 ⇒ 00:08:17.309 Greg Stoutenburg: If I recall correctly, yeah.
41 00:08:17.520 ⇒ 00:08:18.760 Greg Stoutenburg: It was very nice.
42 00:09:08.500 ⇒ 00:09:17.289 Greg Stoutenburg: All right, well, while we wait, Diego, maybe you could fill us in just on a little bit of the recent history of the project. I think this is only my second call with,
43 00:09:17.490 ⇒ 00:09:24.580 Greg Stoutenburg: with the EdenOS, you know, data team. So, where are we at? How are things going so far?
44 00:09:24.920 ⇒ 00:09:26.430 Greg Stoutenburg: What are your priorities right now?
45 00:09:28.020 ⇒ 00:09:41.529 Diego Makarausky: Yeah, so I see that, at least from data and tracking perspective, so, Adam has mentioned some… added some questions there, and he wants us really to be able to, you know.
46 00:09:42.130 ⇒ 00:09:58.810 Diego Makarausky: track everything that happens, on our, like, intake forms, and also, you know, have a full understanding of what’s happening on the HealthOS, ecosystem as well. Right now, we, we…
47 00:09:59.060 ⇒ 00:10:15.130 Diego Makarausky: two weeks ago, we launched with external patients, right? So we have external patients joining, like, from our intake flow. They are completing payments, and then, we’re getting their information that they provide from
48 00:10:15.130 ⇒ 00:10:25.610 Diego Makarausky: the intake flow and sending that to the doctor network, right, to Beluga, and then, they’re reaching out to the patient through our, integration with them.
49 00:10:25.610 ⇒ 00:10:38.370 Diego Makarausky: They are already, like, being able to, like, provide full-body pictures, whatever they need, and then they get prescribed. That prescription goes to, one of two pharmacies that we’re integrated right now.
50 00:10:38.390 ⇒ 00:10:52.459 Diego Makarausky: And then, they already, like, being able to get the medication. So, we have a few hurdles here to overcome, like integrations in some states, or some difficulties in other areas, some…
51 00:10:52.620 ⇒ 00:11:09.490 Diego Makarausky: Implementation that we did, some fixes that we did, some previous orders, we’re still manually needing to manipulate that, but we’re very close to, you know, getting, like, all the new patients that we receive, they… they flow smoothly through the process, end-to-end.
52 00:11:09.670 ⇒ 00:11:19.610 Diego Makarausky: And now, I think the main idea here for us is to, since we have that, goal that Adam, established, like, right, so…
53 00:11:19.890 ⇒ 00:11:26.129 Diego Makarausky: Our North Star metric is going to be, alright, how many patients they complete their third
54 00:11:26.230 ⇒ 00:11:35.029 Diego Makarausky: order with us, right? So, they just not come in and buy a cloth, but they tend to become, like, this recurrent customer.
55 00:11:35.250 ⇒ 00:11:39.510 Diego Makarausky: How do we track everything that’s going on?
56 00:11:39.910 ⇒ 00:11:56.539 Diego Makarausky: every screen that they’re in, if they drop, you know, we can have that tracking, so we can try to identify the main points where we’re leaking, and try to put those plugs, and not just, like, in one intake, but, like, on the recurrency and things like that, so…
57 00:11:56.540 ⇒ 00:11:57.919 Greg Stoutenburg: Yep, yep, very good, yeah.
58 00:11:57.920 ⇒ 00:11:58.789 Diego Makarausky: Yeah, right down.
59 00:11:59.030 ⇒ 00:12:22.549 Greg Stoutenburg: Yeah, sounds good. Yeah, it’s been, it’s been pretty clear that priority is getting a very clear view of what’s going on in intakes, in navigation for intakes, in orders, and in repeat orders. So, very good. Yeah, the tracking plan, the events that I organize there, try to keep it a nice, tidy list, I think I got it down to 22 or so, is very much focused on that.
60 00:12:22.550 ⇒ 00:12:39.939 Greg Stoutenburg: I have also, on the Event Properties tab, I’ve rearranged all of that. In the next little bit here, I’m gonna polish some of the expected values, but then once that’s finished, I’m ready to hand that over as well. And so we can keep going. That’s your team, right? That’s doing the instrumentation?
61 00:12:40.210 ⇒ 00:12:41.340 Greg Stoutenburg: Of the events?
62 00:12:42.020 ⇒ 00:12:58.190 Diego Makarausky: I’m the product manager here on the team, so I kind of help with the priorities and, you know, unblocking the team. The one who leads the engineering team is Girish. Golden works with him. Golden is,
63 00:12:58.190 ⇒ 00:13:11.389 Diego Makarausky: the engineering… the engineer assigned here to work with, analytics. We have another person who is working with him as well on that front. But yeah, I work really closely with them.
64 00:13:11.530 ⇒ 00:13:15.650 Diego Makarausky: as we can, right? We’re on the very different time zones, but.
65 00:13:15.650 ⇒ 00:13:16.180 Greg Stoutenburg: Sure.
66 00:13:16.180 ⇒ 00:13:18.240 Diego Makarausky: I try to work as close as possible.
67 00:13:18.510 ⇒ 00:13:23.129 Greg Stoutenburg: Okay, okay. So they’re leading the instrumentation. Are you, sort of, I mean, are you managing that?
68 00:13:23.240 ⇒ 00:13:29.680 Greg Stoutenburg: that team, and executing on the tracking plan, then? On your side, or is that entirely handed off to them?
69 00:13:30.580 ⇒ 00:13:44.640 Diego Makarausky: Yeah, I just see, what are the main priorities that we need, get the requirements and send it over to them, but on day-to-day, you know, engineering part, that’s with Girish and the team.
70 00:13:44.890 ⇒ 00:13:49.050 Greg Stoutenburg: Okay, got it, alright. Wanted to clarify that. Okay, very good.
71 00:13:50.160 ⇒ 00:14:04.630 Diego Makarausky: For example, if there’s anything that’s blocking you guys, like, because I know that, Adam has been sending several messages on that channel to Robert, saying, I have this plan here, this looks good.
72 00:14:04.630 ⇒ 00:14:10.469 Diego Makarausky: When it’s gonna be delivered, is this accurate? And…
73 00:14:10.630 ⇒ 00:14:23.459 Diego Makarausky: I don’t know if we’re blocking you guys in any way by custom events or whatever, so if that’s the case, please let us know, and we can send that to the team, so…
74 00:14:23.630 ⇒ 00:14:26.670 Diego Makarausky: We can unblock you in and get that done.
75 00:14:27.380 ⇒ 00:14:37.249 Greg Stoutenburg: Okay, yeah, sounds great. Okay. Yeah, from our end, the priority is getting Mixpanel up to, you know, up to snuff.
76 00:14:37.250 ⇒ 00:14:53.609 Greg Stoutenburg: there’s a lot of confusion, there’s a lot of things that… there are concerns that there’s, you know, sort of low trust in what Adam and others are finding in Mixpanel right now, so we want to write that as quickly as we possibly can. So, that’s, that’s something we were talking about before this call, that’s what Zara and I will be talking about after this call.
77 00:14:53.610 ⇒ 00:15:00.370 Greg Stoutenburg: Just to, you know, really have a clear plan so that everyone understands what data’s flowing from where to where.
78 00:15:00.370 ⇒ 00:15:08.259 Greg Stoutenburg: that identity resolution works the way that it’s expected to, and that sort of thing. We think that’s something we can accomplish in the next few days.
79 00:15:09.120 ⇒ 00:15:19.130 Diego Makarausky: Nice. Yeah, Ryan pinged me, earlier this week to, like, for us to know that, mixed panel data was not, like.
80 00:15:19.500 ⇒ 00:15:24.169 Diego Makarausky: Very reliable right now. There were some issues there. Today, he said, yeah.
81 00:15:24.920 ⇒ 00:15:27.620 Diego Makarausky: work with Fulzhog right now.
82 00:15:27.680 ⇒ 00:15:36.249 Diego Makarausky: Because we’re trying to, like, know which screens we should rebuild with the designer here, right, from the intake, so we can, like.
83 00:15:36.260 ⇒ 00:15:50.469 Diego Makarausky: stop those drop-offs and trending increased conversion, and rely on that data to know which ones we should tackle first, right? So yeah, check polls, but we already know which ones we need to tackle right now, so we’re not blocked or anything.
84 00:15:50.510 ⇒ 00:15:52.860 Diego Makarausky: This week and the next, but,
85 00:15:53.360 ⇒ 00:15:59.339 Diego Makarausky: As soon as we make those changes, we’re gonna want to, you know, know if this, had any, any…
86 00:15:59.460 ⇒ 00:16:08.570 Diego Makarausky: actual results, and once we deliver more stuff, we probably want to A-B test that, and to have that in Xpander would be great.
87 00:16:08.920 ⇒ 00:16:10.229 Greg Stoutenburg: Yep, yep, very good.
88 00:16:10.950 ⇒ 00:16:12.569 Greg Stoutenburg: Okay,
89 00:16:13.520 ⇒ 00:16:25.759 Greg Stoutenburg: Anything from your side, Zoran? I mean, I think from my side, the last thing is, you know, polishing up the event properties, handing those over so that they can be instrumented. But without Adam, I think the only other person has you, Zoran.
90 00:16:26.110 ⇒ 00:16:33.670 Zoran Selinger: The only, really, item on my side that I still don’t understand is the URL of the thank you page.
91 00:16:34.660 ⇒ 00:16:36.829 Zoran Selinger: for the… for the noise.
92 00:16:38.060 ⇒ 00:16:49.140 Zoran Selinger: We see all the sessions in our Edge Layer tables, but I see no references to the thank you pages on the Eden Health domain.
93 00:16:49.260 ⇒ 00:16:55.169 Zoran Selinger: I’m not sure if they are getting rewritten as Trident or something else.
94 00:16:55.390 ⇒ 00:16:56.130 Zoran Selinger: Ow.
95 00:16:56.230 ⇒ 00:17:05.649 Zoran Selinger: on the page load of the thank you page. But yeah, I’d like to investigate that, I just have absolutely no reference to what it should be.
96 00:17:07.349 ⇒ 00:17:14.739 Diego Makarausky: So, about that, and… I don’t know if I’m talking stuff here that you already know.
97 00:17:14.879 ⇒ 00:17:17.009 Diego Makarausky: Let me share my screen real quick.
98 00:17:17.679 ⇒ 00:17:19.889 Diego Makarausky: The way that, any…
99 00:17:19.949 ⇒ 00:17:27.979 Diego Makarausky: a couple of… a bit… a little bit more context here. I don’t know how much you already know about the history, but,
100 00:17:27.979 ⇒ 00:17:41.799 Diego Makarausky: the team that joined, you know, that Girish and I started working with, we kind of got this… I wouldn’t call it legacy, but the project was there, you know, we’ve got to get the repository and say, okay, make this happen.
101 00:17:41.799 ⇒ 00:17:50.999 Diego Makarausky: And the way that this system was built, especially in the intake part, the checkout page, needed to be the last one, right?
102 00:17:50.999 ⇒ 00:18:08.819 Diego Makarausky: we couldn’t add many more stuff after that, so the design that we needed to implement had a couple of screens after checkout, like, content forms, and, like, SMS content, and then,
103 00:18:08.829 ⇒ 00:18:16.679 Diego Makarausky: finally, the thank you page. But, the team had a workaround implemented, but, with that.
104 00:18:16.709 ⇒ 00:18:28.549 Diego Makarausky: we, we only see the, like, the same URL, right? What Surf mentioned was, was, and I know that Surf knows, very, very much about this data part.
105 00:18:28.549 ⇒ 00:18:38.699 Diego Makarausky: Plus, we have, like, JavaScript events, all through the flow, so that should not be the blocker for tracking or anything.
106 00:18:38.839 ⇒ 00:18:54.029 Diego Makarausky: But, in terms of URL, once you reach the checkout page here, you complete the payment, you see three simple steps, SMS content, things like that, thank you page, congratulations, it’s all there.
107 00:18:54.339 ⇒ 00:18:57.319 Diego Makarausky: But, the URL stay the same.
108 00:19:02.009 ⇒ 00:19:07.589 Diego Makarausky: I don’t know if that helps, if it doesn’t, if… It’s just a fact here.
109 00:19:08.190 ⇒ 00:19:08.700 gowtham: Nope.
110 00:19:08.700 ⇒ 00:19:09.769 Greg Stoutenburg: Your mutes are on.
111 00:19:10.270 ⇒ 00:19:11.199 gowtham: Yeah, unlike.
112 00:19:11.200 ⇒ 00:19:11.930 Zoran Selinger: Sorry, you’re muted.
113 00:19:13.860 ⇒ 00:19:14.590 gowtham: I mean.
114 00:19:14.590 ⇒ 00:19:15.090 Zoran Selinger: in.
115 00:19:15.460 ⇒ 00:19:16.840 Zoran Selinger: Go ahead, Goten.
116 00:19:17.260 ⇒ 00:19:26.400 gowtham: Yeah, yeah. So, one doubt is, like, Rick, like, you told, like, currently we are not going to work on mix panel, right? Like, we have to be relying on post hoc, right?
117 00:19:27.440 ⇒ 00:19:35.390 gowtham: So, Adam told, like, we want, like, not to work on mixed, like, mixed panelists are unstable, showing some unstable results, correct?
118 00:19:38.180 ⇒ 00:19:39.569 gowtham: Correct me if I’m wrong.
119 00:19:41.250 ⇒ 00:19:42.410 Diego Makarausky: Source.
120 00:19:42.410 ⇒ 00:19:43.619 Zoran Selinger: Sorry, sorry, second.
121 00:19:44.740 ⇒ 00:19:45.840 Zoran Selinger: Can you say again?
122 00:19:47.080 ⇒ 00:19:50.970 gowtham: Am I audible? Is it, is it clear? Okay, just on the… is it clear?
123 00:19:51.520 ⇒ 00:20:03.339 Diego Makarausky: Yeah, I think that’s what the guys were mentioning here a while ago, so they’re still figuring out the mix panel issue, so keep working with postdoc right now until that’s fixed.
124 00:20:03.590 ⇒ 00:20:13.019 gowtham: Okay, so currently I’m working on the, like, the flow of A-B testing with Midspanel, so should I hold that, story, or, like, what should I do?
125 00:20:19.030 ⇒ 00:20:19.520 Zoran Selinger: Yeah, some…
126 00:20:19.520 ⇒ 00:20:20.040 Diego Makarausky: Makes sense.
127 00:20:20.040 ⇒ 00:20:29.380 Zoran Selinger: So, where are you with Mixed Polygreg now? What’s, what’s the status that we should… Consider… .
128 00:20:31.920 ⇒ 00:20:48.429 Greg Stoutenburg: I mean, if we’re asking me, I don’t see… I don’t think we need to be backing away from Xpanel right now. I think we, you know, we sort of… we’ve identified where the gaps are, and we’re working actively to resolve them, so I don’t think you switch to a new tool, just over that, unless… unless for some reason we just end up completely blocked, and we go, well, there’s no way forward here, but…
129 00:20:48.430 ⇒ 00:20:48.930 Diego Makarausky: You know.
130 00:20:49.210 ⇒ 00:20:53.859 Greg Stoutenburg: they’re a… they’re a real solution, so I don’t think we’ll get to that spot.
131 00:20:53.860 ⇒ 00:20:57.530 gowtham: Okay, as of now, we can use Ms. Panel, correct? Okay, okay, yeah.
132 00:20:58.520 ⇒ 00:21:00.729 gowtham: Nope, got it, got it. Thank you.
133 00:21:02.660 ⇒ 00:21:13.709 Zoran Selinger: So when we, and you guys can probably answer, Gautam, you might be able to answer this. So, when we load a…
134 00:21:15.050 ⇒ 00:21:21.059 Zoran Selinger: Content, let’s say content for the thank you message or success message.
135 00:21:21.410 ⇒ 00:21:26.729 Zoran Selinger: In… in the workflow. Are we making… we are making some kind of API call at that moment.
136 00:21:27.320 ⇒ 00:21:32.669 Zoran Selinger: I’m just wondering if I can identify it in Cloudflare, that API call?
137 00:21:33.390 ⇒ 00:21:39.870 Zoran Selinger: Right? And use that as a vis… as a proxy to the visit to the thank you page, right?
138 00:21:40.970 ⇒ 00:21:45.399 gowtham: Okay, you want to, like, specifically, identify thank you page, right?
139 00:21:46.490 ⇒ 00:21:54.229 Zoran Selinger: Yes, I want to identify, yes, the thank you page, yes, exactly, exactly. It doesn’t have to be, it doesn’t have to be,
140 00:21:54.600 ⇒ 00:21:58.929 Zoran Selinger: you know, just a HTTP call to a…
141 00:21:59.240 ⇒ 00:22:05.200 Zoran Selinger: a different URL, but if I can identify an API call in the background.
142 00:22:05.440 ⇒ 00:22:12.860 Zoran Selinger: That is… that’s… that is signaling me that this is a thank you API call. That’s good enough.
143 00:22:14.850 ⇒ 00:22:22.250 gowtham: So, we have an, this, purchase call, like, I think the payment call is that, but that is actually a TRTC call.
144 00:22:22.500 ⇒ 00:22:37.479 gowtham: Okay. So, but actually, what we’re currently doing is, like, we are, triggering the GTM events. Thank you, Google GTM event. So, is it possible for you to, like, use that GTM event and configure that and move through, give it to the next panel?
145 00:22:38.170 ⇒ 00:22:41.250 Zoran Selinger: No, so the… no, no, so G,
146 00:22:41.360 ⇒ 00:22:52.090 Zoran Selinger: the whole point is that we do not use… we do not use GTM. We use something a little bit more reliable, so we are only talking about the requests.
147 00:22:52.090 ⇒ 00:23:04.739 Zoran Selinger: That’s the… that’s the layer of tracking that we are talking about here. It’s very… Okay. GTM is fine, we… we… we know what to do there. I can read from DOM, I can look, like.
148 00:23:05.460 ⇒ 00:23:16.559 Zoran Selinger: visibility events on GTM, that’s fine. We understand all that, and that’s not a problem. The problem is, I want to identify this on the request level.
149 00:23:18.440 ⇒ 00:23:19.290 gowtham: Okay.
150 00:23:19.920 ⇒ 00:23:25.389 Zoran Selinger: So when you look at the Network tab, when you look at the Network tab in the DevTools.
151 00:23:25.840 ⇒ 00:23:30.300 Zoran Selinger: What can I search for? That’s essentially the question that I have.
152 00:23:31.220 ⇒ 00:23:34.920 gowtham: So, thank you, you mean, like, that the order is completed, right?
153 00:23:35.660 ⇒ 00:23:36.760 gowtham: Yeah, companies…
154 00:23:36.760 ⇒ 00:23:37.400 Zoran Selinger: So…
155 00:23:37.900 ⇒ 00:23:45.150 Diego Makarausky: You wanna go through that right now? We can complete a payment here. I can start the page and check that out.
156 00:23:46.840 ⇒ 00:23:47.590 gowtham: Right, okay, you want.
157 00:23:47.590 ⇒ 00:23:48.080 Diego Makarausky: I’m a certain…
158 00:23:49.720 ⇒ 00:23:50.750 gowtham: Okay.
159 00:23:51.150 ⇒ 00:23:56.220 gowtham: So, basically, okay, as of now, like, thank you, gentlemen.
160 00:23:56.700 ⇒ 00:24:01.580 gowtham: Yeah, you can use that, payment, event, and also, like, after that, we have concerns also.
161 00:24:01.680 ⇒ 00:24:05.580 gowtham: Maybe, like, once all the consents are given, we can consider it as thank you.
162 00:24:06.330 ⇒ 00:24:07.000 gowtham: Peace.
163 00:24:07.610 ⇒ 00:24:09.340 gowtham: Maybe the right, the content…
164 00:24:10.430 ⇒ 00:24:12.459 Zoran Selinger: Yeah, I mean, we don’t have to…
165 00:24:12.810 ⇒ 00:24:17.810 Zoran Selinger: Go through this now, if… if… Necessarily, I just…
166 00:24:18.110 ⇒ 00:24:23.320 Zoran Selinger: If you can write up a small snippet explaining to me.
167 00:24:24.630 ⇒ 00:24:35.099 Zoran Selinger: how can I reliably say that this person loaded, let’s say, loaded a thank you page, right? What’s the proxy request that I can use?
168 00:24:35.670 ⇒ 00:24:37.540 Zoran Selinger: as a signal. That’s it.
169 00:24:39.060 ⇒ 00:24:41.630 gowtham: The person has loaded the thank you page, okay.
170 00:24:42.040 ⇒ 00:24:43.270 Girish: Schedulates series?
171 00:24:43.950 ⇒ 00:24:44.940 Girish: You’re shit.
172 00:24:44.940 ⇒ 00:24:47.079 gowtham: Yeah, that’s Girish. Yeah, it’s Girish, yeah.
173 00:24:47.290 ⇒ 00:24:48.000 gowtham: Yeah.
174 00:24:48.510 ⇒ 00:24:51.420 Girish: So, so, I mean…
175 00:24:51.560 ⇒ 00:25:00.450 Girish: We are actually pushing, with custom events, right? A data layer… in the data layer, we are pushing events, right?
176 00:25:00.620 ⇒ 00:25:02.730 Girish: So that is not sufficient.
177 00:25:04.040 ⇒ 00:25:10.610 Zoran Selinger: Yeah, this is… this is different. This is tracking… this is tracking on the request level, so…
178 00:25:11.910 ⇒ 00:25:13.950 Zoran Selinger: That’s… we have something…
179 00:25:13.950 ⇒ 00:25:16.009 Girish: Good evening, good enough.
180 00:25:17.040 ⇒ 00:25:24.440 Girish: I like, request, request layer means, see, we have, we have different,
181 00:25:24.670 ⇒ 00:25:31.629 Girish: I think, intake, and then, we will push…
182 00:25:32.360 ⇒ 00:25:43.310 Girish: data to different layers. Okay. So, I mean, where do you want to see the network tab? You want to see either header, or…
183 00:25:43.650 ⇒ 00:25:50.290 Girish: exactly, We need more context on that, I mean, so that we can understand it, we can…
184 00:25:51.370 ⇒ 00:25:52.850 Girish: Woke out that.
185 00:25:54.560 ⇒ 00:26:03.819 Zoran Selinger: Yeah, so right now, there’s no request for you to change anything. We will try to work with what you built so far.
186 00:26:05.480 ⇒ 00:26:17.540 Zoran Selinger: the question is, how can I know that someone loaded a thank you page, but again, not using
187 00:26:17.660 ⇒ 00:26:19.750 Zoran Selinger: client-level tracking.
188 00:26:20.310 ⇒ 00:26:25.669 Zoran Selinger: We wanna… we use what Cloudflare sees.
189 00:26:25.850 ⇒ 00:26:39.369 Zoran Selinger: for tracking, for this particular purpose, okay? What you built, and the custom events, this is still very important. We will use all of that, but I’m talking about,
190 00:26:39.560 ⇒ 00:26:42.750 Zoran Selinger: A layer that is sitting before that.
191 00:26:43.360 ⇒ 00:26:48.090 Zoran Selinger: just tracking page or API requests.
192 00:26:49.220 ⇒ 00:26:51.119 Zoran Selinger: So, the question is.
193 00:26:52.030 ⇒ 00:26:59.250 Zoran Selinger: when the thank you page needs to show a message, right? It’s happening on the same URL, but you might be…
194 00:26:59.370 ⇒ 00:27:02.649 Zoran Selinger: you might be sending an API call of some kind.
195 00:27:04.420 ⇒ 00:27:07.820 Zoran Selinger: How can I know that this is the thank you page API call?
196 00:27:10.200 ⇒ 00:27:14.850 Zoran Selinger: Because I can then put that in our code, And use this.
197 00:27:16.070 ⇒ 00:27:19.040 Zoran Selinger: for event tracking on Edge.
198 00:27:20.310 ⇒ 00:27:34.119 Zoran Selinger: But this is very, very specific. This is… I’m being very careful with what I’m asking you. There’s a reason why I did not mention Google Tag Manager, or Client Level, or Pixels, or Custom Events. I’m specifically talking about the request level.
199 00:27:37.300 ⇒ 00:27:45.720 gowtham: Actually, like, that page itself is, requested, so the network tab, you said, like, the page, but even that also, like, it’s, same for all the things.
200 00:27:46.530 ⇒ 00:27:48.410 Zoran Selinger: Yeah, yes, yes.
201 00:27:49.110 ⇒ 00:27:49.730 Zoran Selinger: But basically.
202 00:27:49.730 ⇒ 00:27:53.020 gowtham: The version is simpler for all the concerts, yeah.
203 00:27:53.020 ⇒ 00:27:53.889 Zoran Selinger: told me.
204 00:27:54.190 ⇒ 00:27:55.280 Zoran Selinger: That every, like…
205 00:27:55.280 ⇒ 00:27:55.780 gowtham: SMS.
206 00:27:55.780 ⇒ 00:28:10.600 Zoran Selinger: consent, there’s a bunch of things that are happening without the change of the URL, but the last two pages were… steps were thank you and success message, something like that, Diego. You showed me something like that, the last two steps.
207 00:28:12.420 ⇒ 00:28:29.950 Zoran Selinger: So, when you’re changing… when you’re changing what’s shown to the… to the viewer, right? To the… so, yes, congratulations, yes. So, line 52 and 53. What is actually happening in the… in the background? You’re making some kind of request.
208 00:28:31.390 ⇒ 00:28:34.930 Zoran Selinger: To show the thank you message or congratulations message.
209 00:28:35.480 ⇒ 00:28:48.240 gowtham: See, actually, what is happening is, like, they are changing just the conference alone in the same page, because, okay, page levels, there is no change. Just, like, they are having some multiple level of steps done within the same page, like, the conference alone are changing.
210 00:28:48.390 ⇒ 00:29:00.349 gowtham: So, only thing that we can give is, like, as of now, the correct form is, like, we can trigger some, as restore, like, we can trigger some GTAG events. Because one thing that is… the question that is questioned to me is, like.
211 00:29:01.050 ⇒ 00:29:05.100 Zoran Selinger: No, no, no, no, that… That’s pretty much him.
212 00:29:05.290 ⇒ 00:29:06.270 Zoran Selinger: That’s different.
213 00:29:06.270 ⇒ 00:29:07.030 Girish: that…
214 00:29:07.270 ⇒ 00:29:10.070 Zoran Selinger: Anything client tracking, that’s completely different.
215 00:29:10.490 ⇒ 00:29:19.449 Girish: So, if we want to track them back-to-face low price. So, what we are currently doing.
216 00:29:19.590 ⇒ 00:29:39.370 Girish: under the data layer, so in those data layers are good. So, we are actually, this is the event, thank you page view, and we are setting the page name, thank you, step, like I said, thank you. So, I think this is useful for page tracking.
217 00:29:39.490 ⇒ 00:29:41.830 Girish: Right? But,
218 00:29:44.980 ⇒ 00:29:54.850 Girish: Maybe, maybe we can, we can, fire when AP got the backend success event, we can fire.
219 00:29:54.970 ⇒ 00:30:06.930 Girish: like, event order completed, attacked page view, event detective page view, like, we can find a couple of events. So, the GPS data layer payload has all this information.
220 00:30:07.230 ⇒ 00:30:08.560 Girish: That can be…
221 00:30:08.560 ⇒ 00:30:09.240 Diego Makarausky: For example…
222 00:30:09.240 ⇒ 00:30:10.070 Girish: Beep, beep.
223 00:30:10.540 ⇒ 00:30:18.080 Girish: Where do you want to actually capture the events? Is it for GFO, or XPL, or Postman?
224 00:30:18.080 ⇒ 00:30:23.740 Zoran Selinger: So, Girish, we have a Cloudflare worker in place that does this for us.
225 00:30:23.880 ⇒ 00:30:24.790 Zoran Selinger: Okay?
226 00:30:24.930 ⇒ 00:30:39.419 Zoran Selinger: Cloudflare Worker is what’s going to see the requests. This is why I’m talking about the requests, because that’s what… we use Cloudflare Worker for it. We do not wait for the browser to load.
227 00:30:39.580 ⇒ 00:30:42.360 Zoran Selinger: Anything, any pixel, to track.
228 00:30:42.700 ⇒ 00:30:49.610 Zoran Selinger: We use it on the request already. So we are injecting, essentially, some kind of traffic
229 00:30:49.610 ⇒ 00:31:04.439 Zoran Selinger: tracking right on the request. This is why I keep talking about the request. And you guys keep… keep going into the custom events and GTM. That’s not what we’re talking about here. We are talking about Cloudflare tracking.
230 00:31:04.580 ⇒ 00:31:15.059 Zoran Selinger: So it’s before the page even loads, we collect some data. This is why I’m talking about page loads, or API loads, whatever.
231 00:31:15.060 ⇒ 00:31:15.450 gowtham: Yes.
232 00:31:15.770 ⇒ 00:31:19.500 Girish: I got it. Yeah, we can, we can do that.
233 00:31:19.790 ⇒ 00:31:31.900 Girish: And we can, on the URL… I think, on the… I think, Gautam, we can write a separate identical payload, and we can ask those, so that we can…
234 00:31:31.900 ⇒ 00:31:33.500 gowtham: Zoran, yeah.
235 00:31:33.500 ⇒ 00:31:33.849 Zoran Selinger: Is there a.
236 00:31:33.850 ⇒ 00:31:42.389 gowtham: let’s say we give a separate thank you URL, and we put the center page in the thank you URL, is that… is it fine for you?
237 00:31:43.360 ⇒ 00:31:54.619 Zoran Selinger: That… I mean, that would work if… if this is a new page request, that would be visible by Cloudflare. But, again, if you… if you don’t want to do that.
238 00:31:54.880 ⇒ 00:31:55.919 Zoran Selinger: Maybe we can…
239 00:31:55.920 ⇒ 00:31:56.310 gowtham: Okay.
240 00:31:56.310 ⇒ 00:32:00.170 Zoran Selinger: Maybe we can, have… Like,
241 00:32:00.190 ⇒ 00:32:14.749 Zoran Selinger: let’s call it a dummy law… page law, or the API request, they’re just signaling to Edge that the thank you page visit happened, right? It doesn’t have to be visible to the browser at all.
242 00:32:14.750 ⇒ 00:32:22.100 Zoran Selinger: So that’s not necessary. As long as… as long as Cloudflare sees it, this is enough, and I can…
243 00:32:22.130 ⇒ 00:32:28.489 Zoran Selinger: find that, basically, in Cloudflare, I can code a solution that will look for that, and signal it.
244 00:32:28.490 ⇒ 00:32:29.170 gowtham: Okay.
245 00:32:29.170 ⇒ 00:32:38.140 Adam’s iPhone: Really quick, sorry guys, I’m trying to understand two things here. We own both systems, right? So what are we trying to solve for right now?
246 00:32:40.620 ⇒ 00:32:46.839 Adam’s iPhone: This is not like with BASC, where we had BASP, right? Like, we own Eden.health, this is our system.
247 00:32:47.080 ⇒ 00:32:54.820 Adam’s iPhone: you know, we own everything that’s happening on Cloudflare as well, too, so I’m trying to understand what the problem that we’re trying to solve for right now.
248 00:32:55.380 ⇒ 00:33:15.369 Zoran Selinger: Yeah, so this is… this is edge layer tracking, so right now, so we have… we are collecting… we are collecting all the session starts, so you… you might be familiar… you’re familiar with what we’re doing on Edge. So right… right here, so for Eden.help,
249 00:33:15.590 ⇒ 00:33:27.700 Zoran Selinger: it’s… we don’t have a thank you page, which kind of… this is one of the events that we are collecting on Edge. So I’m just trying to identify the request that would tell me, okay, this is a thank you page visit.
250 00:33:28.260 ⇒ 00:33:28.900 Zoran Selinger: Right.
251 00:33:28.900 ⇒ 00:33:35.229 Adam’s iPhone: Oh, got it. So, well, Greg should be on the call, because Greg, we have an event tracking plan.
252 00:33:35.460 ⇒ 00:33:37.730 Adam’s iPhone: That… that hopefully should…
253 00:33:37.730 ⇒ 00:33:38.080 Zoran Selinger: He’s here.
254 00:33:38.080 ⇒ 00:33:47.560 Adam’s iPhone: I should tell you that, right? Because, a thank you page… Really wasn’t a…
255 00:33:47.650 ⇒ 00:33:58.039 Adam’s iPhone: How do I call it? It should be almost renamed as, like, Purchase Confirmed, right? It’s a checkout went through page. I don’t even know what to call it.
256 00:33:58.040 ⇒ 00:34:13.760 Adam’s iPhone: And we just call it a thank you page, because we deal with BASC today, and so I’ve actually gone through a mixed panel and kind of renamed them, like, this thank you page, yeah, the event name stays the same, but actually my description is changing, because we have to change our thinking on there. But again, going back to the…
257 00:34:13.929 ⇒ 00:34:19.340 Adam’s iPhone: The, the thank you page, I’m going back to saying, we have our own ID,
258 00:34:19.550 ⇒ 00:34:26.060 Adam’s iPhone: in our database for… for… for Eden.health, right, that that… that’s gonna be carrying over with.
259 00:34:26.290 ⇒ 00:34:33.900 Adam’s iPhone: And so the question is, how’s that ID gonna be sent to… Bigquery or whatever else.
260 00:34:34.070 ⇒ 00:34:35.739 Adam’s iPhone: Where we’re attaching…
261 00:34:35.780 ⇒ 00:34:54.630 Adam’s iPhone: what you have from Cloudflare, as well in there on the edge layer, because this is one thing, again, that you guys probably have solved, but I haven’t seen it yet inside a segment, and you guys probably have solved inside of BigQuery, is the identity stitching. The identity stitching, for me, I’m seeing that we’re having some issues with identity stitching.
262 00:34:54.710 ⇒ 00:35:06.250 Adam’s iPhone: in segment, and you guys might have solved it for BigQuery because of when we get it from BASC and when it fires off. When it’s our own system, we don’t have to worry about that as much. So, again, I’m trying to go back, is this, like, are we trying to…
263 00:35:06.610 ⇒ 00:35:12.709 Adam’s iPhone: link it to Cloudflare so that we can stitch the identities together? Or, like, what are we trying to do here?
264 00:35:13.780 ⇒ 00:35:25.519 Zoran Selinger: Yeah, so, so Cloudfl… so Segment is already receiving our, Edge Layer ID. So this is… this is already in our identify calls.
265 00:35:25.950 ⇒ 00:35:28.490 Zoran Selinger: That we use in Google Tag Manager.
266 00:35:30.030 ⇒ 00:35:40.949 Zoran Selinger: So there’s a disconnect somewhere, if you were reviewing this, and you say that there might be a disconnect, and that’s what we’re going to review now.
267 00:35:41.250 ⇒ 00:35:42.470 Zoran Selinger: VR…
268 00:35:42.910 ⇒ 00:35:55.390 Zoran Selinger: we’re… I’m meeting Greg after this, and we are going… we are going into identity stitching immediately, to see where the disconnect is. But the idea that you propose…
269 00:35:55.390 ⇒ 00:35:55.720 Adam’s iPhone: them.
270 00:35:55.720 ⇒ 00:36:07.750 Zoran Selinger: the idea of using edge, our edge identifiers, basically everything, everywhere, is… yeah, that’s what we’re going to try to do.
271 00:36:08.080 ⇒ 00:36:12.440 Zoran Selinger: We can link… Too mask, no problem.
272 00:36:12.440 ⇒ 00:36:13.280 Adam’s iPhone: I’ve eaten…
273 00:36:13.280 ⇒ 00:36:16.399 Zoran Selinger: Because we have transaction IDs.
274 00:36:16.400 ⇒ 00:36:17.099 Adam’s iPhone: It’ll be true.
275 00:36:17.100 ⇒ 00:36:20.610 Zoran Selinger: Nice. Connect to, to, bus IDs.
276 00:36:20.810 ⇒ 00:36:21.760 Zoran Selinger: Yup.
277 00:36:21.930 ⇒ 00:36:22.720 Adam’s iPhone: So, I’ll go.
278 00:36:22.720 ⇒ 00:36:31.419 Zoran Selinger: And obviously, order-generated anonymous IDs from segment, we can… we can have identity tables, or…
279 00:36:31.420 ⇒ 00:36:36.389 Adam’s iPhone: Okay, because how I’m thinking about it, right, with this, I’m glad we’re diving into this, is
280 00:36:36.750 ⇒ 00:36:42.440 Adam’s iPhone: when you capture events, there’s different events to capture, right? Some are transactional events, some are…
281 00:36:42.800 ⇒ 00:36:53.440 Adam’s iPhone: operational events, some are behavioral events, right? And so, if it’s a user who’s going on the website, and they’re interacting with the website, well, the only way that we capture some of that interaction
282 00:36:53.660 ⇒ 00:37:05.820 Adam’s iPhone: if it doesn’t get sent to the server, it’s through the client, right? So we have the… we have these client-side events that are happening, and then we have these server-side events that are happening. And so when we think about,
283 00:37:05.970 ⇒ 00:37:11.270 Adam’s iPhone: the… what’s happening in Cloudflare, and say, alright, is Cloudflare trying to help us out with
284 00:37:11.530 ⇒ 00:37:27.439 Adam’s iPhone: understanding the client-side events that are happening more? Are they there trying to help us out with the server-side events more? Or are they trying to help to stitch those two together when the client and the server aren’t seeing whatever event is happening at the same time, saying, hey, by the way, server-side, you didn’t know that this event was happening, because
285 00:37:27.440 ⇒ 00:37:33.369 Adam’s iPhone: it never got to the server yet. But me, in Cloudflare, I was able to look at both, or I was able to…
286 00:37:33.530 ⇒ 00:37:44.400 Adam’s iPhone: have 4 steps in this journey that you saw, but I had 5 steps in this other journey that you didn’t see, and therefore I’m passing this on to you. That’s… that’s, in my head, I’m sure you guys may have already sold for this, but I think that’s… I think what we’re trying to do in the.
287 00:37:44.400 ⇒ 00:37:45.629 Zoran Selinger: Yeah, we are.
288 00:37:45.810 ⇒ 00:37:48.309 Zoran Selinger: We are, for some the university
289 00:37:48.640 ⇒ 00:37:56.360 Zoran Selinger: Yeah, we, we do, we do a lot with identity stitching. We do not only, save, like.
290 00:37:56.540 ⇒ 00:38:02.340 Zoran Selinger: edge ID, edge layer ID. We are picking up identifiers from…
291 00:38:02.470 ⇒ 00:38:07.549 Zoran Selinger: from MixPanel, from Segment, from, from…
292 00:38:07.980 ⇒ 00:38:17.000 Zoran Selinger: things like, catalysts, and we are matching on all of those fields. This is why we have… we can stitch more sessions than
293 00:38:17.460 ⇒ 00:38:26.609 Zoran Selinger: for example, catalysts. Because we would create a catalysts, it’s slightly more than… than they, than they see.
294 00:38:27.180 ⇒ 00:38:37.969 Adam’s iPhone: So I think that maybe part of the conversation, if you guys haven’t already done it, is maybe… maybe presenting a diagram that we can all agree with for saying, this is how identity stitching works today because of BASC.
295 00:38:38.130 ⇒ 00:38:48.580 Adam’s iPhone: This is our recommendation for what we want to do, and this is how each system contributes to it, right? So you can say, you know, and I’m just going to give examples, I can be completely wrong here, but I can say.
296 00:38:48.580 ⇒ 00:38:57.360 Adam’s iPhone: you know, we have Cloudflare out there with grabbing things on the edge, because a lot of things are lost on the edge, and so Cloudflare does a really good job there.
297 00:38:57.360 ⇒ 00:39:09.089 Adam’s iPhone: But Cloudflare starts to become overkill the second that somebody gets in the intake. We don’t need Cloudflare doing that anymore, right? We have different systems, we have Segment through, you know, through the Analytics.js, and we have
298 00:39:09.090 ⇒ 00:39:19.879 Adam’s iPhone: We, we have, our own, Eden.health that, that, that fires these there. And so, yes, we’ll continue this ID, this Cloudflare ID, but…
299 00:39:19.880 ⇒ 00:39:31.569 Adam’s iPhone: you know, it’s not the main ID that matters, it’s just, it’s a stitching ID that goes to a main ID. And then, by the way, these behavioral events that we’re talking about, right, maybe the client-side events.
300 00:39:31.610 ⇒ 00:39:51.429 Adam’s iPhone: you know, we’re gonna have that go through Segment first, and then Segment can populate that downstream inside of BigQuery, or whatever else we want, and then it’s gonna go through here, and here’s where these things are being stitched together. Again, maybe you guys understand this much better than I do, but how I’m looking at it right now, like, as I’ve gone in through some of the data, I’m like, alright.
301 00:39:51.590 ⇒ 00:40:04.980 Adam’s iPhone: maybe they’re stitching it correctly and it’s landing on North Beam correctly, but sometimes when I’m looking at the identity stitching, I’m seeing, like, things not stitched together how they should be, and I’m like, maybe part of that’s a BASC issue? Maybe it’s part of an issue of…
302 00:40:05.120 ⇒ 00:40:23.899 Adam’s iPhone: of where we’re using these downstream tools, like BigQuery, or where we’re gonna be using Segment, or where we’re gonna be using our own database, like Postgres or anything else, and where all these different things are firing together, and making sure that each team knows this is the identity you gotta use, this is where you gotta… this is where you gotta throw it in your downstream systems or anywhere else.
303 00:40:24.390 ⇒ 00:40:24.980 Zoran Selinger: Yeah.
304 00:40:28.870 ⇒ 00:40:36.530 Zoran Selinger: Yeah, that’s exactly… so, Greg, we are jumping into this, and yeah, a diagram is a good idea.
305 00:40:38.150 ⇒ 00:40:49.540 Adam’s iPhone: Okay, so maybe if we get a diagram, and then we can go on to the next subject, and I’ll drop off the call, you guys. That’s the only thing I want to talk about. So, if we can maybe do that for us, I’ll let you guys continue going on with how you guys are thinking about
306 00:40:49.820 ⇒ 00:41:06.580 Adam’s iPhone: how the new HealthOS, what you guys have to do there. But for me, if we can do that, then that solves the first thing, I think, in the layer, which is the identity stitching. One thing I also would then want to talk about, but we can talk about it later as well, too, is the data governance of this as well, too.
307 00:41:06.600 ⇒ 00:41:21.359 Adam’s iPhone: If we’re gonna be doing these type of things, we gotta make sure that we’re having good data governance policies, or else this is gonna get really messy really quick for everything else. It’s gonna break, as you guys know, some of your models, it’s gonna be breaking the things I look at, right? And across those things. So…
308 00:41:21.430 ⇒ 00:41:22.180 Adam’s iPhone: Cool.
309 00:41:22.850 ⇒ 00:41:34.269 Adam’s iPhone: That’s it for me. Thanks, Doron. Thanks, everybody else. I know I just kind of jumped in here, dominated the conversation, now I’m leaving, but if we can, like, with the next conversation, whenever you guys have it, if we can do some of this identity stitching and show a diagram, that’d be great.
310 00:41:34.640 ⇒ 00:41:36.150 Adam’s iPhone: I appreciate that.
311 00:41:37.210 ⇒ 00:41:37.909 Greg Stoutenburg: Sounds good, thanks.
312 00:41:38.270 ⇒ 00:41:39.530 Diego Makarausky: Exactly.
313 00:41:39.530 ⇒ 00:41:39.970 Adam’s iPhone: Thanks, everybody.
314 00:41:42.740 ⇒ 00:41:56.879 Diego Makarausky: I don’t know if it’s valuable here for you guys to see, but I just, like, completed a payment here, so I’m still on the, like, checkout page URL, but I’m on a different screen, and I can show you what happens after.
315 00:41:56.880 ⇒ 00:41:57.330 Zoran Selinger: Okay.
316 00:41:57.330 ⇒ 00:41:58.550 Diego Makarausky: In real life.
317 00:41:58.880 ⇒ 00:42:02.519 Diego Makarausky: So maybe you can have an idea of what we could track.
318 00:42:04.460 ⇒ 00:42:16.589 Diego Makarausky: So, for example, you just… after you complete the payment, your credit card works, you see this, right? So there’s nothing much that you can do here besides log off. You probably won’t do it.
319 00:42:16.740 ⇒ 00:42:18.330 Diego Makarausky: And click next.
320 00:42:20.230 ⇒ 00:42:25.350 Diego Makarausky: After you click next is the SMS consent, screen, so…
321 00:42:25.430 ⇒ 00:42:42.459 Diego Makarausky: We need to check that, Girish, but I imagine that we’re storing what type of, like, consents this customer is providing us, if just for orders, if doctors, if all of them, if nothing. But imagine we’re capturing this.
322 00:42:42.460 ⇒ 00:42:51.050 Diego Makarausky: So, you’re just reaching to this, and you’re just getting this type of events, this type of answers, once you’ve completed the payment. So this…
323 00:42:51.660 ⇒ 00:42:54.550 Diego Makarausky: Means you completed a payment with us.
324 00:42:54.940 ⇒ 00:43:07.049 Diego Makarausky: You can’t move forward without checking this, so this is something that we’re capturing as well. We need to send this to Beluga… we’re capturing this.
325 00:43:07.780 ⇒ 00:43:09.780 Diego Makarausky: And the thank you page is…
326 00:43:10.580 ⇒ 00:43:15.090 Diego Makarausky: nothing, so I think probably would be one of the steps behind
327 00:43:15.670 ⇒ 00:43:18.120 Diego Makarausky: We should think that’s, that might help.
328 00:43:21.220 ⇒ 00:43:24.870 Zoran Selinger: Yeah, okay, okay, we can, we can take that.
329 00:43:26.190 ⇒ 00:43:26.960 Zoran Selinger: In the channel.
330 00:43:27.130 ⇒ 00:43:27.710 Girish: Yep.
331 00:43:28.430 ⇒ 00:43:34.279 Girish: what I understood, It’s about creative multiplicity.
332 00:43:34.490 ⇒ 00:43:36.489 Girish: Secretary, thank you.
333 00:43:37.920 ⇒ 00:43:40.850 Zoran Selinger: Sorry, Garish, you’re breaking up a little bit, I can’t understand.
334 00:43:43.010 ⇒ 00:43:45.760 Girish: Is my wife’s already interested in sub-issues?
335 00:43:46.430 ⇒ 00:44:06.110 Girish: So, I’m telling, like, I mean, regarding the Cloudflare Worker, so, what I understood, just correct me if I’m wrong, so if you want to only track page view, maybe we lose the conversion. So, with Worker, I think you can still capture the event, let’s say, order completed API.
336 00:44:06.280 ⇒ 00:44:17.800 Girish: So, you are trying to capture, like, payment failures, kind of, kind of things with the worker, right? So that’s why you want to use that, right?
337 00:44:18.150 ⇒ 00:44:23.459 Zoran Selinger: Yeah, so I at least need a, a transaction ID,
338 00:44:24.350 ⇒ 00:44:29.499 Zoran Selinger: And the value would be great, but the transaction ID is the… is the least I need there.
339 00:44:31.610 ⇒ 00:44:37.599 Girish: Okay, so API, at least transaction in the sense that payment success, you’re saying.
340 00:44:40.750 ⇒ 00:44:43.710 Girish: Yeah, okay.
341 00:44:43.710 ⇒ 00:44:53.439 Zoran Selinger: Yeah, let’s, let’s take that offline. We are over time here, so, let’s take that offline, and yeah, we’ll get there.
342 00:44:55.040 ⇒ 00:44:58.319 Diego Makarausky: All right. Thanks, guys. Thanks, everyone.
343 00:44:59.200 ⇒ 00:45:00.179 Diego Makarausky: It’s it.
344 00:45:00.180 ⇒ 00:45:01.309 Greg Stoutenburg: Take care, bye.