Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Record Content Type of Detail Pages Correctly in Events #31414

Open
freddyDOTCMS opened this issue Feb 18, 2025 · 1 comment · Fixed by #31446
Open

Record Content Type of Detail Pages Correctly in Events #31414

freddyDOTCMS opened this issue Feb 18, 2025 · 1 comment · Fixed by #31446
Assignees
@freddyDOTCMS
Labels
dotCMS : Analytics Data and Analytics Umbrella Team : Falcon Triage Type : Defect

Comments

@freddyDOTCMS
Copy link
Contributor

Parent Issue

No response

Problem Statement

Currently, when a user retrieves a Page using URL MAP, we log in Analytics 2 Events one for the URL MATCH and the other one for the Page Detail render. but the Content Type for the Page Detail render Events is the URL MAP Content Type when it should be HTML_PAGE

Steps to Reproduce

  • Start dotCMS with the full starter
  • Set up Analytics
  • Hot any Blog Page
  • Check the Analytics Events, you are going to see that the contentTypeName for the PAGE_REQUEST Events is going to be Blog

Acceptance Criteria

Save the PAGE_REQUEST event as a Page Content Type

dotCMS Version

latest in main

Proposed Objective

Please Select

Proposed Priority

Please Select

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response
@freddyDOTCMS freddyDOTCMS moved this from New to Next 1-3 Sprints in dotCMS - Product Planning Feb 18, 2025
@john-thomas-dotcms john-thomas-dotcms changed the title Save Detail Page Content Type Correctly Record Content Type of Detail Pages Correctly in Events Feb 19, 2025
@john-thomas-dotcms john-thomas-dotcms moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning Feb 19, 2025
@jcastro-dotcms jcastro-dotcms self-assigned this Feb 21, 2025
@jcastro-dotcms jcastro-dotcms moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Feb 21, 2025
jcastro-dotcms added a commit that referenced this issue Feb 21, 2025
@jcastro-dotcms
feat(Content Analytics) fixes #31414 : Record Content Type of Detail …
b259544 
…Pages Correctly in Events
@github-actions GitHub Actions
Copy link

PRs:

@jcastro-dotcms jcastro-dotcms moved this from In Progress to In Review in dotCMS - Product Planning Feb 21, 2025
github-merge-queue bot pushed a commit that referenced this issue Feb 24, 2025
@jcastro-dotcms
feat(Content Analytics) fixes #31414 : Record Content Type of Detail …
2d0b56b 
…Pages Correctly in Events (#31446)

### Proposed Changes
* Changing some parameters of the CA Event to include the appropriate
Content Type ID, Name, and Velocity Variable Name.
@github-actions github-actions bot mentioned this issue Feb 24, 2025
Merged
@jcastro-dotcms jcastro-dotcms moved this from In Review to QA in dotCMS - Product Planning Feb 24, 2025
@jcastro-dotcms jcastro-dotcms removed their assignment Feb 26, 2025
@freddyDOTCMS freddyDOTCMS self-assigned this Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@freddyDOTCMS freddyDOTCMS

Labels
dotCMS : Analytics Data and Analytics Umbrella Team : Falcon Triage Type : Defect
Projects
dotCMS - Product Planning
Status: QA
Milestone
No milestone
2 participants
@jcastro-dotcms @freddyDOTCMS