You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Content analytics in dotCMS is not properly detecting when a page is accessed through a vanity URL. The analytics property for identifying vanity URLs always shows false, regardless of whether the page is accessed via a vanity URL or its original URL. This issue affects the accuracy of analytics data, making it difficult for users to track and evaluate the performance of pages accessed through vanity URLs. It impacts marketing teams and content managers who rely on this data for insights.
Screen.Recording.2025-01-15.at.5.39.13.PM.mov
Steps to Reproduce
Log into the dotCMS backend and ensure vanity URLs are configured.
Access a page using its configured vanity URL.
Check the content analytics data for the accessed page.
Observe that the property for identifying vanity URL access is set to false, even though the page was accessed via a vanity URL.
Acceptance Criteria
Content analytics should accurately detect and reflect whether a page was accessed via a vanity URL.
The property should display true when a page is accessed through a vanity URL.
dotCMS Version
Tested on main // Docker // FF
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
The text was updated successfully, but these errors were encountered:
Problem Statement
Content analytics in dotCMS is not properly detecting when a page is accessed through a vanity URL. The analytics property for identifying vanity URLs always shows false, regardless of whether the page is accessed via a vanity URL or its original URL. This issue affects the accuracy of analytics data, making it difficult for users to track and evaluate the performance of pages accessed through vanity URLs. It impacts marketing teams and content managers who rely on this data for insights.
Screen.Recording.2025-01-15.at.5.39.13.PM.mov
Steps to Reproduce
Acceptance Criteria
dotCMS Version
Tested on main // Docker // FF
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
The text was updated successfully, but these errors were encountered: