Meeting Title: Weekly Eden Data Sync Date: 2025-11-12 Meeting participants: Fireflies.ai Notetaker Tigran, Zoran Selinger, Cutter Streeby, Henry Zhao, Ryon, Demilade Agboola
WEBVTT
1 00:04:40.730 ⇒ 00:04:41.760 Henry Zhao: Hey, Cutter.
2 00:04:42.380 ⇒ 00:04:43.270 Cutter Streeby: What’s up, bro.
3 00:04:43.510 ⇒ 00:04:49.460 Henry Zhao: I don’t know if there’s any additional information beyond what we already talked about this morning. I don’t know if Nitesh has joined, I don’t think he has joined in a while, right?
4 00:04:51.090 ⇒ 00:04:55.130 Cutter Streeby: I don’t believe so. The only thing is… UpFluence…
5 00:04:55.330 ⇒ 00:05:01.149 Cutter Streeby: In the Tableau, Fluence shows zero spends for affiliates. I mean, for influencers, still?
6 00:05:01.580 ⇒ 00:05:02.460 Cutter Streeby: There’s a column…
7 00:05:02.460 ⇒ 00:05:07.379 Henry Zhao: Right? After a certain amount of time? You said we don’t… or we started spending with Uploence again.
8 00:05:07.920 ⇒ 00:05:10.529 Cutter Streeby: We’ve been spending with UpFluence for the last 2 months.
9 00:05:11.130 ⇒ 00:05:14.489 Henry Zhao: Okay, I’ll look into that.
10 00:05:15.490 ⇒ 00:05:17.390 Henry Zhao: Checking flips and study.
11 00:05:30.580 ⇒ 00:05:33.650 Henry Zhao: I’ll see if Demolati joins. He might be out the rest of today.
12 00:05:37.210 ⇒ 00:05:38.400 Henry Zhao: Hey, Demolati.
13 00:05:38.550 ⇒ 00:05:40.890 Henry Zhao: There we have… we have Empty melody!
14 00:05:42.220 ⇒ 00:05:43.150 Demilade Agboola: Hi, everyone.
15 00:05:43.950 ⇒ 00:05:44.800 Cutter Streeby: What’s up, bro?
16 00:05:49.220 ⇒ 00:05:54.329 Henry Zhao: Hey, Demolai, we have a question for you on basically all the offline spend.
17 00:05:54.690 ⇒ 00:05:57.570 Henry Zhao: Do you know where we get the upluent spend from?
18 00:06:00.590 ⇒ 00:06:06.150 Demilade Agboola: So a lot of the spend, offline spend, is gotten from either
19 00:06:06.320 ⇒ 00:06:14.680 Demilade Agboola: the Google Sheets or the API. So I believe the Offer API and the catalysts are from… Catalysts are from the API, the rest are from the Google Sheets.
20 00:06:14.830 ⇒ 00:06:16.810 Demilade Agboola: But I might need to cross-check and confirm.
21 00:06:17.650 ⇒ 00:06:20.940 Henry Zhao: Can you… yeah, can you cross-check for us on UpFluence? Because we’re showing zero.
22 00:06:20.940 ⇒ 00:06:26.659 Cutter Streeby: come from Awash, like, he was already working on it with their support, like, a month ago.
23 00:06:27.350 ⇒ 00:06:28.150 Henry Zhao: Oh, okay.
24 00:06:28.150 ⇒ 00:06:32.009 Cutter Streeby: about getting… The spend’s piped directly in.
25 00:06:32.260 ⇒ 00:06:33.799 Cutter Streeby: Byproduct, as well.
26 00:06:38.620 ⇒ 00:06:42.930 Henry Zhao: And Demiladi, do we have revenue from, upfluence, also?
27 00:06:45.130 ⇒ 00:06:47.440 Henry Zhao: Oh, I guess we don’t need to… do we need to know that?
28 00:06:48.440 ⇒ 00:06:51.950 Cutter Streeby: Sure do. We can have a drop-down that says, Influencers.
29 00:06:52.960 ⇒ 00:06:53.880 Henry Zhao: Okay.
30 00:06:54.990 ⇒ 00:06:58.459 Henry Zhao: Alright, let me ticket that, because we’re gonna need to look into that.
31 00:06:59.690 ⇒ 00:07:01.329 Henry Zhao: Who should I assign it to, Demolene?
32 00:07:01.740 ⇒ 00:07:08.070 Henry Zhao: influence… Revenue and spend for product.
33 00:07:11.110 ⇒ 00:07:13.560 Demilade Agboola: Okay, yeah, sure, you can assign that to me.
34 00:07:19.910 ⇒ 00:07:23.799 Henry Zhao: And then I’ll add it to the dash. That’s for product OS dash.
35 00:07:37.520 ⇒ 00:07:54.440 Henry Zhao: Okay, and then Catalyst, I already updated you guys in the thread. Demolade told us that the Catalyst spend in Tableau comes from their API, so it should always be correct, but we just want to double check that after Matthias is done with the reconciliation, and either gets the money back or pays the right amount to Catalyst.
36 00:07:59.670 ⇒ 00:08:00.390 Henry Zhao: Okay?
37 00:08:04.450 ⇒ 00:08:07.709 Henry Zhao: I think that’s… I think that’s pretty much it. Anything else you guys wanted to talk about?
38 00:08:08.710 ⇒ 00:08:17.980 Ryon: Just a high level, Zarin, I’m gonna keep working through the stuff that you and I are talking about in the async list, just minor modifications, Henry, for you to be aware of. I’ll send the list right here.
39 00:08:19.890 ⇒ 00:08:29.619 Ryon: so everyone is aware. These are just my things I’ve found. But at a high level, Zon, one thing I think we need to do for UpFluence, is to…
40 00:08:29.970 ⇒ 00:08:37.700 Ryon: just simply make it so that it’s not firing directly after purchase and DOM ready, that it does
41 00:08:37.700 ⇒ 00:08:53.979 Ryon: like Catalyst wait more towards the end of the actual, intake. So, we could change up the triggers for those, the purchase event, so that it fires, you know, later in the intake. And then I don’t think we need to make it as sophisticated.
42 00:08:54.380 ⇒ 00:09:09.809 Ryon: Catalyst, where it’s like, you know, it’s waiting for this or that thing to show up. I think we just basically use the same sort of triggers that we set up for Catalyst, that says, like, hey, this thing needs to fire closer to the energy intake. That’d be the first step, so that we can make sure we’re getting as close to questionnaire complete as possible.
43 00:09:09.810 ⇒ 00:09:10.170 Zoran Selinger: Yep.
44 00:09:10.170 ⇒ 00:09:13.329 Ryon: And, that’ll, that’ll help.
45 00:09:14.040 ⇒ 00:09:16.589 Ryon: Refine the conversions there, and then…
46 00:09:18.720 ⇒ 00:09:34.670 Ryon: I need to look at edge layer data and their API and figure out… so I’m talking to Awash as well, Henry, trying to figure out, like, hey, like, what did you guys set up, or, like, what was the work being done, back then? Because I don’t know if they have any, like, API which is going to be able to receive information.
47 00:09:34.830 ⇒ 00:09:50.389 Ryon: But if they should, I think it should be pretty straightforward for you guys just to simply set up another cloud job. It’s just gonna send, like, stuff. It’s not gonna be the same as Catalyst, it’ll probably be more like a first-click approach, really like, hey, if you’ve been at Touchpoint in the past 14 days, just send through. You’re good to go.
48 00:09:50.390 ⇒ 00:10:04.619 Zoran Selinger: Yeah, yeah. We’re gonna do the same for Facebook as well, like Cater, we talked about yesterday, so I notified the team today that we are kind of switching the priority a little bit, and trying to pull that a little bit forward.
49 00:10:04.910 ⇒ 00:10:09.530 Zoran Selinger: so, I’m gonna kinda work on that, kick that out.
50 00:10:10.550 ⇒ 00:10:15.620 Zoran Selinger: And we’ll… we’re gonna start, so you should be able to be… Sorry?
51 00:10:15.620 ⇒ 00:10:17.429 Cutter Streeby: Are you using their CAPI?
52 00:10:18.290 ⇒ 00:10:31.919 Zoran Selinger: Of course, yeah, yeah, of course. We’ll lose that, yes. Yes, but we have to agree on some of the details, like event naming and all that. I’ll start that conversation, and we’ll have that ready, yeah.
53 00:10:31.920 ⇒ 00:10:36.330 Ryon: I have a new workspace going on in GTM.
54 00:10:36.990 ⇒ 00:10:41.099 Ryon: call Brian’s, changes. Just put all the stuff in that zone.
55 00:10:41.160 ⇒ 00:11:04.060 Ryon: I had intended it for something else, just rename it, and call it whatever you want to call it. But, yeah. And then, just so you’re aware, Cesar, who works on the EHC side, the Eden Health Club, he is going to be migrating a lot, or removing a lot of the EHC tickets out of our container, because he’s set up another container and another server-side reporting system, which is being used by them, so…
56 00:11:04.060 ⇒ 00:11:05.730 Ryon: We will be officially
57 00:11:05.730 ⇒ 00:11:12.090 Ryon: split. We basically are officially split at this point, they’re not feeding anything from the container, but he’s gonna clean everything out for us, which is really good.
58 00:11:12.560 ⇒ 00:11:18.119 Zoran Selinger: Yeah, you announced that a couple of weeks ago, I’m aware that that’s gonna happen, yeah, thank you.
59 00:11:18.360 ⇒ 00:11:25.679 Ryon: Last, certainly not least, this is just broad for the whole group, we need a table schema map.
60 00:11:25.960 ⇒ 00:11:33.409 Ryon: You know what I mean? Like, I have something for myself that kind of says, like, this connects to this, connects to this, connects to this, but it’s like a mess. Do we have that someplace?
61 00:11:33.410 ⇒ 00:11:36.389 Henry Zhao: Can you show me what you have? What would we probably do?
62 00:11:37.180 ⇒ 00:11:45.819 Ryon: I’m somewhat embarrassed to show you ESI, we’ll show you what I have. So, basically, I tried to use dbDiagram.io, and our tables are too…
63 00:11:47.510 ⇒ 00:11:48.370 Ryon: She’s…
64 00:11:48.640 ⇒ 00:11:56.640 Ryon: there are too many fields, it’s too big. So then I just went another route, and I used a Python script to create, like, a graph, basically. Give me a second here.
65 00:11:58.440 ⇒ 00:12:01.939 Cutter Streeby: So, Ron, what’s the move with Wikid while Ryan looks for that?
66 00:12:03.050 ⇒ 00:12:11.009 Zoran Selinger: Oh… let’s… let’s… so right now, we’re just negotiating this… this trial. You saw the message.
67 00:12:11.010 ⇒ 00:12:11.370 Cutter Streeby: Yeah.
68 00:12:11.370 ⇒ 00:12:20.940 Zoran Selinger: looks like Melissa was out for a day or a couple of days, so let’s… let’s do that this week. I really want to get the
69 00:12:21.130 ⇒ 00:12:23.770 Zoran Selinger: The timeline for their custom work.
70 00:12:24.220 ⇒ 00:12:25.320 Zoran Selinger: As well.
71 00:12:25.650 ⇒ 00:12:40.790 Zoran Selinger: Once we get that, so we’ll… then I’ll have a better idea when that can go ahead. The first step, is… and then we have… we have a few… few steps, that we’ll have to do. I already wrote tickets on our side for it.
72 00:12:40.830 ⇒ 00:12:46.780 Zoran Selinger: So, that’s already planned, we just… I just can’t give you any timeline until Melissa comes back. That’s fine, cool.
73 00:12:46.780 ⇒ 00:12:47.160 Cutter Streeby: Cool, bro.
74 00:12:47.500 ⇒ 00:12:54.210 Zoran Selinger: So here’s at a high level what I’m working on, guys, and this is actually something that Zahra and you and I need to talk about. It’s on my to-do list.
75 00:12:54.260 ⇒ 00:13:16.720 Ryon: Basically, what I’m thinking about is the edge layer raw data, and it’s over here, but the order summary table are basically the two central tables that connect to just about everything at this point, right? And they technically connect to each other via either customer ID or, we’ll use other identifiers that we can connect to the thank you page information here. So, like, it’ll grab things like the hashed IP,
76 00:13:16.720 ⇒ 00:13:23.659 Ryon: the session ID, the user ID, etc. So, like, there are ways to bridge the gap, or to join over from edge to order summary. It’s pretty easy to do.
77 00:13:23.660 ⇒ 00:13:40.349 Ryon: But one of the things that I want to start doing is we’ve got emails sent over here, where it’s capturing the segment anonymous ID, and it’s also capturing other events as well. We’ve got the health info table, this is capturing the segment anonymous ID. We need to start… I talked to Danny Valdez about sending
78 00:13:40.350 ⇒ 00:13:57.059 Ryon: unique user ID, and then also something else to identify so we can join over to this. We’ve got this wait table I asked you guys about. And then, of course, I just want to start, like, piecing everything together so we can start making reports, or start building out things, or understanding the relationship of everything. This is very,
79 00:13:58.350 ⇒ 00:13:59.030 Ryon: I don’t.
80 00:13:59.390 ⇒ 00:14:13.170 Ryon: raw. It’s not the best way to visualize this, but it’s a starting point, of where we are kind of able to connect things together. The only thing I would say, Zarin, is we need to add the GTM
81 00:14:13.720 ⇒ 00:14:32.859 Ryon: unique user ID, UUID, to the edge layer as well. I know you have your own user ID that you’re capturing, and I think you’re capturing the anonymous ID from segment, but it would be a good idea if we captured both the segment anonymous ID and the GTM unique user ID, because that basically allows us to connect over to, like, everything.
82 00:14:33.190 ⇒ 00:14:34.660 Ryon: Pretty much everything at that point.
83 00:14:35.610 ⇒ 00:14:39.009 Ryon: So, yeah, if we had that, basically, edge layer becomes central to
84 00:14:39.180 ⇒ 00:14:44.990 Ryon: everything. Like, there’s nothing. There’s nothing that Azure can’t connect to at this point. So… Yeah.
85 00:14:48.650 ⇒ 00:14:49.700 Zoran Selinger: noted.
86 00:14:50.280 ⇒ 00:14:50.950 Ryon: Coco.
87 00:14:52.210 ⇒ 00:14:53.460 Ryon: I think that’s it for me.
88 00:14:53.900 ⇒ 00:14:54.550 Henry Zhao: November.
89 00:14:56.030 ⇒ 00:14:58.320 Cutter Streeby: So, Henry, you’ll update us on those?
90 00:14:58.600 ⇒ 00:14:59.410 Cutter Streeby: Items?
91 00:14:59.860 ⇒ 00:15:00.410 Henry Zhao: Yep.
92 00:15:00.540 ⇒ 00:15:03.479 Ryon: Perfect. Cool. Awesome. Thanks, guys. Appreciate it.
93 00:15:03.480 ⇒ 00:15:04.840 Henry Zhao: Sarah, my back.