When does personalisation become a bad thing? For those in the marketing, advertising, and – yes – data science industries, it can be a tricky question, one that comes without any easy answers. The tolerance threshold for tailored marketing communications can vary dramatically from person to person, after all, meaning that one shopper’s inspiration is another’s exasperation.
What we can say for sure, though, is that it’s never been easier for advertisers to stray into the wrong territory. FMCG retail in particular is an industry awash with data, ensuring that campaigns and ads can be targeted not just around pre-defined segments and assumed behaviours, but actual purchasing habits from individual – albeit anonymised – customers. Without the right controls, personalisation can quickly become unnecessarily intrusive.
Before we look at how to stop that from happening, I think it’s important that we acknowledge that not all forms of personalised advertising are the same. That’s particularly true in terms of the tactical ways in which personalisation can be used, but equally so at a much higher level too.
Take personalised – or what used to be known as “interest-based” – digital ads. I think we’re all very familiar with how these work; we use a search engine to look something up, or maybe discuss a topic in a social post or chat, and soon after that we begin to see ads featuring products relevant to that theme. Tents and rucksacks for nature enthusiasts, for example, or dog treats and toys for pet owners.
Those ads are obviously effective to some degree; not only are they still with us, a multi-billion dollar industry has been built around them. But thinking purely as consumers, I think we can rightly question how “useful” those adverts really are.
For a start, they can be fairly repetitive, with ads for the same item following us from site to site. They also tend to be disconnected from our actual behaviours, meaning that ads continue to appear even when we’ve purchased a featured item or one similar to it. And at their worst, these ads can feel quite intrusive – reminding us of the trail of data that we leave in our wake when we’re online, and thus ticking over into “creepy” territory.
I’d argue that things are very different when it comes to personalised advertising on ecommerce websites and apps, sites that we tend to visit specifically with a view to buying something. As such, there’s an element at play that doesn’t exist in the examples above: an opportunity for brands and retailers to use personalisation in a way that is genuinely helpful to customers.
Grocery retail is a prime example of the value of helpful personalisation. Shopping for groceries is a fairly utilitarian task, and one that few people truly relish – over say, planning a holiday. New products can inspire us, and there may be pockets of fun and excitement on a shopping trip, but we tend to primarily shop for food out of necessity rather than simply novelty. As a result, anything that can help us save time or make shopping easier tends to hold a great deal of value.
This is where something like dunnhumby’s own Recommenders product comes into its own. Recommenders deliver product suggestions to shoppers in real time. Those recommendations can take the form of everything from relevant complements and substitutions through to items that shoppers normally buy, but don’t have in their baskets when they’re about to check out.
Naturally, a huge amount of behind-the-scenes data science goes into those suggestions. To make sure that recommendations are accurate and effective, we need a complete, 360° view of the Customer, as well as predictive models that can accurately forecast their future needs. That’s something that we achieve through a combination of machine learning, artificial intelligence, and a great degree of computing power.
What results is a structure of around 15,000 datapoints for an average customer. Naturally these are all anonymised, but that still amounts to more than enough information to take us into territory that could easily be considered as intrusive or unhelpful. And that’s why it remains so critically important that we stay true to what’s right for the customer.
To do that, we need to prioritise certain things. To ensure that recommendations are additive, not obstructive, we need to think about things like relevance, timeliness, and context. We – or the algorithms we create – need to really know that a customer is receiving suggestion for the right product in the right way and at the right time.
That’s crucial for brand advertisers, because it maximises the likelihood that a customer will add that item to their basket, and thus their return on advertising spend. But it’s equally – if not more – important for the retailer, since it has major implications for the quality of their customer experience. To prove that personalisation has long term value, we also need to ensure that it is something from which customers genuinely benefit.
More than anything, I think we’re on the cusp of a hugely exciting era for personalisation. There are a multitude of creative applications still waiting to be realised – from the automated delivery of frequently purchased items through to device-delivered reminders about product “use by” dates. The only limitation is our ability to think laterally about what data enables us to do.
Key to all of that, though, is an unwavering commitment to putting the customer at the heart of our decision making. So long as there’s a fair exchange – and that by sharing their data customers receive faster, simpler, and ultimately more valuable shopping experiences – then personalisation has a bright future ahead.
Amplify Customer understanding to create strategies that drive results
Customer First solutionsTruly understand your Customers and unlock your Customer First transformation with Strategy Development, Research & Insights and Organisation Engagement
Build a differentiated Customer strategyCookie | 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. |
fs_cid | This cookie is set by FullStory to store the user’s cookie consent preferences for session tracking. |
fs_lua | This cookie is set by FullStory to record the time of the user’s last activity, helping manage session timeouts. |
fs_uid | This cookie is set by FullStory to assign a unique ID to each user and record session replays and interactions. |
osano_consentmanager | This cookie is set by FullStory’s consent management system (Osano) to store the user’s cookie consent preferences and ensure compliance with privacy regulations. |
osano_consentmanager_uuid | This cookie is set by FullStory’s consent management system (Osano) to uniquely identify a user’s consent session for consistent consent tracking. |
vuid | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
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. |
_fs_tab_id | This temporary session value is used by FullStory to track user activity across multiple tabs. |
_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 set by Google Analytics to throttle request rates and limit data collection on high-traffic sites. |
_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. |
_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. |
__q_state_* | This cookie is set by FullStory to track session state and user interactions across page views. It helps rebuild session context for accurate session replay and analytics. |
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. |
_gcl_au | Set by Google Tag Manager to store and track conversion events. It is typically associated with Google Ads, but may be set even if no active ad campaigns are running, especially when GTM is configured with default settings. The cookie helps measure the effectiveness of ad clicks in relation to site actions. |