Checklist

Does Segment stop after Reject All? We tested two Shopify stores

Run the free scan

We clicked Reject on two Shopify stores running Segment. Events kept sending on both. Only the one using Segment Consent Management stopped its ad scripts.

In brief

On the two Shopify stores we tested, Segment kept sending page and track events after we clicked Reject. What changed depended on whether Segment was connected to the banner. On Store AH, Segment Consent Management was wired to OneTrust. After Reject, every event carried a consent object with only the strictly necessary category on, the device-mode destination scripts stopped loading, and on the next page we saw zero TikTok, Snap, Bing, Meta or Pinterest requests. On Store AI, the Cookiebot banner was not connected to Segment. Events went out with no consent object, and Shopify's own consent state was never set. On both stores the ajs_anonymous_id cookie was still there after Reject.

What we tested and how

In November 2026 we opened two Shopify stores that run Segment, Store AH and Store AI. The window was 2026-11-05, 16:34 to 16:38 UTC+8. The exit was a US direct connection. ipinfo placed it in Wichita, Kansas, US, with no proxy. EU visitors were not in this test. For the method behind this check, see how to spot Segment before Accept.

Each pass used headed Chrome through xvfb, en-US, America/Los_Angeles, GPC off, and a new profile. Each store had four passes: Fresh with no click, Reject, Accept, and a second Reject.

Fresh waited 20 seconds, opened one product page, and waited 20 seconds. Reject and Accept waited 15 seconds, opened the consent layer, clicked, waited 20 seconds, opened one product page, and waited 20 seconds. Segment events are counted once per messageId. The log kept cookie names and storage key names.

The counts are requests the browser sent. Our test network made Chrome reuse one HTTP/2 connection across different hosts, which broke some cross-host requests. On November 15, 2026 (PST) we reran both stores with HTTP/2 switched off. In that rerun, api.segment.io answered all 45 sends from the two stores with HTTP 200, and analytics.js sent each event once.

A US visitor on Store AH did not see a OneTrust banner. Reject All is in the Consent Preferences layer, opened from a footer link, and the click reloaded the page. The first Reject click was at 18.5 seconds and the reload at 19.11 seconds (0.61 seconds). The second was 18.44 to 19.05 seconds, also 0.61 seconds. Next-page rows are after that reload. On Store AI the US visitor saw Cookiebot: an OK button and Preferences, Statistics, and Marketing toggles, already checked. Reject switched the three off, then clicked OK.

Store AH wires Segment Consent Management to OneTrust. The settings file has consentSettings, hasUnmappedDestinations is false, and there are 19 destinations. Four are device-mode: Actions Amplitude on C0002, Google Analytics 4 Web on C0002, Snap Conversions Api on C0004, and TikTok Pixel on C0004.

Swipe to see Accept

Store AH. Fresh did not click. Both Reject passes matched. Accept ran once.

FreshRejectAccept
OneTrust groupsC0001 to C0005C0001 onlyC0001 to C0005
setTrackingConsentall trueall falseall true
marketingAllowed()truefalsetrue
gtag consent updategranteddeniedgranted
Same page after reloadno reload1 page and 2 track, only C0001 onno reload
Next page Segment events1 page and 2 track, all on1 page and 2 track, only C0001 on1 page and 2 track, all on
Next page device-mode scriptsloadednot loadedloaded
Next page TikTok, Snap, Bing, Meta, Pinterest16, 8, 8, 7, 60, 0, 0, 0, 017, 8, 8, 8, 6
ajs_anonymous_id cookiepresentpresentpresent
localStorage ajs_anonymous_id and ajs_user_idpresentpresentpresent

On the Reject next page, what remained was Optimizely and one Amplitude script file referenced by the page HTML. That page had no Amplitude event requests. In the November 15 rerun, the next page sent 1 page and 1 track in every pass because Experiment Viewed did not fire there, and after Reject every event again had only C0001 on.

The Analytics.js OneTrust wrapper docs, on the row where a user rejects all cookies and closes the banner, say: "If workspace has unmapped destinations or strictly necessary destinations, Segment libraries load" and "All events after a user rejects consent flow to unmapped or strictly necessary destinations." On Store AH, hasUnmappedDestinations was false and C0001 stayed on. The browser still sent the page and track events. Device-mode scripts for the other categories did not load after the reload.

Store AI: Cookiebot with no Segment connection

