December Is a Read-Only Month. License Branded Games for Q4 Before the Change Freeze, Not After It.

If you plan to license branded games for a Q4 campaign, the deadline that matters is your client's change freeze, not the launch date on the media plan.

Every year the same conversation happens in November. A brand or an agency has signed off a Christmas activation with a game in it, the creative is approved, the build is nearly done — and then someone on the client's engineering side mentions, almost in passing, that production is locked from mid-month and nothing new goes live until January. The game is finished. It has nowhere to go.

That is not a games problem. It is a release-management problem games walk into, because a game is usually the last thing added to a Q4 plan and the first thing that needs a deploy. The fix is knowing the freeze date in October and picking a delivery shape that never has to cross it.

🧊 The Freeze Is a Real Date, and Nobody Sends You a Calendar Invite

Most large retailers, banks, telcos, airlines, ticketing platforms and logistics companies run a change freeze across their peak trading period. The shape varies, but the pattern is consistent: production deployments stop somewhere between the start and the middle of November, and normal release cadence does not resume until the first or second week of January. Some organisations soften it into a "change advisory" period where every push needs sign-off from someone senior. Functionally that is the same wall with a longer queue in front of it.

What a freeze typically blocks is broader than most marketing teams expect:

• Production deploys to the web estate and the mobile apps
• DNS and CDN configuration changes, including new subdomains
• New third-party scripts and tag manager containers
• New vendor onboarding, security review and data-processing paperwork
• Anything touching payments, identity or the checkout path — usually with no exceptions at all

The awkward part is who knows the date. The marketing lead who briefed you usually does not; the release manager or whoever owns the change calendar does, and they set it months ahead. Ask at kickoff, in writing, and get a date rather than "around the end of November".

💸 The Five Days the Freeze Exists to Protect

The freeze is not bureaucracy for its own sake. It exists because the revenue in that window is enormous and concentrated. Adobe Analytics reported that US consumers spent $257.8 billion online between 1 November and 31 December 2025, up 6.8% year on year, with Cyber Week — the five days from Thanksgiving through Cyber Monday — accounting for $44.2 billion of it and Cyber Monday alone driving $14.25 billion. Twenty-five separate days cleared $4 billion, against eighteen the year before.

Read that from the platform team's chair. A bad deploy on Cyber Monday costs more than most annual marketing budgets, and against that a campaign game is not a rounding error in the risk calculation — it is an unnecessary variable. You will not win that argument in November. Plan so you never have to have it.

The same data carries a second instruction. Smartphones took 56.4% of online transactions across the season, and on Christmas Day mobile drove 66.5% of sales. Whatever you ship has to work one-handed, in portrait, on a mid-range phone.

🍎 App Review Slows From 20 December, and That Rule Has Already Changed Once

If the campaign game ships inside an iOS app, Apple's holiday schedule is a second wall behind the client's. Apple's published guidance tells developers that App Review continues through the holidays but to submit time-sensitive work early, because "reviews may take longer to complete from December 20–26". That is softer than it used to be: in 2020 the announcement was that new apps and updates would not be accepted at all from 23 to 27 December. The policy has moved once already, which is a good reason to check the current year's notice rather than working from what a colleague remembers.

Stack the two constraints and an app-delivered game has to clear the client's mobile release train — often frozen earlier than the web estate — and then a review queue that slows exactly when the campaign peaks. The last comfortable submission is the first week of December, assuming no rejection and no resubmission.

A web build is the escape hatch, and this is where the HTML5-versus-native decision stops being philosophical. A licensed HTML5 title served from a campaign subdomain, or from the licensor's own hosting, is in nobody's review queue and — provided the subdomain exists before the freeze — nobody's frozen pipeline either. That is why most Q4 game activations that ship on time are web games.

📉 Do Not Fund the Plan on an Assumed Q4 Ad Uplift

If the business case for the activation is "Q4 rates pay for it", get your own numbers before you commit. The received wisdom is that Q4 lifts every ad rate. The measured picture in the most recent season was split by platform and format. Bidlogic's Q4 2025 eCPM analysis found Android rewarded video up 24.19% in the US and 23.29% in the UK quarter on quarter, while iOS interstitials fell across every market it studied, with Japan down 34.72%. iOS rewarded video was roughly flat. Treat that as one network's view — the methodology and sample are not fully disclosed — but the directional lesson holds: the uplift is not uniform, and it is not guaranteed on the format or platform you happen to be selling.

For a media-funded brand campaign that matters little. For an operator or publisher planning to monetise seasonal traffic it matters a great deal: model the season on your own trailing rates by format and geography, not on a blog post about Q4 seasonality — including this one.

🧱 Assume You Cannot Patch It After the Freeze Starts

Once mid-November is the last deploy, the design brief changes: you are shipping something that must run untouched for six or seven weeks, while half the people who built it are on leave. Practical consequences, in the order they bite:

• Every piece of copy must be data, not code. Prize names, dates, legal lines, the end-of-campaign message — all of it should be editable in a CMS or a config file outside the frozen system.
• The end date has to be built in. A campaign game that keeps accepting entries on 3 January because nobody could deploy the switch-off is a support problem and sometimes a legal one. Set the end state as data with a timestamp, and test it by moving the clock forward.
• Feature flags get flipped before the freeze, not during it. If a flag needs a deploy to change, it is not a flag.
• The device matrix is tested in October. Old iPhones, 4GB Android handsets, in-app browsers inside Instagram and Facebook, and whatever corporate-managed browser the client's own staff will use to check it.
• Write down the hotfix path. Who can approve an emergency change, what qualifies, how long it takes, and which phone number is answered on 27 December. Agree it while people are still at their desks.

🗂️ Host It Where the Freeze Isn't

Three delivery shapes, ranked by how much freeze exposure each carries:

1. Licensor-hosted, embedded by iframe. Lowest exposure. The games run on the licensor's infrastructure; your client's estate carries an embed that was added before the lock. Updates on the licensor's side do not require your client to deploy anything.
2. Self-hosted on a campaign subdomain with its own pipeline. Low exposure if — and only if — the subdomain, the certificate, the CDN rule and the deploy path all exist before the freeze. Creating a subdomain in December is a change request, and change requests are the thing that is frozen.
3. Bundled into the client's main site or app. Highest exposure. Every change is a release on the frozen train, and on iOS it is also an App Review submission.

Most disappointments in Q4 come from a team assuming they are in shape one or two and discovering in week 46 that they are in shape three.

🎁 Four Q4 Formats and What Each Demands of the Calendar

The daily calendar

Twenty-four doors, one reveal a day. The strongest format in the season because it manufactures return visits, and the least forgiving: all twenty-four days of content must be finished, approved and loaded before the freeze, and any bug repeats twenty-four times.

The instant-win or prize game

The build is small. The legal work is not, and it is the long pole in nearly every one of these projects: terms, eligibility, territory, prize fulfilment and the promotional-lottery rules of every market you run in, all settled by a legal team already handling the rest of Q4.

The leaderboard or tournament

Requires the licensed build to expose a usable score, which is not a given, and requires somebody to watch for abuse over the holiday period when nobody is on shift. If you run one, decide in advance what happens to a suspicious top score when the person who can adjudicate it is away until 5 January.

The seasonal games shelf

Ten to forty licensed titles behind a seasonal front end inside an app, a portal or a loyalty programme. The least glamorous option and the fastest to ship, because the games exist and are already tested — the only new work is the wrapper and the merchandising. It also survives the campaign: on 2 January it is still a games shelf, whereas a bespoke advent calendar is a folder of assets nobody opens again.

An honest word on the other route. If the idea genuinely depends on a custom mechanic inside a specific brand world — the thing only a bespoke build can do — commission a studio and give them a proper run at it. That is a real and often correct decision. It is also a Q3 decision. If you are reading this in autumn with a December date, the realistic paths are a licensed catalogue with seasonal dressing, or a licensed title reskinned to the campaign's art direction.

⚖️ Two Items That Are Slower Than the Build

Branded IP approvals run on the licensor's calendar, not yours, and that calendar has its own December. Build approval rounds in as fixed-length blocks rather than optimistic gaps, and get the style guide before the first pixel.

