Customer Data Science is at the heart of everything we do at dunnhumby. We combine industry-leading techniques, algorithms, processes, and applications to deliver the insights that retailers and brands need in order to make smarter decisions about how to respond to customer behaviour.
Ensuring that our science delivers results as the needs of our clients and their customers evolve is one of our top priorities. How then does dunnhumby create ‘new science’? How do we foster innovation and evolution in our data science practice?
Understanding the business need
The starting point for any evolution in data science is understanding the customer need behind it. Typically, this means asking questions; we might ask how our client team experts are visualising a solution, for instance, or what problem or pain point it is that they’re trying to answer. Getting to grips with the issues that are driving demand for a new solution is often just as important as the development of the solution itself.
Quite often, this means that innovative new approaches originate from the data scientists working closely with our clients. Our commercially minded teammates together with our Applied Data Science teams are very good at distilling client problems down into a clear task that needs to be solved, creating a high-speed prototype solution that offers a fix for that specific objective. That combination of fast-paced innovation and commercial expertise is a very powerful blend.
The job of our global science team is to refine and expand those prototypes. We look at the customer behaviours that we are trying to express mathematically, remove any spurious connections and biases, improve accuracy, and think about how an approach might be applied more broadly. So, while a solution might be created with a very specific use case, we try to ensure that it has wider relevance too. Our data science engineers can then help to ensure any solution works quickly and reliably at scale.
Learning from the past
At dunnhumby, we have the luxury of looking at what has come before. With over 500 data scientists and more than 30 years of experience, it’s not uncommon to find that a problem we’re trying to solve has already been addressed – albeit in an alternative context, or under a different description. That can help us think about how we might use that prior knowledge to answer the question we’re facing today.
Because we’re able to draw on our rich data science history, new science can sometimes take the form of an improvement or replacement of an existing solution. New methodologies and technologies can give us the ability to work more quickly, with greater precision, and with more granularity than we could in the past. New data sources and new science techniques are also possibilities for new science, if they offer and improvement over existing approaches. This can help us transform an existing approach into something new.
Even when we develop something completely new, it will have been built on concepts or knowledge that we already have – and that helps to set us apart. Many large organisations today have data science teams that are capable of building predictive models. The difference is that we’re very likely to be building that model for the hundredth or thousandth time, rather than the first. Our heritage helps us understand where and why models have succeeded and how to replicate that success in the future.
Looking both outside and in
When tackling a new problem, we try not to limit our thinking to just the problem or category at hand. Our data scientists come from a wide range of backgrounds and disciplines, including physics, economics, psychology, medicine, engineering, and operational research, while our global footprint also allows us to bring together ideas from across the world. That breadth of knowledge helps us think differently, bouncing ideas off each other and building up our knowledge in layers.
That desire to bring the outside in isn’t just about our own people, either. As part of our Academic Partnership programme, we work with data science scholars and students around the world, meeting regularly with them to discuss new thinking, research, and industry news. As a result, concepts from other industries often bleed into our own work; alongside Game Theory and DNA research, we’ve seen subjects as diverse as the psychology of jam testing and the rankings of a chess grand master inform our work.
We borrow techniques from each other as well. Across category management, pricing and promotions, and media, everyone at dunnhumby is ultimately focused on maximising the contribution we can make to our clients and their customers.
This ability to share and apply our learnings across different disciplines, whether within our business or elsewhere, is absolutely fundamental and enables us to create new science and foster innovation at dunnhumby.
Julie Sharrocks is dunnhumby’s Head of Science – Customer Data Solutions.
Cookie | Description |
---|---|
cli_user_preference | The cookie is set by the GDPR Cookie Consent plugin and is used to store the yes/no selection the consent given for cookie usage. It does not store any personal data. |
cookielawinfo-checkbox-advertisement | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . |
cookielawinfo-checkbox-necessary | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
CookieLawInfoConsent | The cookie is set by the GDPR Cookie Consent plugin and is used to store the summary of the consent given for cookie usage. It does not store any personal data. |
viewed_cookie_policy | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wsaffinity | Set by the dunnhumby website, that allows all subsequent traffic and requests from an initial client session to be passed to the same server in the pool. Session affinity is also referred to as session persistence, server affinity, server persistence, or server sticky. |
Cookie | Description |
---|---|
wordpress_test_cookie | WordPress cookie to read if cookies can be placed, and lasts for the session. |
wp_lang | This cookie is used to remember the language chosen by the user while browsing. |
Cookie | Description |
---|---|
CONSENT | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
vuid | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
_ga | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_gat_gtag_UA_* | This cookie is installed by Google Analytics to store the website's unique user ID. |
_ga_* | Set by Google Analytics to persist session state. |
_gid | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjSessionUser_{site_id} | This cookie is set by the provider Hotjar to store a unique user ID for session tracking and analytics purposes. |
_hjSession_{site_id} | This cookie is set by the provider Hotjar to store a unique session ID, enabling session recording and behavior analysis. |
_hp2_id_* | This cookie is set by the provider Hotjar to store a unique visitor identifier for tracking user behavior and session information. |
_hp2_props.* | This cookie is set by the provider Hotjar to store user properties and session information for behavior analysis and insights. |
_hp2_ses_props.* | This cookie is set by the provider Hotjar to store session-specific properties and data for tracking user behavior during a session. |
_lfa | This cookie is set by the provider Leadfeeder to identify the IP address of devices visiting the website, in order to retarget multiple users routing from the same IP address. |
Cookie | Description |
---|---|
aam_uuid | Set by LinkedIn, for ID sync for Adobe Audience Manager. |
AEC | Set by Google, ‘AEC’ cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user’s knowledge. |
AMCVS_14215E3D5995C57C0A495C55%40AdobeOrg | Set by LinkedIn, indicates the start of a session for Adobe Experience Cloud. |
AMCV_14215E3D5995C57C0A495C55%40AdobeOrg | Set by LinkedIn, Unique Identifier for Adobe Experience Cloud. |
AnalyticsSyncHistory | Set by LinkedIn, used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
bcookie | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognise browser ID. |
bscookie | LinkedIn sets this cookie to store performed actions on the website. |
DV | Set by Google, used for the purpose of targeted advertising, to collect information about how visitors use our site. |
ELOQUA | This cookie is set by Eloqua Marketing Automation Tool. It contains a unique identifier to recognise returning visitors and track their visit data across multiple visits and multiple OpenText Websites. This data is logged in pseudonymised form, unless a visitor provides us with their personal data through creating a profile, such as when signing up for events or for downloading information that is not available to the public. |
gpv_pn | Set by LinkedIn, used to retain and fetch previous page visited in Adobe Analytics. |
lang | Session-based cookie, set by LinkedIn, used to set default locale/language. |
lidc | LinkedIn sets the lidc cookie to facilitate data center selection. |
lidc | Set by LinkedIn, used for routing from Share buttons and ad tags. |
li_gc | Set by LinkedIn to store consent of guests regarding the use of cookies for non-essential purposes. |
li_sugr | Set by LinkedIn, used to make a probabilistic match of a user's identity outside the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
lms_analytics | Set by LinkedIn to identify LinkedIn Members in the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland) for analytics. |
NID | Set by Google, registers a unique ID that identifies a returning user’s device. The ID is used for targeted ads. |
OGP / OGPC | Set by Google, cookie enables the functionality of Google Maps. |
OTZ | Set by Google, used to support Google’s advertising services. This cookie is used by Google Analytics to provide an analysis of website visitors in aggregate. |
s_cc | Set by LinkedIn, used to determine if cookies are enabled for Adobe Analytics. |
s_ips | Set by LinkedIn, tracks percent of page viewed. |
s_plt | Set by LinkedIn, this cookie tracks the time that the previous page took to load. |
s_pltp | Set by LinkedIn, this cookie provides page name value (URL) for use by Adobe Analytics. |
s_ppv | Set by LinkedIn, used by Adobe Analytics to retain and fetch what percentage of a page was viewed. |
s_sq | Set by LinkedIn, used to store information about the previous link that was clicked on by the user by Adobe Analytics. |
s_tp | Set by LinkedIn, this cookie measures a visitor’s scroll activity to see how much of a page they view before moving on to another page. |
s_tslv | Set by LinkedIn, used to retain and fetch time since last visit in Adobe Analytics. |
test_cookie | Set by doubleclick.net (part of Google), the purpose of the cookie is to determine if the users' browser supports cookies. |
U | Set by LinkedIn, Browser Identifier for users outside the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
UserMatchHistory | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
UserMatchHistory | This cookie is used by LinkedIn Ads to help dunnhumby measure advertising performance. More information can be found in their cookie policy. |
VISITOR_INFO1_LIVE | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | YSC cookie is set by YouTube and is used to track the views of embedded videos on YouTube pages. |
yt-remote-connected-devices | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
_gcl_au | Set by Google Analytics, to take information in advert clicks and store it in a 1st party cookie so that conversions can be attributed outside of the landing page. |