Leaked codes triage

Find the codes extensions spread, keep them out of extension sessions, and watch them.

Start freeAlready use Benson? Sign in
Read the transcript0:59

How codes leak

  1. You made a code for three hundred followers. It's now on fourteen coupon sites.

  2. And every extension tries it at every checkout, giving away a discount you meant for someone else.

  3. Leaked codes triage.

Find the leaked codes

  1. Open Checkout rules to see which codes turn up most in extension sessions, and whether your policy allows them.

  2. Mark the codes you never share publicly. Private codes stay off your allowlist.

Contain them, then watch them

  1. Turn on the strict code policy, and they stop working in extension sessions. The codes on your allowlist keep working, so your real customers are fine.

  2. Benson starts watching a code the moment it spreads. Code watch shows whether it's contained, replaced, or, inevitably, back again.

  3. Fewer extension uses of the codes you meant to keep private. Your VIPs stay very important.

  4. Find this playbook in Benson.

At a glance

Find the codes extensions spread, keep them out of extension sessions, and watch them.

Fewer extension uses of the codes you meant to keep private.

Jump to the steps
The result to look for

Code watch state

4 practical steps

Who it's for

Stores that run influencer, staff, apology or one-off codes.

The problem

You made a code for an influencer's followers, a staff perk or an apology to one unhappy customer. A few weeks later it's on coupon sites, and extensions try it at checkout on orders it was never meant for.

Deleting it isn't free either. The people you gave it to still expect it to work, and a replacement can spread just as fast.

A code made for one audience ends up on coupon sites, and extensions try it at every checkout. Each use gives away a discount you meant for someone else. Containing the leaked ones protects your margin without touching the codes your customers rely on.

Inhaling seagull meme: “Send a discount code to 50 VIPs”, “Check redemptions”, “4,118 uses”, “WHO ARE ALL THESE VIPS”.

How to approach it

  1. Find what's spreading

    The Checkout rules page lists the codes used most in extension sessions, and whether your rules let them through.

  2. Sort public from private

    Mark the codes you never share publicly. Private codes stay off the allowlist.

  3. Contain, then watch

    Once checkout rules are strict, private codes stop working in extension sessions only, so the people you gave them to keep their discount. Code watch shows whether each one stays contained.

The steps

Work through the plan

0 of 4 completed

Progress stays on this device · Local marks are a reading aid; they do not verify your store or change Benson.

  1. To do

    Step 1: See which codes extensions use

    The Checkout rules page lists the codes used most in extension sessions, and whether your rules allow them.

    You decide when this is complete

  2. To do

    Step 2: Mark the codes you never share publicly

    Private codes stay off the allowlist, so they don't work in extension sessions.

    Benson checks this in your account

  3. To do

    Step 3: Make checkout rules strict

    In extension sessions, only the codes you allow work. Auto-tried and leaked codes are turned away with a friendly message.

    • In Benson:Open Checkout rules
    • Included in Pro
    • Open Benson

    Benson checks this in your account

  4. To do

    Step 4: Watch the leaked codes

    Benson starts watching a code when it spreads through extension sessions. Code watch shows whether it's contained, replaced or back again.

    Benson checks this in your account

Common pitfalls

  • Deleting codes in a panic

    It punishes the people you made them for, and the next code spreads the same way. Contain it instead.

  • Allowing everything to be safe

    An allowlist that includes your private codes doesn't protect them. Keep it to the codes you're happy for anyone to use.

  • One code for every audience

    If staff, influencers and apologies share a code, you can't contain one without hitting the others. Give each audience its own.

  • Treating contained as fixed

    Codes turn up again on new sites. Keep an eye on code watch after a campaign ends.

Moe throws Barney out meme: the “Leaked VIP code” gets thrown out, Moe “Deletes it. Makes a new one.”, and it’s straight back: “New code. On a coupon extension by lunch.”

How you'll know it worked

Fewer extension uses of the codes you meant to keep private.

What to watch: Code watch state

Want the method behind the numbers? Read how to measure extension impact.

Do this in Benson

Every store gets every Pro feature free for its first 14 days, no card. Steps that need Pro say so.

Start free

Find out what's leaking. Free forever, no card.

Free forever up to 25,000 sessions a month. Every Pro feature free for your first 14 days. No card. We'll email you about getting started. Unsubscribe any time.