Checklist
What Reject changed on four Pandectes Shopify stores
We clicked Reject on 4 Shopify stores running Pandectes. Shopify's API read no in 0.3 s, but on Store AZ a GTM-loaded Meta pixel sent one event per run.
In brief
We tested four Shopify stores that show a Pandectes banner to US visitors, Stores AY, AZ, BA, and W. On Stores AY, AZ, and BA, Shopify's Customer Privacy API read "no" within 0.3 seconds of the Reject click in all nine Reject runs. On Stores AY and BA the product page then sent nothing to Meta, Google Ads, Pinterest, or Snap. On Store AZ, Shopify's Meta channel pixel sent nothing from the product page, but a second Meta pixel, loaded through a Google Tag Manager template, sent one custom event from the product page in all three runs. Store W's Shopify API already read "no" before anyone clicked, and Decline did not change its product page counts. Technical observation, not legal advice.
What Pandectes documents for Shopify
Pandectes' help article on the Customer Privacy API says that when a visitor picks Accept, Reject, or a custom selection, "the banner reports that choice to Shopify through the official API." It adds that "Everything afterwards belongs to Shopify," meaning which web pixels load and how sales channels follow the choice, and that a Shopify pixel set to Not required "will run regardless of consent."
The article tells merchants to expect four empty strings from Shopify.customerPrivacy.currentVisitorConsent() before a visitor decides. It warns that "in regions where Shopify is not configured to require consent, everything is allowed by default and the test proves nothing." It also says not to judge the integration by "network requests." This test reads them anyway, because the question is what the browser sent.
How we tested
On 2026-11-16 (PST) we ran each store five or six times: Fresh (no click) twice, Reject three times, and Accept once; see other Reject tests we have run. Each run used a new headless Chrome profile on a direct US connection, with HTTP/2 switched off because our test network otherwise produces false errors.
We clicked about 4 seconds after the banner appeared and read currentVisitorConsent() every quarter second for 8 seconds. Then we opened a product page and stayed about a minute without adding to cart. Reject meant the banner's own button: Decline on Stores AY and W, Use Necessary Cookies Only on Store AZ. Store BA's first layer has only Preferences and Accept, so we opened Preferences and clicked Reject all.
Before the click
Stores AY and BA returned empty values from Shopify's API, as Pandectes' article describes. Store AZ returned "yes" for marketing, analytics, and preferences in all six runs before any click, while Pandectes' own getCurrentConsent() showed no decision. Store W returned "no" in all six runs before any click.
Every store contacted Meta before the click. Store AY sent three PageView events, 12 to 17 TikTok requests, 8 Pinterest requests, 6 Google Ads requests, and 1 Snap request, and its Google tag started with all four storage types granted. Store AZ sent a PageView from Shopify's Meta channel pixel. Store BA sent a channel PageView, 2 TikTok events, and 3 Pinterest requests. Store W sent a PageView from a non-channel Meta pixel and 6 to 9 Pinterest requests.
What Reject changed on each store
Swipe to see Google
Reject on Stores AY, AZ, BA, and W. HTTP/1.1, 2026-11-16.
| Store | Reject button | Shopify API, before to after | Meta events on the product page (Fresh / Reject) | Google Ads requests on the product page (Fresh / Reject) | Other requests on the product page after Reject |
|---|---|---|---|---|---|
| AY | Decline | empty to "no" | 7 / 0 | 12 / 0 | GA4 2, Bing 2, TikTok 1 (/api/v2/pixel/inter) |
| AZ | Use Necessary Cookies Only | "yes" to "no" | 2 / 1 (GTM template pixel) | 15 to 27 / 8 to 10 (G100) | GA4 10 to 13 (G100), Bing 1 |
| BA | Preferences, then Reject all | empty to "no" | 2 / 0 | 15 / 0 | GA4 1, in one of three runs |
| W | Decline | "no" to "no" | 0 / 0 | 2 to 4 / 3 to 6 (no gcs) | GA4 1 |
Counts are per run, three Reject runs and two Fresh runs per store. Every request in the table got an answer from the server.
Store AY, where Decline stopped Meta and Google Ads
On Store AY, which runs Pandectes' newer banner, Decline switched Shopify's API from empty to "no" 0.25 seconds after the click in all three runs, and the Google tag got an update denying all four storage types.
With no click, Store AY's product page sent 7 Meta events (4 PageView, 3 ViewContent), 12 Google Ads requests, 7 to 8 Pinterest requests, and 12 to 13 TikTok requests. After Decline it sent 0 Meta, 0 Google Ads, 0 Pinterest, and 0 Snap requests. What remained was two GA4 requests, two requests to bat.bing.com/actionp/0, and one request to TikTok's /api/v2/pixel/inter path, the same in all three runs. On the home page, TikTok received four EngagedSession events 4.5 to 7 seconds after Decline, in every run.
Store AZ, where a GTM-loaded Meta pixel sent one event
On Store AZ, which runs the legacy banner, Use Necessary Cookies Only switched Shopify's API from "yes" to "no" within 0.3 seconds in all three runs.
We saw two Meta pixels on Store AZ. Shopify's channel pixel (a=shopify_web_pixel) sent PageView and ViewContent from the product page in both Fresh runs and none after Reject. The second pixel carried a=tmSimo-GTM-WebTemplate, the marker of a Google Tag Manager template. It sent an event named "Engagement Time 20s" from the product page in all three Reject runs, and Meta answered each with a 200. This pixel was loaded through Google Tag Manager, not through Shopify's Facebook and Instagram channel or an app pixel in Shopify's customer events.
After Reject, Store AZ's product page also sent 10 to 13 GA4 requests and 8 to 10 Google Ads requests, all answered. Every one with a gcs value had G100, meaning ad and analytics storage both denied.
Store BA, where Reject all sits behind Preferences
Store BA's banner shows Preferences and Accept, with Reject all inside the Preferences panel. After that second click, Shopify's API read "no" 0.26 seconds later in each of the three runs.
With no click, the product page sent 2 Meta events from Shopify's channel pixel, 2 TikTok events, 4 Pinterest requests, 3 to 4 Snap requests, 3 Reddit requests, and 15 Google Ads requests. After Reject all it sent none of these. The only request left was a single GA4 hit in one of the three runs.
Store W, where Shopify already read no
Store W's Shopify API read "no" before the click, and Decline left it there. Its product page sent 0 Meta and 0 TikTok events in both Fresh runs and all three Decline runs, and still sent 2 to 6 Google Ads requests without a gcs value, plus one GA4 hit. After Accept, Shopify's API switched to "yes", and the product page sent 3 Meta events from Shopify's channel pixel, 2 TikTok events, and 15 Google Ads requests.
When we tested Store W for our Meta Pixel after Reject article on 2026-10-29, it loaded fbevents.js but sent no Meta event; on 2026-11-16 it sent one Meta PageView from a pixel outside Shopify's channel before any click, in every run.
Meta received the click
On Stores AZ, BA, and W, pressing the reject button sent Meta a SubscribedButtonClick event, answered with a 200. Its buttonText field held the button's label: "Use Necessary Cookies Only" on Store AZ, "Decline" on Store W, and on Store BA two events, "Preferences" and then "Reject all". On Store AY, whose buttons sit inside a pandectes-cmp element, Meta received no SubscribedButtonClick; we did not check why.
Where the browser sent the choice
Each Reject or Accept click sent one POST to consents.pandect.es with the fields path, domain, countryCode, stateCode, status, and preferences. After Reject, status was "deny" and preferences was 7. After Accept, status was "allow" and preferences was 0. All 16 POSTs got a 200, and Fresh runs sent none.
The three legacy-banner stores wrote a cookie named _pandectes_gdpr on page load, before any click. Store AY wrote it only after the click. After Reject, none of the four stores 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.
Setup steps from Pandectes' docs
Steps come from Pandectes' official docs; we did not verify each one.
- Enable the Pandectes Core app embed in your theme editor. Pandectes says the Shopify Customer Privacy integration "is always active" and has no setting to turn on.
- Remove Shopify's own cookie banner (Settings, Customer privacy, Cookie banner, More actions, Remove cookie banner) so visitors see one banner.
- Keep the regions in Shopify's Customer privacy settings in line with your banner's consent model.
Check your own Pandectes store
- In a new private window, open DevTools and run Shopify.customerPrivacy.currentVisitorConsent() in Console before you click. Empty values mean no choice has reached Shopify yet.
- Click your banner's reject button and run it again. On Stores AY, AZ, and BA it read "no" within 0.3 seconds.
- In Network, filter by facebook.com/tr and open a product page. a=shopify_web_pixel marks Shopify's channel pixel. Any other value, or none, means a pixel outside that channel, like the GTM template pixel on Store AZ.
- Filter by pandect.es. The status field of the POST to consents.pandect.es shows the choice the browser sent.
Limits
We tested four stores from one US connection on one evening, five or six runs per store, in headless Chrome. We did not check out, test other regions, test Global Privacy Control, or see any store's Pandectes or Shopify settings. A browser log can't show server-side sending such as Meta's Conversions API. Some GA4 requests on Store AY left from a context our page log did not capture, so they have counts but no gcs values. Klaviyo requests did not complete over our HTTP/1.1 connections, so we left them out.
Related reading
FAQ
Does Pandectes pass Reject to Shopify's Customer Privacy API?
On Stores AY, AZ, and BA it did in all nine Reject runs. Shopify's API read "no" for marketing, analytics, and preferences within 0.3 seconds of the click. On Store W the API already read "no" before the click.
Did Meta receive events after Reject on these Pandectes stores?
From the product page, Stores AY, BA, and W sent no Meta events after Reject. Store AZ sent one custom event, "Engagement Time 20s", from a Meta pixel loaded through a Google Tag Manager template, in all three runs. Its Shopify channel pixel sent none.
What does Shopify's API show before a visitor clicks the Pandectes banner?
For our US visitor it returned empty values on Stores AY and BA, "yes" on Store AZ, and "no" on Store W. Pandectes' own help article says to expect empty values.
Is the reject click sent to Meta?
On Stores AZ, BA, and W, Meta received a SubscribedButtonClick event with the button's label in its buttonText field. On Store AY it did not.
What does the browser send to Pandectes when I click Reject?
One POST to consents.pandect.es. After Reject its status field was "deny" and preferences was 7. The body also carried countryCode, stateCode, path, and domain.
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.
- Pandectes Help Center, How to verify that Pandectes works with the Shopify Customer Privacy API
- Pandectes Help Center, Shopify Customer Privacy API
- Pandectes, Shopify Customer Privacy API Integration
- Pandectes Help Center, 4 Steps to Ensure Compliance
- Pandectes Help Center, Integrations Setup Guide
- Shopify App Store, Pandectes GDPR Compliance
- Shopify, Customer Privacy API