Orchestrating email-first, paid-second reactivation with consistent suppression
Every business with a recurring customer relationship eventually has a lapsed customer problem. The exact threshold for "lapsed" varies (an e-commerce brand might use ninety days; a SaaS subscription, six months) but the pattern is the same. Some meaningful percentage of people who used to buy or engage have stopped, and the brand wants them back.
Email-only reactivation is appealing because the cost is near zero. The trouble is reach. Lapsed customers have, by definition, stopped opening emails. A typical reactivation campaign hits a five to fifteen percent open rate, which means the message reaches a small fraction of the audience.
Paid-only reactivation gets the reach. Custom audience uploads put the lapsed list in front of Meta, Google, programmatic, wherever. The cost is high, though, and a meaningful share of the spend goes to customers who would have reactivated on their own. There is no way to tell from paid impressions which reactivations were caused by the campaign and which would have happened anyway.
The orchestrated approach runs email first, hands non-responders to paid, and suppresses everyone who reactivates from continuing to receive reactivation messaging. That sequence is the recipe. The sending itself is the easy part. The orchestration discipline beneath it does the work. Suppression lists for email and paid have to stay in sync so a customer who reactivates via email Monday isn't still getting paid impressions Friday. Cohort definitions have to stay stable enough that year-over-year measurement is possible. And the cohort itself changes weekly as customers move in and out of lapsed status, which means continuous refresh rather than a one-time export.
A higher reactivation rate than email or paid alone could deliver, with paid spend concentrated on customers email couldn't reach. The measurable target is reactivation rate at a cost per reactivation that beats new-customer acquisition cost by a clear margin. For most consumer brands that margin is significant: reactivating a known customer typically costs a quarter to a third of acquiring a new one. The secondary outcome is cohort hygiene. The discipline of running this orchestration forces clear definitions of "lapsed" and "reactivated" that the rest of the lifecycle program can borrow.
An email service provider or marketing automation platform handles the email leg, with cohort-based sending and suppression list management. The paid leg runs on whichever ad platforms the brand already uses (Meta Ads Manager and Google Ads are the most common pair) with custom audience upload capability. A customer data platform or warehouse-with-activation tool maintains the lapsed cohort and pushes it to both channels. Identity resolution between the email cohort and the matched paid audience keeps them aligned. Some brands run this from a CDP alone, others stack a reverse ETL tool on top of a warehouse, others build it on a marketing-cloud-native segmentation engine. All work.
Compare the tools on Martech Stack Builder
Six roles. Marketing operations owns the orchestration: defining the lapsed cohort, building the email sequence, and setting the handoff rules that move non-responders into paid. Ad operations handles the paid side, pushing audiences to the platforms, managing bids, and running reactivation creative. The work is familiar territory for any ad ops function; the wrinkle is that the audience cycles weekly as the lapsed cohort changes. Identity or CDP ownership sits in between, keeping the audience handed to paid aligned with the cohort defined for email and making sure suppression flows back through both channels. Data engineering comes in only if the lapsed cohort logic requires custom queries against the warehouse rather than off-the-shelf CDP definitions; otherwise the CDP team handles it. Analytics measures reactivation rate against the spend and, ideally, runs an incrementality check against an organic reactivation baseline. Privacy operations or legal should review the consent posture before the first ad-platform push, especially in EU jurisdictions where ad-platform sharing requires a separate consent flag from email marketing.
The orchestration runs in a loop. Cohort definition comes first: identify customers who haven't engaged in the lapsed window (ninety days, six months, whatever the brand defines), excluding anyone who has reactivated within the same period or who has unsubscribed from email. Then the email phase runs, a sequence of two to four messages over two to three weeks, tracking opens, clicks, and reactivation events. When the email window closes, the non-responders (customers who received emails but neither opened nor reactivated) get pushed to paid as a hashed-email custom audience with creative tailored to reactivation. Throughout the campaign, reactivation events flow back into a suppression list. The moment a customer reactivates from either channel, they exit the active campaign across both and enter suppression for the duration of the reactivation window plus a buffer.
The handoff trigger is the absence of engagement. Non-responders get defined by what didn't happen: no open, no click, no reactivation event in the email window. Defining them by positive signal would mean waiting for a "go away" message that lapsed customers almost never send. Negative-signal definition is what makes the cohort actionable.
The match rate from the hashed-email upload to the ad-platform's user base will be lower for lapsed customers than for active ones. Active customers have current emails; lapsed customers may have older ones they no longer use. Match rates of thirty to fifty percent are normal for active-customer audiences; for lapsed customers, expect fifteen to thirty percent. The paid reach is correspondingly smaller than the cohort size suggests.
The cohort and the suppression list both need refresh. The cohort changes weekly as customers cross the lapsed threshold in both directions. The suppression list grows daily with new reactivations. A weekly refresh of both, synced before each major email send and each paid audience push, keeps the orchestration honest. Real-time sync is better if the stack supports it, but weekly is the floor.
Suppression timing is the most common failure mode. A customer reactivates via email on a Monday, but the paid audience refresh doesn't run until Friday, so they continue getting reactivation impressions all week. The fix is sync cadence (daily at minimum, ideally faster) and a clear "exit on reactivation" trigger that updates both channels' suppression lists from a single source. The diagnostic when this fails is paid spend showing impressions to customers who reactivated days earlier. The first three months of running this orchestration usually surface the lag.
Match rate decay catches teams off guard. The cohort size in the warehouse looks healthy (say, fifty thousand lapsed customers), but the matched audience on the ad platform comes in at eight to fifteen thousand. Teams sometimes assume the upload is broken. More often, the lapsed customers just have stale email addresses. Build the expectation into the campaign plan: half to two-thirds of the cohort may not match to paid. The recipe still works on the matched portion, but the cohort size doesn't translate one-to-one to paid reach.
Cohort definition drift is what kills year-over-year measurement. A team decides "ninety days lapsed" works, then six months later someone proposes "let's try four months because we want a bigger list." The change makes sense in the moment. Twelve months later, the team can't compare this year's reactivation rate to last year's because the definitions don't match. Settle on a definition and freeze it for the reporting period. Revisit annually if needed, but treat changes as analytical events worth documenting.
Consent state mismatch is the regulatory failure mode. A customer consented to email marketing but didn't separately consent to ad-platform data sharing. Pushing their hashed email to Meta or Google for audience matching is then non-compliant under GDPR and most US state laws. Verify the consent context before each ad-platform push, not just at customer signup. Building the consent check into the audience-build process is cheaper than retrofitting it after a regulator letter arrives.
The Workshop works out with your team which of these matter for your stack right now, and what to do first: a 90-minute session with the people who own the decision.
Did this recipe match your situation?Anonymous response. Sign up to leave a longer note tied to your account.
Recognize tenure and usage milestones with a touch that reads as personal rather than as a template with a date merged in
Warn the customer before the overage, the roaming charge, or the plan-mismatch cost lands on the bill, so the conversation is about what to do next rather than about why the bill is what it is
Recover the buy-online-pickup-in-store orders that the customer placed and never collected, with the cross-system identity and the in-store inventory signal that the recovery has to coordinate around