What is BFCM tracking monitoring?
BFCM tracking monitoring is the routine of comparing your store's real orders with what each ad platform reports, on a fixed schedule through Cyber Five, so a broken sender, a missing script or a consent fault is caught in hours instead of being discovered in January's results.
This guide starts where our last-minute BFCM fixes ended. That post covered the repairs to make and test before the sale, ending with a freeze. This one covers the five days after the freeze: Thanksgiving Day on Thursday, November 26, Black Friday on November 27, the weekend of November 28 and 29, and Cyber Monday on November 30, 2026.
Adobe forecasts $47.5 billion in US online sales across Cyber Week, up 7.4% year over year, inside a $275.1 billion season from November 1 to December 31. It expects $6.9 billion on Thanksgiving, $12.9 billion on Black Friday and $15.1 billion on Cyber Monday, with a record share of Cyber Week spend arriving on mobile. Those are forecasts published on September 28, 2026, not results, and your store will not follow the national curve hour by hour. They are useful for one thing: they tell you the cost of a silent tracking failure is concentrated into the same days as your highest spend, which is why the monitoring rhythm exists.
We build SignalBridge, so the product section is a vendor describing its own monitoring. The routine itself is tool-neutral. It works with a spreadsheet, your store admin and each platform's diagnostics, which is how most stores should run it, because the comparison has to survive any one tool being the thing that broke.
What should you monitor during Cyber Five?
Three numbers, in this order, because each one tells you whether the next is worth reading:
| Number | Source of truth | What it tells you |
|---|---|---|
| Backend orders and revenue | Your store or payment system, for the same period and revenue definition every time | What actually happened. Every other number is judged against this |
| Platform-reported purchases | Each ad platform's own reporting, read after its normal delay | What the bidding system is learning from. A gap against backend orders is a delivery or attribution question, not yet a performance verdict |
| Spend | Each platform's billing or reporting, checked against your budgets and inventory | Whether the money is going where you intended while the data catches up |
Then two supporting signals, which explain a gap when you find one:
- Delivery health in your tracking tool. Events sent, held back, failed and retried, per platform. A platform that receives nothing for an hour while orders continue has a delivery break. A platform receiving events that its own reporting has not yet counted has a delay.
- Store health. Checkout availability, page speed on your sale landing pages, stock on the products your ads point to, and discount codes applying as expected. A conversion fall caused by an out-of-stock hero product looks exactly like a tracking fall until someone checks the product page.
Do not monitor a blended ROAS dashboard as your alarm. Blended figures move with traffic mix, promotions and refunds, and they cannot tell you whether Meta stopped receiving purchases. Alarms live at the level of one platform against your backend, because that is the level at which a break happens and at which you can fix it.
Set your baselines and thresholds before Thanksgiving
An alarm needs a number written down in advance, or every quiet hour becomes an argument. In the week before Cyber Five, record for each platform:
- The normal gap between backend orders you can tie to that platform and the purchases it reports, over a recent full week. No platform matches your backend exactly. Attribution windows, view-through credit, consent holdbacks and reporting delay all move the figure, so your baseline is a range from your own store, not zero and not a percentage from an article.
- The platform's normal reporting delay, measured when you placed your test orders. If purchases usually appear within a few hours, an empty hour at peak is information. If a route reports the next day, an empty morning is not.
- The delivery failure and holdback rates in your tracking tool on a normal day, so a spike is visible as a spike.
Then write the alarm as a change from that baseline. For example: "If Meta-reported purchases for a completed period fall to less than half of our usual share of backend orders, and delivery shows failures or a silent platform, investigate." The half is an illustration for your own threshold, not a benchmark. A store whose usual gap is small can set a tighter alarm than a store that normally loses a third of its signal to consent choices. What matters is that the threshold, the person who owns it and the first three checks are written down before November 26, in the same document as your freeze note from the BFCM tracking checklist.
The Cyber Five monitoring routine
The routine has three speeds. Hourly checks catch breaks. Daily checks make decisions. The end-of-sale check closes the period honestly.
Step 1: Run the hourly delivery check during your selling hours
Once an hour while your campaigns are spending at peak, one named person answers four questions, in order:
- Is the store taking orders? Backend orders in the last hour against the same hour's expectation from your promotion calendar. If orders themselves stopped, this is a store incident, not a tracking incident.
- Is each platform still receiving events? Open delivery in your tracking tool. Look for a platform that has gone silent, a failure rate climbing above your baseline, or holdbacks spiking after a banner or theme change.
- Is any sale landing page missing its tracking? BFCM pages are created late and copied often. If one campaign's data fell while others held, click its ad, land on the page and check the script is present, exactly as you would a click ID check.
- Is spend behaving? Each platform's spend so far today against its daily budget and your stock. A campaign spending at three times its planned pace into an out-of-stock product is a budget action, not a tracking one.
Write the answers in a shared log with the time. A log that says "14:00 all platforms delivering, Meta reporting lagging as usual" is what stops a second person from re-diagnosing the same delay at 15:00, and it is the evidence you will want in December when a day's numbers are questioned.
Step 2: Place a test order when the numbers disagree, not on a schedule
A test order is your ground truth instrument, and Cyber Five is the worst time to fire it blindly. Place one when a platform's reported purchases and your delivery view disagree: delivery claims success and the platform shows nothing after its normal delay, or the platform shows purchases your backend cannot find.
Use a phone, because Adobe expects most Cyber Week spend on mobile and because your customers are on phones. Start from the campaign in question where you can, complete a real purchase you can refund, and note the order number, time, value and consent choice. Then follow that one order into each platform's diagnostics or test events view. One order tells you whether the path works. It does not tell you the size of a gap, which only the full-day comparison can do.
Do not place test orders through a discount code or gift card flow unless that is the flow you are testing, and remove test orders from both sides of every revenue comparison afterwards.
Step 3: Run the daily reconciliation before you change any budget
Once a day, for the previous full day, build one table per platform. Full days matter because Taboola attributes a conversion to the day of the click rather than the day of the order, Meta and Google report with their own delays, and a partial day compares a complete backend against an incomplete platform and manufactures a crisis.
| Column | Where it comes from |
|---|---|
| Backend orders tied to this platform | Orders carrying its click ID or campaign UTMs, counted once each |
| Backend net revenue from those orders | The same orders after refunds and cancellations, in your chosen revenue definition |
| Platform-reported purchases | The platform's own figure for the day, read after its delay has closed |
| Platform-reported revenue | As reported, before you compare it with your net figure |
| Spend | Platform billing for the day |
| Gap and your note | The difference, with the cause you believe: delay, consent, view-through, a delivery break, or unexplained |
Decide budgets from the backend columns. A campaign whose platform ROAS collapsed while its backend orders held is a reporting problem to note, not a campaign to pause at noon on Black Friday. A campaign whose backend orders and revenue genuinely fell, with delivery proven healthy, is a performance problem, and that is the one you act on. Our true ROAS guide shows how to keep the revenue definitions honest across that table.
Step 4: Fix delivery only, and log every change as an incident
When a check finds a break, the permitted fixes during Cyber Five are the ones that restore the frozen state:
- Re-enable a sender, integration or pixel connection that was switched off or whose authorisation expired, then reconnect it and send a test order.
- Restore a tracking script to a sale landing page or template that lost it in a theme publish, then re-test that page's path.
- Repair a redirect that started stripping a click ID such as
gclid,msclkidortblci, so the server route has something to match on again. - Fix a consent banner fault that stopped recording choices, so granted consent is recorded as granted.
- Roll back a theme or app change that broke checkout events, using the change log rather than a new edit.
The prohibited list is the mirror image. Do not create a new primary goal, change an attribution window, swap which tool sends a platform's purchases, edit event names, or "improve" a value definition mid-sale. Each of those changes the meaning of the numbers you are comparing against your baseline, so you lose the ability to tell a fix from a redefinition. Note the idea, park it in the log, and do it in December with a test week.
Every incident gets four lines: what you observed, what you changed, the test order that proved it, and the time the platform's reporting caught up. If you cannot write the third line, the incident is not closed.
Step 5: Watch stock, speed and spend as tracking problems in disguise
Three operational faults present as tracking failures during Cyber Five:
- The advertised product sells out. Clicks continue, conversions stop, and platform reporting looks broken. The fix is a campaign and inventory decision: pause or redirect the ad, and note the hour so the day's conversion rate is not misread.
- A sale page slows down under load. Visitors leave before the page and its tracking finish loading, so sessions and events fall together. Our native ad tracking guide makes the same point about click-to-session drop-off on slow mobile pages. The fix belongs to the store, and the note belongs in your log.
- A bot surge arrives with the traffic. Suspected bot events filtered before delivery protect the bidding signal. A sudden rise in filtered volume is worth logging and worth checking against your traffic sources, but do not hand-block address ranges during the sale. Record the baseline change and review it afterwards with the bot filter tools comparison.
Step 6: Close Cyber Five with a clean reconciliation, not a victory lap
On December 1, before any post-sale analysis, reconcile the full five days in one table, using net backend revenue and actual spend, and let the late conversions land first. Platforms credit conversions inside their windows for days after the click, so a reconciliation run on Monday night understates the platforms and overstates your tracking gap.
Record three things for next year: the final gap per platform and what explained it, every incident with its fix time, and the thresholds you would set differently. File them with your Q4 tracking playbook. That document, written while the sale is fresh, is worth more in October 2027 than any generic checklist, including ours.
What does each alarm usually mean?
| Symptom | First check | Likely cause |
|---|---|---|
| Orders stopped everywhere | Store checkout and payment status | A store incident. Tracking is downstream of a working checkout |
| One platform silent, others healthy | Delivery view for that platform, then its connection status | An expired authorisation, a switched-off sender or a broken integration |
| Delivery shows success, platform shows nothing | Whether the platform's normal delay has passed, then its diagnostics with a test order | Reporting delay, an unmapped or inactive goal, or events sent to the wrong dataset or property |
| Platform purchases far above backend orders | Whether one order created two conversions | Duplicate browser and server copies, or two senders on one destination |
| Platform purchases far below backend orders | Consent holdbacks and click ID presence on the day's orders | A banner change, a landing page without the script, or a redirect stripping click IDs |
| Conversions fine, revenue wrong | The value definition on a sample order | Tax, shipping, currency or refund handling differs between your event and your comparison |
| Everything fell at the same hour as a theme publish | The change log and one test order | The publish removed a script, a pixel or a consent flow |
Work the table from the top. Most Cyber Five tracking incidents are one of these seven, and the first check is deliberately the cheapest one.
How does SignalBridge monitoring fit this routine?
SignalBridge's Tracking Health shows delivery rates per platform and per pixel, and it can email you when delivery drops below a threshold you set, when a platform goes silent or when Meta Event Match Quality falls. In the routine above, that replaces the manual part of the hourly delivery question: instead of polling a dashboard, the named person starts from the alert and the event stream, finds the affected platform and follows the incident steps.
Three limits keep the routine tool-neutral:
- An alert is not a diagnosis. A silent platform can be an expired authorisation, an unmapped goal or a store that genuinely received no clicks from that platform. The test order and the platform's own diagnostics still decide.
- Delivery success is not platform reporting. SignalBridge can show an event as delivered while the platform takes hours to count it, applies its window, or attributes it to the click day. Reconcile in the platform and in your backend, not only in the sender.
- Consent holdbacks are information, not failures. Events held back because consent was denied or not granted appear in your delivery view. During Cyber Five that count is how you tell a lawful gap from a broken one, and it should move with your traffic sources and banner changes rather than sitting at zero.
If you are not using SignalBridge, the same routine runs from each platform's diagnostics plus a spreadsheet. It takes longer per check, which is an argument for assigning one named person rather than for buying a tool mid-sale. Do not install a new tracking tool during Cyber Five to get better monitoring. Install it in December, test it, and let it earn its place in next year's routine. Pricing starts at $29 a month for 20,000 events and two platforms if you are planning that move, and Tracking Health is included rather than sold as an add-on. Start your 14-day free trial today. No credit card required.
FAQ
What is Cyber Five?
Cyber Five is the five-day shopping period from Thanksgiving Day through Cyber Monday. In 2026 that is Thursday, November 26 to Monday, November 30, covering Black Friday on November 27 and the weekend between. Adobe forecasts $47.5 billion in US online sales across Cyber Week in 2026, with $15.1 billion on Cyber Monday alone.
How often should I check conversion tracking during Black Friday?
Check delivery hourly during your peak selling hours, with one named person answering whether the store is taking orders, whether each platform is still receiving events, whether sale landing pages still carry their tracking, and whether spend is behaving. Then reconcile the previous full day once a day before changing any budget. Hourly checks catch breaks; daily full-day comparisons make decisions, because platforms report with delay.
Why do my platform numbers fall behind my store orders during BFCM?
Start with delay and definitions before assuming a break. Platforms report on their own schedules, Taboola attributes a conversion to the day of the click rather than the order day, view-through and window rules differ from your backend, and consent holdbacks remove some orders lawfully. Compare full days after the normal delay has closed, using orders tied to that platform. A gap that survives that comparison is the one to investigate.
What should I do if a platform stops receiving conversions mid-sale?
Treat it as an incident. Confirm the store is still taking orders, check delivery for that platform, and look for an expired authorisation, a switched-off sender or an unmapped goal. Fix delivery only, place a test order from a phone to prove the path, and log what you observed, what you changed and when reporting caught up. Do not create a replacement goal or change the attribution window during the sale.
Should I change budgets based on platform ROAS during Cyber Five?
Base budget decisions on your backend columns: orders tied to the platform and their net revenue against actual spend. Platform ROAS is what the bidding system sees, so a reporting gap matters for optimisation, but pausing a campaign whose backend orders are healthy, because its platform number lagged, turns a measurement delay into a real revenue loss. Note the gap, prove delivery, and decide on audited numbers.
Can I fix a tracking problem during Black Friday, or should I wait?
Fix delivery during the sale and definitions after it. Restoring a script, a sender, a click ID or a consent flow returns you to the tested state and is safe to prove with one test order. Creating goals, changing windows, swapping senders or renaming events changes what your numbers mean, so those wait until December, when you can test the change against a quiet week.
What should I record for next year's BFCM?
The final five-day gap per platform and what explained it, every incident with the time it was found and fixed, the test orders that proved each fix, and the thresholds you would set differently. Filed with your Q4 playbook while the sale is fresh, that record becomes next year's baseline, which is the document a generic checklist cannot write for you.
Related reading
- Last-Minute BFCM Tracking Fixes: What You Can Still Do This Week — the repairs and freeze that come before this routine
- Complete Q4 E-Commerce Tracking Playbook: Black Friday to New Year — the October-to-January calendar around Cyber Five
- How to Prepare Your Tracking for BFCM 2026 (Detailed Guide) — the eight-week preparation version
- The Complete BFCM Tracking Checklist: Don't Lose Revenue on Black Friday — the full audit your freeze was built from
- How to Calculate True ROAS — the backend reconciliation behind the daily table
- What is Event Deduplication? (And Why You're Double-Counting) — when one order creates two conversions
- Native Ad Conversion Tracking: Taboola, Outbrain & Beyond — click-day dating and slow-page drop-off on native campaigns
- 7 Best Bot Filter Tools for Ad Tracking in 2026 (Compared) — the post-sale review for a bot surge
- Complete Guide to Event Match Quality (EMQ) — what a falling match quality score is telling you
- How to Audit Your Tracking Setup (Checklist for E-Commerce) — the December audit these incidents feed into
- What is Server-Side Tracking? (Complete 2026 Guide) — why server delivery keeps working when browser events do not
Sources
- Adobe, 2026 holiday forecast (September 28, 2026): $275.1 billion forecast US online sales for November 1 to December 31, Cyber Week at $47.5 billion, Thanksgiving at $6.9 billion, Black Friday at $12.9 billion and Cyber Monday at $15.1 billion.
- Reuters, US holiday online sales to grow 6.7% (September 28, 2026): the same Adobe forecast reported independently.
Related Articles
Last-Minute BFCM Tracking Fixes for This Week
Last-minute BFCM tracking fixes before Black Friday on November 27: test orders, deduplication, consent, click IDs and server-side checks for this week.
How to Prepare Your Tracking for BFCM 2026
A Black Friday and Cyber Monday tracking checklist for e-commerce: audit your pixel, set up server-side tracking, fix EMQ and avoid data loss at peak traffic.