Retail, at its core, is a data-driven industry. Each transaction, visit, and interaction now leaves a trail – from sales volumes and basket sizes through to purchase frequencies, page views, opens, likes, and more. Every day, these signals help to shape decisions across marketing, commercial, sales, procurement, and beyond, and with good reason. Retailers that use this data to build mature communications and loyalty strategies can lift their annual sales by as much as 2.5% .
But transactional and behavioural insights in isolation are no longer enough. To turn strategy into meaningful action, retailers also require reliable contact data. Spotting a pattern or predicting behaviours means very little if you can’t actually engage with the person behind them. Simply, a healthy contact database is the foundation of a stronger, more powerful communication strategy.
It's with that in mind that I wanted to share four key ways in which retailers can improve the effectiveness of their “contactability” capabilities.
1. Registration is vital – but it’s only the start
Your customer registration process can have an outsized impact on contactability – so getting it right is imperative. Fields should be clearly structured, and easy for customers to complete; overly long or detailed forms tend to increase abandonment rates, without necessarily delivering better insights. The data you choose to collect should also be relevant to the business and usable.
The same applies to other registration or psychographic data such as favourite sports team, lifestyle, or hobbies. But beware: almost any kind of datapoint can change over time. Basing communications on sensitive but inaccurate information – like marital status, profession, or pet ownership – can cause frustration and drive customers away. An effective registration process will get you off to a great start, but it is only a start.
2. Know what to validate and when
Defining which data points should be validated – and at what stage – is critical for ensuring both fluidity and quality. And this strategic decision should be driven by business strategy, not just technical capability. Assessing the communication mix, the weight of each channel, and the security processes involved in customer interactions is essential to determining how and when data should be validated.
If SMS or WhatsApp is the main communication channel, for instance, then validating the phone number with a real-time code is key. If it’s email, then email validation should be the priority. Moreover, phone and email data can also help to improve match rates in segmented social media campaigns, making their validation – even after initial registration – all the more vital.
3. Integrate data from multiple registration sources
Retailers often capture data across multiple touchpoints – app, website, physical store, call centre, etc. That can create discrepancies and raise doubts about consistency. Integrating these systems with unified validation processes, in terms of both data collection and updates, ensures greater security and efficiency in customer communications.
4. Update, update, and update again
A contact database is a living organism. Even with strong capture and validation processes in place, data quality is not guaranteed over time. Long-term health is dependent upon constant monitoring and action, and neglecting preventative updates is one of the most common reasons for failure.
Without regular updates, a database will quickly become outdated, campaign performance will drop, and reversing this decline will become increasingly expensive and time-consuming. Proactive initiatives and preventative update campaigns are the most effective ways to keep a database healthy.
The negative impact of an outdated or poorly managed contact database goes beyond just marketing performance. At its worst, it can undermine engagement with customers, limit a retailer’s personalisation capabilities, and reduce its level of competitiveness. Inevitably, it can restrict media monetisation opportunities, too, something that can have a direct effect on commercial results.
In a landscape where personalisation is increasingly valued by consumers – and decisive for brand success – retailers that treat their contact database as a living asset will be far better positioned to build long-term relationships and deliver real value to shoppers. Integrity and freshness are the watchwords here, and even small adjustments to your contactability strategy can make a significant difference.
Explore how AI-powered loyalty programmes enhance customer experiences and drive sales with dunnhumby’s personalised, data-driven solutions.
Create experiences that deliver long-term loyalty and customer valueCookie | 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 |
---|---|
passster | Set by Passster to remember that a visitor has entered a correct password, so they don’t have to re-enter it across protected pages. |
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 |
---|---|
fs_cid | Set by FullStory to correlate sessions for diagnostics and session consistency; not always set. |
fs_lua | Set by FullStory to record the time of the user’s last activity, helping manage session timeouts. |
fs_session | Set by FullStory to manage session flow and recording. Not always visible or applicable across all implementations. |
fs_uid | Set by FullStory to uniquely identify a user’s browser. Used for session replay and user analytics. Does not contain personal data directly. |
VISITOR_INFO1_LIVE | Set by YouTube to estimate user bandwidth and improve video quality by adjusting playback speed. |
VISITOR_PRIVACY_METADATA | Set by YouTube to store privacy preferences and metadata related to user consent and settings. |
vuid | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
YSC | Set by YouTube to track user sessions and maintain video playback state during a browser session. |
_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. |
_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. |
__Secure-ROLLOUT_TOKEN | YouTube sets this cookie via embedded videos to manage feature rollouts. |
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. |
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 | Set by LinkedIn, used for routing from Share buttons and ad tags. |
lidc | LinkedIn sets the lidc cookie to facilitate data center selection. |
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. |
lpv[AccountID] | This cookie is set by Salesforce Marketing Cloud Account Engagement. Prevents counting multiple page views within a short window to avoid duplicate tracking. |
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_id[AccountID] | This cookie is set by Salesforce Marketing Cloud Account Engagement. Unique visitor identifier used to recognize returning visitors and track their behavior. |
visitor_id[AccountID]-hash | This cookie is set by Salesforce Marketing Cloud Account Engagement. Secure hash of the visitor ID to validate the visitor and prevent tampering. |
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. |