How to make the most of a Black Friday code freeze
What to ship before your code freeze, what you can still change during it, and how to use the weeks before it to measure on ordinary traffic.
Jump to a section
In short
A code freeze is the stretch before and during your busiest weeks when nobody ships changes to the site. For many stores it starts a few weeks before Black Friday and runs into the new year, so anything that needs your theme, your tag manager or your developer has to land before it. Use the weeks before the freeze to install what you'll rely on, measure on ordinary traffic and set up your sale controls as dated settings. Then peak season needs decisions, not deploys.
Why do stores freeze their code before Black Friday?#
Because a broken release costs the most when traffic peaks. A theme change that slows a product page, or a script that clashes with checkout, does more damage on Black Friday than on any other day, and there's less time to roll it back. A freeze trades flexibility for stability: the site that goes into peak season is the one you tested.
Freezes differ. Some teams freeze everything, including app installs and tag manager publishes. Others allow configuration changes in tools that are already live, with sign-off. Find out which kind yours is, and when it starts, before you plan around it.
What has to ship before the freeze?#
Anything that changes what loads on your site:
- New scripts and tags. Benson's tag is a single script, but it's still a site change. Add it through your theme, your tag manager or your developer while changes are allowed. The install guides cover each platform.
- Tag manager publishes. If you install through Google Tag Manager, publishing the container counts as a release under most freeze rules. Preview mode only shows the tag to you.
- Security and privacy settings. If your site sends a Content Security Policy, the hosts a new tool uses have to be allowed; the CSP notes list Benson's. If you run a cookie banner, check how the new tool fits it; consent and storage explains what Benson does.
- Checkout pieces. On WooCommerce, the strict code policy needs the Benson plugin; on Magento and BigCommerce it needs the checkout guide followed. Do it before the freeze, even if you only switch the policy on for the sale.
A tool you install in November is usually a tool you don't have until January.
What can you still change during a freeze?#
If your freeze allows configuration changes, everything that's a setting in a tool you've already installed. That's the case for getting Benson in early: once the tag is live, the controls are settings in Benson, not code on your site, and they take effect without a release.
- Switch from observe mode to Block, or back.
- Add a rule for one extension, one type of page or a date range.
- Turn on the strict code policy, so only the codes you allow work in extension sessions.
- Mark a code private, or allow a partner's code.
- Put your own offer in the widget.
Observe mode is the undo for pop-up rules: Benson stops hiding anything and keeps recording what it would have hidden.
How should you use the weeks before the freeze?#
Measure while traffic is ordinary. A few normal weeks in observe mode give you your extension share and a baseline to read the sale against.
Test now, not during the sale. A sale changes how everyone shops, so a holdout started in Black Friday week measures the sale rather than your change. October traffic makes a fairer test: put the rule you're considering behind a holdout, and decide before the freeze whether it goes into peak season.
How do you set up controls you can't deploy later?#
Set them up as dated settings, while you can still test them:
- Mark your sale period, so Benson reads the sale against a sale baseline instead of an ordinary week.
- Schedule your rules. A scheduled rule hides extension pop-ups on your storefront only while the sale runs, then switches itself off.
- Check your sale codes. The readiness report lists sale codes extension users could apply, so you can decide which stay public and which go private.
- Lock checkout to your codes in extension sessions, where your platform supports it. Storefront rules and checkout policies are separate controls; this guide explains the split on Shopify.
Who should agree what before the freeze?#
Whoever owns the freeze should know what's live and who can change it. Agree three things in writing: who can switch Block on, tighten the code policy or go back to observe mode during peak; where changes are recorded and who hears about them; and what would make you switch something off.
If your developer or your finance lead needs convincing first, give them the short version: one tag before the freeze, settings after it, and a holdout behind every change that matters.
What should you do during the freeze?#
Watch, and change settings only when the numbers ask for it. The live feed shows extension sessions as they happen, and the sale period readout compares the sale with its baseline. If a code leaks, mark it private and let the strict policy turn it away. That's a setting, not a release. Leave new tests until the sale is over.
What happens after the freeze?#
Read the recap before planning starts again: extension share, excess discount and money protected against your baseline. Decide which rules stay on in January. Then write next year's pre-freeze list while you still remember what you wished you'd had.
