Checklist

10 consent checks to run before Black Friday ad spend goes up

Ten checks to run before Black Friday ad spend goes up. Each names the request to watch and what Reject or GPC changed on Shopify stores we tested.

In brief

Black Friday is November 27, 2026. Before you raise ad budgets, check what your store sends in four kinds of visit: a fresh visit with no click, a visit where the shopper clicks Reject, one where they click Accept, and one with Global Privacy Control (GPC) turned on. Each check below names the request to watch and gives one result from a Shopify store we tested, with a link to the full test. The results were mixed. On Store AK, Reject stopped all ten ad vendors we count on the product page, while GPC stopped only Meta and TikTok. On Store AN it went the other way: Reject changed nothing we measured, and GPC cut ten vendors to two. We ran no new tests for this page. Every result comes from a test we published between November 15 and November 18, 2026, run over HTTP/1.1 and dated in the linked article. Technical observation, not legal advice.

Set up the four visits

Use a new browser profile or a private window for every visit, so no earlier choice carries over. Open DevTools, turn on Preserve log in the Network panel, and keep the Console open.

  • Fresh: load the home page and click nothing.
  • Reject: click the banner's own reject button (Reject All, Decline, Deny, or whatever your banner calls it), then open a product page.
  • Accept: click Accept, then open the same product page. This is your count of what each vendor sends when it is allowed.
  • GPC: turn GPC on and click nothing. Firefox, Brave and DuckDuckGo have a setting; Chrome needs an extension. Confirm navigator.globalPrivacyControl returns true and the page request carries Sec-GPC: 1.

After each click, run Shopify.customerPrivacy.currentVisitorConsent() in the Console and write down the four values. Run each visit at least twice.

1. What fires before anyone clicks

What to check: which ad vendors receive requests on the home page before the shopper touches the banner.

How to test: Fresh visit. Filter Network by analytics.tiktok.com, facebook.com/tr, googleadservices, doubleclick, bat.bing.com and ct.pinterest.com, and count.

What we saw: On Stores AK, AV and AY, analytics.tiktok.com received Pageview and LandingPageView on the home page before anyone touched the banner, in every run (analytics.tiktok.com after Reject). Write down what fires here. You will compare the Reject and GPC visits against this list.

2. Meta's PageView on the landing page

What to check: whether Meta's PageView leaves before the shopper has made a choice on the page an ad sends them to.

How to test: open your home page with utm_source=facebook and a test fbclid in the URL, and click nothing. Filter by facebook.com/tr, find the request with ev=PageView, and check its status code.

What we saw: On the four CookieFirst stores we tested, Stores AT, AU, AV and AW, before anyone clicked, each store's Meta pixel sent a PageView that reached Meta with a 200 (CookieFirst Shopify Reject test).

3. Does Reject reach Shopify, and how fast?

What to check: whether the banner passes the choice to Shopify's Customer Privacy API, and what leaves in the seconds before it does.

How to test: Reject visit. Run Shopify.customerPrivacy.currentVisitorConsent() before the click and again right after. Empty values mean no choice has reached Shopify. Stay on the page for about ten seconds after the click and keep logging, then open a product page and filter by facebook.com/tr and analytics.tiktok.com.

What we saw: On CookieFirst Stores AT and AV, Shopify's API switched to "no" about 0.8 seconds after Deny, and the product page sent no Meta events. Store AU does not load CookieFirst's sh-customer-privacy.js. After Deny, Shopify's API stayed empty, and Shopify's Meta pixel sent PageView and ViewContent from the product page (CookieFirst Shopify Reject test). Timing differed too. On Store AY (Decline), the home page still sent EngagedSession events to analytics.tiktok.com 5.1 to 6.5 seconds after the click, in all three runs, and the product page then sent nothing. On Stores AK and AV, the browser sent nothing more to analytics.tiktok.com after Reject (analytics.tiktok.com after Reject).

4. Count every vendor after Reject, one by one

What to check: each ad vendor's request count, Reject against Fresh. A drop in Meta tells you about Meta only.

How to test: Fresh and Reject visits to the same product page. Count per vendor: Meta, Google Ads, Pinterest, Microsoft UET, Amazon, Reddit, and any other ad host you use. Then add an item to the cart, open checkout, stop when the checkout page loads, and count again. You do not need to place an order.

What we saw: On Store AR, which uses OneTrust, the product page after "Reject All" sent no Meta requests and one Google Ads request. Pinterest (4), Amazon (3), Microsoft UET (2) and Reddit (1) sent the same counts as before, in all three runs (FedEx quarterly opt-out test).

5. Pixels that bypass Shopify's channel

What to check: Meta pixels that run outside Shopify's Facebook and Instagram channel, such as one loaded through Google Tag Manager.

How to test: Reject visit. On the product page, open each facebook.com/tr request and read the a parameter. a=shopify_web_pixel marks Shopify's channel pixel. Any other value, or none, means a pixel outside that channel.

