Black Friday can change the shape of a normal week. More people may arrive at once, promotions send visitors to pages they have not seen before, and small checkout or navigation problems become harder to ignore. Preparing your website analytics before the rush gives your team a clearer way to see what is happening and where to investigate.
In 2026, the main Black Friday window runs from November 24 through November 30. Use the days before it to check your tracking and choose the questions you want your reports to answer. Analytics will not make a site handle more requests, but it can help you notice changes and respond with better information.
1. Decide what you need to learn
Start with a short list of important journeys. For an online shop, that might be a visitor landing on a campaign page, viewing a product, adding it to a cart and reaching checkout. For a service business, it could be reading an offer, opening a plan page and completing a contact form.
Choose the key pages and actions your team will watch. Keep the list small enough to use during a busy day. If every page and event is treated as equally important, the signals that matter can get lost in the noise.
2. Set a useful baseline
Look at a normal period before the campaign and note the measures that help explain your chosen journeys: visitor activity, popular entry pages, navigation between pages and the points where people leave. If you have comparable dates from a previous campaign, use them as context, not as a promise that this year will behave the same way.
Write down the date range, timezone and any changes you already know about, such as a new landing page or a different promotion. That record makes it easier to tell a genuine shift from a comparison that used different dates or pages.
3. Check tracking before traffic arrives
Confirm that the Hitsteps tracking code is present on the pages you want to measure and that the selected website is receiving visits. Use one tracking setup for the site; installing a second copy can count activity twice. Check key pages on desktop and mobile, and make sure campaign landing pages are included.
Then review which features your team has enabled and can access. Godview gives a real-time view of visitors. Heatmaps and session recordings are separate tools with their own plan and site-setting requirements. Form and error tracking can add useful context where available, but the tracking code by itself does not enable every feature. Verify your own setup instead of assuming a feature is collecting data.
Hitsteps has a Free plan. Check the current feature access for your site before you make heatmaps or recordings part of your campaign workflow.
4. Watch the journey, not only the total
During the campaign, a larger visitor count is only one part of the picture. Check which pages people arrive on, what they view next and where a journey appears to stop. Compare the pattern with your baseline and investigate meaningful changes rather than reacting to every short-lived fluctuation.
When an unexpected pattern appears, use the detail available to your team. A heatmap can show where visitors clicked or scrolled on a page. A session recording, when enabled, can help you review an individual journey. Form or error information can help narrow down an issue when those features are available. These views provide evidence to investigate; they do not tell you every visitor’s intention or prove that one change caused a result.
5. Give the team a simple response plan
Decide who will check analytics and when. Agree on what should prompt a closer look, such as an important page receiving visits but showing an unexpected next step, or an error appearing around a form. Keep a short incident note with the time, affected page, what you observed and what your team changed.
Analytics is one input to that response. Pair it with your site’s own uptime, application and hosting checks. If the site slows down, your technical monitoring and infrastructure team need to investigate capacity and server health; visitor analytics alone cannot diagnose or fix those conditions.
After November 30, compare the campaign with your baseline using the same definitions and date boundaries. Record what changed, what remains uncertain and what you would prepare differently next time. A clear, honest review is more useful than treating one busy week as a forecast.
See the analytics view
Try the live demo with no signup: Open the Hitsteps Godview demo. It shows example data from a made-up shop, not real visitors from your website.