Store AI shows Cookiebot and does not connect that banner to Segment. The settings file has no consentSettings and no device-mode destinations. src1 sends to api.segment.io. src2 sends to a Segment proxy on the store's own subdomain.

Swipe to see Accept

Store AI. Fresh did not click. Both Reject passes matched. Accept left the toggles on and clicked OK.

FreshRejectAccept
Cookiebotimplied, all trueexplicit, three falseexplicit, all true
setTrackingConsentnot callednot callednot called
Shopify consent stringsemptyemptyempty
marketingAllowed()truetruetrue
gtag consent updategranteddeniedgranted
Next page src12 track2 track2 track
Next page src21 page, 3 identify, 2 track1 page1 page, 3 identify, 2 track
Consent object on the eventsnonenonenone
Next page Meta /tr, Snap2, 22, 22, 2
Next page TikTok, Pinterest49, 1011, 418, 10
Next page Bing, Hotjar5, 20, 05, 2
ajs_anonymous_id and ajs_user_idpresentpresentpresent

On Reject, the only track names in the log were Page Viewed and Product Viewed, both on src1. src2 sent 1 page. The identify calls and the 2 track events on src2 did not appear. No Store AI event carried a consent object. In the November 15 rerun, src2 sent no events in any of the five passes, so the src2 row describes November 5 only. TikTok and Pinterest counts also differed between the two days. On November 15 the next page sent 4 TikTok and 4 Pinterest requests on Fresh, and 5 and 4 after Reject.

Consent in Segment Connections says: "Events without the consent object continue to flow to destinations without consent enforcement." The browser sent Store AI's events with no consent object.

What happens to ajs_anonymous_id

Reject left ajs_anonymous_id in place on both stores. On Store AH the cookie was present at the end of Fresh, Reject, and Accept, and localStorage held ajs_anonymous_id and ajs_user_id. On Store AI the cookies ajs_anonymous_id and ajs_user_id were present at the end of all three passes, and localStorage held both names.

The Analytics.js identity docs say: "Segment writes the user's IDs to the user's local storage, and uses that as the Segment ID on the cookie whenever possible." The same page shows the cookie name ajs_anonymous_id. For other cookies that stay after Reject, see does Reject All clear cookies. For storage key names, see localStorage after Reject on Shopify.

Why the US visit matters

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 passes used the US direct exit. On Fresh, both stores sent Segment events. We did not run an EU visitor.

The OneTrust wrapper docs say: "Opt-In and Implied statuses are treated in Segment's OneTrust wrapper as Opt-In." On Store AH the US visitor had no banner, and groups C0001 to C0005 were already on before any click. On Store AI, Cookiebot's Fresh record was method implied, with the three toggles already true.

Check your own store in DevTools

We ran similar checks for HubSpot after Decline, Hightouch after Reject, and pixel vs cookie after Reject.

  1. In Network, filter segment.io and the hostname of your own Segment proxy, if the store has one.
  2. After Reject, open the /v1/t and /v1/p request bodies and look for context.consent.categoryPreferences.
  3. Filter next-integrations. See whether device-mode scripts still load after Reject.
  4. In Console, run Shopify.customerPrivacy.currentVisitorConsent() and marketingAllowed().
  5. In Application, check whether the ajs_anonymous_id cookie and the localStorage copy are still there.

Connecting Segment to your banner (from the docs)

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

  1. In the Segment workspace, create consent categories and map destinations to them. The overview says: "The events, stamped with the consent object, are then sent downstream to any destinations in categories that an end user consented to share data with." See Consent Management.
  2. Pass those categories into analytics.js with the OneTrust wrapper, or with your own wrapper that adds the consent object. See Consent in Segment Connections and the OneTrust wrapper.
  3. On Shopify, the banner has to call setTrackingConsent. Store AI's banner never did. See the Customer Privacy API.

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

This is a technical observation, not legal advice.

FAQ

Does Segment stop sending events when a visitor rejects cookies?

On both stores we tested, no. With Segment Consent Management, events keep going but carry the visitor's consent choice, and destinations in rejected categories are not loaded in the browser.

Does Reject All delete ajs_anonymous_id?

Not on either store we tested. The cookie and the localStorage copy were still there after Reject.

Is my Shopify consent state passed to Segment automatically?

Not on Store AI. Its banner never called Shopify's setTrackingConsent, and Segment events had no consent object. Store AH's site set both.

Sources

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

Save a US-baseline technical record

After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.

Does Segment Stop After Reject All? | ConsentProbe