Checklist

What Deny changed on four CookieFirst Shopify stores

We clicked Deny on 4 Shopify stores running CookieFirst. On Store AU, which lacks sh-customer-privacy.js, Shopify's Meta pixel sent on the next page.

In brief

We tested four Shopify stores that show a CookieFirst banner to US visitors, Stores AT, AU, AV, and AW. Three of them load CookieFirst's sh-customer-privacy.js, the script CookieFirst's Shopify guide adds so the banner can talk to Shopify's Customer Privacy API. On Stores AT and AV, Shopify's consent API switched to "no" about 0.8 seconds after Deny, and the product page sent no Meta events. Store AU does not load the script. After Deny, Shopify's API stayed empty, and Shopify's Meta pixel sent PageView and ViewContent from the product page in both rounds. On Store AW the switch to "no" came late in 2 of 5 Reject All runs, and the next page sent three Meta events. Technical observation, not legal advice.

What CookieFirst documents for Shopify

CookieFirst offers a Shopify app and a manual embed. For the manual embed, its installation guide adds a second script, sh-customer-privacy.js, under the banner code "to make the banner communicate with the Shopify customer privacy api". A separate article tells merchants to switch off Shopify's own banner but keep the Customer Privacy regions on, so the API keeps controlling Shopify's built-in analytics, Google, and Facebook integrations.

CookieFirst's public API page says CookieFirst.consent returns the visitor's current choice, and that changing consent after the first choice reloads the page. Its autoblock article says blocking needs the newer consent.js embed placed high in the head. All four stores loaded CookieFirst's no-autoblock banner build.

How we tested

