Running Consent Pro V2 on a Webflow project that integrates Shopify via Shopyflow. After scanning, the Manager shows several hundred uncategorized trackers, all attributed to shopyflow.io as the provider, with 14-digit numeric names.
I cross-checked these in Shopify admin, each numeric “tracker name” matches an individual product ID in the connected catalog. So the scanner is treating dynamic Shopify product IDs as if each were a separate tracker, instead of aggregating them under a single shopyflow.io provider entry. The count grows on every rescan, and manual per-tracker categorization with “Fill with AI” isn’t feasible at this scale.
This is a client project under NDA, so I can’t share staging URL, Webflow read-only link, or screen recordings publicly. Could someone from the Finsweet team reach out via DM so I can share all the reproduction details (URL, read-only link, Loom showing the product ID correlation) privately?
We dug through the Consent Pro V2 documentation looking specifically for bulk categorization, provider-level grouping, or wildcard/regex rules for tracker aggregation — and we couldn’t find anything covering that kind of functionality, so we can’t confirm it exists as a built-in feature right now.
What you’re running into — the scanner treating each dynamic product ID as a separate tracker instead of grouping them under a single shopyflow.io provider entry — does appear to be a limitation in how the scanner handles dynamic third-party identifiers. There’s no documented mechanism to teach it that certain numeric values belong to the same service.
This is genuinely worth raising with the Finsweet team directly, and we want to make sure it gets in front of them — both for investigation and as input for the product roadmap. We’ve escalated similar scanner limitation cases before and the team takes them seriously.
Given your NDA, no need to share anything publicly. @Support-Luis or @Support-Pedro can reach out via DM to collect reproduction details privately whenever you’re ready.
Just let us know if you’d like that DM escalation, and feel free to pass along any additional context about catalog size, your Shopyflow setup, or the specific tracker types being detected — that’ll all be useful for the team.
To add on to this, this is a case of dynamic url fragmentation problem. The scanner is fingerprinting tracker identity by full URL so each product ID becomes a unique tracker key rather than being rolled up under the shopyflow.io domain.
It could be loading product-specific resources at URLs like cdn.shopyflow.io/[product-id]/ then hashing that full path as the tracker identity instead of normalizing to the domain or a pattern.
You need to first of all clear the backlog by bulk categorizing. In the Consent Pro V2 manager, filter the uncategorized list by provider = shopyflow.io, select all, and assign a single category e.g. Necessary
The category should be Necessary if the Shopify integration is required for the site to function (product display, cart, checkout), or Functional if it’s enhancement-only.
Then to prevent recurrence, create a tracker pattern/rule. Consent Pro V2 supports custom tracker rules where you define a URL pattern (regex or wildcard) and a category. Create one rule matching *.shopyflow.io or shopyflow.io and assign it the appropriate category. New product IDs picked up on future rescans will match the rule and won’t accumulate as uncategorized.
How to create a tracker rule
Head to your Consent Pro V2 manager
Navigate to Trackers/Cookie Manager
Look for a Custom Rules/Tracker Rules/Add Tracker button
Create the rule with these values:
- Name: Shopyflow
- Provider: shopyflow.io
- Match pattern: shopyflow.io or *.shopyflow.io
- Category: Necessary/Functional
- Description: Shopify product catalog integration via Shopyflow
The save and trigger a rescan
Let us know how it goes, I also sent you a DM asking for more site details
