Checklist
Consentmo Unavailable on the Shopify App Store: We Tested Reject on 2 Live Stores
Consentmo's Shopify listing shows not currently available. We clicked Reject on 2 stores still running it. One still sent Meta and TikTok page events.
In brief
Consentmo's listing on the Shopify App Store shows "This app is not currently available on the Shopify App Store" (as of October 27, 2026 UTC). On two stores that still run its banner, the banner still loads and still records a Reject. What happens next differs by store. On Store S, after Reject, the next page set a new _fbp cookie and sent a Meta PageView, and the TikTok Pixel sent a Pageview too. On Store U, Meta, Bing UET, Microsoft Clarity and Google Ads sent nothing on the next page after Reject, but The Trade Desk still sent 12 and 13 requests in our two runs. We tested both stores on October 27, 2026. Not legal advice.
What we checked and when
Listing status, as of October 27, 2026 UTC: the Shopify App Store listing at apps.shopify.com/gdpr-backpack shows "This app is not currently available on the Shopify App Store." We found no statement from Consentmo about the listing as of that date.
We tested on 2026-10-27, 08:15-08:22 UTC, from a direct US connection. The browser was headed Chrome, with a new profile for each run. Both stores showed a Consentmo banner. The first layer had Preferences, Reject, and Accept. On both stores, Reject appears to be the merchant's own banner setup; we did not check their Consentmo settings. These runs do not stand in for every store that has Consentmo installed.
Nine runs in total. Store S had one Fresh run with no click, two Reject runs, and one Accept run. Store U had two Fresh runs, two Reject runs, and one Accept run. Each run opened the homepage, used that run's banner button, then opened one product page. We did not add a product to the cart, open checkout, or fill in a popup.
On every run the banner was on screen, and app.consentmo.com/users/versioning returned status enabled.
Store S: after Reject, the next page set a new _fbp and sent PageView
Counts are requests on the next product page. Fresh had no click. Reject and Accept are separate runs.
| Request on the next page | Fresh (no click) | Reject run 1 | Reject run 2 | Accept |
|---|---|---|---|---|
Meta facebook.com/tr | 1 (PageView) | 1 (PageView) | 1 (PageView) | 2 (PageView, ViewContent) |
TikTok analytics.tiktok.com/api/v2/pixel | 3 | 5 | 4 | 5 |
GA4 /g/collect | 5 | 5 | 5 | 5 |
The TikTok count includes one timing request that belongs to the page we had just left.
_fbp was present before the Reject click and absent after it. A new _fbp was set 1139 ms after the product page navigation started on Reject run 1, and 913 ms after it on Reject run 2.
The banner recorded Reject. cookieconsent_status was deny. cookieconsent_preferences_disabled listed analytics, marketing, and functionality on both stores. Store S's cookie also listed saleofdata.
We counted requests and read the consent cookies. We did not decode what each request carried, so this does not tell you how Meta or TikTok used them.
The banner recorded Reject, and on the next page a new _fbp was set and Meta and TikTok page events were sent.
Store U: four vendors sent nothing after Reject, The Trade Desk sent 12 and 13 requests
Counts are requests on the next product page. Fresh run 1 and Fresh run 2 had no click. The Accept run is a separate pass and is not in this table.
| Request on the next page | Fresh run 1 | Fresh run 2 | Reject run 1 | Reject run 2 |
|---|---|---|---|---|
Meta facebook.com/tr | 2 | 2 | 0 | 0 |
Bing UET bat.bing.com | 5 | 5 | 0 | 0 |
| Microsoft Clarity | 3 | 3 | 0 | 0 |
| Google Ads | 9 | 9 | 0 | 0 |
The Trade Desk adsrvr.org | 12 | 12 | 13 | 12 |
insight.adsrvr.org/track/realtimeconversion (POST, part of the row above) | 1 | 1 | 1 | 1 |
| ID sync requests to Tapad, Rubicon, AppNexus (Xandr), and media6degrees.com | 6 | 6 | 7 | 7 |
After Reject, _fbp was absent. The product page did not set it again. Both Reject runs ended with no _fbp.
Each Reject run sent 2 user_engagement hits, 0.27-0.38 s after navigation started, then no GA4 requests and no page_view for about 15 s.
The Trade Desk row counts requests to adsrvr.org. One request in each run, Fresh and Reject, was a POST to insight.adsrvr.org/track/realtimeconversion. The ID sync row counts requests to Tapad, Rubicon, AppNexus (Xandr), and media6degrees.com.
We counted requests. We did not decode what each request carried, so this does not tell you how The Trade Desk used them.
Before anyone clicks
Before any click, the homepage had already sent requests, including script downloads, to Meta, TikTok, and Google Ads on Store S, and to Meta, Bing UET, Microsoft Clarity, Google Ads, and The Trade Desk on Store U. Microsoft Clarity made 6 requests on each of Store U's 5 runs. See Meta Pixel and CAPI before Accept.
The banner extension these runs loaded
All 9 runs loaded gdpr-backpack-940.
Check your own store in 5 minutes
A longer checklist for the same kind of pass is how to audit cookies before Accept.
- Open your store in a normal (not headless) Chrome window, in a private window so no old cookies apply.
- Open DevTools, Network tab, tick "Preserve log".
- Click Reject on the Consentmo banner.
- Clear the Network log (the 🚫 icon).
- In Application > Cookies, check whether
_fbpis gone. - Open any product page. Filter Network by
facebook.com/tr,tiktok,bat.bing,adsrvr. Anything listed was sent after your Reject. - Check Application > Cookies again for a new
_fbp.
What this test doesn't show
These are two US stores. Reject appears to be the merchant's own banner setup; we did not check their Consentmo settings, so the tables do not describe every store running Consentmo.
We loaded the homepage and one product page. We did not test add to cart or checkout.
We counted whether requests were sent and how many. We did not decode the request contents, so this page does not classify those requests.
We did not observe server-side requests, including CAPI. See Meta CAPI after Reject All.
FAQ
Can I still use Consentmo?
We can't say. The listing shows "not currently available". Ask Consentmo directly; the listing says to contact them for support.
Did Reject stop the pixels?
On Store U, Meta, Bing UET, Microsoft Clarity and Google Ads sent nothing on the next page, and The Trade Desk still sent 12 and 13 requests. On Store S, the next page set a new _fbp and sent a Meta PageView, and TikTok sent a Pageview.
Does this mean these stores broke a law?
No conclusion. We only counted requests. Not legal advice.
Related guides
The other Reject and Decline captures, and the checklist for doing this pass yourself.
Not legal advice
Not legal advice.
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.