Checklist

HubSpot on two Shopify stores: what fired after Decline

Run the free scan

Two Shopify stores running HubSpot: Decline didn't stop page views or __hstc. What we captured and why the banner never reached HubSpot.

In brief

On a Shopify store with its own Accept / Decline banner, HubSpot kept logging page views after we clicked Decline, and its __hstc and hubspotutk cookies stayed. The banner told Google's consent mode about the choice and never told HubSpot.

What we tested

We captured Store AF and Store AG on 2026-11-04, between 16:12 and 16:18 UTC+8. The exit was a direct US connection from Wichita, Kansas, with no proxy. Each pass used headed Chrome via xvfb, language en-US, timezone America/Los_Angeles, GPC off, a 1366x900 window, and a new browser profile. The log kept cookie names and storage key names.

Store AF's banner is a script the theme ships, 4,915 bytes, read on 2026-11-04. The buttons are Accept, Decline, and Preferences, with one analytics toggle. The page HTML includes a HubSpot tracking loader from js.hs-scripts.com. HubSpot's banner.js loaded on these passes, and no HubSpot banner was on screen.

Store AG's banner is HubSpot's own. The first layer has a single Accept button, no Decline button, and no settings link. Accept leaves __hs_notify_banner_dismiss. The page HTML includes a HubSpot tracking loader.

HubSpot's Shopify integration page says: "By installing the Shopify (Data Sync) integration, the HubSpot tracking code will be added to your Shopify store automatically." Both stores had the loader in the HTML. We did not open either HubSpot account.

A Fresh pass waits 60 seconds and does not click. A Decline or Accept pass waits for the banner, waits 1 more second, runs a DOM click(), stays 35 seconds, opens the first product link on the home page, and stays 15 seconds. Store AG has no Decline button, so that pass left the banner up and clicked nothing. Store AG's Accept pass stopped on the home page.

HubSpot request counts cover hosts under hs-scripts.com, hs-analytics.net, hs-banner.com, hsadspixel.net, usemessages.com, hscollectedforms.net, hsforms.com, and hubspot.com. The page-view image in the tables is track.hubspot.com/__ptq.gif.

This capture has no EU exit, no checkout, no signed-in visit, and no chat window. HubSpot's account reports are not in the log.

Store AF: Decline saved, HubSpot not told

Four passes on Store AF. Fresh did not click. Decline ran twice. Accept ran once. On a Decline pass the first __ptq.gif is the home-page view: 0.18 seconds after the click on Decline 1, and 0.23 seconds after the click on Decline 2 (3.33 minus 3.15, and 2.97 minus 2.74). The product-page __ptq.gif is the one this section uses.

Swipe to see request counts

Store AF. Seconds from navigation start. HubSpot requests before the click, on the same page after it, and on the next page.

RunClickBefore clickSame page afterNext page__ptq.gifCookies at end
Freshno click19no clickno next page5.35__hstc, hubspotutk, __hssc, __hssrc
Decline 13.1511716, page opened at 38.163.33, 43.92same four cookies
Decline 22.7411818, page opened at 37.752.97, 40.31same four cookies
Accept3.4810917, page opened at 38.495.72, 45.14same four cookies

The product page opened at 38.16 seconds on Decline 1 and at 37.75 seconds on Decline 2. __ptq.gif then went out at 43.92 and 40.31, which is 5.76 seconds and 2.56 seconds after that page opened. Both passes still had __hstc, hubspotutk, __hssc, and __hssrc at the end. __hs_do_not_track was absent. Cookies written earlier are a separate check, in Reject All doesn't clear cookies already set.

The three clicked passes wrote cookieConsent, analyticsConsent, and cookieConsentVersion. Fresh had none of those keys.

Accept, Decline, and Save on Store AF call one function in that banner script. It writes the three keys above. It calls gtag('consent', 'update', ...) with analytics_storage set from the choice, and with ad_storage plus two other flags held at denied. It pushes cookie_consent_update onto the dataLayer and fires a window event. The function does not call Shopify.customerPrivacy.setTrackingConsent, _hsq.push(['doNotTrack']), _hsp.push(['setHubSpotConsent', ...]), or disableHubSpotCookieBanner.

HubSpot's tracking code was never told about the Decline. We base this on the banner script itself: it updates Google consent and the dataLayer, and contains no call to HubSpot's consent or do-not-track functions.

See Google consent mode and GTM tags.

Decline and Accept runs look the same from HubSpot's side. On Accept the product page opened at 38.49 seconds, __ptq.gif went out at 5.72 and 45.14, and the four cookies at the end matched both Decline passes.

Store AG: HubSpot's own banner, Accept only

Three passes on Store AG. The banner has no Decline button, so this table has no Decline click.

Swipe to see request counts

Store AG. Accept is the only button. The Accept pass did not open a product page.

RunClickBefore clickSame page afterNext page__ptq.gifCookies at end
Freshno click11no clickno next page2.80__hstc, hubspotutk, __hssc, __hssrc
Banner left openno Decline button11no clickno next page2.38same four cookies
Accept3.56110product page not opened2.03same four, plus __hs_notify_banner_dismiss

On Fresh, __ptq.gif went out at 2.80 seconds, inside 11 HubSpot requests over the 60-second wait. The pass that left the banner open sent __ptq.gif at 2.38 seconds, again with 11 HubSpot requests. Accept was clicked at 3.56 seconds. __ptq.gif had already gone out at 2.03 seconds. After that click the same page sent 0 further HubSpot requests, and the pass did not open a product page. __hs_do_not_track was absent on all three Store AG passes. Accept added __hs_notify_banner_dismiss.

None of the Store AG passes wrote cookieConsent, analyticsConsent, or cookieConsentVersion.

HubSpot says this usually means: "If HubSpot cookies are loading before consent has been collected, it's likely that your consent banner policy type is set to Notification." We could not open Store AG's HubSpot settings.

currentVisitorConsent() on Shopify.customerPrivacy was recorded twice on each clicked Store AF pass, twice on the Store AG pass that left the banner open, and twice on Store AG Accept. Every one of those readings had empty strings for marketing, analytics, preferences, and sale_of_data. marketingAllowed(), analyticsProcessingAllowed(), and saleOfDataAllowed() returned true beside those strings. The two Fresh passes have no consent reading in the capture file.

Postscript after Reject recorded empty Shopify consent strings on a US visit, on other stores.

Shopify's Customer Privacy API says that a region not set to require consent allows all processing by default. These passes used the Kansas exit. The region list in each store admin stayed closed.

What would have told HubSpot

Steps below come from the official docs. We did not verify each one.

  1. HubSpot's consent banner FAQ says: "Unless you're using the Cookiebot integration, managing HubSpot cookies with a third-party banner requires a custom developed setup." Source: HubSpot consent banner FAQ.
  2. window.disableHubSpotCookieBanner = true turns HubSpot's own banner off. _hsp.push(['setHubSpotConsent', {analytics, advertisement, functionality}]) passes analytics, advertisement, and functionality consent into HubSpot. After a refusal, HubSpot's docs treat the visitor as anonymous, and doNotTrack also stops that anonymous data. Source: Consent banner API.
  3. doNotTrack sets a __hs_do_not_track cookie and stops page views, events, and visitor identification. Source: Enable do not track.
  4. Consentmo's HubSpot integration calls doNotTrack when Analytics consent is missing. When that consent is present it calls doNotTrack with {track: true} plus trackPageView, and it turns HubSpot's banner off. Source: Consentmo HubSpot integration.

How to check HubSpot on your own store

For the pass that happens before any click, see how to check HubSpot before Accept.

  1. Open a new private window, load the store, and click Decline.
  2. In DevTools, open Network and filter for __ptq. Open a product page. Watch for another __ptq.gif.
  3. Open Application. Look for __hs_do_not_track. Check whether __hstc is still stored.

Want Fresh, Reject, and Accept recorded for you? See EU audit pricing. The EU audit is $49 and clicks Reject; the free audit is one US visit and does not.

FAQ

Does Decline remove HubSpot cookies?

On Store AF, no. __hstc, hubspotutk, __hssc, __hssrc were present at the end of both Decline runs, and no __hs_do_not_track was set.

Does HubSpot fire before any click?

On both stores, yes. In runs with no click, __ptq.gif went out at 5.35 seconds on Store AF and 2.38 to 2.80 seconds on Store AG; in the AG Accept run it went out at 2.03 seconds, before the click at 3.56.

Is a Google Consent Mode update enough?

Not for HubSpot on Store AF. HubSpot reads its own consent API, per its docs, and the banner only called gtag.

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.

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.

HubSpot After Decline: What Still Fires | ConsentProbe