ABOUT THIS EPISODE
Text us your thoughts on the episode or the show!
Unlock the secrets of data-driven marketing with Vishnu Vankayala, the visionary founder and CEO of CustomerLabs. Gain exclusive insights into the world of first-party, second-party, and third-party data, and learn how to navigate the complexities of data privacy and tracking restrictions. Vishnu sheds light on the transformative power of first-party data, revealing how it can elevate your marketing strategies in an increasingly privacy-conscious digital landscape. Discover the game-changing shift from traditional tracking to server-to-server connections and the ways ID resolution can sharpen your performance marketing strategies.
Explore the burgeoning field of first-party data operations (1PDOPS) as we discuss the role of ID resolution in creating a cohesive identity across multiple platforms. Vishnu shares his expertise on unifying disparate system IDs to enhance lead quality and marketing performance. Learn how the synergy between CRM data and marketing operations can empower platforms like Google, Facebook, and LinkedIn to generate high-quality leads. This episode is a treasure trove of knowledge for marketing professionals eager to optimize campaigns and reduce costs while navigating the challenges of privacy regulations.
Elevate your networking game by tuning into our conversation with Vishnu about the power of LinkedIn for knowledge sharing. He shares invaluable tips on using the platform to connect with industry leaders and exchange insights. This episode promises to be a rich resource for anyone looking to harness the power of data in digital marketing. Join us and become part of a community that values learning, growth, and collaboration.
Episode Brought to You By MO Pros
The #1 Community for Marketing Operations Professionals
IN THIS EPISODE
SHOW NOTES 🔗
TRANSCRIPT 🔗
00:00:23.830 --> 00:00:29.663
Hello everyone, welcome to another episode of OpsCast brought to you by MarketingOpscom and powered by all the MoPros out there.
00:00:29.663 --> 00:00:35.399
I am your host, michael Hartman, again flying solo, as we are approaching that.
00:00:35.399 --> 00:00:39.164
We're now well within a week to Masa Palooza 2024.
00:00:39.164 --> 00:00:49.265
So hopefully we will see many of you there Joining me today to catch us up on what is happening with first-party cookies and all that entails.
00:00:49.265 --> 00:00:57.902
We'll also talk about, I think, second and third-party cookies, but we'll get there, but also, I guess, just first-party data in general is Vishnu Venkayala.
00:00:57.902 --> 00:01:12.599
Vishnu is founder and CEO of Customer Labs and for those of you who were at Mopspalooza 2023, you may recognize that name from last year, when they won the award for most innovative marketing technology presented by the MarTech Weekly 100 Awards.
00:01:12.599 --> 00:01:15.191
So pretty excited to have that.
00:01:15.191 --> 00:01:19.271
Vishnu has held several roles in higher education after starting his career in software development.
00:01:19.271 --> 00:01:21.957
So interesting career path.
00:01:21.957 --> 00:01:22.459
Vishnu.
00:01:22.459 --> 00:01:23.962
Thank you for joining me today.
00:01:25.170 --> 00:01:25.792
Thank you, michael.
00:01:25.792 --> 00:01:33.873
Thanks very much for having me here and hi everyone who is a great fan of MOps.
00:01:35.096 --> 00:01:37.962
Yes, we're ready to have you All right.
00:01:37.962 --> 00:01:49.170
So I know we said we would talk about first-party data and first-party cookies and whatnot, but I think it would be useful to take a step back and talk about what kind of what that let's do some definitions right.
00:01:49.170 --> 00:01:49.712
What does that mean?
00:01:49.712 --> 00:01:53.570
There's I think I've, I know I've definitely heard first party and third party.
00:01:53.570 --> 00:01:54.694
Those will make sense, I guess.
00:01:54.694 --> 00:01:58.510
Data and or cookies, uh, I think occasionally I've heard second party.
00:01:58.510 --> 00:02:10.581
Um, but maybe you can help us with a baseline like definition of those two or three, you know you can clarify if there should be two or three only and what's the difference between those.
00:02:15.909 --> 00:02:16.271
Absolutely no.
00:02:16.271 --> 00:02:37.643
So usually most of us just get understanding of first party, second party and third party data and when it comes to first party, anybody who is interacting with the particular business and they would be able to eventually share that information is entirely first party, 100% concentrated and 100% shared by the first party user when they're interacting with you.
00:02:37.643 --> 00:02:43.179
So, for example, right now we are on the podcast, now you know me and I'm sharing my name, my details.
00:02:43.179 --> 00:02:44.334
This is first party.
00:02:44.334 --> 00:02:49.562
And let's say you are inviting someone to the podcast through a friend.
00:02:49.562 --> 00:02:51.353
That is second party data.
00:02:51.353 --> 00:02:56.644
So, say, michael, I know Vishnu and Mike introduces me to you.
00:02:56.644 --> 00:02:58.052
That's second party data.
00:02:58.052 --> 00:02:59.216
So I'm a friend of a friend.
00:02:59.717 --> 00:03:02.003
Third party, entirely not related.
00:03:02.003 --> 00:03:10.378
I shared my details with somebody else and they share the data with you in terms of, for example, hey, these are the group of people you might be interested in talking to you.
00:03:10.378 --> 00:03:20.181
Why don't you just reach out to them in a more non-aggressive way or more privacy-centric way?
00:03:20.181 --> 00:03:39.599
So that is the third-party data, and most of the businesses interact with first, second and third-party data without them knowing, without them, day in, day out, and the primary angle is whenever someone shares the data with us, how do we eventually collect it, store it and activate it?
00:03:39.599 --> 00:03:46.116
Because it is 100% concentrated, it is your data, and how effectively you can use it is the whole game here.
00:03:46.959 --> 00:03:47.360
Got you.
00:03:47.360 --> 00:03:48.562
I'm just curious.
00:03:48.562 --> 00:04:07.681
So I think I get the distinction between second-party and third-party data the way you described it, but from a practical day-to-day technology standpoint it seems to me like there wouldn't be all that much difference in that.
00:04:07.681 --> 00:04:10.516
But am I missing a piece of this?
00:04:12.602 --> 00:04:15.960
No, so I mean there will be a slight difference.
00:04:15.960 --> 00:04:19.521
The second party is basically like we are collaborating with, let's say, uber.
00:04:19.521 --> 00:04:21.677
Uber shares the data with the driver.
00:04:21.677 --> 00:04:23.369
That's primarily second-party data.
00:04:23.369 --> 00:04:29.338
So you know that they will be sharing the data with someone else and that is the second-party level.
00:04:29.338 --> 00:04:35.862
So we both know we are in a contract and when I share the data with you, it automatically shares, for example, amazon.
00:04:35.862 --> 00:04:38.442
Amazon saves the data with the delivery partner.
00:04:38.442 --> 00:04:39.549
What is the data?
00:04:39.549 --> 00:04:44.293
So it could be just a phone number, it may not be the name, but how do they share the data?
00:04:44.293 --> 00:04:45.014
Is the whole idea?
00:04:45.034 --> 00:04:46.898
Okay, they share the data is the whole idea.
00:04:46.898 --> 00:04:47.057
Okay.
00:04:47.057 --> 00:05:06.398
So there's sort of maybe contractual is an extreme, but some sort of either, I guess an explicit agreement that this data that you're sharing with that I'm sharing with you, vishnu, that you are able to share it with other entities, that you also have some sort of agreement with.
00:05:06.398 --> 00:05:09.317
That's right In terms of how they would handle that.
00:05:09.317 --> 00:05:19.884
Okay, that makes sense, whereas third-party data is also shared, but maybe done so without that.
00:05:19.884 --> 00:05:24.198
Maybe there's some implied consent a little bit Okay.
00:05:26.551 --> 00:05:42.297
So eventually, if you take ad algorithms or ad platforms not algorithms so eventually what happens is we are sharing as much data as possible, but then these guys don't reveal the first name or last name, so eventually what they do is based on the data.
00:05:42.297 --> 00:05:52.220
Whatever we collect, they start showing the ad and eventually, without sharing the whole detail, so that's the third-party kind of data, how they use it.
00:05:52.220 --> 00:06:00.523
And then you have outbound email marketing or there are companies which can identify the users when they come to your website.
00:06:00.523 --> 00:06:02.135
It is third-party data sharing.
00:06:02.135 --> 00:06:03.514
So someone comes to the site.
00:06:03.514 --> 00:06:05.080
I will give the email address.
00:06:05.080 --> 00:06:06.676
That is entirely third-party data.
00:06:06.676 --> 00:06:07.796
So that is not the data anybody owns.
00:06:07.796 --> 00:06:08.322
It's just that they enrich the data and give it to address.
00:06:08.322 --> 00:06:08.645
That is entirely third-party data.
00:06:08.645 --> 00:06:08.809
So that is not the data anybody owns.
00:06:08.809 --> 00:06:12.139
It's just that they enrich the data and give it to you based on the third-party identifiers.
00:06:13.041 --> 00:06:13.601
Got it Okay.
00:06:13.601 --> 00:06:18.211
So that's really helpful to clarify that, okay.
00:06:18.211 --> 00:06:33.760
So the other piece of this which kind of surprised me is that when you and I talked before, you talked about first-party data, that we can have first-party data both unknown and anonymous, or unknown users or, I guess, maybe mostly visitors.
00:06:33.760 --> 00:06:42.717
So I'm trying to wrap my head around that, because I thought first-party data meant we knew who you were, but it doesn't sound like I understood that right.
00:06:43.721 --> 00:06:47.075
Yeah, no, I mean 99% of the people.
00:06:47.075 --> 00:06:56.730
When we speak to them, everyone thinks whenever someone is identifiable, he's first party data.
00:06:56.730 --> 00:06:57.591
That's not actually right.
00:06:57.591 --> 00:07:00.553
The understanding is anyone who lands on the website.
00:07:00.553 --> 00:07:15.506
If you are able to identify them, like, for example, based on a cookie or based on an identifier if you're able to place it across, at this point, what you don't know is their name or PAI personal identifier information that's what you don't know.
00:07:15.506 --> 00:07:22.660
But if you can collect it and if you can activate it, that's still the first part of the data.
00:07:22.660 --> 00:07:25.258
But the question is how can you collect it?
00:07:25.258 --> 00:07:30.173
How can you activate it at scale, despite someone is actually sharing their PII?
00:07:30.173 --> 00:07:35.577
So that's the identified users and non-identified users.
00:07:35.577 --> 00:07:38.158
Who is coming to the site is still the first-party data.
00:07:39.251 --> 00:07:59.561
Okay, so if I'm someone and I'm going to a website for the first time, they may identify me with a cookie, some sort of identifier, but until I have an interaction of some sort where it reveals my PII or other data about me, then I still remain unknown or anonymous from that standpoint.
00:07:59.561 --> 00:08:00.842
Exactly Okay, got it.
00:08:03.591 --> 00:08:11.902
The major angle here is how do we keep those identifiers, because, let's say, you're going to have 30,000 or 40,000 people coming and landing on the website.
00:08:11.902 --> 00:08:15.198
How are we going to keep those identifiers intact?
00:08:15.198 --> 00:08:22.504
How are we going to use them so that we'd be able to reach out to these customers who came to your site and share that data?
00:08:23.350 --> 00:08:25.533
Right, yeah, I can see how that would be very valuable.
00:08:25.533 --> 00:08:38.076
All right, so it's interesting that we're having this conversation about the topic of first-party, third-party, second-party data at this point, because I think it was what 18, 24 months ago that Google was talking about in Chrome.
00:08:38.076 --> 00:08:44.990
They were going to disable or remove its support of third-party cookies, right, I think that was basically it, but then it got.
00:08:44.990 --> 00:08:47.594
I guess I'm not even sure right now.
00:08:47.594 --> 00:08:54.202
It was either postponed or completely taken off the table, so maybe you can help.
00:08:54.202 --> 00:08:55.826
What is the current state of that?
00:09:04.550 --> 00:09:09.111
And what do you expect the outcome or what do you expect that's going to happen in maybe the near-term future, mid-term future?
00:09:09.111 --> 00:09:10.432
No, I mean, google eventually lost their whole.
00:09:10.432 --> 00:09:12.433
I mean they decided not to deprecate their third-party cookies anymore.
00:09:12.433 --> 00:09:14.954
So that's the latest information, what we have.
00:09:14.954 --> 00:09:23.217
But whenever someone thinks of third-party cookies, they almost assume that it's not privacy-centric.
00:09:23.217 --> 00:09:29.740
That's the way the narration has been built by competitions of Google.
00:09:30.420 --> 00:09:40.363
And what Google intelligently started doing is they started bringing in consent a lot into their entire ad platforms.
00:09:40.363 --> 00:09:57.140
So, for example, the moment you land on the website, especially in Europe or GDPR-oriented countries, you have to give a consent, even to identify you, and without giving the consent, there is nothing you can actually pass back to Google or Google AdWords, or even Facebook, for that matter.
00:09:57.140 --> 00:10:05.480
So the Google has taken a very different approach, saying look, we will use third-party cookies, but we will use only when the user is consented.
00:10:05.480 --> 00:10:17.237
And I think it's a fair approach, because you still wanted to reach out to the people who is coming to the website, who is sharing the data, but with the consented mode.
00:10:17.237 --> 00:10:19.717
So they launched new technology.
00:10:20.472 --> 00:10:21.370
Can I interrupt real quick?
00:10:21.370 --> 00:10:29.429
So are they doing that global Like it's just a global decision, that that's the way it's going to be, that global like it's just a global decision, that that's the way it's going to be?
00:10:29.429 --> 00:10:36.872
Or is it only in more regulated environments like Europe, where there's GDPR, castle in Canada, etc.
00:10:36.932 --> 00:10:38.938
Yeah, no, you're right.
00:10:38.938 --> 00:10:42.559
So right now the consent is highly.
00:10:42.559 --> 00:10:55.839
I mean, google has made it mandatory in GDPR regulated countries, especially in Europe and UK, whereas in the US still the consent is not highly.
00:10:55.839 --> 00:11:01.285
Google did not make it mandatory in non-GDPR areas.
00:11:01.285 --> 00:11:12.664
I foresee that that will be changing pretty soon because Google will start having those consents in pretty much in all the countries, eventually based on the regulations, based on the privacy laws.
00:11:13.889 --> 00:11:21.221
Yeah, I mean, it's me Just the way I think about this stuff, right, I want to keep it simple.
00:11:21.221 --> 00:11:24.177
I would probably try to keep it as simple as possible.
00:11:24.177 --> 00:11:28.307
Do the same thing globally, then how you use that is is a different thing.
00:11:28.307 --> 00:11:29.672
You know, you could choose to.
00:11:29.672 --> 00:11:41.382
I guess, for lack of a way you say, way of saying it, you ignore, right, some of that if you didn't get explicit, um consent about that, force people in the us or whatever.
00:11:41.382 --> 00:11:51.664
But absolutely okay, yeah, so so as far as we know, right, right, google doesn't have any new plans to restrict third-party cookies through Chrome.
00:11:52.049 --> 00:11:52.653
At this moment.
00:11:52.653 --> 00:11:54.278
Yes, Interesting.
00:11:57.052 --> 00:12:16.861
But what I foresee happening in the background being in this tracking, profiling kind of technology in the background, the way Google and Facebook started moving their whole tech is they're moving away from the browsers and they started moving into server-side angles.
00:12:16.861 --> 00:12:38.970
So, for example, google recently launched something called 1P domain tracking, so first party, so all the tracking will happen from server to server and enhanced conversions, which is the way of identifying the user who is doing what on the website, and similarly, consent mode is another big thing which Google has launched.
00:12:38.970 --> 00:12:58.701
So, although they don't, they're saying they're not going to deprecate the third-party cookies, but the usage of third-party cookies inside the Google technologies or that platforms will eventually go down even without us knowing, and having a right technology to maintain all these data is quite important.
00:12:59.802 --> 00:13:16.855
Okay, I will admit I am not sure how that server-to-server piece works with a user going to a website, but I know that it's not like I'm going directly from my computer to some server, right, there's other hops along the way.
00:13:16.855 --> 00:13:18.654
I assume it's something related to that.
00:13:18.654 --> 00:13:20.920
Okay, yeah, which makes sense.
00:13:20.920 --> 00:13:28.198
Okay, and I don't think we need to get into the rabbit hole of that kind of level of technology, yeah, Okay.
00:13:28.198 --> 00:13:31.203
So let's bring it back to what?
00:13:31.203 --> 00:13:32.906
Into the rabbit hole of that kind of level of technology?
00:13:32.906 --> 00:13:34.028
Okay, so let's bring it back to what's the impact.
00:13:34.028 --> 00:13:40.233
So, for most of our audience, right, marketing operations professionals how should they be thinking about using first-party data?
00:13:40.233 --> 00:13:41.379
Maybe they're not doing anything yet.
00:13:43.651 --> 00:13:50.100
Most people out there, if they've got a marketing automation platform, they've probably got some sort of tracking script that that works with that.
00:13:50.100 --> 00:13:57.636
You know, I know, I know for sure Eloqua and Marketo do, I'm sure HubSpot does, and I'm going to assume whatever they're calling Salesforce.
00:13:57.636 --> 00:14:01.636
Salesforce is Pardot stuff nowadays.
00:14:01.636 --> 00:14:05.014
If anyone's still using it has something like that too.
00:14:05.014 --> 00:14:09.976
But that's essentially, I think, in most cases, third-party data.
00:14:09.976 --> 00:14:19.082
I think there are some options on those to turn it into first-party data, but it's kind of getting into gray area for me in terms of how I understand it.
00:14:19.082 --> 00:14:21.634
But anyway, long story short.
00:14:21.634 --> 00:14:25.202
How should our audience be thinking about first-party data?
00:14:25.202 --> 00:14:25.831
Should they be?
00:14:25.831 --> 00:14:27.576
If they're not actively doing it, should they be pursuing it?
00:14:27.576 --> 00:14:28.958
Is there like what are the benefits of it versus third-party data?
00:14:28.958 --> 00:14:29.360
Should they be?
00:14:29.360 --> 00:14:30.884
If they're not actively doing it, should they be pursuing it?
00:14:30.884 --> 00:14:32.307
Is there, like what are the benefits of it versus third-party?
00:14:32.327 --> 00:14:32.850
data, that kind of stuff.
00:14:32.850 --> 00:14:38.520
Yeah, so we just touched base about the server-to-server connections, right?
00:14:38.520 --> 00:14:40.938
So what happens in the previous days?
00:14:40.938 --> 00:14:54.456
If you want to track something, you place a JavaScript inside on your website and it loads on the browser and starts picking back that information back and forth between that platform, so the analytics platforms, et cetera.
00:14:55.775 --> 00:15:22.624
And now that browsers are restricting such kind of behavior, tracking most of the companies like, for example, google or Facebook they eventually started working on the server-side tracking and with the marketing ops professionals when I met them, when I saw them, it's primarily oriented towards maintaining the CRM, running email, marketing aspects of it.
00:15:22.624 --> 00:15:54.942
Those are the kind of areas they were focusing a lot and I think it's time for them to start looking at this also as one of the functions, and that particular function will focus more on how do we start tracking the data from the website and how do we unify the customers whenever someone is landing on the website and becoming a lead, and whenever someone becomes a lead and becomes an opportunity, how can we bring that back and push it back into the platforms.
00:15:54.942 --> 00:15:57.057
So, if you look at it, how do you use it?
00:15:57.057 --> 00:16:03.940
So one is optimizing the campaigns not only for the leads, but also for the bottom funnel conversions, like opportunities or deal one.
00:16:03.940 --> 00:16:16.052
And similarly, whenever you try to ID those users who are coming and landing on the website, how can we use this in audience for retargeting purposes and obviously to do all those things?
00:16:16.113 --> 00:16:23.697
What we need is a very integral part, something called ID resolution, and that ID resolution is what happens between the systems.
00:16:23.697 --> 00:16:43.928
So, for example, the Google, the Facebook or LinkedIn should know Michael has landed on the website and I want to target Michael or show an ad or give a nudge on Google and LinkedIn that hey, this is the ad you are interested in, can you go and book a demo?
00:16:43.928 --> 00:16:48.701
So when you want to act on those retargeting campaigns, this is a primary aspect.
00:16:48.701 --> 00:16:51.689
The ID resolution would be the primary aspect.
00:16:51.689 --> 00:16:53.518
Someone should invest.
00:16:53.518 --> 00:17:08.153
So, marketing operations so far they have been looking at GTM as one of the area and then they add a line between performance marketing and typical sales-led organization.
00:17:08.153 --> 00:17:16.447
Now the marketing operations can also bring the data back into performance marketing and be able to enable performance marketers a lot with the data, what they collect.
00:17:16.447 --> 00:17:21.741
So that's the shift, what we are looking at and what we are trying to make in the market.
00:17:22.671 --> 00:17:24.237
Sorry, just a clarification for you.
00:17:24.237 --> 00:17:26.598
When you say performance marketing, what does that mean to you?
00:17:26.598 --> 00:17:28.135
I don't want to make any assumptions here.
00:17:29.389 --> 00:17:54.278
So performance marketing is basically people who spend media buyers, so media buyers who generate the leads by running ads on Google and ads on facebook, linkedin, tiktok, wherever the platform they are, and that's what I meant by performance marketers okay, so it might also be, I think, called demand gen or lead gen or digital marketing as well.
00:17:54.437 --> 00:17:56.000
Right, okay, got it.
00:17:56.000 --> 00:17:56.581
Okay.
00:17:56.581 --> 00:17:59.612
Yeah, um, okay, that makes sense.
00:17:59.612 --> 00:18:04.155
This ID resolution stuff, though, so could you maybe?
00:18:04.155 --> 00:18:14.007
I have a pretty good idea what that means, but maybe could you drill down on that a little bit and you know what is it and why.
00:18:14.007 --> 00:18:18.070
Why is it?
00:18:19.174 --> 00:18:21.826
so important to this whole bit with first party data.
00:18:21.826 --> 00:18:43.899
Yeah, so ID resolution primarily, when I speak with sales-led organizations who have been investing a lot on Salesforce, eloqua, marketo kind of areas, what they're trying to do is I have a person in Marketo and I want the same person to be in Salesforce, so use the same email address to create a unified record.
00:18:43.899 --> 00:18:48.580
Now I just spoke about the consent a couple of minutes ago.
00:18:48.580 --> 00:19:05.273
So a user lands on the website let's say a user gives consent, saying, hey, look, you can use my data for tracking and without the ID resolution on that particular moment, you won't be able to send that consent parameter back into Google.
00:19:05.273 --> 00:19:13.973
When the user becomes a lead, and whether it is giving a consent or denying a consent, it has to start from the day it lands on the website.
00:19:13.973 --> 00:19:18.937
So right now you're an anonymous user.
00:19:18.937 --> 00:19:22.944
And how do you create an identity for this user is very, very important.
00:19:22.944 --> 00:19:32.538
So one you create a first-party identity who is an anonymous user, which we call it a pseudo ID, and then the user becomes a known user.
00:19:32.538 --> 00:19:44.777
He enters back into the CRM and this is the point where you have to attach the pseudo ID with the real ID, which can be Salesforce ID, it can be HubSpot ID or any other CRM, for that matter.
00:19:44.777 --> 00:20:02.516
And when you send them back, for example, now, today I'm a lead and tomorrow I became an opportunity, and I have to push this opportunity back into Google or Facebook or LinkedIn, and now the LinkedIn should know whether you have given a consent for me to use that data or not.
00:20:02.516 --> 00:20:07.649
So this whole part is being connected by ID resolution.
00:20:08.151 --> 00:20:19.403
So, generally, for any systems to work, id resolution is mother of everything and without getting that piece right, you won't be able to do this properly.
00:20:19.403 --> 00:20:24.862
You will see results, very mediocre results 50, 60 percentage returns.
00:20:24.862 --> 00:20:37.219
But if you want to push the markup, the id resolution piece is something you have to get it right, starting from how do you place the server, set cookies so it stays intact it stays there literally forever and how do you collect the data?
00:20:37.219 --> 00:20:47.867
So, for example, you click an ad, google creates something called google click id and Google creates something called Google Click ID and Facebook creates something called Facebook Click ID and LinkedIn creates something called LIFAT ID.
00:20:47.867 --> 00:20:49.133
How do you collect it?
00:20:49.413 --> 00:20:52.877
When you're an anonymous user and when you become a lead, how do you attach it?
00:20:52.877 --> 00:20:54.393
And when you make an opportunity.
00:20:54.393 --> 00:20:59.232
How do you attach all this information and push it back into that platform so that it knows?
00:20:59.232 --> 00:21:02.000
These are the kind of users who are becoming opportunities.
00:21:02.000 --> 00:21:03.855
These are the kind of users who are becoming opportunities.
00:21:03.855 --> 00:21:04.317
These are the kind of users who are junk.
00:21:04.317 --> 00:21:08.420
Let's not target more so that's how you can connect the dots between the systems.
00:21:09.530 --> 00:21:16.523
Okay, so this is like it's generating a master ID that connects all the other individual systems IDs.
00:21:16.523 --> 00:21:23.780
Okay, I'm oversimplifying it, I'm sure, but it seems my small brain is working.
00:21:25.131 --> 00:21:26.235
That's exactly what it is.
00:21:26.235 --> 00:21:43.439
So you create one ID and you collect all the IDs and put these things together and whenever you send that information back into that particular system, you make sure you're sending the right ID back into the system, because LinkedIn doesn't know the Google ID, facebook doesn't know the Google ID, so you have to send the right IDs back into the systems.
00:21:46.093 --> 00:21:55.942
So can it also help with sort of connecting the dots between, say, someone's work email address and personal email address?
00:21:57.810 --> 00:22:00.359
Well, the Google and Facebook knows it.
00:22:00.359 --> 00:22:03.378
We may not know it, but they know it.
00:22:03.378 --> 00:22:18.963
So when you send the data back into Google and Facebook, eventually they would be able to figure out personal email address and work email address, but as a first-party data we will know only whichever the data is shared by that particular user.
00:22:20.131 --> 00:22:21.296
Okay, that makes sense.
00:22:21.296 --> 00:22:23.952
Cool, All right.
00:22:23.952 --> 00:22:25.277
Well, that's really helpful.
00:22:25.277 --> 00:22:44.875
So one of the things I think we talked about is that, to use this at scale, you need to operationalize it, and you used the term with me, first-party data ops, so again, I can imagine what that is, but why don't you give us a definition?
00:22:44.875 --> 00:22:45.458
What is that?
00:22:45.458 --> 00:22:46.259
Why is it important?
00:22:47.382 --> 00:22:47.542
Yeah.
00:22:47.542 --> 00:22:54.939
So again, like I just mentioned, marketing operations professionals, so far they have been helping a lot.
00:22:54.939 --> 00:22:59.360
The sales team not primarily helping out.
00:22:59.360 --> 00:23:07.738
I wouldn't say not primarily, but as far as I know they couldn't help performance marketing team or media buyers or digital marketing team a lot.
00:23:07.738 --> 00:23:15.921
Now, with this data, can we power the media buyers or performance marketing team to get the maximum?
00:23:15.921 --> 00:23:24.721
So let's say, for example, the sales team says I have a problem with quality, can we help the digital marketing team to generate high-quality leads?
00:23:24.721 --> 00:23:29.741
And if they want to reduce the CPU, can you use this 1PDOPS to do it?
00:23:29.741 --> 00:23:34.676
So that's where we are carving out, slicing it down.
00:23:34.696 --> 00:23:46.098
Saying 1PDOPS is basically the future of advertisement and collecting it, activating it is very important and there lies a lot of technology in between.
00:23:46.098 --> 00:23:48.197
It's not a simple solution.
00:23:48.197 --> 00:23:55.259
You have to work on multiple bits and pieces so that you collect it, store it and activate it in a seamless fashion.
00:23:55.259 --> 00:24:02.780
So what we are anticipating in a few years is the 1PDA ops will eventually become a division.
00:24:02.780 --> 00:24:15.060
Every single company, whether it is e-commerce or whether it is a non-e-commerce company, will have one specialist who will be working on this 1PT ops, but it's very, very in a specialist role.
00:24:17.232 --> 00:24:17.734
It makes sense.
00:24:17.734 --> 00:24:33.136
Okay, so there's conceptually, first-party data operations and then there are platforms which I think enable this, maybe even yours In my head.
00:24:33.136 --> 00:24:46.701
I'm trying to kind of compare and contrast that to something that we actually just recently talked to somebody about again customer data platforms, which seems like it would be a natural place to do that we actually just recently talked to somebody about, again customer data platforms, which it seems like it would be a natural place to do.
00:24:46.701 --> 00:24:49.038
That ID resolution, some of those things as well.
00:24:49.038 --> 00:24:51.798
What's the difference?
00:24:51.798 --> 00:24:57.041
What makes one better than the other?
00:24:58.951 --> 00:25:00.075
This is the exact problem.
00:25:00.075 --> 00:25:01.519
What we have been facing right.
00:25:01.519 --> 00:25:13.591
Cdp is not well defined and in the last two to three years, everyone started calling themselves a cdp marketing automation platform.
00:25:13.591 --> 00:25:16.299
Yes, we are a cdp email marketing platform.
00:25:16.299 --> 00:25:20.151
We are a cdp data warehouse activation platforms we are a cdp.
00:25:20.151 --> 00:25:30.459
So everyone started calling themselves CDP and I love the term CDP because I came across the term CDP somewhere about 2017, 2018.
00:25:30.459 --> 00:25:39.406
And it's like an awesome feeling to have some name for everything we have been doing.
00:25:39.406 --> 00:25:48.201
But everyone started jumping into the bandwagon calling themselves a CDP and we were like, okay, fine, this is not something where we want to be so.
00:25:48.201 --> 00:25:51.298
So the definition was missing.
00:25:51.298 --> 00:25:54.118
And when you say CRM, you know what the CRM does.
00:25:54.118 --> 00:25:56.979
When you say marketing automation, you know what the marketing automation does.
00:25:56.979 --> 00:25:59.557
When you say email marketing platform, you know what it does.
00:26:01.692 --> 00:26:06.720
I would argue that when you say CRM, there's actually lots of different things going on in people's heads.
00:26:06.720 --> 00:26:08.261
But I digress.
00:26:10.184 --> 00:26:10.485
I agree.
00:26:10.485 --> 00:26:12.192
So it could be the same issue.
00:26:12.192 --> 00:26:13.575
What happened with the CRM?
00:26:13.575 --> 00:26:20.004
So CRM is supposed to do a basic functionality and eventually it started moving away.
00:26:20.004 --> 00:26:28.820
The same thing might be happening with CDP, and it started moving away from what it was, or what at least we wanted to define it.
00:26:28.820 --> 00:26:33.221
And then we thought, okay, fine, we don't want to be in that competition.
00:26:33.221 --> 00:26:37.259
Either we should have enough money to define the CDP.
00:26:37.259 --> 00:26:43.918
This is what the CDP is like, how big companies like Salesforce are trying to do, or some of the companies are trying to do.
00:26:43.918 --> 00:26:57.558
We don't want to get into that war, we don't want to be in that particular area, and we decided let's focus on a small area where we can create impact, which is nothing but one video Collected, stored, activated as simple as that.
00:26:57.558 --> 00:27:00.017
So just stick there.
00:27:00.750 --> 00:27:04.520
Okay, so see if I can recap this.
00:27:04.520 --> 00:27:23.940
So if I'm talking to a customer data platform and they are saying they can do something like first-party data collection and ID resolution, yeah, that is a sort of a, that's a piece of the puzzle.
00:27:23.940 --> 00:27:26.248
It's not probably the full thing of what a CDP does.
00:27:26.248 --> 00:27:38.801
Whereas the first-party data ops is primarily that sort of collection, identification and then how you leverage it through some channels, dataops is primarily that sort of collection, identification and then how you leverage it through some channels.
00:27:39.864 --> 00:27:41.674
Yep, no, you're exactly right.
00:27:41.674 --> 00:27:56.440
So that's the idea, but then now everyone calling themselves CDP lost that definition, so eventually it's becoming very cloudy in the customer's mind.
00:27:56.440 --> 00:27:59.374
It makes no sense to go and explain that.
00:27:59.374 --> 00:28:12.519
The moment we started positioning as first party data ops, there's a clear definition, there's a clear value and we are able to close deals much faster than calling ourselves a CDP.
00:28:13.550 --> 00:28:13.770
Okay.
00:28:13.770 --> 00:28:31.320
So if I'm sitting here listening to all this and I'm thinking well, google's not getting rid of third-party data, our performance marketing activities are performing well, you know why should I care about this first-party data and operationalizing it?
00:28:31.320 --> 00:28:38.462
What would be your argument for why our listeners should be focused on this if they haven't already?
00:28:38.462 --> 00:28:41.049
Is there any tangible benefit?
00:28:41.049 --> 00:28:50.879
Because anything like this requires effort, money, change to an organization to put in place.
00:28:52.191 --> 00:28:53.978
No, it's really a good point.
00:28:53.978 --> 00:29:11.601
That's what we have been advocating Since 2023, early 2023, january, google started pushing AI a lot, facebook started pushing AI a lot, and LinkedIn they just started very recently, maybe two, three months ago.
00:29:11.601 --> 00:29:17.363
So what they really want is hey, you have the best customers, give it to me.
00:29:17.363 --> 00:29:20.960
You have non-converting customers give it to me.
00:29:20.960 --> 00:29:28.899
And you have high-value customers give it to me and I will go and find similar customers like that.
00:29:28.899 --> 00:29:31.878
So how fast can you do it?
00:29:31.878 --> 00:29:33.256
How soon can you do it?
00:29:33.256 --> 00:29:35.739
How well you can do it is the whole idea.
00:29:36.210 --> 00:29:45.115
So, for example, you click an ad, you should collect that GCClick ID and you pick an opportunity.
00:29:45.115 --> 00:29:48.700
Can you send that back into Google in a matter of seconds?
00:29:48.700 --> 00:30:07.615
So that's where this first-party DevOps comes into play, and if you're not making those connections between the systems, it's basically saying I mean, like you are just brushing out with whatever the information Google is trying to give it to you without powering the data.
00:30:07.615 --> 00:30:11.139
So Google recently came up with something called Data Manager.
00:30:11.139 --> 00:30:24.778
The Data Manager is purely how can you send the data back into Google Ads so that it learns from your business, which is entirely first-party data, and it brings more customers, like, whichever the way you want.
00:30:24.778 --> 00:30:28.817
You want high-value customers, it will go and be able to find high-value customers.
00:30:28.817 --> 00:30:32.918
If you want a category of customers, it can actually go and bring a category of customers.
00:30:32.918 --> 00:30:34.184
You can actually go and bring a category of customers.
00:30:34.184 --> 00:30:39.541
So that's what's changing here, with first-party data.
00:30:42.191 --> 00:30:48.824
So that sounds like a speed and efficiency kind of benefit.
00:30:48.824 --> 00:30:54.021
Are there any other like I'll call it financial-type benefits that might come from something like this?
00:30:55.029 --> 00:30:55.310
Yeah.
00:30:55.310 --> 00:30:57.980
So speed, efficiency to do what?
00:30:57.980 --> 00:31:12.795
So, ideally, if you want to reduce the CPL, or if you want to reduce, let's say, for example, optimize for more high-quality leads, which we generally call it as LTOs lead-to-opportunity rate, so how do you increase the lead-to-opportunity rate?
00:31:12.795 --> 00:31:15.501
Only by bringing the high-quality leads into the funnel.
00:31:15.501 --> 00:31:21.720
So can you close the loop, the feedback loop, by sending the data between your CRM and Google Ads.
00:31:21.720 --> 00:31:41.339
So, in terms of real money, people will start seeing can you reduce CPL cost per lead by X amount, or can you increase the opportunity ratio by X amount, or can you increase the number of leads we would get?
00:31:41.339 --> 00:31:49.315
So all these would be the direct impact of ROI, not only the speed and efficiency, but the direct impact on the marketing, direct impact on the revenue.
00:31:51.432 --> 00:31:55.162
So just okay, all those things would be great.
00:31:55.162 --> 00:32:05.918
How would a first-party data ops platform or enabling first-party data ops to scale, like how would that actually do that?
00:32:05.918 --> 00:32:18.341
I'm trying to connect the dots to a reduction in cost per lead, or you said, I think, something like I'm going to paraphrase here.
00:32:18.341 --> 00:32:22.864
I think what you meant was like higher converting opportunities or something like that.
00:32:23.826 --> 00:32:27.710
Yeah, so high quality leads is the whole game, right?
00:32:27.710 --> 00:32:37.484
So literally two weeks ago, linkedin has switched don't optimize for the leads, but optimize for the quality leads.
00:32:37.484 --> 00:32:46.039
And similarly in Google, when you set up a campaign, you don't only go after the leads, you can also go after the high value leads.
00:32:46.039 --> 00:32:57.097
So now you collect the data, you click the ad, you know which keyword you have been searching for on Google and you have been marked as an opportunity.
00:32:57.097 --> 00:33:11.873
And now that opportunity needs to be told to the system so that the AI understands okay, this is the person who these kind of people is, what these businesses are interested in, and it will go and automatically adjust the bidding in the background.
00:33:11.873 --> 00:33:14.978
Be able to bring in leads similar to that.
00:33:16.212 --> 00:33:28.620
That's how you increase the lead to opportunity percentage and when you want to reduce the CPL and this is one of the insurance companies in Canada what they have started doing is they started working on the retargeting campaigns.
00:33:28.620 --> 00:33:32.222
So retargeting campaigns whoever comes and lands on the website.
00:33:32.222 --> 00:33:38.878
They started working on retargeting campaigns because of the audience who came to the website did not make the decision.
00:33:38.878 --> 00:33:44.241
It automatically started bringing their leads lead cost quite low.
00:33:44.241 --> 00:33:48.800
And the third aspect is lookalike audiences on Facebook and LinkedIn.
00:33:48.800 --> 00:33:58.221
So you send the lookalike audiences back into LinkedIn and Facebook and automatically you would be able to run campaigns to attract more people like them.
00:33:58.221 --> 00:34:04.002
So that's how the loop is being closed right now, with a lot of feedback back into the ad systems.
00:34:09.693 --> 00:34:14.730
So see if I'm understanding this correctly, then See if I'm understanding this correctly, then.
00:34:14.730 --> 00:34:31.074
So by doing this and getting this sort of rapid feedback, I guess from both systems, you're able to better target where you're spending, because I think the majority of the costs.
00:34:31.074 --> 00:34:40.345
Well, let me clarify, because I'm not super familiar with linkedin or facebook, where the costs are, is it based on, uh, impressions or clicks, or how is that?
00:34:40.345 --> 00:34:43.893
How do you, how is it the cost drivers for those?
00:34:44.875 --> 00:34:50.164
both impressions has, uh, the cost, or the click has the cost.
00:34:50.164 --> 00:34:54.361
But the final measurable cost where you can actually control is the CPL.
00:34:54.361 --> 00:34:57.599
How much are you spending for generating a lead?
00:34:57.599 --> 00:34:58.935
That's the final cost.
00:34:58.935 --> 00:35:07.665
So if you are able to reduce that cost by sending the right kind of feedback back into the system, that's the big win for most of the companies.
00:35:07.665 --> 00:35:12.204
That is one part of the problem one part of the problem.
00:35:13.310 --> 00:35:30.297
I assume, then, that if it's based on both the audience size, the target so your impression numbers, as well as the people, the conversion of those to click-throughs and ultimately to leads, that what you're able to do with this is then to better sort of narrow those windows.
00:35:30.297 --> 00:35:34.517
I don't know how.
00:35:34.517 --> 00:35:47.875
I would call it micro-targeting, but essentially you're targeting a smaller group, right, so by default, you're already going to be reducing the cost if the major driver is the volume of people you target, right, so you can, you're going to get, and you're probably a.
00:35:47.875 --> 00:36:06.844
There's probably a higher propensity of matching, say, say, the lookalikes right, matching people who look alike because you're providing a more detailed set of data and behavior to the system to be able to do matching, especially as algorithms get more sophisticated with AI, et cetera.
00:36:08.831 --> 00:36:10.839
That's exactly what people have been doing, right?
00:36:10.839 --> 00:36:19.722
So people have been setting up campaigns into multiple segments, multiple ways to identify which cities are actually giving more leads, which kind of person is giving more leads.
00:36:19.722 --> 00:36:30.229
Now that everything has become AI-driven, how can you transfer the knowledge of whatever you have been seeing on the CRM into the system is the whole game.
00:36:30.229 --> 00:36:38.338
So now, whatever you said is right, but the targeting options interest-based options are becoming very, very low right now.
00:36:38.338 --> 00:36:40.490
So let's go back to the privacy, right?
00:36:40.490 --> 00:36:47.832
So privacy is now stopping us targeting a very small subset of people where you know they will definitely convert.
00:36:47.832 --> 00:36:50.076
So now that is not there.
00:36:50.076 --> 00:36:55.105
How can you train the AI algorithm in the background with high quality leads?
00:36:55.105 --> 00:37:01.478
So you have to send the data back so AI learns this is a good lead, this is a bad lead.
00:37:01.478 --> 00:37:02.200
This is a good lead.
00:37:02.200 --> 00:37:04.164
This is a high value lead, this is a low value lead.
00:37:04.164 --> 00:37:06.939
So that's the feedback loop, is what we're trying to do.
00:37:08.392 --> 00:37:09.477
Oh, okay, I get it.
00:37:09.477 --> 00:37:12.072
So it's not just like click-throughs but also like downstream.
00:37:12.072 --> 00:37:23.563
This person we targeted in this campaign as it looked like they clicked, they eventually became a lead, but this other person displayed it clicked through, didn't become a lead.
00:37:23.563 --> 00:37:27.147
We send those two back and it gets smart.
00:37:27.147 --> 00:37:43.438
It kind of looks at the differences in those two people that were initially targeted and gets smarter about okay, well, if we make any volume, I can imagine right, like single points probably are not indicative, but if you get enough of a pattern, you can get better.
00:37:43.438 --> 00:37:45.263
Okay, yeah, that makes sense.
00:37:45.390 --> 00:37:47.959
And this all connects back to the privacy right.
00:37:47.959 --> 00:37:52.252
So the third-party cookie is still not going away, but it still goes back to the privacy.
00:37:52.252 --> 00:38:01.463
Because of the privacy loss, the interest-based targeting, the audience-based targeting, everything is now taking away from the customers.
00:38:01.463 --> 00:38:11.834
Now that these are all taking away from the customers, ea has to do the job, which means you have to transfer all the knowledge you have in the CRM or the business back into the ad systems.
00:38:11.834 --> 00:38:13.660
So that's the heavy lifting for you.
00:38:14.371 --> 00:38:15.629
So that's how the whole thing is connected.
00:38:15.629 --> 00:38:42.085
It seems I was going to use the word obvious, but it feels a little bit obvious that if you have first-party data data, that is, specifically things that you're interested in collecting about your audience and the people who interact with your organization that that would be more valuable than third party less directly connected to your business data.
00:38:42.085 --> 00:38:49.237
I mean, it seems like a fairly obvious thing, so I assume that's more or less true.
00:38:49.237 --> 00:38:51.442
Let me ask you this.
00:38:51.442 --> 00:39:03.637
So one last thing Do you think is there a difference in how you would think about this for, say, b2c versus B2B organizations?
00:39:05.034 --> 00:39:20.783
Yeah, B2C needs a lot of feedback, pretty much in real time time, because we are talking about purchases, impulsive purchases so B2C needs much more real-time data for the campaigns to perform day in, day out.
00:39:20.783 --> 00:39:22.175
It's almost like stock.
00:39:22.175 --> 00:39:23.633
That's how I see.
00:39:23.633 --> 00:39:26.081
When I speak with marketers.
00:39:26.081 --> 00:39:30.650
They almost treat the media platforms like stock trading, day in, day out.
00:39:30.650 --> 00:39:34.633
They are always in pressure and they need a lot of this data going in, going out.
00:39:34.633 --> 00:39:36.474
B2b is slightly relaxed.
00:39:36.474 --> 00:39:45.640
It's okay if you could actually feed that system back, maybe a few hours later or a day later, but you still need to work on the whole system.
00:39:45.640 --> 00:39:50.643
So B2B is slightly complex because the journey is not intact.
00:39:50.643 --> 00:39:59.488
People land on the website today, they become a lead after, let's say, 10, 15 days and then they become an opportunity after 60 days, so the sales cycle is pretty long.
00:39:59.488 --> 00:40:09.234
So you need to have strong systems to track everything day in, day out.
00:40:09.234 --> 00:40:14.499
But at the same time, the difference is a huge amount of data in B2C and a little bit less data in B2B, but two different beasts altogether.
00:40:15.000 --> 00:40:24.990
Yeah, okay, that makes sense, and it sounds like it's not necessarily a difference in the data you use, but one.
00:40:24.990 --> 00:40:35.117
It's a difference in, maybe, volume, but also in how and when you use it to optimize what you're doing from a go-to-market standpoint.
00:40:36.571 --> 00:40:37.615
Yeah, that's a good point, right.
00:40:37.615 --> 00:40:41.361
So for B2C the optimization works in a very different way.
00:40:41.361 --> 00:40:54.720
Can I get more high-value customers we call it as high AOV people who can spend, let's say, three times of the regular AOVs and for us in the B2B, can I get a qualified lead?
00:40:54.720 --> 00:40:58.861
So those differences act very majorly.
00:40:58.861 --> 00:41:03.115
So how they optimize the campaigns works in a very different way in both the angles.
00:41:03.115 --> 00:41:10.100
But end of the day the feedback is same between both the systems, but the angle they take is entirely different.
00:41:10.682 --> 00:41:11.085
Got it All right.
00:41:11.085 --> 00:41:13.725
This has been really for me, has been helpful to get out me.
00:41:13.725 --> 00:41:18.442
It's been helpful to get out to speed on what's going on in this world.
00:41:18.442 --> 00:41:21.006
So we covered a lot of ground.
00:41:21.006 --> 00:41:25.053
Is there anything that we didn't cover that you want to make sure that our audience hears about?
00:41:25.073 --> 00:41:39.484
Yeah, I mean, I think in the next one or two years you will see all the ad platforms moving into service tracking and all the platforms would be asking for more data, more first-party data to close the feedback loop.
00:41:39.484 --> 00:41:52.534
So it's a very good time to start on this understanding of 1P, deops, service tracking, capi, enhanced conversions etc.
00:41:52.534 --> 00:41:53.756
And anyone who is interested.
00:41:53.756 --> 00:41:58.920
They can always have a look at chat with us to understand what's going on here, happy to share that knowledge with them.
00:42:00.101 --> 00:42:04.445
Perfect, all right, well, so let's wrap it up there, and maybe this will be.
00:42:04.445 --> 00:42:14.115
You led me into the next question, which is, if folks want to keep up with what you're doing and talk about, or this space in general, what's the best way for them to do that?
00:42:14.115 --> 00:42:15.900
Linkedin.
00:42:16.251 --> 00:42:17.276
LinkedIn would be the best place.
00:42:17.276 --> 00:42:30.439
We are quite active on LinkedIn, so they can find me out with a simple search Vishnu Customer Labs We'd be able to find me, connect me on LinkedIn and happy to share the knowledge as much as possible.
00:42:31.221 --> 00:42:31.702
Fantastic.
00:42:31.702 --> 00:42:34.639
Vishnu, thank you so much for sharing this.
00:42:34.639 --> 00:42:40.917
Got pretty techy, geeky, but I think it was well worth the dive into it.
00:42:40.917 --> 00:42:42.240
So thank you for that.
00:42:42.240 --> 00:42:49.018
As always, thank you to our audience for continuing to support us with your listening and rates and things like that.
00:42:49.018 --> 00:43:00.344
As always, if you have ideas for topics or suggestions for guests or want to be a guest, please reach out to Naomi, mike or me and we will take you up on that.
00:43:00.344 --> 00:43:02.435
Until next time, everybody Bye.
00:43:04.039 --> 00:43:04.300
Thank you.