martech cookbookSearch recipes & patternsSign up
Recipe·Updated 23 September 2026

Post-conversion suppression

Stop showing ads to people who already bought

01Problem

You're spending money showing retargeting ads to people who already bought from you. The customer who completed checkout on Tuesday is still seeing ads for the product they bought when they open Instagram on Wednesday. Finance sees the retargeting line item and asks why conversion costs aren't going down. Marketing assumes the platforms are handling it automatically. They mostly aren't.

This is the use case every marketing team says they've solved and most haven't.

02Outcome

Reduce retargeting ad spend on converted users on the primary paid social platform (typically Meta). Realistic effect on a campaign that wasn't previously suppressing: ten to twenty-five percent reduction in retargeting spend on the converted segment, depending on conversion rate and audience overlap. Measure yours before you start: match last month's retargeting audience against your conversions, and the overlap is what suppression recovers. Customer experience improvement as a secondary effect: fewer ads for products already owned.

03Ingredients
  • Conversion events
  • Hashed email identifier
04Equipment

Anything that can push an audience to an ad platform: a CDP with a destination connector, a marketing automation tool with audience export, a reverse-ETL job from a warehouse, or a manual CSV upload if the volume is low enough. The capability needed is "send a list of hashed identifiers to an ad platform's audience API on a schedule." Most modern stacks have this in some form.

05Staff
  • Marketing ops
    CriticalAudience configuration on the source side, exclusion setup on the ad platform
  • Ad ops
    CriticalCampaign-side exclusion application, audience attachment to the right campaigns
  • Analytics
    SupportingBefore-and-after measurement of retargeting spend on the converted segment

Three roles, working in coordination but not in lockstep. Marketing ops owns the audience configuration on the source side and the exclusion setup on the ad platform. The campaign-side exclusion application and audience attachment fall to ad ops. Analytics runs the before-and-after measurement of retargeting spend on the converted segment. The recipe ships in weeks rather than months because the Staff list is short and the handoffs are limited.

06Technique
INPUTSPROCESSACTIVATIONMIDConversion eventsHashed emailidentifierAnon->knownstitchingConverted audienceSuppression& exclusionLatency-tieredselectorFast audience syncAd-platformexclusion listMeta retargeting

Work in this order. At this readiness level it is four steps, on one platform.

  1. Pick the one platform where retargeting spend is largest. This recipe suppresses there only; the cross-platform version is a separate recipe.
  2. Make the conversion carry the identifier that platform matches on. Usually the purchase email, hashed the way the platform's audience matching expects. Check that it is the email customers actually use on that platform, or the match rate will disappoint.
  3. Push the converted audience on a schedule faster than the retargeting cycle, typically within twenty-four hours, and apply it as an exclusion on every retargeting campaign on that platform.
  4. Give the exclusion an end date. Decide how long a buyer stays excluded before repeat-purchase campaigns can reach them again. Set-and-forget suppression slowly excludes your best customers from everything.

Anonymous-to-known stitching does the linking in step 2, suppression and exclusion logic is steps 3 and 4, and latency-tiered channel selection is the timing decision in step 3.

07Gotcha
Failure 01

The recipe at this level only covers one platform. Meta gets suppressed. Google Display, TikTok, and any programmatic retargeting partners keep hitting the same customer with ads for the thing they just bought. If retargeting spend doesn't drop the way you expected, this is usually why. The cross-platform version of this recipe is a separate, harder problem.

Failure 02

The second failure: the suppression audience often doesn't expire. Customers who bought once get permanently excluded from any campaign that uses the converted audience as a negative, including campaigns that should be reaching them for repeat purchase. Suppression at this readiness level is set-and-forget, and set-and-forget is part of what makes it low-readiness.

WorkshopFor your stack·The questions this recipe raises

Eight questions this recipe raises for your stack.

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.

  1. 01Conversion event with a stable, matchable identifierThe purchase event tied to the email the platform's audience matching expects.
  2. 02Hashing format for platform audience matchingGetting the hash the platform wants so the match actually lands.
  3. 03Anonymous-to-known stitching for the conversionTying the conversion to whatever identifier the ad platform needs.
  4. 04Audience push: connector, reverse-ETL, or scheduled uploadSending the hashed list to the audience API on a cadence the stack supports.
  5. 05Campaign-side exclusion attachmentAttaching the converted audience as a negative to the right retargeting campaigns.
  6. 06Update latency under the retargeting cycleWhy the suppression has to refresh inside twenty-four hours to deliver the outcome.
  7. 07Audience expiry so converters are not permanently excludedThe undo for the set-and-forget that also blocks repeat-purchase campaigns.
  8. 08Before-and-after measurement on the converted segmentReading retargeting spend on the people who already bought, and which platforms still leak.

If you're seeing your own retargeting spend in this recipe and want to know whether your stack can actually deliver this outcome, the Workshop is where we figure that out together.

Most teams arrive convinced they've solved this and leave with a clearer view of which platforms are still leaking spend on customers who already bought.

take this to the martech workshop→

Did this recipe match your situation?Anonymous response. Sign up to leave a longer note tied to your account.

Related recipes