Checklist

Does FullStory keep recording after Reject? Two Shopify stores, tested

We clicked Reject on two Shopify stores. FullStory still sent /rec/page and /rec/bundle (HTTP 200). OneTrust and Ketch paths differed.

In brief

We tested two Shopify stores with FullStory. On both, recording requests continued after Reject. Store AJ uses OneTrust: we opened Cookie Settings, clicked Reject Non-Essential Cookies, and still saw 4 /rec/bundle calls on the same page, then 1 /rec/page and 6 /rec/bundle on the next page, all HTTP 200, matching Accept. That store's public OneTrust cookie list puts fs_uid and fs_lua under Performance; after Reject only C0001 stayed active. Store AM uses Ketch: Customize, Reject All, then Confirm. After Confirm the banner was gone. We still saw 4 /rec/bundle on the same page and 1 /rec/page plus 7 /rec/bundle on the next page, all HTTP 200, on both Reject runs. On AM, Shopify marketing and analytics were already no after Confirm; that did not stop FullStory. We did not see FS('shutdown') on either store. The fs_uid and fs_lua cookie names were still present. Loading fs.js alone is not proof of recording; /rec/page and /rec/bundle with HTTP 200 are. US visitors only. Not legal advice.

What we tested

In November 2026 we opened two Shopify stores that load FullStory, Store AJ and Store AM. Each run was a US visitor on a direct connection, no proxy, GPC off, headed Chrome, en-US, time zone America/Los_Angeles, and a new profile. See session replay before Accept for the before-click check.

Store AJ ran on 2026-11-05, from 00:54 to 00:57 America/Los_Angeles, with the exit in Wichita, Kansas. We ran Fresh with no click, Reject twice, and Accept once. A US visitor did not see a banner. Reject is footer Cookie Settings, then Reject Non-Essential Cookies. Accept is the same screen, then Confirm My Choices, with the defaults left on. Fresh and the clicked runs each waited 20 seconds, opened one product page, and waited 20 seconds.

Store AM ran on 2026-11-05, from 17:50 to 17:52 PST, with the exit in Virginia Beach, Virginia. We ran Reject twice, and the runs matched. The Ketch first layer shows Customize and Accept All, with no Reject on that layer. Reject is Customize, then Reject All, then Confirm. The after-consent wait starts when Confirm finishes, and the banner and preference layer were gone. We waited 20 seconds, opened one product page, and waited 20 seconds.

The clicks and the consent tools differ, so the tables keep Store AJ and Store AM apart. The runs are these two stores, US visitors, November 2026. We did not run an EU visitor.

What FullStory sent after Reject

Recording evidence on these runs is /rec/page or /rec/bundle with HTTP 200. Loading fs.js means the script reached the browser, and that load is not recording evidence.

Store AJ

Swipe to see Accept

Store AJ, OneTrust. Fresh did not click. Both Reject runs matched. Accept ran once.

FreshReject (x2, matched)Accept
OneTrust active groupsC0001-C0005C0001 onlyC0001-C0005
gtag consent updatenonedeniedgranted
Same page /rec/bundle after the clickn/a44
Next page fs.js loads122
Next page /rec/page111
Next page /rec/bundle666
Recording request status200200200
Call to FS('shutdown')not seennot seennot seen
fs_uid and fs_luapresentpresentpresent
Shopify consent fieldsemptyemptyempty
Shopify marketingAllowed()truetruetrue

Store AM

Swipe to see more

Store AM, Ketch. Both Reject runs matched. Reject only.
Reject (x2, matched)
Same page /rec/bundle after the click4
Next page fs.js loads2
Next page /rec/page1
Next page /rec/bundle7
Recording request status200
Call to FS('shutdown')not seen
fs_uid and fs_luapresent
Shopify consent before Confirmmarketing yes, analytics yes, preferences yes, sale_of_data yes
Shopify consent after Confirmmarketing no, analytics no, preferences yes, sale_of_data yes

Store AJ's next page sent 1 /rec/page and 6 /rec/bundle on Fresh, on both Reject runs, and on Accept. Store AM's next page sent 1 /rec/page and 7 /rec/bundle on both Reject runs. The same page after the click sent 4 /rec/bundle on AJ Reject, AJ Accept, and both AM Reject runs. Next-page bundles stay 6 on AJ and 7 on AM.

Every counted /rec/page and /rec/bundle request returned HTTP 200. That status is what the browser received.

