Checklist

What localStorage and sessionStorage keep after Reject on Shopify stores

We logged localStorage and sessionStorage key names on three Shopify stores running Cookiebot, with no click, after Deny, and after Allow all.

In brief

We logged localStorage and sessionStorage key names, never values, on three Shopify stores running Cookiebot, from a US connection on November 2, 2026. Each store got a pass with no click, a pass that clicked Deny, and a pass that clicked Allow all. On Store Q, the product page after Deny held 28 localStorage keys, against 40 with no click and 51 after Allow all. The keys missing after Deny included _gcl_ls, _pin_unauth_ls, and two referrer keys that Meta's pixel wrote on the other two stores. Elevar's sessionId and userId keys stayed, and so did five TikTok keys in sessionStorage. On Store Z, Google Tag Manager and Meta's pixel wrote their keys about 7 seconds before Deny, and all three keys were removed at the Deny click. On Store AA, the product page held the same 12 localStorage keys with no click and after Deny, and keys from Elevar, Google, and Meta appeared only after Allow all. Not legal advice.

What we recorded, and what we did not

Each pass started in a new browser profile. The script opened the homepage, waited for the Cookiebot banner, waited 4 more seconds, and clicked. On the no-click pass it only marked the time. Twelve seconds later it scrolled and opened the same product page on every pass, then stayed there for about 14 seconds.

We listed the key names in localStorage and sessionStorage three times on each pass: right before the click, 12 seconds after it, and at the end of the product page. We never read a value. On Stores Z and AA, a script also wrapped setItem, removeItem, and clear in every frame. That gives us the second each write or removal happened, counted from the click, and the script that made the call. Store Q ran before that wrapper was added, so for Q we have the three lists from the top page and nothing in between. Every write or removal we describe on Store Q is inferred from those snapshots.

When the call stack named the script, we name the vendor. When we matched a vendor only from the key's prefix, we write "likely". Some keys on Z and AA were written by Shopify's web pixel sandbox, which hosts many apps at once. For those, the stack shows Shopify, and the app name comes from the prefix.

Counts are distinct key names after we replaced IDs in names with <id>, so wpm-ri-<id>-<id>-z counts once. Our wrapper also showed up as six fake keys (getItem, setItem, and four more) inside one frame on Z and AA. We removed those from every count.

We did not test canvas, audio, or other fingerprinting. IndexedDB had no databases on Z or AA in any snapshot. Cookies are a separate question, covered in Does Reject All clear cookies already set?

Swipe to see localStorage and sessionStorage

Table 1. Keys on the product page at the end of each pass

StoreWhere Deny islocalStorage: no click / Deny / Allow allsessionStorage: no click / Deny / Allow all
Q, Nov 2Inside Customize40 / 28 / 5132 / 32 / 43
Q, Oct 26Inside Customize38 / 24 / 5134 / 34 / 47
Z, Nov 2After Customize16 / 13 / 249 / 9 / 10
AA, Nov 2First layer12 / 12 / 3214 / 14 / 17

Table note: October 26 counts are raw key names. November 2 counts merge names that differ only by an ID, which accounts for part of the drop in Store Q's sessionStorage count.

Which keys disappeared after Deny?

On Store Q, the top page had 41 localStorage keys right before Deny and 18 twelve seconds after it. Ten of the missing keys were back on the product page. Thirteen were not.

Swipe to see more

Table 2. Store Q localStorage keys gone after Deny and not back on the product page
KeyLikely vendor
_gcl_lsGoogle (Google Tag Manager wrote it on Z and AA)
lastExternalReferrer, lastExternalReferrerTimeMeta (Meta's pixel wrote them on Z and AA)
_pin_unauth_lsPinterest
_axwrt_backupAppLovin AXON
__kl_key, $referrer, $last_referrerKlaviyo (Klaviyo wrote them on AA)
Shoplift_ClientId, Shoplift_Analytics, shoplift_last_pageview, shoplift_last_pageview_atShoplift
landing_pageNo match

These removals are inferred from snapshots, so we cannot say which second each one happened or which script removed it.

On Store Z, the wrapper caught the timing. Google Tag Manager wrote _gcl_ls 7.0 seconds before Deny. Meta's pixel wrote lastExternalReferrer and lastExternalReferrerTime 6.9 seconds before Deny. All three were removed 0.0 seconds after Deny and were not on the product page. In the same 0.3 seconds, five more localStorage keys were removed, four of them with AddShoppers-style names (likely AddShoppers). Two were back by the 12-second snapshot, and the other three were back on the product page. The log also shows removeItem calls for the same names in sessionStorage, where those keys never appeared. Our log does not record which script made the removal calls.

On Store AA there were no Google or Meta keys to remove. At the Deny click, removeItem calls hit 10 localStorage keys that were already there: three Gorgias keys, klaviyoOnsite, Riskified's rCookie, a Shop sign-in key, and four snowplowOutQueue_* keys. Five were back by the 12-second snapshot and the other five were back on the product page. The log also has removeItem calls for Snowplow's _sp_id.<id> and _sp_ses.<id> 5.3 seconds after Deny, and for four affiliate* keys 0.3 seconds after Deny. None of those names appeared in any snapshot.

Which keys stayed after Deny?

On Store Q, 18 localStorage keys were in all three snapshots of the Deny pass, and 10 more came back on the product page. The ones with a vendor match:

Swipe to see more

Table 3. Store Q keys still there on the product page after Deny
StorageKeysLikely vendor
localStorageNine ___ELEVAR_GTM_SUITE--* keys, including --sessionId, --userId, and --sessionCountElevar
localStorageklaviyoOnsiteKlaviyo
localStorage_applovin_pixel_versionAppLovin, from the key name
localStorage_grd_idf, _grd_sid, groundUserIdWriter not confirmed
sessionStoragett_sessionId, tt_pixel_session_index, tt_s_pixel_session_index, tt_appInfo, tt_appInfo_v2TikTok
sessionStorage_axsidAppLovin AXON
sessionStorage_rdt_cfgReddit

The five TikTok keys were in all nine snapshots across the three passes. In the request log for the same Deny pass, TikTok sent 3 requests on the homepage starting 2.7 seconds after Deny and 0 on the product page.

Store Q changed between our two captures. On October 26, our AppLovin AXON test found _axsid as the only AXON storage key after Reject. On November 2, _applovin_pixel_version was also on the product page after Deny. The November 2 Deny pass also kept _grd_idf, _grd_sid, and groundUserId, which were not there on October 26.

On Store Z, the keys that stayed after Deny were written 5.7 to 7.1 seconds before it. UserWay, an accessibility widget, wrote four keys, including uw-uid 6.5 seconds before Deny. TW_EXT_page^viewed_<id> was written from inside Shopify's web pixel sandbox 7.1 seconds before Deny, and its prefix points to X. Our request log for Store Z matched no X requests on any pass. In sessionStorage, three keys from an SMS sign-up app stayed on all three passes, along with Shopify's consentHeader and _shs_state.

On Store AA, everything written before the click was back by the product page. That list is Gorgias chat keys, Riskified keys, klaviyoOnsite and klaviyoPagesVisitCountV2, the snowplowOutQueue_* keys, and Shopify keys. They were written 1.1 to 4.0 seconds before the click.

Was anything written after Deny?

On Store Q, the product page after Deny had no localStorage key that the no-click pass lacked. Three sessionStorage keys showed up after the click mark on all three passes, including the no-click pass, so Deny did not trigger them.

On Store Z, no key was first written after Deny. The amount of writing changed, though. After the click, the localStorage log counted 138 setItem calls on the no-click pass, 1,954 on the Deny pass, and 1,122 on the Allow all pass. removeItem calls were 10, 1,835, and 922. We logged the number of these calls, not the keys they touched.

On Store AA, two sessionStorage keys were written after Deny, and both were also written on the other two passes. Klaviyo wrote klaviyoFormSubmit 7.5 seconds after Deny, the same second as Klaviyo's first request after Deny. A product-history key from a Shopify agency app was written 16.6 seconds after Deny, on the product page. Its call stack showed only Cookiebot's auto-blocking wrapper, so we could not name the script.

What did Allow all add?

On Store Q, Allow all added 11 localStorage keys and 11 sessionStorage keys compared with the no-click pass. Seventeen of the 22 start with _grd_. The others include Klaviyo's __kla_viewed and __kla_viewed_reviewed_items, bhpx_processed_events (likely beehiiv), and Shoplift_Analytics. Store Q has no timing for these.

On Store Z, Allow all added 8 localStorage keys, all written from inside Shopify's web pixel sandbox 16.8 to 17.3 seconds after the click, on the product page. They are TW_EXT_product^viewed_<id>, four AddShoppers-style keys such as asProductViewHistory, and audienceLastLoadedDatetime, userInfoCache, and userInfoLastLoadedDatetime.

On Store AA, Allow all added 20 localStorage keys, and most arrived within 1.4 seconds:

Swipe to see more

Table 4. Store AA localStorage keys written after Allow all
Seconds after Allow allKeysWriter
0.3__kl_key, $referrer, $last_referrer, kl-post-identification-syncKlaviyo
0.6 to 1.1Nine ___ELEVAR_GTM_SUITE--* keysElevar
0.6A cart session keyNot named in the log
0.8_gcl_lsGoogle Tag Manager
1.4lastExternalReferrer, lastExternalReferrerTimeMeta
16.9__kla_viewed, __kla_viewed_reviewed_items, shopify:webmcp_adapter_loadedKlaviyo; the store's page

Same vendor, different store

Swipe to see more

Table 5. The same keys on three stores (no click / Deny / Allow all)
KeyStore QStore ZStore AA
_gcl_lsYes / No / YesYes / Removed at Deny / YesNo / No / Yes
lastExternalReferrerYes / No / YesYes / Removed at Deny / YesNo / No / Yes
Elevar keys (9)Yes / Yes / YesNot on storeNo / No / Yes
klaviyoOnsiteYes / Yes / YesNot on storeYes / Removed at Deny, back within 12 s / Yes

On Stores Q and Z, the Google and Meta keys were written before anyone clicked. On those passes Shopify's consent API read no for marketing, analytics, preferences, and sale of data, and Cookiebot had recorded no choice. On the no-click pass the keys were still there at the end of the product page.

Elevar had 9 keys on every Store Q pass. On Store AA, Elevar sent 3 requests before the click and 3 on the product page in the Deny pass, but wrote no storage keys until Allow all. The same app can leave different storage behind depending on how the store and its banner load it.

The European Data Protection Board's Guidelines 2/2023 on the technical scope of Article 5(3) of the ePrivacy Directive (version 2.0, adopted October 7, 2024) name local storage next to cookies as information a browser keeps on the device (paragraph 44). The guidelines say the directive sets no minimum time that information must persist to count as stored (paragraph 37). They also say Article 5(3) applies when information kept on the device, or anything derived from it, is accessed.

Google's consent mode overview describes ad_storage denied in terms of advertising cookies and device identifiers. The page does not mention localStorage. On Stores Q and Z, _gcl_ls was gone after Deny.

Whether a rule applies to a given store, and whether an exemption fits a given key, are legal questions. This test does not answer them. Not legal advice.

How to check your own store

  1. Open a private window and load the page. Before you touch the banner, open DevTools, go to Application, and copy the key names under Local storage and Session storage.
  2. Click Reject (or Deny). Wait 12 seconds and copy the key names again.
  3. Open a product page in the same window and copy them a third time.
  4. Close the window. Repeat in new private windows with no click and with Accept.
  5. Compare names across the three passes. Values are not needed for this.

Snapshots miss keys that are written and removed within a second. On Stores Z and AA, cookiebottest was written and removed 0.0 seconds after Deny. A Hotjar test key on Z and a Klaviyo test key on AA went the same way. Snapshots also miss a key that is removed at the click and written back before you look, which happened to klaviyoOnsite on AA. To see those, wrap setItem and removeItem in a script that logs the key name and time and drops the value. Check each frame, because an iframe from another origin has its own storage.

Requests are a separate check. A store can stop sending requests to a vendor and still hold that vendor's keys, as TikTok's session keys did on Store Q. Tracking pixel vs cookie after Reject All covers that difference for requests and cookies.

Limits of this test

This is three stores running Cookiebot, tested from one US connection, with one pass per state. We captured Store Q on October 26 and November 2, 2026, and Stores Z and AA on November 2 only, the same passes as Cookiebot price increase: record what Reject stops before you switch. Store Q has snapshots of the top page only, with no timing, no call stack, no iframes, and no IndexedDB. On Store Z, an SMS sign-up overlay covered the banner, so we clicked Cookiebot's buttons with a DOM click(). A visitor would close the overlay first, which could change what loads. Our log records which script wrote a key on Z and AA, but not which script removed one. Vendor names marked "likely" come from key prefixes. We recorded key names, never values, so we cannot say what a key held or whether it identified anyone. We did not run an EU visit or a GPC pass, log in, add to cart, or check out. Another Cookiebot setup, region, or banner type can give different results. These results do not say any store did anything wrong. Not legal advice.

FAQ

Does Reject clear localStorage?

It depended on the store and the key. On Store Q, 13 of the 41 localStorage keys present before Deny were gone on the product page, including keys likely from Google, Meta, and Pinterest. On Store Z, the Google and Meta keys were removed at the Deny click. On Store AA, every key removed at Deny was back by the product page. Not legal advice.

Is localStorage covered by cookie consent rules?

The EDPB's 2024 guidelines on Article 5(3) of the ePrivacy Directive list local storage next to cookies as information stored on the device. How that applies to a given store is a legal question. Not legal advice.

Can a key be removed at Deny and come back?

Yes. On Store AA, 10 keys were removed at the Deny click and all 10 were there again by the end of the product page. On Store Z, five keys were removed within 0.3 seconds of Deny and came back. A single DevTools snapshot shows neither the removal nor the rewrite.

What is the difference between localStorage and sessionStorage here?

sessionStorage belongs to one tab and is cleared when that tab's session ends. localStorage stays until a script or the visitor removes it. On Store Q, TikTok's session keys were in sessionStorage on every pass.

Did you read the stored values?

No. Our script listed key names only and dropped values before anything was written to disk. We replaced store names and IDs inside key names with placeholders such as <id>.

Sources

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

What localStorage Keeps After Reject | ConsentProbe