Black Friday tracking checklist: what to test the week before

Black Friday is the worst weekend for tracking to break: spend is at its peak and bidding algorithms learn from the conversions they receive. Freeze tag changes a week before, place one real test order and follow it into every ad platform, and check the parts that change for the sale: discounts, banners, landing pages and redirects.

Published 2026-10-27

Why the week before matters

Automated bidding in Google Ads, Meta and TikTok optimises towards the conversions it is told about. If purchases stop arriving, arrive twice, or arrive with the wrong value, the algorithm adjusts bids on wrong data during the days you spend most. Platform status pages are slow to say so: Google Ads, for example, marks a purchase action as awaiting conversions when none were recorded in the last seven days. A four-day sale is over by then.

Sales weeks are also when sites change most: new banners, pop-ups, landing pages, discount apps and checkout tweaks. Each one can move or remove a tag. The checks below take an afternoon.

1. Freeze tag and checkout changes

Agree a date, ideally a week before the sale, after which nothing changes in the tag manager, the consent banner, the checkout or the theme without a test order afterwards. If a change has to go out, the person who ships it runs step 2 again.

2. Place one real test order and follow it everywhere

Buy something cheap with a discount code, the way a customer would, from an ad click if you can. Then find that order in each platform:

GA4: open DebugView (with the Tag Assistant debug mode on) or the Realtime report and look for the purchase event with its transaction_id, value and currency.
Google Ads: under Goals → Conversions, check that the purchase action's status is not Misconfigured or Needs attention. Tag Assistant shows whether the conversion tag fired on the confirmation page.
Meta: in Events Manager, the Test Events tab shows the Purchase event from your browser, and from the Conversions API if you use it.
TikTok, Microsoft, Pinterest and others: each has a test or diagnostics view in its events manager. Check every platform you will spend on during the sale.

Write down the order number and the value you paid. You will need both for the next two steps.

3. Check the value after the discount

Black Friday orders carry larger discounts than usual, so a value that ignores them inflates your return on ad spend exactly when you are judging the sale. Compare the value each platform received with what you paid:

The value should be the amount after discounts. Google Analytics does not subtract the discount parameter for you: the item price should already be the discounted price.
Decide whether value includes tax and shipping, and make every platform use the same rule.
currency must be a three-letter ISO code (USD, EUR, SEK). A missing currency can make the value unusable.
A value of 0 or a fixed placeholder value (often 1) means the tag is not reading the order total.

4. Make sure every order counts once

Duplicate purchases are as damaging as missing ones: they tell the algorithm a campaign sells better than it does.

Google Ads and GA4: send the order number as the transaction ID (transaction_id). Google Ads uses it to drop a second conversion with the same ID, for example when a customer reloads the confirmation page.
Meta pixel plus Conversions API: send the same event name and the same event ID (eventID in the pixel, event_id on the server) from both. Meta only deduplicates events received within 48 hours of each other.
Two tags for the same platform: a theme, a shop app and the tag manager can each install a pixel. Two pixel IDs, or the same event twice per page, show up in the scan as duplicate findings.

5. Test the cookie banner both ways

If the banner was restyled or moved for the sale, test it again. Open the site in a private window and check two paths:

Accept: tags start, and Google receives a consent update with granted values.
Reject all: advertising pixels stay quiet, and Google tags only send cookieless pings if you use Consent Mode.

The free scan runs both paths in a real browser and reports what each platform sent.

6. Test every campaign landing page and redirect

Sale campaigns often point at new landing pages, short links or promo URLs that redirect to a collection. If a redirect drops the query string, the ad click ID (gclid, fbclid, ttclid, msclkid and others) is lost and the sale cannot be tied back to the ad. Open each final URL from your ads with a test click ID added and check it is still in the address bar after the page loads.

7. Decide who watches the numbers, and how

During the sale, check once each morning:

Orders in your shop for the previous day, against purchases reported by GA4 and each ad platform. The numbers never match exactly, but the ratio should stay roughly the same from day to day. A sudden drop on one platform is the signal.
The status of the purchase conversion action in Google Ads and the event overview in Meta Events Manager.

Write down who can fix a tag over the weekend and how to reach them. A broken tag found on Saturday morning and fixed on Monday costs most of the sale.

The checklist

Freeze date agreed and shared.
Test order placed with a discount code; order number and value noted.
Purchase found in GA4, Google Ads, Meta and every other platform you spend on.
Value is after discount, same tax and shipping rule everywhere, currency set.
Transaction ID and Meta event ID sent; no second pixel.
Banner tested with accept and with reject all.
Every campaign landing page keeps its click ID through redirects.
Morning check and weekend contact agreed.

Run the free scan: it loads your page in a real browser, accepts and rejects the banner, follows redirects with test click IDs and reports what every platform received.

Check your own site

Sources

Based on the platforms' public documentation; menus and names change, so check the linked pages if a step looks different.