Checklist
The FedEx order's quarterly opt-out test, tried on 3 Shopify stores
CalPrivacy's FedEx order requires opt-out testing every quarter. We ran Fresh, Reject and GPC three times on 3 Shopify stores and logged every ad request.
In brief
On November 10, 2026, CalPrivacy announced that Federal Express Corporation will pay a $2,975,000 fine under a stipulated order. The agency's Enforcement Division alleged that fedex.com shared visitor data with ad tech companies, did not honor Global Privacy Control (GPC) signals, and offered cookie controls that did not stop all sharing. FedEx neither admits nor denies those findings. The order requires FedEx to test its opt-out setup in staging and production at least once a quarter, and whenever it adds a new tracker. We ran that kind of test on three Shopify stores from a California IP: a fresh visit, a visit where we clicked the store's reject button, and a visit with GPC on. Each state ran three times. On Store AN, after we clicked Reject, Shopify's Customer Privacy API stayed yes on all four purposes, and all ten vendors on the product page, including Meta, Google Ads, X and Pinterest, sent the same request counts as a fresh visit. GPC cut those ten vendors to two. On Store AK, Reject stopped all ten vendors we count, but GPC stopped only Meta and TikTok. On Store AR, Reject stopped Meta and most Google Ads requests, while GPC left the same seven vendors running as on a fresh visit. A quarterly test that checked only the banner would have missed what we saw on Store AK, and one that checked only GPC would have missed Store AN (Reject All testing). Technical observation, not legal advice.
What the FedEx order asks for
The CalPrivacy Board adopted the order on November 6, 2026. It covers conduct from July 1, 2023 to October 27, 2025. FedEx admits only paragraphs 1 to 5 (the parties, jurisdiction and the company's size) and neither admits nor denies the rest of the findings. The parts that turn into a testing routine:
Swipe to see the obligation
What FedEx must do
| Paragraph | What FedEx must do |
|---|---|
| 62 | Scan its websites and apps at least quarterly and keep an inventory of trackers that sell or share personal information |
| 62(b) | Configure those properties to honor opt-outs sent by GPC or through another required method |
| 63 | Test those configurations in staging and production at least quarterly, and whenever a new tracker is added |
| 65 | Offer a "Do Not Sell or Share My Personal Information" or "Your Privacy Choices" link |
| 66 | Explain how any cookie control used for opt-outs applies to selling and sharing |
| 70 | Keep these obligations for three years |
Paragraph 63 does not list test steps. The method below is ours (decision and stipulated order; checking your policy against what your site sends).
The test we ran
We used headless Chrome with a new profile for every visit, US English, Los Angeles time, and a direct connection that geolocates to San Jose, California. Each visit loaded the home page, waited for the banner, then opened a product page and stayed about 30 seconds. We ran three states:
- Fresh: no click, GPC off.
- Reject: click the store's own reject button on the first banner.
- GPC: no click. Every request carried the
Sec-GPC: 1header, andnavigator.globalPrivacyControlreadtruebefore page scripts ran.
During each visit we read Shopify's Customer Privacy API (Shopify.customerPrivacy.currentVisitorConsent()) every quarter second for eight seconds, on the home page and again on the product page. We counted requests to ad and analytics vendors, not script downloads, and took status codes from Chrome's network log. Across 27 visits we saw 1,655 such requests. None returned a 4xx or 5xx status, and 23 had not finished when the page changed. The counts below are from the product page, the second page of each visit and the first one loaded after a Reject click.
Store AK: Reject stopped all ten vendors, GPC stopped two
Store AK uses Ketch with "Accept All Cookies" and "Reject All Cookies" on the banner. Shopify's API reads yes for all four purposes before anyone clicks, and the home page sends requests to ten vendors, including a Meta PageView and two TikTok events.
After "Reject All Cookies," the API flipped to no on all four within 0.28 seconds. Two to four Amazon requests went out in the first 0.15 seconds. The product page then sent nothing to any of the ten vendors, in all three runs.
With GPC on, the API read sale_of_data: no from the first page load, with the other three still yes. Meta and TikTok sent zero requests on both pages. The other eight vendors sent the same counts as a fresh visit: on the product page, 12 Google Ads and Floodlight requests (those that carried a Consent Mode code read G111, meaning ad and analytics storage granted), 4 Pinterest, 3 Microsoft UET, 3 Amazon, 2 Reddit, 2 GA4, and one each to Tapad and Google's cookie-matching endpoint.
Store AN: GPC cut most vendors, Reject changed nothing we measured
Store AN also uses Ketch. Its banner offers "Accept All" and "Reject All Non Essential." A fresh visit sends requests to ten vendors on the product page, including Meta PageView and ViewContent, 12 Google Ads requests, 4 to X, and 4 to Pinterest.
We clicked "Reject All Non Essential" in all three runs and the banner closed. Shopify's API stayed yes on all four purposes for the rest of the visit. The product page sent the same requests to the same ten vendors as a fresh visit, in all three runs. In a separate check, Ketch's stored record showed the click (banner.rejectAll) while its analytics and advertising purposes still read allowed, with the legal basis set to disclosure. We cannot see why the store set it up this way.
With GPC on and no click, the API read sale_of_data: no. The product page sent 11 Google Ads and Floodlight requests and 1 GA4 request; those carrying a Consent Mode code read G111. Meta, X, Pinterest, Microsoft UET, Amazon, Reddit, Snap and Tapad sent zero.
Store AR: Reject stopped Meta, GPC was recorded and the page stayed the same
Store AR uses OneTrust with "Reject All" and "Accept Cookies." For our California visitor, OneTrust's cookie already had groups C0002, C0003 and C0004 (OneTrust's default IDs for performance, functional and targeting) set to 0 before any click, and Shopify's API read marketing: no and sale_of_data: no. The home page still sent 20 Google Ads and Floodlight requests, 4 Pinterest, 4 Amazon, 2 Microsoft UET and 1 Reddit. The product page added Meta PageView and ViewContent and 28 to 30 Google Ads requests.
After "Reject All," the product page sent no Meta requests and one Google Ads request, and GA4 switched to consent code G100 (both storage types denied). Pinterest (4), Amazon (3), Microsoft UET (2) and Reddit (1) sent the same counts as before, in all three runs.
With GPC on, OneTrust's cookie recorded isGpcEnabled=1. The product page sent requests to the same seven vendors as a fresh visit: 28 Google Ads requests, Meta PageView and ViewContent, 4 Pinterest, 3 Amazon, 2 Microsoft UET and 1 Reddit (GPC recorded, marketing still loads).
Meta logged the reject click
On Stores AK and AN, the Meta pixel sent a SubscribedButtonClick event at the moment we clicked reject, with the button label ("Reject All Cookies", "Reject All Non Essential") in the request. That happened in all six Reject runs. SubscribedButtonClick is the event Meta's pixel sends for its automatic button-click tracking. On Store AK, it left the browser before Shopify's API switched to no.
How to run this test on your own store each quarter
- Open a new browser profile or a private window with no saved cookies. Note the date, browser version and your location.
- Open DevTools, turn on Preserve log in the Network panel, and load your home page without clicking anything. In the Console, run
Shopify.customerPrivacy.currentVisitorConsent()and write down the four values. - Filter the Network panel by your vendors' hosts (
facebook.com/tr,analytics.tiktok.com,googleadservices,doubleclick,bat.bing.com,ct.pinterest.com). Count requests on the home page, then open a product page and count again. - Start over in a clean profile and click your banner's reject button. Read the API again right after the click, then count on the next page.
- Start over with GPC on (Firefox, Brave and DuckDuckGo have a setting; Chrome needs an extension). Confirm
navigator.globalPrivacyControlreturnstrueand the page request carriesSec-GPC: 1. Load the same pages without clicking and count again, or use our GPC check. - Click your "Do Not Sell or Share" or "Your Privacy Choices" link and confirm it opens the place where a visitor can opt out.
- Repeat each state at least twice. One run can be thrown off by a pop-up or a slow script.
- Run the test again whenever you add an app, pixel or tag manager tag, because paragraph 63 of the FedEx order ties testing to new trackers as well as the calendar (when to re-run a cookie audit).
What to write down
Swipe to see the example
Example from Store AN
| Field | Example from Store AN |
|---|---|
| Date, time, location | November 17 to 18, 2026 PST, California IP |
| State | Reject ("Reject All Non Essential") |
| Shopify API before / after | yes, yes, yes, yes / yes, yes, yes, yes |
| Vendors on the next page | 10 of 10 seen on a fresh visit |
| Vendors that stopped | none |
| Status codes | all 200 or 204 |
| Runs that matched | 3 of 3 |
Keep the log files or screenshots with the record. A dated record from each quarter shows when a change appeared (what GPC evidence to keep).
Limits
- Three stores, one California location, one night (November 17 to 18, 2026 PST). Stores change their setups, and a later run can differ.
- We counted requests leaving the browser. We did not see what vendors do with them or whether anything is sent server to server.
- GPC came from a request header and a JavaScript property set by our script, not from a browser's own GPC setting.
- We did not test logged-in visits, checkout, mobile apps or staging sites, all of which paragraph 63 covers for FedEx.
- We did not open or submit the stores' opt-out links or forms.
- Store letters match our earlier posts: Store AK is the same store as in analytics.tiktok.com after Reject.
FAQ
What did CalPrivacy fine FedEx for?
CalPrivacy's Enforcement Division alleged that fedex.com shared visitor identifiers with ad tech companies while its privacy policy said it did not sell or share personal information, that it did not honor opt-out preference signals such as GPC, that it had no Do Not Sell or Share link, and that its cookie controls did not stop all sharing. FedEx neither admits nor denies the findings and agreed to pay $2,975,000.
What does "quarterly opt-out testing" mean in the FedEx order?
Paragraph 63 requires FedEx to test the settings on its websites and apps in both staging and production at least once a quarter, and whenever it adds a new tracking technology, to make sure opt-out requests are given full effect. The order does not list the test steps.
Does the FedEx order apply to my Shopify store?
The order binds FedEx only. It shows what CalPrivacy asked one company to do. Whether the CCPA applies to your business is a legal question for your counsel.
Is testing the Reject button enough?
Not on the stores we tested. On Store AN, after Reject, Shopify's Customer Privacy API stayed yes on all four purposes and all ten vendors' request counts matched a fresh visit, while GPC cut ten vendors to two. On Store AK it was the other way around. Test both paths.
How do I check GPC on a Shopify store?
Turn GPC on, open a clean window, and run Shopify.customerPrivacy.currentVisitorConsent() in the Console. On Stores AK and AN, GPC showed up as sale_of_data: no. On Store AR that value was already no on a fresh visit, and the change showed up in OneTrust's cookie instead. Then count requests to your ad vendors on the next page and compare them with a fresh visit.
How many runs does a quarterly test 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.