Mergers and acquisitions (M&A) are a fact of life in today’s grocery industry. In the past 12 months alone, for instance, ALDI acquired Winn-Dixie and Harveys Supermarket in the Southeastern US, Sainsbury’s purchased 10 locations from Homebase in the UK, and Carrefour added 60 hypermarkets and 115 supermarkets to its portfolio thanks to a deal with Louis Delhaize. Little surprise, then, that the global retail sector saw a twofold increase in M&A deal values1 between 2023 and 2024.
There are plenty of questions that retailers need to ask before deals of this kind can go through. "Have we done our due diligence?" for instance. "Will our cultures align? How will the deal be structured?". Other than for a very specific group of people, however, "what will happen with our loyalty programme?" typically isn’t one of them.
And yet, there’s every reason that it should be. As revealed in our Power of Personalised Loyalty report, companies that get loyalty right can boost their profitability by more than 40%. Maintaining that opportunity throughout the process of a merger or acquisition should be at the top of the agenda. So, with that in mind, let’s look at how retailers can successfully integrate one loyalty programme into another.
Depending on your overall familiarity with the field of data science, it may surprise you to learn that the merging of two loyalty programmes isn’t a data-centric challenge—not primarily, at least. Certain issues do need to be taken into account (not least the handling of sensitive customer information), but the main issues here aren’t driven by data. Instead, the main challenges revolve around subjects like brand strategy, customer impact, and operational capacity.
Let’s start with the first: brand strategy. It’s a generally accepted fact that no two companies share the exact same positioning. There may be overlap, but two different organisations will inevitably have their own proposition to the market. As a result, when two retailers join forces—either through merger or acquisition—two different brand strategies also need to be knitted together.
There are many possible outcomes here. Some retailers might choose to make their merger or acquisition "invisible" to end customers, for instance, combining strengths behind the scenes but with no explicit change in their individual positioning. Others might instead choose to make it public, perhaps even actively promoting the change to customers. And, in the event of an outright acquisition, there may simply be no choice; folding one brand into another is unlikely to go unnoticed, after all.
Whatever the result, working out what this new, unified entity will stand for is a critical first step—and that’s because loyalty programmes tend to be heavily aligned with a brand’s strategic focus.
Say that convenience is one of a retailer’s main differentiators, for example. To support that through their loyalty programme, they might focus on delivering rewards that are quick and easy to redeem. If sustainability is part of a retailer’s brand positioning, they might focus on eco-friendly rewards or offer carbon offset coupons to shoppers. The specific circumstances might vary, but a good loyalty programme typically serves as a reflection of the brand as a whole.
Because of that, setting a unified strategic vision first is essential when two companies unite. Not only does it help to solidify the new brand’s "promise" to customers, it provides the framework on which a successful loyalty programme can be built, too.
Naturally, the choices you make around brand strategy can have a significant impact on the shape that your new, integrated loyalty programme takes—and three issues warrant specific discussion.
This is where terms and conditions become so important. If data is to be aggregated across multiple banners, new permissions will need to be sought. The same is true if an existing loyalty programme is being folded into a new one—you may be acquiring new customers, but you’re not automatically acquiring their consent. If in doubt, it’s always better to assume that you don’t have the right to use someone’s data without establishing new terms and conditions first.
If anything, the creation of a unified loyalty programme gives retailers an excellent opportunity to review their relationship with customer data as a whole. From how data is collected and how it is used, even through to how it is organised, this is a great time for retailers to ensure they have sufficient consistency and accuracy across their (combined) dataset.
The answer to those questions isn’t necessarily "no". This is why the integration of loyalty programmes needs to be a customer-led activity. A good loyalty experience doesn’t have to be a homogenous one; instead, it should respect the preferences of different audiences. The challenge then is to ensure that one brand doesn’t "win" at the expense of another.
In the example above, for instance, the supermarket and discounter would need to go into that relationship with a clear understanding that customers interact with their loyalty schemes in fundamentally different ways. Acknowledging that shopper needs differ across brands is vital to the creation of a successful long term strategy.
Keeping loyalty programmes separate isn’t necessarily any easier, however. If you acquired four small grocery chains, each with its own loyalty programme, you’d then need to ask if you had the operational capacity to manage those schemes independent of one another.
Every approach comes with its own pros and cons. What’s important is to work which will deliver the best results for customers based—which means being able to manage that activity successfully.
Integrating loyalty programmes will never be a simple task. At the same time, nor does it have to be a needlessly complex one. By taking things one step at a time—and thinking logically about the best way to proceed—merging and acquiring retailers can turn a daunting prospect into a manageable process. Most importantly of all, by remaining true to what’s right for their customers, they’ll come out of that process stronger, too.
1 M&A in Retail: A Rebound—and No Sign of Letting Up – Bain & Company, 4th February 2025
Explore how AI-powered loyalty programmes enhance customer experiences and drive sales with dunnhumby’s personalised, data-driven solutions.
Invest in loyalty and personalisationTruly understand your Customers and unlock your Customer First transformation with Strategy Development, Research & Insights and Organisation Engagement
Design the right strategy with the Customer at the centerCookie | 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. |