Prize mechanics carry a second timeline: any game whose outcome decides who wins something needs its rules, record-keeping and territory scope settled before launch, because the winning score becomes evidence in a dispute. Both are calendar items, not tasks, and both belong in October.

🚫 Five Ways a Q4 Games Campaign Dies in the Freeze

• Nobody asked for the freeze date. The single most common failure. It is a two-minute question at kickoff and a three-week problem in week 46.
• Vendor onboarding was left until the build was done. Security review, DPA and supplier registration at a bank or telco can take longer than the game does, and that process freezes too.
• The subdomain was requested in December. A ten-minute DNS change becomes a January change request.
• The end date lives in code. The campaign is over, the game is still live, and the only person who can turn it off is on leave.
• The plan assumed a Q4 ad-rate lift that did not arrive on that platform. See the eCPM split above; fund from what you can verify.

📋 The 2026 Dates, Worked Backwards

For planning purposes this year: Thanksgiving falls on 26 November 2026, Black Friday on 27 November, Cyber Monday on 30 November. Working back from a 1 December live date:

• Early October — confirm the freeze date in writing; start vendor onboarding and security review; agree licence scope, territory, term and formats.
• Mid October — titles selected and played on real devices; branded approvals submitted; prize terms with legal; subdomain, certificate and CDN path created.
• Early November — build complete; all copy in the CMS; end-date logic tested by moving the clock; full device matrix signed off.
• Before the freeze — deployed, live behind a flag, hotfix path documented with names and numbers.
• 1 December to early January — nothing ships. Merchandise, report, and let it run.

One more date worth putting on the plan: the days immediately after Christmas, when new devices are unwrapped and set up, are among the strongest of the year for casual play. A campaign that switches off on 24 December leaves that window on the table.

🎯 What You Get When You License HTML5 Games From a Direct Licensor

Forestry Games has operated since 2017 and licenses a catalogue of 1,049 titles spanning HTML5 games and Android APK games, with titles also published on Google Play and the Apple App Store. For a seasonal activation, the practical value of a direct licensor is that the titles already exist and have already been tested, so the calendar above starts at selection rather than at production.

A licence conversation covers scope, territory and term, which formats you receive — HTML5 builds you can host on your own infrastructure, APK builds for Android distribution, source where applicable — plus branding and hosting options if you would rather the serving sat outside your client's frozen estate. Where a catalogue of that size helps in Q4 is optionality: you can shortlist forty titles, play them on the actual devices, and cut to the ten that hold up, instead of hoping one bespoke build lands. If you are scoping a seasonal campaign now, browse the catalogue, look at how to license HTML5 games by category, or start from the games built for marketing campaigns.

🧸 Licensing Branded Games for Campaigns, Portals and Events

Forestry Games also develops HTML5 games in-house and works with branded IP, with brand partnerships including Disney, Nickelodeon, Cartoon Network and Warner Bros. Businesses can license branded game content through Forestry Games for marketing campaigns, white-label game portals, live events and mobile apps, alongside the generic catalogue.

Branded work carries the extra approval layer described above, which is precisely why it belongs at the front of a Q4 timeline rather than the end. The useful next step is to send the use case — surface, territory, term, campaign dates, and whether you need branded or generic titles — and ask for a licence scope in return. If you want to see the delivery shape before committing, ask for a portal demo or look at what a catalogue membership includes.

✅ Ask One Question at the Next Kickoff

Everything above collapses into a single question you can ask this week, of every Q4 project you are involved in: what date does production lock, and who can approve an exception? Get the answer in writing from the person who owns the change calendar, then set your own internal delivery date two weeks before it.

If the answer is mid-November — and it usually is — you have roughly six weeks to pick titles, clear approvals, settle prize terms and deploy. Comfortable for a licensed catalogue with seasonal dressing. Tight for a reskin. Not enough for a bespoke branded build, and knowing that in early October is worth more than any amount of effort in December. Send the campaign dates and the surface with your first enquiry, and ask the licensor what is genuinely deliverable before the freeze rather than what is theoretically possible after it.