Skip to main content

Offline matching and the catalog from Dell

A couple of weeks ago I saw an ad on my phone for the new Dell XPS laptop. Out of curiosity I clicked on it, and started configuring a couple of options just for fun. I read a lot of good reviews about the upcoming XPS laptop, how the design rivals that of Apple’s MacBook laptops, and how certain configurations come with Linux preinstalled. I played around with the options, and configured two beast laptops just for fun, then I left and have not thought about it anymore, since I am not in the market for a new laptop, being satisfied with my Surface 3 laptop and all.

A couple of weeks later, I received a Dell catalog for the first time, addressed to me and not to the usual “Current Resident”, that has more details about the XPS laptops, gaming laptops, desktops, and peripherals that Dell sells. The catalog also included a 15% discount, which was a nice touch.

I wondered how I got that catalog, even though I have not explicitly sign up for it, nor request one, nor provide any information while configuring the laptops on Dell’s website. Then I remembered offline matching.

There are offline matching data companies, that collect customer activity in the offline world, such as purchases associated with gift and loyalty cards from grocery stores, gas stations, brick and mortar retailers, etc., where names and addresses are available, and use a bridge between the online-offline world to match the activity online with that offline. The bridge can be an email address, a third-party cookie, swap ID-match, or a hashed ID, etc., and after bridging, the data on the customer activity is holistic. I bet that’s probably what happened, and I ended up getting the catalog.


Labels:

Comments

Post a Comment

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...
2 comments
Read more

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...
Post a Comment
Read more

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...
Post a Comment
Read more