On 2026-11-15 (PST) we ran each store three ways: Fresh (no click), Reject (the banner's Deny or Reject All button), and Accept; see other Reject tests we have run. Every run used a new headless Chrome profile on a direct US connection, en-US, with the clock set to Los Angeles time. CookieFirst's own consent record labeled the visit "US".

On the home page we waited for the banner, clicked about 4 seconds later, and read Shopify.customerPrivacy.currentVisitorConsent() every quarter second for 8 seconds. Then we opened a product page, read the API again for 8 seconds, and stayed about 90 seconds in total. We did not add anything to the cart.

We ran the full set twice. Our test network made Chrome reuse one connection across different hosts under HTTP/2, which broke some cross-host requests, so the second round ran with HTTP/2 switched off. Delivery numbers below come from the second round. We ran Store AW's Reject three more times because its first two runs disagreed. Chrome's network log tells us whether a server answered each request.

Before the click

None of the four stores had a stored choice when the page opened. On Stores AT, AU, and AV, Shopify's consent API returned empty values for all four purposes. On Store AW it returned "yes" in some runs and empty values in others.

Before anyone clicked, each store's Meta pixel sent a PageView that reached Meta with a 200. Store AW sent five to seven Meta events on the home page. On Stores AT, AV, and AW, every Google hit before the click that carried a gcs value had G111, Google's code for ad and analytics storage both granted. Store AU's hits were a mix of G111 and G100. Store AV also sent two TikTok events and three Pinterest requests before the click.

What Deny changed on each store

Swipe to see Google

Reject on Stores AT, AU, AV, and AW. HTTP/1.1 round, 2026-11-15. Store AW's other Reject runs are in the next section.

StoreButtonShopify API after the clickMeta events on the product pageTikTok and Pinterest on the product pageGoogle hits on the product page (gcs)
ATDenyempty to no, 0.77 s0noneGA4 1 (G100, user_engagement); Google Ads 0
AUDenyempty, stayed empty2, PageView and ViewContentnoneGA4 5 (G100); Google Ads 8 (G100)
AVDenyempty to no, 0.76 s0TikTok 0, Pinterest 0GA4 1 (G100, user_engagement); Google Ads 1 (google.com/ccm/collect, no gcs)
AWReject Allempty to no, 1.75 s0noneGA4 4 (G100); Google Ads 4 (G100)

Fresh and Accept on all four stores sent 2 to 6 Meta events from the product page.

On Store AT, Deny switched Shopify's API from empty to "no" 0.77 seconds after the click. The product page sent no Meta event and no Google Ads request. Its one GA4 hit, a user_engagement event sent as the product page opened, carried gcs=G100, meaning both storage types denied.

Store AV followed the same pattern, with the switch at 0.76 seconds. Its product page sent nothing to Meta, TikTok, or Pinterest, all three of which had fired before the click.

Store AU, where Deny did not reach Shopify's API

Store AU loads CookieFirst's consent.js without sh-customer-privacy.js. After Deny, CookieFirst.consent showed performance, functional, and advertising as false. Shopify's API kept returning empty values until the end of the run.

The page reloaded 0.6 seconds after the click and sent a new Meta PageView. On the product page, Shopify's Meta pixel sent PageView and ViewContent, and Meta answered both with a 200. Both rounds gave the same result. Every Meta request on this store carried a=shopify_web_pixel, the marker of Shopify's Facebook and Instagram channel.

On the same store, every GA4 and Google Ads hit from the reload on carried gcs=G100, and the product page hits also had npa=1.

Store AW, where the switch came late in 2 of 5 runs

Store AW loads the script, and in three of five Reject All runs its API read "no" 1.7 to 1.8 seconds after the click. Those runs sent no Meta event from the product page, and their Google hits carried gcs=G100.

In the other two runs the API had not switched before we left the home page. On the product page, Meta received ViewContent, PageView, and ViewContent, and Google Ads received nine hits with gcs=G111. In one of these runs the API already read "no" 0.33 seconds after the product page opened, and the Meta events left at 1.6 seconds. We did not find out why the pixel still sent after the API read "no".

In all five runs, about one second after the click and before the switch, Meta also received a ViewContent and a PageView from the home page.

Meta received the click

On all four stores, pressing Deny or Reject All sent Meta a SubscribedButtonClick event. Its buttonText field held the button's label, "Deny" or "Reject All", and Meta answered with a 200. Accept sent the same event with "Accept all". These events left at the moment of the click, before Shopify's API changed.

Where CookieFirst records the choice

Each click sent one POST to api.cookiefirst.com/prod/consent. The body had preferences, action, apiKey, config_version, consent_policy, granular_metadata, tcstring, acstring, url, visitor_country, visitor_region, and visitor_id. After Deny, preferences was necessary true and performance, functional, and advertising false, with action set to "store". All eight POSTs in the second round got a 204 on the preflight and a 200 on the POST. Fresh runs sent none.

CookieFirst's Shopify app listing says proof of consent is "safely stored in European Datacenters." Our log shows the browser sending the record and the server's status code. It can't show what CookieFirst does with the record.

A CookieFirst store with no US banner

We also loaded a fifth Shopify store, Store AX, that 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's Shopify app lists "Hide banner outside EEA and UK" as a plan feature. We only ran Fresh on this store.

Check your own CookieFirst store

  1. Open your store's page source and search for sh-customer-privacy.js. If only consent.js or banner.js is there, compare your setup with CookieFirst's Shopify installation guide.
  2. Open a new private window, open DevTools, and in Console run Shopify.customerPrivacy.currentVisitorConsent(). Empty values mean no choice has reached Shopify yet.
  3. Click your banner's Deny button and run the same command. On Stores AT and AV it read "no" within a second.
  4. In Network, filter by facebook.com/tr and open a product page. Check the ev value of each request.
  5. Filter by cookiefirst.com and find the POST to /prod/consent. Its preferences field shows what CookieFirst saved.

Limits

We tested five stores from one US connection on one evening, two rounds per store plus three extra Reject runs on Store AW. We used headless Chrome. We did not check out, test other regions, or see any store's CookieFirst or Shopify settings. A browser log can't show server-side sending such as Meta's Conversions API. Our first round ran over HTTP/2 on a network that merged hosts onto shared connections, so we report delivery from the second round only, and we did not check Klaviyo delivery, which the second round's HTTP/1.1 connections did not get through.

FAQ

Does CookieFirst connect to Shopify's Customer Privacy API?

CookieFirst's Shopify guide adds a script, sh-customer-privacy.js, for that. On the three stores we tested that load it, Shopify's API changed after Deny. On Store AU, which does not load it, the API stayed empty after Deny.

Does CookieFirst show its banner to US visitors on Shopify?

On Stores AT, AU, AV, and AW it did. On Store AX our US visitor saw no banner, and CookieFirst reported all categories as accepted without a click.

Did Meta receive events after Deny on these CookieFirst stores?

On Stores AT and AV, the product page sent no Meta events after Deny. On Store AU it sent PageView and ViewContent in both rounds. On Store AW it sent three events in 2 of 5 runs.

Is the Deny click sent to Meta?

On all four stores, the click sent Meta a SubscribedButtonClick event with the button's label, such as "Deny", in its buttonText field.

Where does CookieFirst send my choice?

To api.cookiefirst.com/prod/consent, as one POST per click. After Deny the preferences field listed performance, functional, and advertising as false.

Sources

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

CookieFirst Shopify Reject Test on 4 Stores | ConsentProbe