What we saw: On Store AZ, which uses Pandectes, Shopify's Meta channel pixel sent nothing from the product page after Reject. A second Meta pixel, loaded through a Google Tag Manager template, sent an event named "Engagement Time 20s" from the product page in all three Reject runs (Pandectes Shopify Reject test).

6. The reject click itself

What to check: whether Meta's automatic button-click tracking reports the reject click.

How to test: Reject visit. Filter by facebook.com/tr and look at the moment of the click for ev=SubscribedButtonClick. Its buttonText field holds the button label.

What we saw: On Pandectes Stores AZ, BA and W, pressing the reject button sent Meta a SubscribedButtonClick event with the button's label. On Store AY, Meta received no SubscribedButtonClick (Pandectes Shopify Reject test).

7. GPC, as its own visit

What to check: what GPC changes, separately from Reject, and whether Shopify reads it on the first page. The two can give opposite results on the same store.

How to test: GPC visit with no click. Run currentVisitorConsent() as the home page loads and check that sale_of_data reads "no". Then count vendors on the product page and compare with the Fresh visit.

What we saw: On Store AK, Shopify's API read sale_of_data: no from the first page load. Reject stopped all ten vendors we count there, but GPC stopped only Meta and TikTok. On Store AN, Reject changed nothing we measured, and GPC cut ten vendors to two. On Store AR, OneTrust's cookie recorded isGpcEnabled=1, and the product page sent requests to the same seven vendors as a fresh visit (FedEx quarterly opt-out test).

8. Cookies written before the click

What to check: ad cookies that were set before the shopper chose, and whether they are still there after Reject.

How to test: Reject visit. Note cookie names in Application > Cookies before the click, then again at the end of the visit. Names are enough; you do not need the values.

What we saw: After Reject, none of the four Pandectes stores, Stores AY, AZ, BA and W, had Shopify's _shopify_marketing or _shopify_analytics cookies at the end of the run, and the _fbp cookie each store set before the click was still there (Pandectes Shopify Reject test).

9. Does your banner show up for the shoppers your ads reach?

What to check: whether the banner appears at all for visitors from the places you advertise to.

How to test: Fresh visit from each region you target. Note whether a banner appears, and read currentVisitorConsent() without clicking.

What we saw: Store AX runs CookieFirst but showed our US visitor no banner. Without a click, CookieFirst.consent returned all four categories as true and Shopify's API returned "yes". The home page sent three Meta events and the product page two (CookieFirst Shopify Reject test).

10. Save a baseline before the sale

What to check: a dated record of what your store sends today, before the last Black Friday app or pixel goes in.

How to test: Sign in and run the free scan (button below) on your store URL. It is one fresh browser visit from the US outside California, to the URL you enter only, and it records cookies, requests and screenshots. It does not click the banner, open other pages or turn on GPC, so checks 2 to 9 still need the visits above. Run it again after your last change for the sale, and compare.

What we saw: In our FedEx test we ran each state three times per store. Most counts matched exactly, but a few vendors varied by one or two requests between runs (FedEx quarterly opt-out test). Compare several runs before you trust a count.

What to write down

For each visit: the date, time and your location; the state (Fresh, Reject, Accept or GPC) and the exact button label; Shopify's four consent values before and after the click; the request count per vendor on the product page and at checkout; and how many runs matched. Keep the log files or screenshots with the record. For more on what each test covers, see Reject All testing.

Limits

Every result on this page comes from tests we published earlier, on public Shopify stores, from US connections, over HTTP/1.1, between November 15 and November 18, 2026. Stores change their setups, and a later run can differ. A browser log shows requests leaving the browser. It can't show server-side sending such as Meta's Conversions API. These results describe the stores we tested, not Shopify stores in general. Store letters match the linked articles.

FAQ

What should I test before Black Friday ads go live?

Four visits in clean browser profiles: no click, Reject, Accept, and GPC on. Count requests per ad vendor on a product page and at checkout, and read Shopify.customerPrivacy.currentVisitorConsent() after each click.

Is testing the Reject button enough?

Not on the stores we tested. On Store AN, Reject changed nothing we measured, while GPC cut ten vendors to two. On Store AK, Reject stopped all ten vendors and GPC stopped two.

My banner recorded Deny. Did the pixels stop?

Check the network as well as the banner. On Store AU, the banner took the Deny click, but Shopify's API stayed empty and Shopify's Meta pixel sent PageView and ViewContent from the product page.

Does every Shopify store show US visitors a banner?

Not in our tests. Store AX runs CookieFirst but showed our US visitor no banner, and its Meta pixel sent events on the home page and the product page without a click.

Can a browser test show Conversions API events?

No. Server-side sending such as Meta's Conversions API runs from the merchant's server, so it does not appear in the browser's network log.

How many runs does each visit need?

We ran each state three times per store. Most counts matched exactly, but a few vendors varied by one or two requests between runs, so one run per state is too few to trust.

Sources

These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.

    Black Friday Consent Checklist Before Ads | ConsentProbe