Last month, Tommy Lamb, Head of Lifecycle Marketing at WITHIN and former Director of Retention at TheRealReal, SEPHORA, and Teleflora, shared how marketers can easily orchestrate content and personalization across the customer lifecycle to drive growth.
Tommy presented the power of customer retention over acquisition for increased LTV by answering the question: What steps can you take to maximize the effectiveness of your owned channels and improve revenue?
If you missed the event, you can watch it here.
Brands typically have teams that manage acquisition by working on search, social, display, and other digital campaigns. This can lead to inefficiencies, as teams scramble for budgets between Facebook, Google, and TV.
Inconsistent messaging across channels, including a brand’s own website, ultimately leads to a fragmented customer experience even before the first purchase.
Owned media and retention teams often fight over attribution and touchpoint incrementality, which leaves the consumers overwhelmed by excessive messaging (three emails a day in some circumstances), out-of-touch SMS messaging, and a loyalty program rewarding the wrong type of behavior.
How do brands solve this problem?
By leveraging a concept called relationship marketing.
Relationship marketing is not about paid, owned, or brand. It’s about developing a genuine relationship with the customer.
Brands that use relationship marketing fuse creative performance, owned and paid, so that they adhere to branding practices, but also focus on performance metrics before and after a purchase.
“It’s not brand, it’s not paid, it’s not owned. It’s about developing that relationship with the customer.” – Tommy Lamb, Head of Lifecycle Marketing at WITHIN.
Related: What Is Lifecycle Marketing? Creating the Path to Loyal Customers
KPIs and metrics that vary across teams typically aren’t aligned with a brand’s primary goal: long-term profitability.
Most companies, use new customer acquisition, retention, or revenue as primary KPIs. But your brand’s marketing performance will be more streamlined when it is guided by a north star KPI.
The issue with CPA as a goal for customer retention is that it doesn’t take into account the quality of the customer. CPA doesn’t consider margin rate, repeat purchase rate, or potential halo effects in promotions.
Your brand needs to identify the most valuable segments to center marketing efforts around attracting and retaining these customers.
Retaining customers is 5 to 8 times less expensive than acquiring customers; you still need to pinpoint the 20% of customers that drive 80% of revenue.
Which brings us back to the question of performance metrics.
Revenue optimized ROAS as a metric is one step better, because it takes into account the dollar amount of the order, but it still doesn’t consider repeat rate or margin.
LTV, or lifetime value, is the ultimate KPI because it centers on the entire potential profit stream of the customer.
However, it can be challenging to get everyone on your team to buy into the idea of LTV, especially for paid media and branding efforts. LTV can be difficult to measure, hard to optimize for, and overall seem intangible without proper calculation capabilities.
Watch the full webinar recording here.
“LTV or long-term profit is the gold star KPI as it’s forward-looking at the entire profit stream of the customer.” – Tommy Lamb, Head of Lifecycle Marketing at WITHIN.
First, you need to organize customers that may look the same because they made the same first purchase. You can separate customers based on more granular measurements such as purchase history, acquisition channel, engagement signals, how they are interacting with customer service teams, or even NPS scores.
Additionally, you can compute LTV customers based on whether they shop at a discount, if they buy full price, and any demographic or psychographic data accessible.
You then use these data points to project how much that customer will likely spend with the brand over a specific period of time, usually between one and two years.
Here’s a fictional example to illustrate this point…
Let’s say that Shane and Olivia have both purchased from your brand. Shane has a much higher LTV and repeat purchase rate, so your focus should be on acquiring and retaining customers like Shane.
What most brands get wrong is that they stop at analysis and move into actual implementation based on these personas.
Want an action-packed guide to attracting, acquiring, and retaining high LTV customers? Check out our Free eBook on Lifecycle Marketing for more!
Finding your high LTV customers starts with strong attribution capabilities. Your brand should be able to evaluate the impact of every touchpoint, channel, and device a user interacts with on their path to purchase.
Going back to our examples of Shane and Olivia, Shane has a very different LTV and also a very different path to purchase than Olivia. Our goals are to weigh those channels appropriately and start to figure out where we can scale.
Take a paid media example: If Olivia ran a branded search on Google for Nike Jordans before making a final purchase and we attribute the sale with branded search, the attribution doesn’t take into account all of the interactions that Olivia has had with Nike leading up to the search.
And then a retention example: If a customer receives an email or SMS from a brand offering 25% off denim, then they drive to the store and make a purchase, the store gets all the credit, while online doesn’t.
To remedy issues with attribution, you can bring in media mix modeling, multitouch attribution, and incrementality testing capabilities.
If you’re ready to take your LTV efforts to the next level in 2022 and beyond, talk to us at WITHIN. We help the world’s most prominent brands like Nike, Shake Shack, and Casper maximize the value of their marketing across channels.
Chris Chan is a content writer at WITHIN.
Get industry insights and news directly to your inbox.
Thank you. Check your email for details on your request.
Cookie | Duration | Description |
---|---|---|
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
checkForPermission | 10 minutes | This cookie is set by Beeswax to determine whether the user has accepted the cookie consent box. |
cookielawinfo-checkbox-advertisement | 1 year | 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 | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | 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". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | 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. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_uetsid | 1 day | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
_uetvid | 1 year 24 days | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
Cookie | Duration | Description |
---|---|---|
__hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
__lotl | 5 months 27 days | This cookie is set by Lucky Orange to identify the traffic source URL of the visitor's orginal referrer, if any. |
_ga | 2 years | 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 recognize unique visitors. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 2 years | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | 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. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_lo_uid | 2 years | This cookie is set by Lucky Orange as a unique identifier for the visitor. |
_lo_v | 1 year | This cookie is set by Lucky Orange to show the total number of visitor's visits. |
_lorid | 10 minutes | This cookie is set by Lucky Orange to identify the ID of the visitors current recording. |
hubspotutk | 1 year 24 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
IR_gbd | session | Impact Radius sets this cookie to store a unique ID which is used to identify the user's device, when they return to the websites that used the same network. |
Cookie | Duration | Description |
---|---|---|
__qca | 1 year 26 days | The __qca cookie is associated with Quantcast. This anonymous data helps us to better understand users' needs and customize the website accordingly. |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
_mkto_trk | 2 years | This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo. |
B | 1 year | This Cookie is used by Yahoo to anonymously store data related to user's visits, such as the number of visits, average time spent on the website and what pages have been loaded. This data helps to customize website content to enhance user experience. |
bito | 1 year 1 month | This cookie is set by Beeswax for advertisement purposes. |
bitoIsSecure | 1 year 1 month | Beeswax sets this cookie for targeting and advertising. The cookie is used to serve the user with relevant advertisements based on real time bidding. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
mc | 1 year 1 month | Quantserve sets the mc cookie to anonymously track user behaviour on the website. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
tuuid | 2 years | The tuuid cookie, set by BidSwitch, stores an unique ID to determine what adverts the users have seen if they have visited any of the advertiser's websites. The information is used to decide when and how often users will see a certain banner. |
tuuid_lu | 2 years | This cookie, set by BidSwitch, stores a unique ID to determine what adverts the users have seen while visiting an advertiser's website. This information is then used to understand when and how often users will see a certain banner. |
Cookie | Duration | Description |
---|---|---|
__pdst | 1 year | No description available. |
_an_uid | 7 days | No description available. |
_dc_gtm_UA-61749619-1 | 1 minute | No description |
_dlt | 1 day | No description |
_hjSession_1771567 | 30 minutes | No description |
_hjSessionUser_1771567 | 1 year | No description |
_nx-nocache | session | No description available. |
6suuid | 2 years | No description available. |
A3 | 1 year | No description |
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ | session | No description |
AnalyticsSyncHistory | 1 month | No description |
BIGipServerab44web-nginx-app_https | session | No description |
bounceClientVisit3783c | 30 minutes | No description |
bounceClientVisit3783v | 30 minutes | No description |
dgzsdl08v4 | 10 minutes | No description |
IR_11658 | session | No description |
li_gc | 2 years | No description |
tableau_locale | session | No description available. |
tableau_public_negotiated_locale | session | No description available. |
test | 1 year | No description available. |