Meeting Title: Meta and North Beam Sync Date: 2025-08-04 Meeting participants: Robert Tseng, Andrew O’Neil
WEBVTT
1 00:01:13.870 ⇒ 00:01:14.680 Andrew O’Neil: Hello!
2 00:01:15.500 ⇒ 00:01:16.490 Robert Tseng: Hey, Andrew.
3 00:01:20.110 ⇒ 00:01:21.469 Andrew O’Neil: How’s your day been so far.
4 00:01:22.390 ⇒ 00:01:29.649 Robert Tseng: Yeah, mondays are always kind of meeting heavy in the morning. And then yeah, just trying to figure out how the week’s gonna go.
5 00:01:30.070 ⇒ 00:01:32.280 Andrew O’Neil: Yeah, yeah, that makes sense.
6 00:01:33.140 ⇒ 00:01:36.519 Robert Tseng: How was that? You were off Thursday, Friday last week?
7 00:01:36.980 ⇒ 00:01:49.809 Andrew O’Neil: I was working in the morning. I was. I was traveling a little bit, so I didn’t have my like normal connection. But yeah, I was monitoring things, and I’m now fully caught up this morning. For this call.
8 00:01:50.210 ⇒ 00:01:54.060 Robert Tseng: Cool. Yeah. Do you do anything fun? Where’d you? Where would you go?
9 00:01:54.920 ⇒ 00:01:59.220 Andrew O’Neil: Just back home in Wisconsin. Nothing like too crazy
10 00:02:00.080 ⇒ 00:02:01.750 Robert Tseng: You’re usually in Chicago right?
11 00:02:01.910 ⇒ 00:02:04.230 Andrew O’Neil: Yeah. Yeah. So not that. Not that far.
12 00:02:05.650 ⇒ 00:02:08.020 Robert Tseng: I’m coming to Chicago next month. By the way.
13 00:02:08.419 ⇒ 00:02:10.589 Andrew O’Neil: Oh, cool for fun, or for.
14 00:02:10.590 ⇒ 00:02:12.369 Robert Tseng: For shop talk. I think.
15 00:02:12.370 ⇒ 00:02:12.870 Andrew O’Neil: Oh, yeah.
16 00:02:12.870 ⇒ 00:02:14.416 Robert Tseng: Reference. Yeah.
17 00:02:15.760 ⇒ 00:02:21.570 Robert Tseng: I forget the dates exactly sometime in mid September. So if you’re around, I’ll hope to see you. Then.
18 00:02:21.830 ⇒ 00:02:23.690 Andrew O’Neil: Cool. Yeah, that that sounds great.
19 00:02:24.140 ⇒ 00:02:24.920 Robert Tseng: Yeah.
20 00:02:26.100 ⇒ 00:02:30.821 Robert Tseng: cool. Yeah. I know that we thank you for getting around. I was just starting to read your messages.
21 00:02:31.070 ⇒ 00:02:32.060 Andrew O’Neil: Yeah, yeah.
22 00:02:32.290 ⇒ 00:02:38.300 Robert Tseng: Yeah, I know I set this call for north theme stuff. But maybe we’ll just kind of just chat through the meta things really quick, and then we can.
23 00:02:38.300 ⇒ 00:02:38.710 Andrew O’Neil: Sure.
24 00:02:39.137 ⇒ 00:02:42.982 Robert Tseng: Over that. So I’m just reading your message.
25 00:02:44.000 ⇒ 00:02:51.599 Robert Tseng: yeah. So the browser pixel pause connection. The chappy pot was paused as well as of today.
26 00:02:52.344 ⇒ 00:02:56.899 Robert Tseng: Yeah, do we know what happened or like? I didn’t know.
27 00:02:57.160 ⇒ 00:02:58.524 Andrew O’Neil: No, no, the
28 00:02:59.150 ⇒ 00:03:12.199 Andrew O’Neil: What I mean by Cappy. There! There was a cappy from Gtm. The server container that one was bought, so I’m kind of recapping that to my knowledge, I haven’t seen anything with segment, but I was not referring to that setup.
29 00:03:12.200 ⇒ 00:03:19.330 Robert Tseng: Okay, cool. Yeah. So yeah, I mean, they. I guess they never turned on the the stuff after we told them that they should turn back, or they.
30 00:03:20.070 ⇒ 00:03:29.659 Robert Tseng: We never advised them to turn it back on. But they wanted to send duplicate things through Google Tag manager. So. But it seems like they didn’t even end up doing that. So.
31 00:03:30.350 ⇒ 00:03:44.470 Andrew O’Neil: Yeah, and what’s I’m still torn as to whether I would recommend them doing that because so basically like what I just shared the last image of there. What I’ve done is essentially
32 00:03:44.550 ⇒ 00:04:08.149 Andrew O’Neil: tried. My best to replicate the logic that we’re using with segment. So, for example, we’re looking for the the event. Id that’s coming from Ga. 4. It’s firing for all purchases. Not just 1st purchases because previously in Meta, they were exclusively using 1st time purchase
33 00:04:08.150 ⇒ 00:04:30.650 Andrew O’Neil: for their quote, unquote purchase event. You can see here that that’s that’s updated so like. So the 1st big update is the trigger is now firing for all purchases. Which is what I think closely aligns with what segment is doing. And then, importantly, it was using. They have
34 00:04:30.670 ⇒ 00:04:53.082 Andrew O’Neil: weirdly a couple different event id variables in their container. Not sure why they would do that. Maybe. Probably I don’t know. Multiple people set it up either way. What I did is I updated the variable for event Id to match. What with what is Ga, 4 is using, since that’s what a wish had built using segment.
35 00:04:53.450 ⇒ 00:04:54.150 Robert Tseng: Yeah.
36 00:04:54.310 ⇒ 00:05:11.409 Andrew O’Neil: But the but at its core, though this setup you know there are extra checks that our Cappy models looking for like, is there a transaction? Id. Did the order get canceled? Or is it null? That
37 00:05:11.410 ⇒ 00:05:35.602 Andrew O’Neil: this browser implementation? I can try to think if if we can build in that logic. But it’s gonna struggle to completely match how we’re sending data on the server side which will ultimately lead to different event totals between browser and server. Usually you want those to be as one to one as possible.
38 00:05:36.090 ⇒ 00:05:53.360 Andrew O’Neil: which kind of then leads me to say, like, you know if they’re getting good coverage out of the server, do they even need to send this extra browser one? So that’s a lot to throw at you happy to like, dive deep into, you know, wherever you have questions.
39 00:05:53.360 ⇒ 00:06:00.717 Robert Tseng: Yeah, no, I’m following. So I mean so for the server model, there’s something that I checked with the wish was, and maybe you can confirm, but
40 00:06:02.320 ⇒ 00:06:09.489 Robert Tseng: basically like they wanted both approaches because they were afraid that one is gonna miss, some thing that.
41 00:06:09.490 ⇒ 00:06:09.959 Andrew O’Neil: They do it.
42 00:06:09.960 ⇒ 00:06:24.370 Robert Tseng: Yeah. I don’t think that there was a case where the browser caught something that the server didn’t but it all the other the other way around it did so like there were like, I, I think I
43 00:06:25.030 ⇒ 00:06:27.254 Robert Tseng: posted some query, I guess,
44 00:06:27.970 ⇒ 00:06:31.310 Robert Tseng: that I had written that basically showed like a number of
45 00:06:31.750 ⇒ 00:06:36.600 Robert Tseng: valid purchase events that didn’t come through. Gtm, that we did catch in segment.
46 00:06:36.880 ⇒ 00:06:37.540 Andrew O’Neil: I’m right.
47 00:06:37.540 ⇒ 00:06:47.690 Robert Tseng: For those situations. We’re not using a Ga. For event. Id, because there’s nothing to match on. And then we’re I asked away to generate our own Id. So that was kind of how he built that final model. So.
48 00:06:47.690 ⇒ 00:06:48.130 Andrew O’Neil: Perfect.
49 00:06:49.330 ⇒ 00:06:56.689 Robert Tseng: Yeah. So I I guess we could just make sure that that’s the case. And that they’re
50 00:06:57.210 ⇒ 00:07:01.649 Robert Tseng: are. Yeah. Well, but I mean? That’s that’s what I found last week.
51 00:07:02.181 ⇒ 00:07:15.470 Robert Tseng: And then, regarding like the 2 things you pointed out on the event. Ids! What were like the what were they using for the event? Id, if not the A. 4 id, I thought. That’s what they I thought that was the whole point. They wanted to be able to match the A. 4 id.
52 00:07:15.690 ⇒ 00:07:33.706 Andrew O’Neil: They they had inconsistent so they have different variables floating around. That’s what that like the braces there, Gtm, are showing they have different ones. So I think some of the Meta events were using the same as Ga. 4. Some of them were not
53 00:07:34.090 ⇒ 00:07:54.440 Andrew O’Neil: for purchase. There was a different. There’s this unique event, Id, which is a different variable than our event. Id standard and that the event id standard. That’s what ga, 4 is using so every anything that is showing in G 4 is gonna use that but yet again.
54 00:07:54.440 ⇒ 00:08:00.650 Andrew O’Neil: during auditing this, I kind of uncovered. They’re inconsistent with what variables they’re using.
55 00:08:01.110 ⇒ 00:08:01.890 Robert Tseng: I see.
56 00:08:02.500 ⇒ 00:08:04.530 Robert Tseng: Okay, that makes that. I mean that
57 00:08:04.810 ⇒ 00:08:16.200 Robert Tseng: I don’t understand why they are so insistent on us. Matching ga 4 id like. It doesn’t seem like it’s being used like, what’s the purpose of that? Why can’t we just put our own like, yeah, why, why couldn’t we just put our own
58 00:08:16.820 ⇒ 00:08:20.019 Robert Tseng: like generated event, id from segment, for everything.
59 00:08:20.450 ⇒ 00:08:39.850 Andrew O’Neil: Yeah, the the only thing with that is the segment event Id just has to match with what Gtm can see. So if Gtm can see that segment event. Id, we can use that but if that is sending from the server and Gtm. Can’t intercept that. That’s where there could be problems, if you know.
60 00:08:39.850 ⇒ 00:08:52.239 Andrew O’Neil: we’re using different event ids. But as long as Gtm. Pick can pick that up, then it event. Id is really just to to dedupe things. There’s really no value that it’s providing other than that service.
61 00:08:52.460 ⇒ 00:08:53.140 Robert Tseng: Okay.
62 00:08:53.707 ⇒ 00:09:04.149 Robert Tseng: Well, then, I guess I would want to make sure that the generated event Id that we use actually can be read in Gtm, because I guess I don’t. I didn’t really realize that.
63 00:09:04.640 ⇒ 00:09:10.160 Andrew O’Neil: Correct. Yes, if yeah, if we want to switch event ids, that will be a dependency.
64 00:09:10.640 ⇒ 00:09:13.680 Robert Tseng: Yeah, cause right now the model is sending.
65 00:09:14.540 ⇒ 00:09:32.690 Robert Tseng: We’re sending more events than what Gtm is capturing. And so, and for the ones that don’t overlap with what we’re that don’t have ga 4 ids. We’re creating our own event id and pushing that in. So those may not actually be, they may not actually be caught by gtm, if it’s not formatted correctly.
66 00:09:33.150 ⇒ 00:09:34.310 Andrew O’Neil: Right, right.
67 00:09:34.310 ⇒ 00:09:50.000 Robert Tseng: Okay. So I think that’s something to check. And then on the trigger, as far as like custom custom purchases, whereas 1st time purchases all the purchase events should be 1st time purchase events. Actually so. I think we already just do that in the in the model like.
68 00:09:50.350 ⇒ 00:10:08.300 Robert Tseng: which is like. I don’t. I don’t believe the Gtm. Like custom 1st time purchase event like. I don’t believe that is 1st time purchases only which is why we needed. Why, which is why I I we decided to do it. For like from from the
69 00:10:08.920 ⇒ 00:10:10.800 Robert Tseng: from from bigquery in the data model.
70 00:10:11.100 ⇒ 00:10:11.880 Robert Tseng: Sure.
71 00:10:11.880 ⇒ 00:10:12.450 Andrew O’Neil: That makes sense.
72 00:10:12.560 ⇒ 00:10:18.236 Robert Tseng: I just don’t think that they’d be able to do. They’d be able to do it from the single web book they use for
73 00:10:19.130 ⇒ 00:10:20.919 Robert Tseng: like prefer for for that event.
74 00:10:21.180 ⇒ 00:10:22.290 Robert Tseng: So.
75 00:10:22.290 ⇒ 00:10:22.860 Andrew O’Neil: Yep.
76 00:10:23.160 ⇒ 00:10:23.900 Robert Tseng: Yeah.
77 00:10:25.060 ⇒ 00:10:30.719 Robert Tseng: okay, so it sounds like we have a little bit more Qa to do. But I think we should. Yeah, if you feel like.
78 00:10:30.870 ⇒ 00:10:34.729 Robert Tseng: well, yeah, I don’t really know what the right approach is to tell them.
79 00:10:35.210 ⇒ 00:10:35.830 Andrew O’Neil: Yeah.
80 00:10:36.090 ⇒ 00:10:36.840 Robert Tseng: Yeah.
81 00:10:37.180 ⇒ 00:10:59.090 Andrew O’Neil: Other thing to consider what’s ultimately you want it for for any sort of meta tracking you want to get the event, count straightened out that I think we made significant progress on because the logic we’re using now, I think it’s a lot closer. The other important thing is Meta Meta’s ability to then match purchases
82 00:10:59.090 ⇒ 00:11:20.260 Andrew O’Neil: back to people who saw the ad that attribution process, and it relies on like sending back as much either customer data or meta like customer parameters and that’s usually where the pixel is better than the server, like the Meta’s pixel, has, like
83 00:11:20.400 ⇒ 00:11:37.500 Andrew O’Neil: by default, all of these different tracking parameters enabled, like the Facebook like. There’s a couple cookies that come with it. Of course those aren’t getting. They’re losing their value as more browsers block them. But, like, for example, our
84 00:11:37.740 ⇒ 00:11:59.209 Andrew O’Neil: the pixel is sending a Facebook click. Id. But I did look, and our server segment event is not so, even though the event totals would be closer, the browser Pixel might be better at matching back to customers. Of course we can get around this by making sure that our
85 00:11:59.220 ⇒ 00:12:15.350 Andrew O’Neil: server events is sending as much customer information as possible, but that is generally where the browser has an edge. Still, even in this age of Ios tracking because it can by default have all of those parameters.
86 00:12:15.970 ⇒ 00:12:25.330 Robert Tseng: I see. Yeah, I mean, I think I I stripped out some of the customer data fields because of just I think we were sending too much data to Meta first.st So
87 00:12:25.490 ⇒ 00:12:33.850 Robert Tseng: I think there’s some healthcare, specific things that I don’t know if you would be able to like, speak to, but, like, from my understanding, I
88 00:12:33.950 ⇒ 00:12:42.839 Robert Tseng: I already stripped out things. And I I think what I’m sending is compliant now. But yeah, we don’t have fest. We don’t have Facebook click Id, and
89 00:12:43.700 ⇒ 00:12:50.650 Robert Tseng: I don’t really know where to pull that from other. If it were not the pixel I got, I don’t. Yeah, I don’t, not not entirely sure.
90 00:12:50.790 ⇒ 00:12:51.900 Andrew O’Neil: No.
91 00:12:52.670 ⇒ 00:12:53.310 Robert Tseng: But.
92 00:12:53.310 ⇒ 00:13:09.009 Andrew O’Neil: You would see the most gain with that in terms of parameters, so I can at least speak to like the click. Id should be hipaa healthcare compliance. That’s just a meta tracking. I could see where zip code state that could get a little dicey.
93 00:13:09.010 ⇒ 00:13:24.450 Andrew O’Neil: but in terms of like where they have to gain. It’s like, you know, 90% of the gain is sending the click Id. The other parameters would maybe get you 10% better, but they would and and Facebook even calls us out, and they’re set up like
94 00:13:24.530 ⇒ 00:13:39.320 Andrew O’Neil: their the match rate. I don’t know the exact magnitude, but it would be. The the best value they get is from that click id which you can grab from a cookie that’s installed. Whenever someone clicks on an ad.
95 00:13:39.700 ⇒ 00:13:42.190 Robert Tseng: Yeah, okay,
96 00:13:44.140 ⇒ 00:13:56.380 Robert Tseng: So I mean, I don’t think we’re gonna bring that cookie into the warehouse, and then, like, push it from the server like that seems like that’s just something that the pixel will send. So maybe that does make sense to send both the pixel and the server. Yeah.
97 00:13:56.860 ⇒ 00:14:25.839 Andrew O’Neil: Right? Right? So like it generally like when it matches, it’ll say, Okay, these 2 have the same event. Id you know. Let’s grab the click id from the the pixel will then use the server, you know, and then it’ll you know it’ll dedupe it and then match it, based on what both of the server and the browser components. So I think that would probably get them as close to a solid setup as they can get.
98 00:14:26.580 ⇒ 00:14:30.160 Robert Tseng: Okay, got it. So I guess the last step is just
99 00:14:30.330 ⇒ 00:14:36.750 Robert Tseng: yeah. Making sure that the event Ids will match between the 2 approaches. And then, yeah, I guess.
100 00:14:38.030 ⇒ 00:14:42.500 Robert Tseng: Yeah, is there anything else that we need to check before we can? Just yeah, before this is
101 00:14:42.640 ⇒ 00:14:43.630 Robert Tseng: ready to go.
102 00:14:44.110 ⇒ 00:14:54.830 Andrew O’Neil: No event. Id, and then, yeah. Then it just just a matter of republishing the the the pixel from Gtm, then they should be really, really good to go.
103 00:14:55.420 ⇒ 00:15:05.929 Robert Tseng: Okay, cool. Yeah. So if you don’t mind, just kind of drafting that message, basically sending it to them, letting them know, like, kind of where we’re at your perspective on the on the Qa side. And then.
104 00:15:06.275 ⇒ 00:15:12.869 Robert Tseng: yeah, once we kind of make sure that the event ids are kind of the same from from both approaches, and we should be able to ship it.
105 00:15:13.070 ⇒ 00:15:13.735 Andrew O’Neil: Cool
106 00:15:14.570 ⇒ 00:15:16.919 Andrew O’Neil: Do you have a preference for what slack channel.
107 00:15:17.662 ⇒ 00:15:30.900 Robert Tseng: Yeah, probably I know you’re added to a bunch, and I’m not really sure which ones they’re what they’re called in your workspace. But there’s 1 marketing analytics specifically, mk, analytics. That’s the one that you should send it in.
108 00:15:31.070 ⇒ 00:15:33.819 Robert Tseng: And you can just tag Kevin and Mattesh. Yeah.
109 00:15:35.050 ⇒ 00:15:35.580 Andrew O’Neil: Perfect.
110 00:15:36.400 ⇒ 00:15:50.154 Robert Tseng: Yeah. And then we’ll just give them a caveat that you know, if we don’t have an event Id to match on, because we’re sending a unique event from the server that’s not caught by the pixel. We’re not gonna have a click id for that, either. So like, that’s just not gonna happen yeah, right?
111 00:15:50.400 ⇒ 00:15:50.920 Andrew O’Neil: Bye.
112 00:15:51.480 ⇒ 00:15:56.600 Robert Tseng: It would be good to know, like what you know, what percentage of like. I don’t know like how.
113 00:15:56.800 ⇒ 00:16:00.869 Robert Tseng: what, what’s the impact. But I don’t really know how much, how we can measure that.
114 00:16:01.160 ⇒ 00:16:14.190 Andrew O’Neil: Meta does give some. I’ll include some screenshots. From what the tool is showing. But let’s see if they they did include. Let me just see this. They they have some estimation, and I don’t.
115 00:16:14.420 ⇒ 00:16:19.433 Andrew O’Neil: I’d maybe put it a grain of salt, but it’ll give you it says
116 00:16:20.260 ⇒ 00:16:27.539 Andrew O’Neil: according to them, at least a hundred percent Median increase in additional conversions reported.
117 00:16:27.760 ⇒ 00:16:31.369 Andrew O’Neil: I don’t know if I fully believe that that level of magnitude
118 00:16:31.670 ⇒ 00:16:33.770 Robert Tseng: Yeah, I don’t know. Mediums don’t mean anything to me.
119 00:16:33.770 ⇒ 00:16:40.989 Andrew O’Neil: Yeah, yeah, yeah. But it’s it’s like they should. They should get a better match rate. That’s what Meta is trying to say.
120 00:16:40.990 ⇒ 00:16:42.570 Robert Tseng: Okay, sir.
121 00:16:43.530 ⇒ 00:16:49.839 Robert Tseng: Okay, cool. And then so let’s talk about the north theme thing. I know that like
122 00:16:50.640 ⇒ 00:16:53.290 Robert Tseng: Stuart has messaged you a bit as well, and.
123 00:16:53.450 ⇒ 00:16:54.300 Andrew O’Neil: Yeah.
124 00:16:54.620 ⇒ 00:17:02.150 Robert Tseng: Yeah. So I think I will just share my screen.
125 00:17:07.990 ⇒ 00:17:09.739 Robert Tseng: Thanks for this.
126 00:17:18.119 ⇒ 00:17:24.310 Robert Tseng: Yeah. So I’m referencing from the slack channel. Zoom in a bit. That’s not too much.
127 00:17:28.230 ⇒ 00:17:42.029 Robert Tseng: so yeah, basically, I read through all Stuart’s notes. And I was like, okay, look, I think what we can do is. Yeah, we’re having polytomic. They’re like an Etl tool. They’re building the bidirectional integration for us between North theme and bigquery.
128 00:17:42.270 ⇒ 00:17:42.820 Andrew O’Neil: Perfect
129 00:17:43.700 ⇒ 00:17:50.609 Robert Tseng: Yeah. So then we will be able to push data probably faster than we’d be able to through segment. And segment doesn’t have this integration, anyway.
130 00:17:51.205 ⇒ 00:17:56.570 Robert Tseng: Yeah. So we’re basically using polytomic as a catch. All for anything else that segment doesn’t have out of the box.
131 00:17:57.156 ⇒ 00:18:02.139 Robert Tseng: That way. We’re not like blocked by having one tool that has limited connectors.
132 00:18:03.570 ⇒ 00:18:08.428 Robert Tseng: yeah. So that’s you know, I think these are my, I think these are some of the impacts. I think they would have
133 00:18:09.980 ⇒ 00:18:17.440 Robert Tseng: Yeah, I think he is concerned, like he has this idea of like, I don’t know what the heck this is edge layer, and all this stuff like.
134 00:18:17.849 ⇒ 00:18:29.830 Robert Tseng: yeah, I guess I just said we we would talk about it. Here’s a doc. I don’t know if you’ve got a chance to read through it. I think it’s more of a technical specs, maybe not super relevant to you on how exactly all of it’s going. But
135 00:18:31.410 ⇒ 00:18:34.300 Robert Tseng: yeah, I guess maybe what is relevant is just.
136 00:18:34.300 ⇒ 00:18:34.820 Andrew O’Neil: Hmm.
137 00:18:34.820 ⇒ 00:18:35.920 Robert Tseng: That.
138 00:18:37.780 ⇒ 00:18:42.476 Robert Tseng: Yeah, I mean, we would be sending these fields into North Beam pretty much. And then
139 00:18:42.890 ⇒ 00:18:50.115 Robert Tseng: I’m not really sure if this captures like I I don’t. I just don’t really understand what he’s saying here. So
140 00:18:50.850 ⇒ 00:18:57.239 Robert Tseng: I don’t know if you’re familiar with this yeah concept. Yeah.
141 00:18:57.880 ⇒ 00:19:03.280 Andrew O’Neil: Yeah, so it’s essentially the idea is that the it’s like today.
142 00:19:03.390 ⇒ 00:19:32.093 Andrew O’Neil: the or like, our connection is is like dependent on like page load and and the site server and whatnot. This would kind of introduce a way to track or like deploy analytics as close to like where the the user is connecting from which has shown, or in in the use cases, to improve tracking capabilities, because if someone like leaves a page or abandons
143 00:19:32.600 ⇒ 00:19:57.680 Andrew O’Neil: before you know, marketing, tracking can load, you know, that’s a click. Or you know, data that we’re missing out on the edge server helps to mitigate that by like, pretty much being an instantaneous connection to grab that click click, id, or utm parameters before user has a chance to abandon. Yeah. And in fitting the so
144 00:19:58.920 ⇒ 00:20:21.100 Andrew O’Neil: obviously the the setups that have the most to gain from deploying that are ones where we’re not having good attribution today. You know, if if they’re if you’re seeing, you know, a lot coming through is direct, or if there’s a huge gap between the clicks that a platform is reporting like Meta. And what
145 00:20:21.100 ⇒ 00:20:40.019 Andrew O’Neil: you know, the what we’re seeing on an analytics side that could indicate that, you know, there’s people bouncing. Or you know, we’re we’re losing tracking so without that data point, it’s hard for me to say like, is it worth it to pursue this in terms of extra work to, you know. Put on this extra, you know.
146 00:20:40.150 ⇒ 00:20:42.786 Andrew O’Neil: Cherry on top, if you want to call it that
147 00:20:43.050 ⇒ 00:20:43.700 Andrew O’Neil: Yeah. But
148 00:20:43.700 ⇒ 00:20:53.599 Andrew O’Neil: but you know, for setups that that we do see a lot of either data missing or data getting misattributed. This can help improve that match rate.
149 00:20:54.160 ⇒ 00:20:54.840 Robert Tseng: I see.
150 00:20:55.200 ⇒ 00:21:13.560 Robert Tseng: Okay? Yeah. I generally understand the setup there. Yeah. So we’d be using a Cdn like server to go. And basically access the data at an earlier point before, like the browser side. So this is like, yeah, Pre Pre Javascript firing, or whatever. Yeah, I guess.
151 00:21:13.560 ⇒ 00:21:15.190 Andrew O’Neil: Yes, exactly.
152 00:21:15.482 ⇒ 00:21:25.440 Robert Tseng: I mean, that doesn’t seem like it’s that hard to set up. But also, like, Yeah, I think once you like like you said, I don’t really understand the incremental impact of it. So.
153 00:21:25.440 ⇒ 00:21:26.160 Andrew O’Neil: Correct.
154 00:21:26.610 ⇒ 00:21:28.500 Robert Tseng: Yeah, I guess.
155 00:21:29.430 ⇒ 00:21:31.370 Robert Tseng: Is it fair that we just say like.
156 00:21:32.630 ⇒ 00:21:37.729 Robert Tseng: no, we’re not gonna do that until we understand like that. We’re having
157 00:21:38.150 ⇒ 00:21:45.240 Robert Tseng: a bunch of direct traffic, or like, Yeah, I don’t know. And to me these are just like General, like best practices. He pulled out of Gpt, so I don’t really
158 00:21:45.710 ⇒ 00:21:48.098 Robert Tseng: like this is not really like that.
159 00:21:49.270 ⇒ 00:21:51.639 Robert Tseng: Taylor, like I I don’t think this is I.
160 00:21:52.050 ⇒ 00:21:52.370 Andrew O’Neil: No.
161 00:21:52.370 ⇒ 00:21:53.900 Robert Tseng: Our actual situation, so like.
162 00:21:53.900 ⇒ 00:21:54.310 Andrew O’Neil: No.
163 00:21:54.310 ⇒ 00:21:55.359 Robert Tseng: Really, sure, yeah.
164 00:21:55.810 ⇒ 00:22:17.560 Andrew O’Neil: Yeah, it’s it’s hard to know the exact like amount like. And our server, like, yeah, the the Gpt is under selling, or it’s server tracking is like, very, very good. And even with the Ios updates, like, we’re not losing like as much as this that screenshot is leading us to believe.
165 00:22:18.660 ⇒ 00:22:25.759 Andrew O’Neil: Of course, like each clients, you know, account can look different. So you know, to me it’s worth it to pursue it.
166 00:22:26.210 ⇒ 00:22:39.430 Andrew O’Neil: If we have the data to support. Hey, we’re missing out on these, or we’re seeing the the data is coming in now. But it’s just not getting read correctly. That’s when you would add, add this on to like, supercharge your setup.
167 00:22:39.780 ⇒ 00:22:40.440 Robert Tseng: Okay.
168 00:22:40.660 ⇒ 00:22:46.229 Robert Tseng: So maybe we just do what we’re what we kind of plan to do.
169 00:22:46.560 ⇒ 00:22:52.070 Robert Tseng: Obviously, we’re gonna roll out the Meta stuff and then like on the Northeam side. Then I don’t know. It’s like we kind of have to
170 00:22:52.500 ⇒ 00:22:57.809 Robert Tseng: set this up 1st and then see kind of where we’re at, and then, if it needs more than we can pursue, it.
171 00:22:58.150 ⇒ 00:23:06.603 Andrew O’Neil: Right. It’s like this is our 1 1 point. Oh, you know, if if we need to, we can roll it out as a 2 point. O you know almost like versions.
172 00:23:07.450 ⇒ 00:23:12.309 Robert Tseng: Okay, cool. Then. Yeah. Do you mind giving that kind of like, kind of advice.
173 00:23:12.310 ⇒ 00:23:12.640 Andrew O’Neil: Yeah.
174 00:23:12.640 ⇒ 00:23:14.039 Robert Tseng: To them as well.
175 00:23:14.040 ⇒ 00:23:15.140 Robert Tseng: Yes, absolutely.
176 00:23:15.690 ⇒ 00:23:17.370 Andrew O’Neil: I can follow up in that thread.
177 00:23:19.160 ⇒ 00:23:23.818 Robert Tseng: Got it alright. Well, then, I think that’s really what this week will will look like.
178 00:23:24.980 ⇒ 00:23:30.180 Robert Tseng: just making sure that the meta deployment is bye
179 00:23:31.280 ⇒ 00:23:36.610 Robert Tseng: goes well, and then I think the north beam stuff away. She’ll probably.
180 00:23:36.820 ⇒ 00:23:43.739 Robert Tseng: or once polytomic, is ready to get that set up. We’ll probably review in there. But I don’t really see us getting around to the other sources this week.
181 00:23:43.860 ⇒ 00:23:47.019 Robert Tseng: I feel like that’s that’s pretty much all. We’ll we’ll have time for.
182 00:23:47.140 ⇒ 00:23:48.600 Andrew O’Neil: Yeah, yeah, that’s.
183 00:23:48.600 ⇒ 00:23:49.070 Robert Tseng: Already a lot.
184 00:23:49.070 ⇒ 00:23:49.534 Andrew O’Neil: But.
185 00:23:50.000 ⇒ 00:24:01.330 Robert Tseng: Yeah, yeah, I guess like, timing wise like, does that work? Monday, Wednesday. Kind of stand up for you, or just like being able to check in at that those 2 days, and then it’ll be around to do ad hoc messages.
186 00:24:01.600 ⇒ 00:24:02.360 Andrew O’Neil: Absolutely.
187 00:24:02.690 ⇒ 00:24:04.049 Robert Tseng: Okay, cool.
188 00:24:04.160 ⇒ 00:24:11.289 Robert Tseng: and then hours wise, like, kind of how are we doing? Do you feel like that? Was a good estimate to start with or like. What is that? Where? Where are we at now?
189 00:24:11.570 ⇒ 00:24:25.691 Andrew O’Neil: Yeah, it’s a lot, I think, was spent just just getting up to speed on things and kind of familiarizing myself with your team with Eden. With all the things going on, I feel like I have a better like sense of like the lay of the land.
190 00:24:26.020 ⇒ 00:24:49.689 Andrew O’Neil: And it’s hard, because, like, you know, a lot of this tracking work is like at this stage. It’s, you know, to like giving the engineers requirements, making sure that everything is good to go. Then, obviously, there’s like the Qa stage. So yeah, I think the hours have been fine, like I haven’t, you know, exceeded it. I don’t anticipate, you know, exceeding the the 10 h this week.
191 00:24:49.971 ⇒ 00:25:02.920 Andrew O’Neil: But obviously, if, if, like later on in the process, if you know, the engineers have built their query. And now it’s a lot of Qa. Or making sure. Then, you know, obviously, we could revisit that. But I don’t have any concerns right now.
192 00:25:03.350 ⇒ 00:25:13.937 Robert Tseng: Okay, cool? Then. Yeah, I think that makes like that. I think 2 check-ins a week probably seems fine. And then I ultimately, I want like Henry to be
193 00:25:14.780 ⇒ 00:25:18.501 Robert Tseng: kind of be your go to person. And I I don’t really want to be that
194 00:25:18.720 ⇒ 00:25:19.110 Andrew O’Neil: I’m sure.
195 00:25:19.110 ⇒ 00:25:32.349 Robert Tseng: In the next week or 2. So yeah, I’ll probably have him set up some cadence with you. I don’t. I don’t really want you guys to be doing too many meetings so hopefully between the 2 team team things and
196 00:25:33.180 ⇒ 00:25:39.899 Robert Tseng: maybe he’ll meet with you once a week. And then, yeah, I I think we should be able to keep this going.
197 00:25:40.300 ⇒ 00:25:41.520 Andrew O’Neil: Yeah, sounds good.
198 00:25:42.020 ⇒ 00:25:58.190 Robert Tseng: Okay, cool? Well, then, I’ll give him the update. Now that he’s back on kind of where I see this and off going to yeah. And then, just to give you a heads up, just I mean, at this, we do have like 10 plus other clients like I need to split my time elsewhere, and I want to go in.
199 00:25:58.190 ⇒ 00:25:58.680 Andrew O’Neil: Absolutely.
200 00:25:58.680 ⇒ 00:26:05.940 Robert Tseng: Get more of this work so that I can, you know, also give you more clients. So that’s what I would like to
201 00:26:06.370 ⇒ 00:26:12.570 Robert Tseng: work on like I think so far, I think I’ve appreciated your kind of
202 00:26:13.050 ⇒ 00:26:25.834 Robert Tseng: I think you’re able to speak to fairly comfortable being client facing like not just purely just like technical jargon or whatever. So I think this is, this is good, like I I, you definitely have
203 00:26:26.670 ⇒ 00:26:33.540 Robert Tseng: The experience to like work with a wide range of clients, which gives me more peace of mind about this whole process. So yeah.
204 00:26:33.540 ⇒ 00:26:34.250 Andrew O’Neil: Thanks, Robert.
205 00:26:34.590 ⇒ 00:26:37.770 Robert Tseng: Yeah, yeah. So I think I I would like to go and
206 00:26:38.422 ⇒ 00:26:48.419 Robert Tseng: try to help get get you more. Get you more business as well like with us. So I think that’s that’s kind of where where I’d like to see this going.
207 00:26:48.700 ⇒ 00:26:50.540 Andrew O’Neil: Awesome. Yeah, that sounds great to me.
208 00:26:50.770 ⇒ 00:26:57.867 Robert Tseng: Okay, cool, alright. Well, if you have any questions, you know you can lean on the team, or if anything, you can always slack me directly.
209 00:26:58.130 ⇒ 00:26:58.770 Andrew O’Neil: Cool.
210 00:26:58.980 ⇒ 00:27:00.990 Andrew O’Neil: I’ll start to lean on Henry, too.
211 00:27:01.230 ⇒ 00:27:09.249 Robert Tseng: Great. Yeah. Just put. Make him answer the question. If he doesn’t get it like I mean, obviously, I’ll step in. But just trying to empower him a bit more.
212 00:27:09.760 ⇒ 00:27:12.999 Andrew O’Neil: Sounds good. I can help with all direct things to him, too.
213 00:27:13.320 ⇒ 00:27:14.750 Robert Tseng: Okay, thanks. Andrew.
214 00:27:14.750 ⇒ 00:27:18.040 Andrew O’Neil: Alright, yeah, thanks. Chat. And Robert talks later. Thanks.