ABOUT THIS EPISODE
Text us your thoughts on the episode or the show!
What happens when all your digital breadcrumbs—personal emails, professional accounts, device IDs, and physical addresses—get connected into a single identity? Jeremy Katz, SVP of Product Solutions, Identity and Data at Merkle, takes us deep into the fascinating world of identity resolution and first-party data.
Starting with his unconventional path from English major to data analytics leader, Jeremy shares the pivotal moments that shaped his understanding of how organizations can build comprehensive customer views. He breaks down complex concepts like identity graphs, customer data platforms, and the technical challenges of defining seemingly simple terms like "customer." Through real-world examples from his experience implementing enterprise-wide customer data hubs, Jeremy illustrates how companies struggle with and ultimately solve the puzzle of connecting fragmented customer information.
Looking toward the future, Jeremy identifies emerging trends that will reshape how organizations manage and leverage identity—from AI-driven audiences and synthetic data to retail media networks and data collaboration through clean rooms. Whether you're a marketing operations professional trying to implement a CDP or a business leader trying to understand the strategic value of your first-party data, this episode offers crucial insights into one of marketing's most foundational yet complex challenges.
Episode Brought to You By MO Pros
The #1 Community for Marketing Operations Professionals
IN THIS EPISODE
SHOW NOTES 🔗
TRANSCRIPT 🔗
00:00:26.396 --> 00:00:31.995
Hello, welcome to another episode of OpsCast brought to you by MarketingOpscom, powered by all the MoPros out there.
00:00:31.995 --> 00:00:34.522
I'm your host, michael Hartman, flying solo today.
00:00:34.522 --> 00:00:43.837
We'll get Naomi and or Mike back soon, I'm sure, and I know Mike is getting ready for Spring Fling 2025 coming up in a little for a month.
00:00:43.837 --> 00:00:47.472
So if you haven't already done that, go check it out and sign up, if you can go.
00:00:47.472 --> 00:00:50.138
But joining me today is Jeremy Katz.
00:00:50.138 --> 00:00:55.094
Jeremy is currently SVP of Product Solutions, identity and Data at Merkle.
00:00:55.094 --> 00:01:02.962
Jeremy is a data analytics and marketing technology leader with 15 plus years of experience delivering value and building high performing teams.
00:01:02.962 --> 00:01:08.703
He is skilled at solving complex challenges at the intersection of technology, strategy and storytelling.
00:01:08.703 --> 00:01:15.484
His background spans digital marketing leadership and ad tech slash market tech across multiple organizations prior to joining Merkle.
00:01:15.484 --> 00:01:17.075
So, jeremy, thanks for joining me today.
00:01:18.409 --> 00:01:19.615
Thanks for having me Excited to be here.
00:01:20.210 --> 00:01:28.644
Yeah, this is going to be fun and you know, our topic is kind of in the realm of first-party data and things like that that we're going to focus on.
00:01:28.644 --> 00:01:49.786
But before we, before we get into that, I'd love for you to, because you have an interesting uh as I would say is the case for most of our guests, right a interesting career journey, and you recently joined merkle, which is uh, for those who don't know a large consultancy agency, but prior to that, you spent most of your working career in in-house at brands.
00:01:49.786 --> 00:02:15.381
So once you maybe walk through a little more of your career and how you know what led to you joining merkle, and while you're doing that this is something we didn't plan for, but I typically throw this in there like I would love to know if there were any sort of key, pivotal moments, you know, decisions you had to make that led you one way or another, or key people, right, who played an outsized role in your career trajectory.
00:02:16.990 --> 00:02:20.290
Yeah, great, and that could be one of two ways right.
00:02:20.290 --> 00:02:25.276
It could be somebody who I learned from and learn what to emulate, or it could be things I learned to mistakes.
00:02:25.389 --> 00:02:32.080
I learned not to repeat as I got out of my career, things I don't want to do, things I will not do when I'm in that position, kind of thing.
00:02:32.121 --> 00:02:33.890
Exactly so.
00:02:33.890 --> 00:02:39.824
I started my career sort of where many people in data and analytics start as an English and journalism major.
00:02:39.824 --> 00:02:47.742
That's a little bit tongue in cheek, but when I came into the corporate world I was really trying to find where do I add value?
00:02:47.742 --> 00:02:52.698
And I had a background in journalism and English and I ended up starting in communications.
00:02:52.698 --> 00:03:03.640
So communications sort of quickly turned into marketing and I worked in a lot of marketing roles and digital marketing roles early on in my career and a lot of it was getting thrown in the fire.
00:03:04.040 --> 00:03:07.596
So for example, hey, do you want to learn how to run an email program?
00:03:07.596 --> 00:03:09.502
I'm like sure, I can't code HTML.
00:03:09.502 --> 00:03:11.056
I don't know how to do any of that, but I'll learn.
00:03:11.056 --> 00:03:14.158
So I got thrown in the mix a lot early on.
00:03:14.158 --> 00:03:20.717
And yeah, I mean you talk about pivotal moments my first job my boss quit two weeks in.
00:03:20.717 --> 00:03:33.508
So all of a sudden I was leading, you know, marketing for North America at UTC United Technologies in Connecticut, for North America at UTC United Technologies in Connecticut, and doing PR, marketing, all kinds of stuff that I was not really ready for.
00:03:33.508 --> 00:03:36.157
But I don't know if you're ready for a lot of things early in your career.
00:03:36.157 --> 00:03:36.919
You got to learn to go.
00:03:36.919 --> 00:03:44.723
So learning this marketing as a practitioner and marketing automation.
00:03:44.723 --> 00:03:48.310
I'm not sure we even called it back then, but a lot of it was hey, you got to figure out.
00:03:48.471 --> 00:03:49.816
It was e-marketing when I was doing it.
00:03:50.211 --> 00:03:54.861
Yeah, E-marketing website marketing Right A lot of terms that are no longer being used.
00:03:55.871 --> 00:04:14.979
I was able to kind of, like I say, hop from channel to channel and really kind of start putting a picture together of how these things worked in harmony and you know, eventually I ended up moving into the exciting world of insurance, which I actually say is very interesting when you get into it, but from the outside it can be a little dry.
00:04:14.979 --> 00:04:22.723
And when I did that, I eventually moved into sort of more of a support role, I would call it at the center of the organization.
00:04:23.350 --> 00:04:27.332
So now you know, all my customers were marketers, like I, had been up to that point.
00:04:27.332 --> 00:04:33.795
So now you know, all my customers were marketers, like I, had been up to that point, and we had basically built out sort of a centralized MarTech function at that time.
00:04:33.795 --> 00:04:35.658
And but I kind of stumbled into that.
00:04:35.658 --> 00:04:39.679
I would say I'm always been interested in the technology aspects and kind of how things work.
00:04:39.679 --> 00:04:45.923
And it was back in the day when the MarTech conference there was one in Boston used to be in person.
00:04:46.303 --> 00:04:48.384
They're all digital now, but back then it was in person.
00:04:48.784 --> 00:04:49.605
Well, not all of them.
00:04:49.605 --> 00:04:51.486
I mean Muff's Blues is not.
00:04:51.506 --> 00:04:51.947
That's right.
00:04:51.947 --> 00:04:52.407
There you go.
00:04:52.407 --> 00:04:59.264
But I had gone to that conference and just pulled together some slides and I came back to my my CMO.
00:04:59.264 --> 00:05:02.596
She wanted to know what what I learned and I said, well, there's a thing called a CDP.
00:05:02.596 --> 00:05:11.495
I'm not sure if you've heard about it, but it's kind of a big deal.
00:05:11.495 --> 00:05:13.783
It's growing and eventually that led me into the role to build a MarTech team.
00:05:13.783 --> 00:05:15.509
You know, on board a CDP in the organization and you know.
00:05:15.528 --> 00:05:24.360
So a lot of my career has been luck and timing, but always being ready, always staying hungry and learning and trying new things and ultimately I think that's kind of what led me to Merkle.
00:05:24.360 --> 00:05:44.994
You know I've gone to date on the analytics, you know, sort of by accident, not by accident, but you know, as my path has taken me and you know I decided to kind of challenge, take on a new challenge, sort of reinvent myself and sit in a different perspective yet again, which is now I get to work with, you know, companies and clients across many different verticals and I'm learning a ton again.
00:05:44.994 --> 00:05:50.605
I feel like I'm almost back at the beginning of my career in some ways with the amount of learning that's happening.
00:05:50.605 --> 00:06:00.823
But yeah, I'm excited at what I'm doing and I feel like if you're not learning and if you're sort of not progressing forward, you're falling behind, especially in this climate today.
00:06:00.823 --> 00:06:03.239
So yeah, that's kind of a quick snapshot.
00:06:03.850 --> 00:06:08.809
So you mentioned you did communications and then into marketing, and so I'm always curious.
00:06:08.809 --> 00:06:14.023
So I have my idea of, like, when I think about communications versus marketing, what it is.
00:06:14.023 --> 00:06:16.177
But how do you differentiate those?
00:06:18.470 --> 00:06:23.398
Well, I have a very direct take of how I got into, I would say, communications, which was, you know.
00:06:23.418 --> 00:06:29.966
I used to write articles for newspapers back when they were printed on paper and delivered on paper to write articles for newspapers.
00:06:29.986 --> 00:06:42.918
Back when they were printed on paper and delivered on paper, and I remember creating articles 600 word articles, investigative sort of journalism in nature and I remember I got like $100 an article or something like that and they asked me would you want to do like work for a business profile?
00:06:42.918 --> 00:06:52.923
I think I got paid like 3x the amount for the business profile and I was like, oh okay, this is a way to take my journalism skills and maybe apply it for companies.
00:06:52.923 --> 00:07:05.515
And so my first job, I actually brought a portfolio of my articles in that I had written at the time and they're like oh well, you can write for our internal company blog and actually created an internal social media site at the time.
00:07:05.515 --> 00:07:09.173
So I was kind of like taking the same skillset a social media site at the time.
00:07:09.173 --> 00:07:15.153
So I was kind of like taking the same skill set and I would call that more like internal comms, which led into pr and then supporting our, our leadership team too.
00:07:15.173 --> 00:07:17.799
So that's kind of how I think about the communications aspect.
00:07:17.860 --> 00:07:19.812
But okay, that's kind of how I do too.
00:07:19.812 --> 00:07:39.582
I just I was like it's like internal communications, pr, ir, executive, executive presentations and things like that, right, okay, yeah, yeah, yeah, yeah, that's as opposed to marketing, which is more customer like, directly customer focused in general, right, whether it's demand gen or you're doing sales enablement or product marketing, yeah, okay, interesting.
00:07:39.582 --> 00:07:52.635
So my guess is you're the guy who, when you're an English major, that you like diagramming sentences because you know you like the structure, oh, I got a nerd out on diagramming sentences.
00:07:52.735 --> 00:07:53.298
I still would.
00:07:53.298 --> 00:07:54.883
I don't do it anymore, but I yeah.
00:07:54.883 --> 00:07:55.969
I love diagramming sentences.
00:07:55.969 --> 00:08:00.701
I like breaking down things to their essence and putting them together and seeing how they work.
00:08:01.912 --> 00:08:23.499
So it's so funny because I'm the engineer here in this call and I'm a data guy and I nearly failed out of seventh grade english because I just like this diagramic sense thing is the stupidest thing I've ever heard of and I, like I, I did the bare minimum, like I, literally I think it's the worst grade I've had all my entire life and I really was very close to failing that class.
00:08:23.759 --> 00:08:31.457
So, um, so irony there, you know, the data nerd, the guy who likes structure, is the one who didn't want to diagram sentences.
00:08:31.457 --> 00:08:52.333
All right, so you mentioned that you've been doing a lot with data and analytics and recently in your career you've been spending time with first party data, identity resolution and you mentioned CDPs, identity resolution and you mentioned CDPs.
00:08:52.333 --> 00:08:54.865
So, yeah, we've had guests on and have talked about CDPs and we've had guests on and talked about first party data.
00:08:54.865 --> 00:08:57.115
I don't think we've talked to anyone about identity resolution.
00:08:57.115 --> 00:09:10.718
But maybe what we start with, what are your working definitions of those and if there's any other terms that are relevant for our conversation, like what's the working definition of those and how are they related and different?
00:09:11.901 --> 00:09:17.435
Sure, yeah, and I think you know first party data is probably one of the easier places to start.
00:09:17.435 --> 00:09:23.098
You know it's data that you're collecting, you own, and it could be current customers.
00:09:23.098 --> 00:09:27.193
It could be you know prospects who fill out a form on your site but don't convert.
00:09:27.193 --> 00:09:29.942
But it's data that you've collected as an organization.
00:09:29.942 --> 00:09:46.081
You have the rights to that data, you own it and you can leverage that for acquisition, for cross-sell, up-sell, et cetera, versus like a second party where it's a partner sharing their data with you, or a third party where maybe you're buying or renting data that you can use to decorate.
00:09:46.081 --> 00:09:49.360
We call it that first party data Decorate okay.
00:09:49.970 --> 00:09:50.731
Which you know.
00:09:50.731 --> 00:09:53.701
It's an old-school term, maybe a little bit, but I still like the term decorate.
00:09:53.701 --> 00:09:55.096
It makes it sound fancy, I guess.
00:09:55.096 --> 00:10:03.062
But ID resolution to me is there's all these pieces of information around who you are.
00:10:03.062 --> 00:10:04.514
I'll use myself as an example.
00:10:04.895 --> 00:10:05.619
I live in Chicago.
00:10:05.619 --> 00:10:10.393
I live in an apartment building, so I have an address associated with that building.
00:10:10.393 --> 00:10:15.310
I've got my name and my first name and last name on my postal box downstairs.
00:10:15.310 --> 00:10:23.636
I've got an email address that I use, a Gmail address, and I've got some Yahoo stuff I use for fancy football, old email addresses.
00:10:23.636 --> 00:10:26.262
I have all these pieces of information.
00:10:26.262 --> 00:10:30.019
Call it terrestrially me as a person that lives in an address.
00:10:30.019 --> 00:10:35.040
And then I go on the Internet at my house and I have an IP address.
00:10:35.040 --> 00:10:42.863
You know the user agent pings against my device and knows my device ID, all these digital fragments and pieces of information out there.
00:10:43.730 --> 00:11:05.543
And to me, the resolution or the resolving piece is understanding that all that belongs to Jeremy Katz and bring that down to a single identity Right, and usually that's through an identity graph which is looking at the relationship between all those things and I would say, like the distance between those points, the stronger they are, it's a shorter distance.
00:11:05.543 --> 00:11:12.156
So it's funny because, like, my email address is the same for the last 20 plus years, the one I use, you know, every day.
00:11:12.156 --> 00:11:21.689
Sure, my address has changed three times in the last five years, so you know it depends on which piece of information is updated and how frequently it's updated.
00:11:21.689 --> 00:11:31.976
But understanding who people are is really the foundation of identity resolution and usually you're engaging, you know, an outside organization to do that, and that's sort of what we do in my current role.
00:11:31.976 --> 00:11:34.497
There's a number of companies that do parts of that.
00:11:34.497 --> 00:11:39.377
So now is that is that so?
00:11:39.538 --> 00:11:41.565
yeah, I think we talked about this like my.
00:11:41.565 --> 00:11:46.773
Where I cut my teeth in the marketing domain was database marketing and I was building.
00:11:46.773 --> 00:11:53.841
I built a 50 million household database and the whole concept of householding was new to me at the time.
00:11:53.841 --> 00:11:57.589
It was mostly a consumer-oriented kind of idea.
00:11:57.589 --> 00:12:03.995
But is that related to this, or is it just a separate thing altogether, or how does that fit in?
00:12:04.937 --> 00:12:05.639
That's a good question.
00:12:05.639 --> 00:12:12.922
I think entity resolution is the broader, you know domain identity resolutions contained within the entity.
00:12:12.981 --> 00:12:21.635
So we think about grains and I'm trying to get too nerdy too quickly here but grains of data.
00:12:21.635 --> 00:12:23.986
Right, like me, as an individual, I roll up to a household and it's even more complex than that.
00:12:23.986 --> 00:12:34.584
Right, I mentioned living in an apartment building, so we have, like, the family household, the TV household that I have inside my walls here, and then I live in a unit, a physical unit.
00:12:34.584 --> 00:12:42.077
Right, all of that is a grain that goes up from me as an individual.
00:12:42.077 --> 00:12:43.020
And it's the same on the B2B side.
00:12:43.020 --> 00:12:47.913
Right, like you work at a company, that's an entity, you have a role within that company and you probably have a business profile.
00:12:47.913 --> 00:12:53.985
You know that's the stuff that your business email, you're going on LinkedIn, your LinkedIn account, you know, has business content on it.
00:12:54.049 --> 00:12:56.799
So it's like those different grains.
00:12:56.799 --> 00:13:01.962
I think about them as, like the whole the old school, you know, grandparent, parent, child relationship.
00:13:01.962 --> 00:13:05.016
You know when you think about it and know it could be one to many.
00:13:05.016 --> 00:13:19.004
It could be, you know one to one, but those grains are kind of what we talk about in in that entity resolution space interesting, and my guess is, some of this gets out into the uh for lack of better term dark web.
00:13:19.024 --> 00:13:37.279
Because it's funny, because, like literally may have been today, maybe today or yesterday, I got an email that was sent to four like one email, but was sent to four different email addresses that are all linked to me, two of which I don't really use.
00:13:37.279 --> 00:13:47.660
I think one was from my you know, my, my right I graduated college from, and one was like an old hotmail account that I don't really use anymore and it was weird.
00:13:47.660 --> 00:13:48.673
I was like what did like?
00:13:48.673 --> 00:13:49.507
So I was like an old hotmail account that I don't really use anymore and it was weird.
00:13:49.507 --> 00:13:49.658
I was like what did?
00:13:49.658 --> 00:13:49.780
So?
00:13:49.780 --> 00:14:02.139
I was like, oh, somebody somehow found all this stuff about me and I probably deleted it because I was like this is probably not somebody I want to be dealing with, that they're going out there and scraping stuff that's out there, like that.
00:14:02.139 --> 00:14:08.192
So okay, so that all makes sense.
00:14:08.192 --> 00:14:13.593
I see the connection to my database marketing days when I was building households.
00:14:13.593 --> 00:14:14.554
I get the.
00:14:15.314 --> 00:14:30.303
I actually think the complexities for B2B are more significant because of the complexity one bit, which is, you know, not only are you part of an organization but maybe you're part of a specific business unit or a location, right.
00:14:30.303 --> 00:14:43.553
And if they have multiple locations or multiple business units I even worked for one company where one person could be we had sort of separate this goes down to CRM, right.
00:14:43.553 --> 00:14:50.399
We had separate accounts for different almost like not quite team level, but kind of like team levels for specific things.
00:14:50.399 --> 00:14:58.670
We sell this product to this group and this other product to this other group, and sometimes somebody could be in more than one place so we'd have like intentional duplicates too.
00:14:58.670 --> 00:15:02.279
So you're dealing with all that kind of noise.
00:15:03.682 --> 00:15:11.822
So maybe before we get into what you're doing now, but like when you were in-house, do you have any project?
00:15:11.822 --> 00:15:20.021
Like, give me an example of how this concept of these different things and how did that get happen?
00:15:20.021 --> 00:15:21.124
What were some of the big challenges?
00:15:21.124 --> 00:15:22.164
And then, how was that?
00:15:22.164 --> 00:15:26.794
I guess this is a technology solution at the end of the day, right, just bringing this stuff together.
00:15:26.794 --> 00:15:30.159
How did that get leveraged to help the business?
00:15:31.769 --> 00:15:36.858
Yeah, and I'll try to tie it back to the CDP example too, because I think that's where I first really got deep into this.
00:15:36.858 --> 00:15:46.035
You know we actually created you know for all intents and purposes a customer database, you know to start here, and it was called Customer Hub.
00:15:46.035 --> 00:15:54.482
That Customer Hub, if you will, had sort of multiple lines of business, all the information we had on our customers brought into one physical.
00:15:54.482 --> 00:15:58.778
At the time it was an on-premise database, one place.
00:15:58.778 --> 00:16:05.280
Now, when you do that, even inside an organization, you may have a customer that sits in two business lines.
00:16:05.280 --> 00:16:07.533
To your point, that may have bought two different products.
00:16:08.235 --> 00:16:15.318
So we didn't even try to resolve it at first, we just brought it all together and we said, okay, you know, Michael Hartman has three email addresses.
00:16:15.318 --> 00:16:16.261
What's the best one to use?
00:16:16.261 --> 00:16:20.221
If he's given us three email addresses, what's the one that he usually transacts with us on?
00:16:20.221 --> 00:16:30.871
And so I think that was the first foray was kind of building an internal asset that we could use for customer information across our organization.
00:16:30.871 --> 00:16:36.793
The uses of that are relatively straightforward, right, Like I want to send you mail or I want to send you an email.
00:16:37.576 --> 00:16:44.290
You shouldn't have the experience you had where you get, you know, three emails sent to your different email addresses, as if you're a different person in each one.
00:16:44.290 --> 00:16:47.852
So I think there were some really basic use cases to start.
00:16:47.852 --> 00:16:52.956
And then when you bring a CDP on top of that, it's like how do you ingest all of that?
00:16:52.956 --> 00:16:58.839
And some light resolution happens in a CDP it's all your first party data, but then that goes out to multiple channels.
00:16:58.839 --> 00:17:04.103
So that might go out to email site personalization etc.
00:17:04.103 --> 00:17:11.307
And you're able to know it's one person you're orchestrating from a central place and then distributing that out across multiple channels.
00:17:11.307 --> 00:17:15.339
So I know CDPs have evolved quite a bit since the early days.
00:17:15.339 --> 00:17:18.789
Almost everything is called a CDP now and it's very different.
00:17:19.952 --> 00:17:28.567
I was trying not to laugh when you said CDPs, you know old school, because they haven't really been around that long, right yeah, in the grand scheme of things.
00:17:28.567 --> 00:17:30.506
Five, maybe 10 years.
00:17:31.019 --> 00:17:34.048
Yeah, it feels like in the digital marketing data tech space.
00:17:34.048 --> 00:17:35.652
That's like somehow way longer.
00:17:39.622 --> 00:17:43.612
But being able to tie those things together really helped me understand all the components.
00:17:43.612 --> 00:17:50.006
And then the question was all right, you've got all your customer data together, you've got a CDP, you're able to market to people.
00:17:50.006 --> 00:17:51.843
What about your website?
00:17:51.843 --> 00:17:55.712
What about all the different experiences happening in your website?
00:17:55.712 --> 00:18:06.941
And we at the time I think we had like four or five different portals for different parts of the business with different logins, and I mean just making sense of that is a relatively complex challenge.
00:18:06.941 --> 00:18:12.108
But then, at the end of the day, you've got data coming in and you've got to figure out how to make it all connect.
00:18:12.108 --> 00:18:21.741
And I think that's ultimately where it started going deeper into identity resolution and digital signals and like bringing that all back to the same profile right right, um, and it's a.
00:18:22.222 --> 00:18:23.886
It's a never-ending battle.
00:18:23.886 --> 00:18:26.571
Right to get that right sure, okay.
00:18:26.612 --> 00:18:30.887
So I have a couple questions.
00:18:30.887 --> 00:18:53.233
So, on the like you brought all this stuff back together in CDP and you mentioned pushing it out, I think you said pushing it I'm paraphrasing pushing it back out to some of the maybe frontline systems, right, whether it's CRM, Was it being used to maybe inform transactional stuff?
00:18:53.233 --> 00:19:02.807
So, hey, I'm a salesperson, I can see this activity of key people in my account and you have that as something that you inform, like if I have to make a call or send an email.
00:19:02.807 --> 00:19:04.325
Was it being used that way?
00:19:04.325 --> 00:19:17.625
Or was it being used for, say, website personalization or targeting with social based on whether it's lookalikes or whatever like how was it?
00:19:17.625 --> 00:19:21.347
How was that used once that you did that kind of brought everything together?
00:19:22.878 --> 00:19:28.032
Yeah, and that was the fun part for me being a marketer and knowing what everyone wanted to do across the Oregon.
00:19:28.032 --> 00:19:31.329
I think I had 180 use cases to start.
00:19:31.329 --> 00:19:35.204
They had to prioritize and you know, knock some off that list.
00:19:35.444 --> 00:19:44.649
So one of the cool things we did was we used a different service for identifying people in the phone centers.
00:19:44.649 --> 00:19:49.488
So when somebody calls in, it would pop, you know the phone number and get their profile started.
00:19:49.488 --> 00:19:51.261
So when you greet somebody you know who they are.
00:19:51.261 --> 00:20:05.450
So we were really able to take that to a different level, improve the match rates and improve the ability for our sales reps to be able to know who was calling in, in in on the service side too, and then also kind of pop a little profile of that customer.
00:20:05.450 --> 00:20:09.530
What's their most recent four or five interactions, you know.
00:20:09.530 --> 00:20:11.281
But there was a lot of things we did too.
00:20:11.281 --> 00:20:14.645
We were able to help with our survey programs for NPS programs.
00:20:15.126 --> 00:20:15.366
Okay.
00:20:15.386 --> 00:20:18.391
Just by kind of like bringing all that data together for the deployment.
00:20:18.490 --> 00:20:27.956
So for our listeners and watchers who NPS, if you're not familiar, net promoter score right so.
00:20:29.000 --> 00:20:29.805
Yeah, A lot of acronyms in this space.
00:20:29.805 --> 00:20:30.670
Thanks for spelling that out for me.
00:20:30.670 --> 00:20:40.795
And then you know, COVID is actually a really good example of, you know, having to send an email out to your entire customer population a couple of times, especially in the insurance space.
00:20:40.795 --> 00:20:43.605
You know, we actually people weren't driving All of a sudden.
00:20:43.605 --> 00:20:46.051
One day people are driving and the next day no one's driving.
00:20:46.051 --> 00:20:50.827
So a lot of companies, like ours at the time, gave back premium at that time.
00:20:51.368 --> 00:20:57.750
So we had to send a lot of communications to customers and it was timely because we had built this capability.
00:20:57.750 --> 00:21:09.519
We were able to be very precise in our mailings, understand who was getting emails, who was, you know, kind of more traditional paper based and be precise in how we mailed and communicated with our entire customer population.
00:21:09.519 --> 00:21:19.372
You're talking, you know, millions and millions of customers and relatively large company and it was wasn't seamless, wasn't perfect, but it was pretty smooth, based on what we had built.
00:21:19.372 --> 00:21:20.723
So just basic communication.
00:21:21.205 --> 00:21:21.928
Yeah, and it was also.
00:21:21.928 --> 00:21:39.059
So you're kind of hitting on the next part of follow up I had, which is I've been at different places, only one that I did tried to do the exercise of defining the characteristics of this is a customer or this is a person.
00:21:39.059 --> 00:21:40.103
What is the minimum?
00:21:40.103 --> 00:21:41.686
How do we define that?
00:21:41.686 --> 00:21:47.903
Did you go through that kind of exercise of having clear definitions about that?
00:21:47.903 --> 00:21:55.423
I'm just curious A how long did that take and how did you?
00:21:55.423 --> 00:22:02.104
Because I'm going to guess, if you get enough people in the room, you get 10 people and you're going to get 10 different opinions about what is a customer.
00:22:02.987 --> 00:22:03.187
Yes.
00:22:04.383 --> 00:22:05.046
I joke all the time.
00:22:05.046 --> 00:22:09.807
The hardest thing as a marketing ops person is when somebody comes to you and says we need to send an email to all our customers.
00:22:09.807 --> 00:22:13.506
Yeah, what do you mean?
00:22:14.420 --> 00:22:16.969
It seems like that should be an easier answer than it is.
00:22:18.443 --> 00:22:21.112
It absolutely sounds like it should be a no-brainer, but it is not.
00:22:21.819 --> 00:22:21.980
Yeah.
00:22:21.980 --> 00:22:24.709
So I guess I'll stick with the because it's fresh in my mind.
00:22:24.709 --> 00:22:28.766
I'll stick with the insurance example Independent insurance agents.
00:22:28.766 --> 00:22:30.127
Are those our customers.
00:22:30.127 --> 00:22:38.726
The actual insureds that we support are those customers Non-customers who are engaged in an accident with our customers claimants.
00:22:39.980 --> 00:22:56.147
There's roles for each of these things and so I think, like I tried to expand the definition of a customer to at least include anybody who is a current we call them enforced customer, has a current policy with us, as well as anybody who is a current we call them enforced customer, has a current policy with us, as well as anybody who we've interacted with.
00:22:56.588 --> 00:23:11.187
You know, in the last we actually pulled 10 years of data in to start that we have information on they're either a former customer they quoted with us, you know they had some interaction with us and we had them as a core customer, and then we kind of had the agents as a separate group.
00:23:11.187 --> 00:23:28.963
But think about all the attributes and interactions and roles you're now attaching to all those profiles, and that's where I think like it's less, it's less just science, there's some art to it and getting all the business people in a room and making sure they they can, you know, have their input into how you define those things.
00:23:28.963 --> 00:23:32.011
But ultimately, ultimately you got to keep it simple, right, it's got to still be usable.
00:23:32.011 --> 00:23:37.231
So you can't have, you know, 55 versions of, maybe a data element.
00:23:37.231 --> 00:23:40.990
You've got to try to keep it somewhat grouped logically, so it's usable.
00:23:41.560 --> 00:23:44.529
So in my experience, I agree with you that we should keep it simple.
00:23:44.529 --> 00:23:51.647
But in my experience, what tends to happen is people keep thinking of I don't even know that I would call them outlier cases.
00:23:51.647 --> 00:24:04.221
But take a small example right, one of your customers over the lifetime of them being there, like at any point in time they may be, you know someone who's in the process of engaging with you.
00:24:04.221 --> 00:24:06.994
They're not currently a paying customer, what you call enforced, right?
00:24:06.994 --> 00:24:13.605
Uh, then they become that, uh, they end up being a claimant in another case, like with someone else who's an enforced guest.
00:24:13.605 --> 00:24:20.625
So it could easily go like oh well, this person, at any point in time or in a given situation, has a different status.
00:24:20.625 --> 00:24:24.379
Like, how do you, did you deal with that, did you?
00:24:24.379 --> 00:24:36.256
Oh, yeah, yeah, okay, how did you go about getting to resolution on those kinds of seemingly simple but challenging questions?
00:24:37.860 --> 00:24:42.091
Yeah, we actually had some really smart people on the data science side to who helped me.
00:24:42.091 --> 00:24:52.153
In fact, I think we actually got a patent on one of the data models that we built out and it was really it kind of brought together time time as a constant, like place and time.
00:24:52.153 --> 00:24:55.328
The individual, who they are, doesn't change as much.
00:24:55.328 --> 00:24:58.769
Right, the attributes around them change, but who that person is doesn't change.
00:24:58.769 --> 00:25:04.859
And then some of the roles and the kind of like you know I won't get into all the detail, but the aspects around the data model.
00:25:04.859 --> 00:25:22.812
So you may be a customer at one point, a prospect, at another point, a claimant, you could be an agent, you could be an independent agent selling our product and the customer, and so the ability to sort of build a flexible data model that reflected those changes over time is also important.
00:25:22.812 --> 00:25:28.060
And now there's a whole practice around customer journey analytics and understanding the customer journey.
00:25:28.521 --> 00:25:31.047
This is in the early stages of when that was kind of picking up.
00:25:31.047 --> 00:25:39.649
So that's kind of what led me into analytics is they're like all right now we want you to help build out that journey analytics perspective for our claims and operations area.
00:25:39.649 --> 00:25:44.288
So yeah, we dealt with that quite a bit and I think it's not linear, right, it could change.
00:25:44.288 --> 00:25:59.066
It goes back and forth in between those situations and, to be honest, to this day I still remember the most valuable customer segment in our prospecting was always former customers, because they've seen you, they've engaged with you, they know you, so the response rates are always higher.
00:25:59.066 --> 00:26:08.701
So, very interesting in how you think about you know the loop, as opposed to like a linear you know flow of how people interact with you.
00:26:09.321 --> 00:26:21.748
Yeah, and I wanted to drill down into those because I suspect you know, given what I know about the profile of our listeners and our audience, is there's going to be enough people who have probably never gone through this.
00:26:21.748 --> 00:26:31.106
And would you know if they were said, hey, let's go, we want to bring in a CDP or we want to build a data warehouse or data lake that brings all our customer data together?
00:26:31.106 --> 00:26:43.064
It will be more complicated than you think it will be because of all these things that will come up.
00:26:43.064 --> 00:27:04.807
Customer is a great example of the kind of word that I talk about a lot with people, where, if you say that word and you're in a room of people like everyone's hearing it from their own context and they're going to have an idea of what that means and they may overlap with the person next to them or the other people in the room, but there's probably not a hundred percent overlap.
00:27:06.711 --> 00:27:30.468
And, yeah, you get that into a broader context of you know, just within marketing, you probably don't have it If you go marketing and customer support or we go marketing and sales, and it starts to get really challenging to, to to get to a decision on that, and so I'm with you.
00:27:30.468 --> 00:27:51.070
You want to keep it simple, which probably also affects the ability of whatever technology you're using to handle volume and things like that, and then also affects usability, but also you want it to be as complete as you need for the use cases, like it's not a small task.
00:27:51.070 --> 00:27:53.427
So appreciate you sharing that.
00:27:54.620 --> 00:27:56.807
Yeah, if I could opine for one second on CDP.
00:27:56.827 --> 00:27:57.730
Please do, I just did.
00:27:58.421 --> 00:27:59.064
A lot of them.
00:27:59.064 --> 00:28:07.250
It's like just load your data in and magically it'll all be cleaned up and you'll have perfect profiles, and that's something that I've learned through the pain of going through this.
00:28:07.250 --> 00:28:09.307
It's not that easy.
00:28:09.307 --> 00:28:11.500
You have to do some prep and get your data in order.
00:28:11.500 --> 00:28:16.564
When you bring a tool like that and that goes for any tool right, that can go for a marketing automation platform too.
00:28:16.564 --> 00:28:25.863
There's upfront work that'll make your life a lot easier, and it's not the fun work sometimes, but it's the work that is going to help you be successful at the next stage.
00:28:26.965 --> 00:28:27.607
Well, I think this is.
00:28:27.607 --> 00:28:29.873
It falls into the category to some degree.
00:28:29.873 --> 00:29:02.475
It falls into the category of why I tell people, like, don't go down the path of going from no reporting to say we're going to build a dashboard because you're going to and also are issues, and then you can go back and address them right, whether it's a process issue or a system issue or a people issue, and usually some combination.
00:29:02.475 --> 00:29:10.144
So like, don't, like, I want to make sure what I didn't hear from you is don't do the cdp thing until you get your data in order, because if you do that, you'll never do a cdp thing, which is fine.
00:29:10.686 --> 00:29:11.829
But take a step.
00:29:12.221 --> 00:29:23.591
That's how you learn yeah, yeah, yeah, no, I'm a big believer like, expose this stuff and it brings light on it, and then you can make improvements and it becomes a bit of a uh, a fly.
00:29:23.591 --> 00:29:25.204
We can get a flywheel effect right.
00:29:25.204 --> 00:29:27.836
You find a problem, you solve the problem, it gets better.
00:29:27.836 --> 00:29:29.807
You find the next problem, you solve it, you get, you know, and so I'm a big believer in that.
00:29:29.807 --> 00:29:30.631
And you know the problem, it gets better.
00:29:30.631 --> 00:29:32.519
You find the next problem, you solve it, you get, you know, and so I'm a big believer in that.
00:29:32.519 --> 00:29:35.990
And you know, reporting CDP has probably fallen into a similar category.
00:29:36.920 --> 00:30:02.233
Okay, so I want to get back into this identity resolution stuff, because something that you and I talked about as we were kind of getting ready for this is that you've now started work I don't know, I can't remember if it was at Merkle or where it was before, where you were, um, you were actually connecting professional profiles and personal profiles together about a person and somehow leveraging that.
00:30:02.233 --> 00:30:05.345
So a number of questions like hey, did I understand that right?
00:30:05.345 --> 00:30:05.866
And B?
00:30:05.866 --> 00:30:09.367
Um, how does that generally work?
00:30:09.367 --> 00:30:19.389
And then C, are there any implications in terms of privacy or you know that kind of concerns there that you have to deal with when you're doing that.
00:30:21.520 --> 00:30:24.529
Yeah, I'll try to take the first two and then the privacy one.
00:30:24.529 --> 00:30:31.006
We could go, we could talk a lot about that, because there's obviously that's a that's a challenge in a lot of components of this, even on the consumer side as well.
00:30:31.006 --> 00:30:46.461
You know, and again I I mentioned earlier I think about how I I got exposed to a lot of things very early on in my career and, like the example I've already given, you know, we had small business, medium businesses, consumers, sort of all in the in the insurance space.
00:30:46.461 --> 00:30:55.589
We had all those different categories, um, so it was something that we had to, I had to understand relatively early, and it's could be different partners you work with too.
00:30:55.589 --> 00:31:03.634
So it's not always the case that you're going to work with somebody who's really good at the identity resolution for a consumer and data for a consumer.
00:31:03.634 --> 00:31:11.516
You may have to work with a different company who's really good at the business side, right, and oftentimes they approach it from the other direction.
00:31:11.516 --> 00:31:15.096
So when I think of a consumer-based identity resolution, you're starting with people.
00:31:15.096 --> 00:31:20.397
You're starting with their personal profile, like I mentioned earlier, all the information about me as an individual.
00:31:20.397 --> 00:31:26.417
On the business side, you get a lot of companies that are really good at understanding the company dimension first.
00:31:26.417 --> 00:31:27.730
So they kind of go in inverse.
00:31:27.730 --> 00:31:42.973
They go from what's the industry SIC code and what is the types of things they sell and they kind of start with the company and then they ladder down to divisions and organizations at the top, decision makers, and they kind of go that way down to the individual.
00:31:44.356 --> 00:31:52.209
I think the other thing I would just mention is it's not that hard if you think about a business email like you don't have to be that smart to think about.
00:31:52.209 --> 00:31:54.677
If I know the format of a business email like you don't have to be that smart to think about.
00:31:54.677 --> 00:31:56.704
If I know the format of a business email, is it first name, dot, last name at company dot com.
00:31:56.704 --> 00:32:05.058
It's relatively easy, probably for a lot of people that are in the more in the sales space or B2B space, to understand how to reach individuals in that company.
00:32:05.058 --> 00:32:10.738
The challenge is it's so ethereal like your role could change your company changes.
00:32:10.738 --> 00:32:16.126
Role could change your company changes.
00:32:16.126 --> 00:32:22.206
So like the durability of that business email is not as powerful as like your physical address or your personal email, but it's the linkages that happen across both.
00:32:22.247 --> 00:32:28.307
I think LinkedIn is a great place you know as an example right, most people are on LinkedIn.
00:32:28.307 --> 00:32:32.305
They have their personal email address is how they sign up for the platform.
00:32:32.305 --> 00:32:35.471
But they have their company and they have information about their.
00:32:35.471 --> 00:32:39.759
You know their job, you know, probably, history of their jobs, you know in that profile.
00:32:39.759 --> 00:32:50.681
So I'm just going to use that example and, you know, think about how, how LinkedIn is also marketing right to individuals and enabling advertisers to reach those individuals on platform.
00:32:50.681 --> 00:32:54.075
You know it's it's really based on those business characteristics.
00:32:54.075 --> 00:32:57.451
Once they go off platform, you're still marketing to people.
00:32:58.153 --> 00:33:04.916
So that linkage of like, say, email, your login information that they're able to aggregate up and that gets to the privacy piece.
00:33:04.916 --> 00:33:10.388
Right, usually it's done in the aggregated way, it's not in an individual way to build audience pools for targeting.
00:33:10.388 --> 00:33:15.447
And that connectivity is something that my current company does really well.
00:33:15.447 --> 00:33:20.328
It's an interesting kind of approach, which is we have all this depth of knowledge on people.
00:33:20.328 --> 00:33:27.613
We've also built this secondary, you know, kind of view of businesses and business information and now we're trying to bridge that gap.
00:33:27.613 --> 00:33:34.248
So we've connected on those you know elements, right, those identification elements like a personal email and business email.
00:33:34.268 --> 00:33:44.866
But at the end of the day, it's about reaching those people with advertising or with messaging or with experiences, so it can get relatively complex based on the information you have.
00:33:44.866 --> 00:33:46.591
You could also have phone numbers.
00:33:46.591 --> 00:33:50.690
You could have business addresses, right, but it's a similar concept.
00:33:50.690 --> 00:33:53.718
It's just you're going to get a smaller pool to start with.
00:33:53.718 --> 00:34:07.952
You're going to actually get a drop from the personal information into the business side, so your quality is going to be hopefully better, but your audience size is going to shrink and part of that is because of the nature of the identifiers.
00:34:07.952 --> 00:34:10.409
They're not as durable as the personal side.
00:34:10.409 --> 00:34:13.356
But I started touching on it a little bit.
00:34:13.445 --> 00:34:36.528
I think you know privacy and security there's, there's concerns that you know are whether you're in the U S, outside the U S, that that very state by state in the U S and certainly you know, in the EU is probably the only place I can think of that has a relatively large number of companies under a single framework with GDPR, but a lot of that is focused on digital.
00:34:37.209 --> 00:34:43.100
You know, if you think about like I'm old enough to remember the phone book, you would get a phone book dropped in your driveway.
00:34:43.100 --> 00:34:45.168
It's got everyone's address and everyone's phone number.
00:34:45.168 --> 00:34:56.192
Like the nature of how terrestrial data has has evolved over the last 25 years, 30 years, has evolved over the last 25 years, 30 years.
00:34:56.192 --> 00:34:56.774
It's pretty easy to find.
00:34:56.774 --> 00:34:58.139
You know people's like phone numbers and addresses and things.
00:34:58.139 --> 00:34:59.123
Even now you know out there on the web.
00:34:59.123 --> 00:35:07.372
So I think there's like almost like we've been conditioned to expect that in some ways, and there's services out there where you can like send people mail right to their house.
00:35:07.372 --> 00:35:09.666
Digital is kind of a new frontier though.
00:35:09.666 --> 00:35:17.817
Digital it's like when you sign on to a site now and the pop up comes up, you know, do you accept cookies and privacy policies and all that?
00:35:18.205 --> 00:35:23.295
Yeah, these are terms and conditions which we all agree to, but nobody ever reads Just click and move past it.
00:35:23.316 --> 00:35:34.740
Yeah, I mean, usually, if you stopped and look at what they're putting in there, it's going to say things like you're allowing us to use your information for aggregated advertising or different solutions.
00:35:34.740 --> 00:35:37.851
And I'm not saying don't click on that, that's your own decision to make.
00:35:37.851 --> 00:35:40.614
But you saw the whole Google thing over the last couple of years.
00:35:40.614 --> 00:35:42.050
Right, cookies are going to go away.
00:35:42.050 --> 00:35:45.975
Now they're going to kind of put that choice back in the hands of consumers.
00:35:45.975 --> 00:35:49.235
Do they want to click yes or no and accept cookies or not?
00:35:49.235 --> 00:35:51.352
So it's a rapidly evolving space.
00:35:51.352 --> 00:35:51.954
And accept cookies or not?
00:35:51.954 --> 00:35:54.405
So it's a rapidly evolving space.
00:35:54.405 --> 00:36:01.885
What I would say is expect that you're going to get aggregated pools of people to target, but at some point they're based on real identity.
00:36:01.885 --> 00:36:02.749
It could be a seed.
00:36:02.749 --> 00:36:07.729
You know that it's based on and lookalike models and other things kind of boost those audiences up and that's what.
00:36:07.769 --> 00:36:08.452
Google's doing.
00:36:08.452 --> 00:36:13.014
All these walled gardens are doing is building kind of inside their, their walls.
00:36:13.014 --> 00:36:15.970
You know they're building targeting pools based on interest.
00:36:15.970 --> 00:36:19.768
You know, like I love sneakers, I get targeted with sneaker ads all the time.
00:36:19.768 --> 00:36:34.736
I'm sure I'm part of some pools all over the place that say you know sneaker lover, or you know jordan fan, that, um, that enables me to get targeted advertising as I'm crossing throughout the web, even if they don't know who I am at an individual level.
00:36:35.965 --> 00:36:57.293
Interesting, yeah, okay, but that's I think it's fascinating because I think that's and maybe this is all related to tied to the COVID stuff too I think there was a more of a push to connect personal and professional profiles because people at least a large chunk of, say, office workers were now working from home.
00:36:57.293 --> 00:37:02.059
Right, they were no longer in an office identifying where they were and who they are.
00:37:02.059 --> 00:37:09.475
You know it's, it was a new, new challenge, but it sounds like there's progress on that for better or worse.
00:37:09.475 --> 00:37:13.411
Right, it's, it's like I'm.
00:37:13.411 --> 00:37:14.781
I'm like you, like I remember a time.
00:37:14.922 --> 00:37:21.767
I remember when I was doing database marketing and, um, there is one question I have for you because you touched on it.
00:37:21.787 --> 00:37:32.355
But, like, I hired third parties to provide data and then process data because the volumes were so big that we didn't have the internal technology to be able to process it at the volume it was.
00:37:32.355 --> 00:37:48.653
But I remember, even at that time, right being just sort of dumbfounded about how much data was either directly about people or could be inferred about people based on things like their five-digit zip code, right.
00:37:48.653 --> 00:37:55.711
And when you got a nine-digit zip code, it's like in the US, right is even more granular in just how accurate.
00:37:55.711 --> 00:38:02.672
It was in a general sense, and now you've just got gobs more data because technical term, yeah.
00:38:02.672 --> 00:38:04.576
So, uh, do you still?
00:38:04.576 --> 00:38:11.685
Do you still find that you have to when you were doing cdp stuff and all that, like, um, I guess now all this is cloud-based.
00:38:11.685 --> 00:38:25.091
This that wasn't the case back when I was doing this, so is there still a lot of data processors that are doing this for some of the companies you've worked with, or what's that market like?
00:38:25.994 --> 00:38:26.615
Yeah, there are.
00:38:26.615 --> 00:38:31.777
I mean thinking back again to things I wish I knew at the time.
00:38:32.298 --> 00:38:32.498
Right.
00:38:32.538 --> 00:38:34.724
Thinking back again to things I wish I knew at the time.
00:38:34.724 --> 00:38:43.553
We ended up building the customer hub asset in a legacy on-prem database and then immediately moved it to the cloud like a year later, and that took like a year and a half, so these things are not overnight.
00:38:43.553 --> 00:38:53.357
Luckily, if you start in the cloud today like Snowflake is a good example there's a lot of composable capabilities now where you can separate storage and compute.
00:38:53.357 --> 00:39:00.296
So now it's like I only pay for the data that I store and then when I want to call it or query it, I'm only paying for that compute.
00:39:00.296 --> 00:39:02.353
I don't have to buy a bunch of space ahead of time.
00:39:02.985 --> 00:39:08.478
I can kind of like match it to my supply and demand, which has been a pretty big game changer.
00:39:08.478 --> 00:39:35.759
One of the things that I think is fascinating you hear the word composability everywhere now Like we're actually taking a lot of our identity services and instead of saying, send us your data in a very secure SFTP secure way, we'll do the processing and append data and send it back to you, we're saying we're going to package up our apps and then we're going to containerize them and let you put them in your database so you can kind of run those services as a native app inside your environment.
00:39:35.759 --> 00:39:40.355
It's almost like bring your own right, you can bring your own identity, bring your own data into your ecosystem.
00:39:40.985 --> 00:39:50.057
I will say that's leveled the playing field a little bit, where you don't have to now go out and buy a huge set of on-prem hardware and build those databases.
00:39:50.057 --> 00:39:53.975
But you still have the challenge of it's expensive when you do massive scale.
00:39:53.975 --> 00:39:57.916
So it kind of depends on like what industry you're in, what's your target market.
00:39:57.916 --> 00:40:03.310
Are you talking about 5 million people or are you talking about, like you know, a couple hundred million?
00:40:03.310 --> 00:40:11.028
It can scale quickly, but I think that's less of a challenge now than it used to be, largely because of the rise of some of these cloud providers.
00:40:11.468 --> 00:40:45.105
Yeah, so you touched on the volume, which is, I think you and I both have worked at B2C, b2b you more than me, probably in both worlds, but I mean my view is generally I think B2C the big challenge is volume and B2B the big challenge is volume and B2B the big challenge is the complexity of the data and the structures and the lack of controls about the data, particularly when you start getting into sales realm, right, sales and customer success, because you've got people who are trying to get you know.
00:40:45.105 --> 00:40:50.873
They've got incentives not necessarily to focus on quality, data quality and it's not their fault, right, it's just the reality.
00:40:50.873 --> 00:40:59.673
So, like in your experience, what do you see as things that are similar common challenges in the B2C space?
00:40:59.673 --> 00:41:05.939
Based on the B2B space, do you see other major differences or am I off my rocker about the ones I saw?
00:41:07.564 --> 00:41:08.025
No, you're right.
00:41:08.025 --> 00:41:17.165
I think the volume challenge usually means you have to start with, let's say, your first-party data, to go back to that and build a lookalike model and scale it Right.
00:41:17.165 --> 00:41:19.551
Yeah, a couple hundred million people.
00:41:19.551 --> 00:41:22.938
We have, I think, like 270 million or so people in our graph.
00:41:22.938 --> 00:41:25.331
It's like the 18 plus population of the US.
00:41:25.331 --> 00:41:27.737
Like how much of that market do you want to go after?
00:41:27.737 --> 00:41:29.189
And you can kind of scale up from there.
00:41:29.189 --> 00:41:31.676
The business side is a lot more complex, though.
00:41:31.676 --> 00:41:33.918
You get down into the all those relationships right.
00:41:33.918 --> 00:41:36.420
Like you want to reach a decision maker.
00:41:36.420 --> 00:41:41.106
You want to reach somebody who's responsible for buying this type of software, if you're selling to them in that regard.
00:41:42.109 --> 00:41:44.796
So quality becomes an important aspect.
00:41:44.796 --> 00:41:46.420
But also it's more expensive.
00:41:46.420 --> 00:41:50.390
I mean the scale on the consumer side means you can get cheaper inventory.
00:41:50.390 --> 00:41:52.734
You know at scale you're paying lower CPMs.
00:41:52.734 --> 00:42:04.329
Anyone who's advertised on LinkedIn versus advertised like in Google right, you'll know like it's scale on one side and lower CPMs and a lot tighter scale and it's like more expensive per.
00:42:04.329 --> 00:42:23.596
So I think it actually makes it even more important that you know what your target is in the B2B space and you're able to kind of use the insights you can gather around somebody to make sure you're, you know, putting putting your uh, your eggs in the right basket and making sure you can drive the results you want, um, especially when you get to like frequency and other aspects.
00:42:23.636 --> 00:42:31.288
So um yeah, that's the only thing I would say to you is the, the uh, the spend side of it is different.
00:42:32.750 --> 00:42:35.194
The spend side of it is different.
00:42:35.194 --> 00:42:36.336
Spend side is different.
00:42:36.336 --> 00:42:39.260
It's higher on the B2B side because of the complexity.
00:42:39.260 --> 00:42:50.738
Okay yeah, more costly Kind of makes sense to me, right, Because you're trying to solve a little more complex network problem, right?
00:42:50.738 --> 00:42:54.242
Connections, all these different things, Okay, Okay.
00:42:54.242 --> 00:43:02.430
Okay, we've covered a ton of ground and we're going to probably need to wrap up here soon, but is there anything that we haven't covered here that you like?
00:43:02.430 --> 00:43:02.831
Hey, what is?
00:43:02.831 --> 00:43:08.737
These are the major trends that are happening in CDPs or identity resolution.
00:43:08.737 --> 00:43:12.793
You know that people should be aware of as they're working with their organizations.
00:43:14.606 --> 00:43:16.295
Yeah, so this will be our little future.
00:43:16.295 --> 00:43:18.445
We have to use the word AI in a conversation.
00:43:18.565 --> 00:43:25.079
We can't talk about data and not mention AI Just ai at the end of everything.
00:43:25.079 --> 00:43:31.347
So I guess the one thing I'll mention is AI-driven audiences, and synthetic data is a huge thing.
00:43:31.347 --> 00:43:35.932
So you're getting a lot of like think about the globe, the entire world.
00:43:35.932 --> 00:43:41.533
It's hard to get addressable IDs on the entire globe, especially with this patchwork of privacy.
00:43:41.533 --> 00:43:48.814
So one of the things that's happening now is AI driven audiences or synthetic audiences, where I can like model out a whole country's population.
00:43:48.814 --> 00:43:55.490
I can test things in that, instead of doing like a survey panel, I can test things out before it happens, right.
00:43:55.490 --> 00:44:01.611
So that's a really interesting and fascinating space for anybody who's interested in AI and synthetic data.
00:44:01.611 --> 00:44:05.579
I would say retail media networks are fascinating.
00:44:05.579 --> 00:44:09.327
I'm getting more into that now that I'm on the agency side Retail media networks.
00:44:10.412 --> 00:44:10.974
what does that mean?
00:44:11.585 --> 00:44:15.857
So that means I am a retailer or a company and I have my first party data.
00:44:15.857 --> 00:44:17.672
I'm actually going to become an advertiser now.
00:44:17.672 --> 00:44:25.031
I'm going to use that information that I have for my customers and I'm going to kind of there's kind of two paths right, and usually you do a little bit of both.
00:44:25.031 --> 00:44:33.119
I can create audiences of my first party customers and can serve those to other second parties to use for targeting.
00:44:34.706 --> 00:44:37.393
Think about like Walmart and amazon and all those big companies.
00:44:37.393 --> 00:44:39.906
The other side of it is like my own space.
00:44:39.906 --> 00:44:45.538
If I'm like a grocer, maybe I have like advertisement screens in my aisles and I can.
00:44:45.538 --> 00:44:48.489
Cpg brands can use that space to advertise.
00:44:48.649 --> 00:44:56.806
So it's kind of what I thought, yeah, it's kind of what I thought, yeah, and it's kind of a space that really only large publishers could do before Right.
00:44:57.006 --> 00:44:57.949
Yeah, it's blowing up now.
00:44:57.949 --> 00:44:58.330
Yeah.
00:44:58.450 --> 00:45:01.850
Yeah, okay, interesting, and then anything else.
00:45:02.886 --> 00:45:04.394
Last thing I'll say is data collaboration.
00:45:04.394 --> 00:45:15.881
It used to be like you know how do I use my data to drive my outcomes, but now it's like how do I partner with another company and overlap our data and see where there's opportunities and that's where you get into, like clean rooms and other aspects?
00:45:15.921 --> 00:45:28.316
so just to drop one more buzzword at the end there I'll clean rooms, yeah, meaning, meaning where we combine our data, but we don't let like we don't uh no one's share it.
00:45:28.316 --> 00:45:34.233
Yeah, yeah okay, okay, that was always used for measurement before now it's used for.
00:45:34.666 --> 00:45:45.306
Let's actually overlap and see you know what, what shared audiences we have or what unique audiences we have, and um, a lot of partnerships are happening now around the ability to do that at scale now.
00:45:45.306 --> 00:45:47.812
So interesting yeah, I'll.
00:45:47.812 --> 00:45:52.531
I won't say any more buzzwords that'll, otherwise I'll be here yeah, no, it's okay.
00:45:52.751 --> 00:46:01.596
Um, this has been fascinating and it's a little bit of me remembering where I started my marketing journey.
00:46:01.596 --> 00:46:03.780
So very interesting stuff.
00:46:03.780 --> 00:46:04.728
Jeremy, appreciate it.
00:46:04.728 --> 00:46:08.809
If folks want to connect with you, learn more about what you're doing or just follow up with you.
00:46:08.809 --> 00:46:10.214
What's the best way for them to do that?
00:46:11.365 --> 00:46:12.790
I'd say LinkedIn is probably the best way.
00:46:12.790 --> 00:46:13.854
Look me up on LinkedIn.
00:46:13.854 --> 00:46:17.693
I think it's JeremyCCatz at LinkedIncom, or something very basic.
00:46:18.354 --> 00:46:19.998
Got it, got it Okay, perfect.
00:46:19.998 --> 00:46:21.790
Well, thank you, jeremy.
00:46:21.790 --> 00:46:40.013
Again, thanks to our audience for continuing to support us and, as always, if you have suggestions for topics or guests or you want to be a guest, feel free to reach out to Naomi, mike or me through LinkedIn or through the marketingopscom community and we'd be happy to talk to you about that.
00:46:40.013 --> 00:46:41.315
Until next time, bye, everybody.