Before your code freeze
Get everything that touches your site in before the freeze, so peak season only needs settings.
Read the transcript1:06
Why before the freeze
Every year, weeks before Black Friday, someone says the words: code freeze.
After that, anything that needs your theme, your tag manager or your developer waits until January.
Before your code freeze.
The tag and the checkout piece
Benson needs one tag. Add it through your theme, Google Tag Manager or your developer, and publish it while you still can.
Install the checkout piece too, even if you only switch the code policy on for the sale.
Send your developer the brief, so Benson goes in with one change. They'll appreciate it. Probably.
A normal month, a test, your sale rules
Watch a normal month in observe mode, and test a rule behind a holdout now, while the weeks are still ordinary.
Then schedule your sale rules, so pop-ups are hidden only while the sale runs.
Who changes what during peak
And agree who can change what during peak. Benson settings aren't deploys, so nobody has to ring the developer on Black Friday.
When the freeze starts, every switch you might need is already in place, or a setting away.
Find this playbook in Benson.
At a glance
Get everything that touches your site in before the freeze, so peak season only needs settings.
Nothing on your site has to change during peak. Every switch you might want is already in place, or a setting away.
Peak protection ready
7 practical steps
Who it's for
Stores with a code freeze before their peak season. Start a month before the freeze if you can.
The problem
Somewhere in late autumn your team stops changing the site. Theme edits, scripts and tag manager changes wait until January, because nobody wants to break checkout in the busiest weeks of the year.
That's sensible. It also means anything you want during peak has to be in place before the freeze starts, and coupon extensions are at their busiest in exactly those weeks.
Many stores stop changing their site weeks before Black Friday and don't start again until the new year. Anything that needs your theme, your tag manager or your developer has to land before then. Benson needs one tag, and after that every blocker rule, checkout rule and offer is a setting in Benson, so you can still act during peak without a deploy.

How to approach it
Ship the code early
Benson needs one tag, plus the checkout piece on some stores. Get both reviewed and published before the freeze.
Use the quiet weeks
Observe a normal month, and test any rule you're considering behind a holdout while traffic is ordinary.
Make peak a settings job
Schedule your sale rules and agree who can change what, so nothing needs a deploy once the freeze begins.
The steps
Work through the plan
0 of 7 completed
Progress stays on this device · Local marks are a reading aid; they do not verify your store or change Benson.
- To do
Step 1: Get the tag in before the freeze
It's the only change Benson makes to your site. Add it through your theme, Google Tag Manager or your developer, and publish it while you still can.
- In Benson:Check your install
- Open Benson
Benson checks this in your account
- To do
Step 2: Install the checkout piece too
On some stores, strict checkout rules need the Benson app, plugin or checkout guide in place first. Do it now, even if you only make them strict for the sale.
- In Benson:Open Checkout rules
- Included in Pro
- Open Benson
Benson checks this in your account
- To do
Step 3: Clear Benson with whoever owns the freeze
Send your developer the brief. If your site has a content security policy or a cookie banner, Benson goes into them in the same change.
- In Benson:Brief your developer
- Open Benson
You decide when this is complete
- To do
Step 4: Watch a normal month
Observe mode records what Benson would hide, without hiding anything. A few ordinary weeks give you a baseline to read the sale against.
- In Benson:Watch live
- Open Benson
Benson checks this in your account
- To do
Step 5: Test now, not during the sale
Ordinary weeks make a fair test. Put the rule you're considering behind a holdout now, and decide before the freeze whether it stays on for peak.
- In Benson:Start a holdout
- Open Benson
Benson checks this in your account
- To do
Step 6: Schedule your sale rules
A scheduled rule hides extension pop-ups on your storefront only while the sale runs. Set it up before the freeze, and nothing needs deploying during it.
- In Benson:Add a scheduled rule
- Open Benson
Benson checks this in your account
- To do
Step 7: Agree who changes what during the freeze
Benson settings aren't deploys. Your team should still know who can switch on Block, tighten your codes or go back to observe mode during peak.
- In Benson:Open the team kit
- Open Benson
You decide when this is complete
Common pitfalls
Leaving the checkout piece for later
On some stores strict checkout rules need it. If it isn't installed before the freeze, it isn't switching on during peak.
Forgetting the security policy or cookie banner
If your site has a content security policy or a consent tool, Benson goes into them in the same change. Leave them out and the tag may not load.
Testing during the rush
Peak traffic makes a poor test. Decide which rules stay on for peak before the freeze, using ordinary weeks.
Nobody owns the switches
Settings don't need a deploy, but they do need an owner. Agree who can switch on Block, tighten codes or go back to observe mode.

How you'll know it worked
Nothing on your site has to change during peak. Every switch you might want is already in place, or a setting away.
What to watch: Peak protection ready
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.

