Having published our predictions about what 2023 could have in store for retailers and CPGs, it’s time to turn our attention to one of dunnhumby’s other big focus areas: data.
Not to be confused with our already revealed data science trends, in this post we get the inside track from Alison Williams on how the year ahead might shape up from a data management perspective.
Accessibility is a big issue for any data-driven organisation. The easier we make it for people to get hold of the data they need, the more likely it is that they can use that information in collaborative, outcome-focused ways. Much as accessibility is commonly recognised as A Good Thing™, though, it’s also something that becomes increasingly hard to deliver as data volumes continue to grow.
That challenge is where architectural approaches like data meshes and data fabrics come into play. And, while both of those concepts are designed to break down key barriers to accessibility like silos and duplication, they’re also underpinned by different operational philosophies that bring an additional layer of complexity to proceedings.
A data mesh, for instance, takes a decentralised approach to data management, proposing a people-centric design that prioritises ownership and agency of data on a “per business function” basis. Data fabric, on the other hand, aims to bring together disparate systems in a centralised and automation-supported way.
Grossly oversimplified though these definitions may be, they do at least speak to the opposing nature of the two philosophies. While there might not be any hard deadline for organisations to work towards in terms of “picking” one of those approaches, 2023 is likely to see many beginning to think about which side of the fence their long term data future lies on.
The more data you have, the more important data governance becomes. Just like accessibility, however, governance is a problem that scales; more data equates to a greater number of data policies that need to be developed, enacted, and checked. Computational governance offers a way to alleviate some of that burden, and its importance will only increase through 2023 and beyond.
At its core, computational governance provides a way to automate the process of checking whether a data policy is being adhered to. As Dr. Sven Balnojan writes in this excellent piece on computational governance, this is a three-stage process that first requires each policy to be converted into an algorithm that can be comfortably processed by a computer.
Different levels of automation can then be applied to that algorithm, ranging from early warning systems that require human intervention before data can be accessed, through to fully autonomous systems that handle policy checks on an independent basis. It’s a fascinating idea – one that is too complex to do full justice to here – and one that promises to gain a great deal of traction over the coming months.
What if you could get the same amount of value from a large consumer dataset without ever coming close to touching the sensitive information that we’d all rather remained hidden? That’s the primary objective of Privacy Enhancing Technologies (or, PETs), and it’s an issue that could see a significant amount of progress during 2023.
While the general concept of PETs can be traced all the way back to the late 1990s, it is one that has newfound relevance in the face of global health crises like the Covid-19 pandemic. Essentially allowing the analysis and sharing of information globally to take place without the underlying data ever needing to be exposed, PETs offer a potential solution to the often conflicting goals of personal privacy and public good.
Numerous approaches to PETs already exist, with many more being researched and developed. In July last year, government agency Innovate UK ran a £700,000 competition aimed at discovering new solutions to real-world privacy use cases; expect that kind of traction to continue.
Every industry on earth is under scrutiny as to its environmental impact right now, and data science is no different. Big data requires big computation and storage to manage and analyse effectively, and that has significant repercussions from a power consumption, physical waste and sustainability standpoint.
While there might not be any immediate solutions to that challenge, we can at least expect the industry as a whole to step up to the issue and acknowledge that improvement is needed. Transparency will be the first step, with cloud providers under increasing scrutiny to acknowledge the volume of turn-over and therefore waste of physical hardware created by their exponential growth in recent years. Longer term radical disruption through concepts such as quantum computing may be the only way to make a significant impact.
Whether it’s the future of human interaction or simply an ill-advised waste of $36bn remains to be seen, but one thing that’s certain about the metaverse is that there’s no getting away from it anytime soon. Despite significant shareholder alarm, the company formerly known as Facebook looks dead set on continuing its investment into virtualising the internet.
Whichever side of the metaverse coin you land on, it does at least hold the potential to serve as a new – and potentially very different – source of data. New sources of information, of course, also require new protocols and procedures around privacy, and it’s hard to say just yet quite how valuable the information generated might actually prove to be. Just because it’s new doesn’t mean it’s useful, after all.
Will it bring us to a new level of understanding about human behaviours, or simply serve as a shiny (but ultimately short-lived) distraction that promises much and delivers little? The jury is still firmly out for now, but 2023 should at least see the answers around the metaverse start to shape up just a little bit more.
A look at dunnhumby’s unique Customer Data Science, which is at the core of everything we do.
Data Science solutionsCookie | 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. |