Today is April 22, 2026. Black Friday is November 27 — 31 weeks away. That sounds like plenty of time until you stack the 2026 migration calendar on top of Smart Bidding’s learning-phase math, and the calendar collapses. Smart Bidding needs at least 50 conversions or 3 full conversion cycles to calibrate — a minimum of 21–30 days, and every pause resets the clock to zero. Working backward from Cyber Monday, that puts the real BFCM readiness deadline at late August, which means clean conversion signal needs to be shipping by the end of July, which means the server-side infrastructure underneath it needs to be operational in June. The decisions you make this month are BFCM decisions, even if nothing about them feels like BFCM yet.
This Week: What’s Already Live
Two major 2026 migrations have already happened and most WooCommerce store owners haven’t processed them.
Meta’s one-click Conversions API went live on April 15, 2026 — seven days ago. For the 75–80% of SMBs historically kept off CAPI by implementation complexity, the one-click route is now available. It is also a migration-lock decision: once Meta hosts the pipeline, leaving requires rebuilding tracking from scratch. That decision is typically made in Q3 under BFCM pressure, without understanding the trade-off. Make it now, deliberately, or make it later, reactively.
Google’s Performance Max April 2026 updates — Channel Performance Timeline, Final URL report, asset-level actual metrics, 10,000 negative keywords — are live and usable today. The structural decisions these reports unlock (campaign splits, asset-group composition, negative keyword lists, Customer Match exclusion) are inputs to your BFCM campaign structure, not outputs. Make them in April, let the algorithm settle, and you enter the late-August learning window with clean structure. Make them in October and you’re calibrating during the traffic event.
The single April action that matters more than any of the above: document your current tracking configuration in writing. When AI Max auto-migrates in September and something breaks, the diagnostic requires knowing what the configuration was before the migration. Nobody writes that down until they need it.
June 2026: The Enhanced Conversions Migration Gate
Google Ads collapses Enhanced Conversions into a single unified toggle in June 2026. The separate method selector — global site tag, Google Tag Manager, Google Ads API — disappears from the UI. Auto-migration applies only to accounts with pre-accepted customer data terms.
Plugin-based WooCommerce setups cannot accept those terms on the account’s behalf. If the account-level customer data terms haven’t been clicked through by a human with admin access, the account sits outside the auto-migration path and has to be fixed manually — in a migration month when Google Ads support queues are saturated.
The decision required in May: log into each Google Ads account used by the store, navigate to account-level settings, and confirm the customer data terms status. If they aren’t accepted, accept them. This is the single highest-leverage 30-minute task in the entire BFCM calendar.
End of July: The Real Back-Stop
If conversion signal isn’t clean and server-side by the end of July, the late-August Smart Bidding calibration window runs on broken inputs — and BFCM runs on a mis-calibrated algorithm. Everything in this section is conditional on the signal underneath being trustworthy.
Conversion signal quality compounds across the learning period. An algorithm trained on 30 days of partially blocked client-side conversion events doesn’t underperform by 10% during BFCM — it underperforms by 30–40% on the specific days that matter most, because the inputs that trained it diverged most sharply from reality under peak traffic. This is why Smart Bidding optimized on polluted signals finds the wrong customers: the optimization objective the model is chasing isn’t the same as the orders your warehouse ships.
You may be interested in: Why GA4, Meta, and Google Ads Will Never Show the Same Number for Your WooCommerce Store
Late August: Start the 90-Day Learning
This is the real BFCM prep week — 14 weeks before Cyber Monday, 13 weeks before Black Friday. At this point, every structural decision should already be made. Conversion actions, bidding strategies, conversion values, audience exclusions, creative rotation: all locked. Budget adjustments are fine. Structural edits are not, because they restart the learning period.
The math: 21–30 days to calibrate Smart Bidding + 30 days of clean campaign performance you can reference to make BFCM budget decisions + buffer = 90 days total before Cyber Monday. Count backward from November 30: late August.
Stores that make major tracking changes between late August and Cyber Monday are running experiments, not campaigns.
September 2026: AI Max Absorption
Google AI Max for Search auto-upgrades every remaining Dynamic Search Ads campaign, Automatically Created Assets campaign, and campaign-level broad-match setup. The migration is not optional. DSAs can no longer be created after the September cutoff.
The critical number: AI Max requires 100+ monthly conversions per campaign to operate effectively — double Smart Bidding’s 50-conversion threshold. WooCommerce stores that consolidated into AI Max-eligible structures during August will have 30 days of calibration before the conversion threshold starts mattering during Q4. Stores that hit September still using DSAs get auto-migrated into a campaign structure requiring twice the conversion volume, with 60 days to figure out how to deliver it.
The action for September: verify conversion counts per campaign for the three months prior. Any campaign below 100 monthly conversions should be either consolidated with adjacent campaigns before the auto-migration, or accepted as a campaign that will underperform during AI Max learning.
Late October: Attribution Windows and the YoY Warning
25% of early holiday purchasing starts well before Black Friday (Klaviyo research). Attribution windows configured for a 7-day click model will miss the long-tail buyers researching in late October and purchasing in late November. Verify attribution settings by mid-October, not the week before BFCM.
And the warning nobody is publishing: the Q4 2025 YoY baseline is compromised. HUMAN Security measured a 144.7% surge in AI-agent and agentic-browser traffic targeting e-commerce sites during the 5-day 2025 BFCM window. Any 2026 year-over-year comparison reads against a 2025 baseline inflated by that agent traffic — not a true human-buyer baseline.
A 2026 YoY that shows “down 20% vs 2025” may actually be “flat vs 2025 humans, minus the 2025 bot noise.” The fix is filtering agent traffic out of the 2025 historical record before running the comparison, which requires a warehoused dataset the store owns — not a platform dashboard.
November 27: The Infrastructure You Built Six Months Ago
BFCM runs on the tracking, conversion signal, campaign structure, and YoY-baseline hygiene established between April and October. There is no meaningful engineering work to do during BFCM itself. The best November week is a boring November week — monitoring dashboards that were built in September, budget adjustments within structures finalized in August, and inventory/fulfillment focus uninterrupted by tracking fires.
The worst November week is one where a migration-lock decision made under pressure in Q3 starts showing unexpected behaviour on November 28, and the pre-migration configuration was never documented. That is the week this article exists to prevent.
The One Rule That Makes the Rest Work
Every deadline on this calendar — Enhanced Conversions unified toggle in June, Smart Bidding learning starting in August, AI Max absorption in September, attribution window reconciliation in October — depends on one structural precondition: clean server-side conversion signal operational before June. If the signal underneath is still client-side and losing data to ad blockers, consent refusal, and ITP by June, every upgrade layered on top of it is optimizing broken inputs.
This is why the April action is architectural, not tactical. The tactical decisions (which negative keywords, which attribution window, which bidding strategy) are downstream of whether the store owns its conversion data or rents it from Google and Meta.
Here’s How You Actually Do This
Transmute Engine™, Seresa’s first-party Node.js server that runs on your own subdomain (e.g. data.yourstore.com), captures WooCommerce conversion events server-side and writes them to BigQuery while routing them to Google Ads, Meta, and GA4 in parallel. That gives you the clean signal Smart Bidding needs, the warehoused dataset required to filter 2025 agent traffic out of your YoY baseline, and the reconciliation layer that confirms platform-reported conversions match real orders. It is the single April infrastructure decision that makes every June–September migration easy instead of reactive.
Printable Summary: The BFCM 2026 Calendar
- This week (April 22): Document current tracking config in writing. Make the Meta one-click CAPI decision deliberately, not under Q3 pressure. Set PMax campaign structure.
- May: Confirm Google Ads customer data terms are accepted at account level. This is the 30-minute task that prevents June migration pain.
- June: Enhanced Conversions unified toggle goes live. Verify auto-migration completed cleanly. Server-side conversion signal must be operational by now.
- End of July: Clean conversion signal shipping to Google Ads and Meta. No structural tracking changes after this point without a calibration budget.
- Late August: Start the Smart Bidding BFCM prep. Lock campaign structure, bidding strategy, conversion values. Only budget changes from here.
- September: Audit campaigns against AI Max 100-conversion threshold. Consolidate sub-threshold campaigns before auto-migration absorbs them into a structure that will underperform.
- Mid-October: Verify attribution windows capture early-holiday purchasers. Pre-filter 2025 agent traffic from historical data to get a clean YoY baseline.
- November 27 (BFCM): Monitor the infrastructure you built. Make zero tracking changes. The best BFCM week is a boring BFCM week.
Frequently Asked Questions
Now. Today is roughly 31 weeks from Black Friday (November 27, 2026) and only 9 weeks from the June Enhanced Conversions migration. Smart Bidding needs a 21–30-day clean learning period before a major traffic event, which puts the real BFCM readiness deadline at late August — not November. Working backward, that means conversion signal must be clean and shipping by the end of July, which means the server-side infrastructure underneath it needs to be operational in June. Stores that treat this as a November problem are consistently 60–90 days late.
At minimum 21 days before the first expected BFCM traffic spike, and ideally 30–45 days. Smart Bidding’s learning period restarts whenever significant bid or conversion-value changes are made, so large structural edits made in November will still be calibrating when Cyber Monday starts. The practical rule: finalize conversion actions, bidding strategy, and conversion values by mid-October, then leave structure alone and only adjust budgets. Creative and audience changes have lower learning-period impact than conversion or bidding changes.
Four major ones. Meta’s one-click CAPI went live April 15, 2026 — a migration-lock decision for SMBs. Google Ads collapses Enhanced Conversions into a single unified toggle in June 2026, with auto-migration applying only to accounts with pre-accepted customer data terms. Google AI Max absorbs all remaining Dynamic Search Ads and Automatically Created Assets campaigns in September 2026. Meta removed 7-day and 28-day view-through attribution windows on January 12, 2026. Each one interacts with WooCommerce tracking differently; the April–September period is when the decisions lock in.
Because the comparison year is polluted. HUMAN Security measured a 144.7% surge in AI-agent and agentic-browser traffic targeting e-commerce sites during the 2025 BFCM window. Any 2026 YoY comparison reads against a 2025 baseline inflated by that agent traffic — not a true human-buyer baseline. The fix is filtering agent traffic out of the 2025 historical data before running the comparison, which requires your own warehoused dataset since most analytics platforms did not flag this traffic at the time.
Get clean server-side conversion signal operational before June. Every downstream migration — Enhanced Conversions unified toggle, AI Max upgrade, Smart Bidding learning period, attribution window reconciliation — depends on the signal underneath being clean. If June arrives and you’re still relying on client-side pixels losing data to ad blockers and consent refusal, every upgrade after that point is optimizing on broken inputs. The structural April action that makes every June–September action work is moving conversion tracking server-side onto infrastructure you own.
Print the calendar. Tape it to the wall. The week of April 22 is the week to start, not the week of November 22. Start at seresa.io.