On Store AJ, after Reject Non-Essential Cookies, calls through window.FS passed OneTrust events into FullStory, including OneTrustGroupsUpdated. The wrapper shows calls that go through window.FS. We did not see a call to FS('shutdown') on either store.

The cookie names fs_uid and fs_lua were present at the end of every AJ run and both AM Reject runs. We kept the names only. See does Reject All clear cookies.

Store AJ labeled FullStory as Performance

Store AJ publishes an OneTrust cookie list, the file the preference center offers for download. fs_uid and fs_lua are in C0002, Performance Cookies.

Before any click, and on Fresh and Accept, the active groups were C0001, C0002, C0003, C0004, and C0005. After Reject Non-Essential Cookies, the only active group was C0001, from the click through the end of both Reject runs. The gtag consent update was absent on Fresh, denied on both Reject runs, and granted on Accept.

Shopify.customerPrivacy.currentVisitorConsent() returned empty strings for marketing, analytics, preferences, and sale_of_data on Fresh, Reject, and Accept. marketingAllowed() stayed true.

OneTrust says to test and confirm Cookie Auto-Blocking. On Store AJ, /rec/page and /rec/bundle continued after Reject and returned HTTP 200. We did not record whether Cookie Auto-Blocking was enabled.

Store AM set Shopify analytics to no, and recording continued

Before Confirm, Store AM's Shopify consent strings were marketing yes, analytics yes, preferences yes, and sale_of_data yes. After Confirm they were marketing no, analytics no, preferences yes, and sale_of_data yes. Both Reject runs matched, and the end-of-run read matched the after-Confirm read. preferences and sale_of_data stayed yes.

After Confirm, the same page sent 4 /rec/bundle requests, and the next page sent 1 /rec/page and 7 /rec/bundle. Those requests returned HTTP 200. Shopify marketing and analytics were already no, and the recording requests still left the browser.

The Customer Privacy API says: "For regions that are configured to require consent, non-essential purposes are not allowed by default until consent is given. For other regions, the default behavior is to allow all processing purposes." These runs were US visitors in November 2026. On Store AJ the four consent strings stayed empty and marketingAllowed() stayed true. On Store AM, Confirm wrote marketing no and analytics no, and left preferences and sale_of_data at yes.

What stopping FullStory takes, per its docs

Steps below come from the official docs; we have not verified each one.

  1. Auto-Blocking. OneTrust says: "If you have enabled Cookie Auto-Blocking with OneTrust, the Fullstory javascript should be blocked automatically. Please test and confirm."
  2. Delayed startup. Set window['_fs_capture_on_startup'] to false before the snippet loads, then call FS('start') when you are ready to capture. Consent management says to call start() when consent is granted.
  3. On each page after reject, call FS('shutdown'). Capture data says: "Once FS('shutdown') is invoked, Fullstory will no longer receive data from the user's device. However, the "shutdown" state does not persist across page boundaries in the web browser." To persist the "shutdown" state, you must call FS('shutdown') on each page.

Check your own store in DevTools

Use a new browser profile. A US visit in November 2026 does not describe an EU visitor, and these two stores do not describe every theme.

See Clarity and Hotjar before Accept for the before-Accept check, and Clarity after Reject All on Shopify for a Reject All capture on Shopify.

  1. In Network, filter fullstory.com.
  2. After Reject, look for rs.fullstory.com/rec/bundle and /rec/page, and note the HTTP status.
  3. Open the next page and check those paths again. FS('shutdown') on one page does not persist onto the next page.
  4. In Application, look for the cookie names fs_uid and fs_lua. Leave the values out of notes and tickets.
  5. In Console, run Shopify.customerPrivacy.currentVisitorConsent() and read marketing, analytics, preferences, and sale_of_data separately.

See EU audit pricing The EU audit is $49 and clicks Reject; the free audit is one US visit and does not.

Does Reject stop FullStory?

On the two Shopify stores we tested, no. After Reject, both still sent /rec/page and /rec/bundle with HTTP 200 on the next page (AJ: 1 page and 6 bundles; AM: 1 page and 7 bundles).

Does Reject delete the fs_uid cookie?

Not on either store we tested. The fs_uid and fs_lua cookie names were still present after Reject and on the next page.

If my CMP lists FullStory as Performance, or Shopify analytics is no, is that enough?

On Store AJ, FullStory was listed under Performance and recording continued. On Store AM, Shopify marketing and analytics were no after Confirm and recording continued. The script also has to be blocked, or the page has to call FS('shutdown') on every page.

This is a technical observation, not legal advice.

Sources

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

FullStory After Reject on Two Shopify Stores | ConsentProbe