Handling Page URL Cardinality in Workspace at Scale

Question

Has anyone else struggled with the Page URL dimension hitting cardinality limits in Workspace? On heavier traffic months, I’m seeing 10–15% of URLs rolled into Low Traffic, which makes the stakeholder dashboards pretty unreliable.

I know Adobe generally recommends leaning on Page Name or classifications, but that doesn’t always cut it when the request is for an exact URL list. We’ve tried a few things:

Classifying off a clean URL key (helpful but introduces latency + governance overhead).
Segmenting by page categories (good directional view, but not enough detail for stakeholder asks).
Falling back to Data Warehouse pulls (accurate but not self-service friendly).

Curious how other enterprise teams are dealing with this:

Any practical ways you’ve kept URL-level visibility in Workspace without blowing up cardinality?
Are there approaches you’ve found that give business users “exact URL” access without sending them to Data Warehouse every time?
And has anyone leaned on CJA as a workaround here — does it actually solve the long-tail URL reporting pain?

Would love to hear what’s working (or not) for others.

bjoern__koth · Accepted Answer

Hi @jarrell43

sounds like you are capturing URLs including all query and hash values which, in certain cases lead to low traffic if these are calculated on a visitor or session base. The reporting benefits are questionable I'd say.

Depending on your URL structure I would recommend to

only capture the domain and pathname and strip all query params and hashes
should there be a dynamic part in the pathname like /path/to/<user id>/pageOrDocument, replace it with something generic like "user id" or "document id"

The simplest way to get a clean URL would be a custom code data element in your tag manager that returns.

return document.URL.split("?")[0].split("#")[0];

This should give you a high level consolidation of all of your unique URLs.

@jennifer_dungan afaik CJA does not have this limitation anymore.

Jennifer_Dungan · Answer

As far as I am aware, CJA would have the same sort of "low traffic" buckets.

I am curious, how many URLs are you dealing with and what sort of reports would require needing to see every single URL directly out of Adobe?

Even the Adobe Workspaces will only show up to 400 values at a time.. and the export from Workspaces will only support up to 50,000 values at a time. Unless you are using a Segment of "Section A" then show me all URLs and that list is a manageable amount to view in a report (but limited by Low Traffic)... You can also use Data Warehouse pulls, but that has other challenges of not being able to de-duplicate metrics like UVs or Visits....

Honestly, we do very little reporting using the URLs. When we do use URLs is when we are digging into potential issues or doing spot checks.. so we just stick with URLs we do have, and if the issue is all "low traffic" then we use our data lake to help augment the investigation...

Essentially, this has rarely been a problem for us... but I would like to know more about your needs to see if I can make any recommendations.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded