A Black Friday landing page has one job: take a shopper from the ad headline to a product in the cart at the right price. If a filter breaks along the way, the price on the list differs from the cart, or the code field rejects a valid entry, the discount alone will not save the sale. A desktop preview rarely reveals these faults, because your team already knows where to click.
This guide splits the work into two stages: testing the path to checkout before launch and observing the first 48 hours, followed by a short review recorded as tasks. Team preparation is covered in our guide to Black Friday customer support. You will not find load testing or page speed measurement here either, since those need different tools.
What to check on a promotion page before launch
List the elements a shopper must get through to buy a promoted product, each with a specific test and a description of what counts as a blocker.
Scroll the table sideways to see all columns.
| Element | Pre-launch test | Blocker signal |
|---|---|---|
| Entry from ads and newsletter | Open every campaign link on a phone | Home page instead of the offer, or an empty list |
| Filters and sorting | Narrow the list by category, size and price | No results, or the filter resets after going back |
| Price display | Compare the price on the list, product page and cart | Different amounts or no reference price |
| Product page | Choose a variant and add it to the cart | Disabled button with no explanation |
| Code field | Enter a valid, an invalid and an expired code | The message does not say what to fix |
Pick three products for the test: the one you advertise most, one with variants and one the promotion does not cover. The last one shows whether the page is honest about the missing discount. Note each result right away with the page address and device.
Phone and filters under real shopper conditions
Walk the whole path on a phone held in one hand, without zooming and without saved browser data. Check that the promotion banner does not push the product list below the first screen and that a countdown or code bar does not cover the add-to-cart button. Cookie, newsletter and chat windows should not stack over the same area.
Filters fail more often on a promotion page than in a regular category, because the list mixes products from different departments. Apply a filter, open a product and go back with the back button: the list should keep the selection and the scroll position. For weaker results on phones in general, see our guide to mobile conversion.
Price display: the same amount on every screen
The promotional price appears in several places: the banner, the list, the product page, the cart and the order summary. Each may pull data from a different source, so compare amounts for all three test products. Also check that the reference price is visible and readable on a narrow screen.
For sales to consumers in the EU, Article 6a of Directive 98/6/EC, inserted by Directive (EU) 2019/2161, requires every announcement of a price reduction to state the lowest price the trader applied during a period of at least 30 days before the reduction. UOKiK, the Polish consumer authority, notes that this duty has applied in Poland since 1 January 2023. EUR-Lex, UOKiK. The sources describe the obligation but do not settle how to calculate the price in your store, and other markets have their own rules; this text is not legal advice.
The test does not assess legal compliance, only consistency: does the shopper see the same information on every screen? If the reference price appears on the product page but disappears from the promotion list, log it as a blocker and pass it to whoever owns pricing. If a shopper then asks about the pre-reduction price in chat, the guide to questions about the lowest 30-day price has ready replies.
From product page to cart and code field
- Add a product with a variant.Pick a size or colour and check that the cart shows that variant at the product page price.
- Change the quantity and remove an item.The cart should recalculate the total without jumping to an empty view and without dropping the discount.
- Enter a valid code.Check that the discount lowers the total and that the message confirms which items it applies to.
- Enter an invalid and an expired code.The message should say what is wrong and must not clear the cart.
- Reach payment and stop there.Check the summary, delivery cost and discounted price, but do not place a real order.
Error messages are part of the path, not an extra. A bare "Invalid code" pushes people to retype or leave the store. A line such as "This code is valid from 00:00 on Friday" or "This code excludes the Outlet category" lets the shopper decide what to do. Reasons a code gets rejected, and how to reply to the customer, are covered in our guide to a discount code that does not work.
If all this works but shoppers still abandon purchases, look further on, at the checkout form. The method of breaking the path into stages is explained in our article on how to find the cause of abandoned carts. The test should end with a list of blockers, each with an owner and a fix date.
The first 48 hours: recordings and clicks at peak
A pre-launch test will not catch everything, because real shoppers use other phones, arrive from different campaigns and combine filters nobody thought of. So plan short behaviour reviews on the promotion page for the first two days. The aim is to find where people get stuck before the ads send more visitors there.
In Meetlead Analytics you can filter session recordings by visited page, device, source and campaign so you can watch phone visits that came from a specific newsletter. The click map ranks the most-clicked elements and, when recordings are retained, links to the related visits. Scroll depth shows whether people reach the products below the banner, and a configured purchase goal shows the funnel all the way to the order. Enable heatmaps and recordings for the site before launch, because you cannot replay visits that were never captured.
- After two hours, watch a few phone recordings that ended on the promotion page.
- Check the click map for banners and elements that look clickable but lead nowhere.
- Compare entries from each campaign with the visits that reached a product page.
- Read chat questions about price, codes and size availability.
- After 24 and 48 hours, repeat the review and note what changed after fixes.
Treat bursts of clicks on one element, or clicks with no visible effect, as a hint about where to look rather than proof of a bug. Our guide to rage clicks and dead clicks explains how to tell them apart and confirm the cause. During the peak, fix only confirmed purchase blockers and log everything else for later.
A post-promotion review recorded as tasks
After the campaign, gather the observations in one place while the context is fresh. Each one should include the page address, device, a recording link and a description of what the shopper was trying to do. In Meetlead Projects you can link a task to a recording, so whoever ships the fix can return to the same visit. Below is a sample task from a fictional clothing store.
Size filter loses the selection after returning from a product page (phone, Safari). Page: promotion list. Observation: in several recordings shoppers return and reset the filter or leave. Reproduction: confirmed on a test phone. Expected result: the list keeps its filters and position. Due: before the next campaign.
Rank fixes by purchase impact and certainty using the simple scoring in our guide to prioritising fixes from heatmaps and recordings. If a change would reach the site just before the holidays, first check the rules in our piece on freezing website changes.
Questions about a Black Friday promotion page
When should you test the promotion page before launch? Early enough to fix the blockers you find and run the test again. Do the first pass once final products and prices are in place, and the second after the last copy or code changes. Testing a draft without real prices misses the most important check: consistent amounts across screens.
Can you change the page during the promotion based on recordings? Yes, but only when an observation points to a confirmed purchase blocker, such as a broken filter or button. Save design changes and new banners for the review. Log every peak-time fix with its time so you can separate the periods before and after it in your data.
