feat(Content Analytics) #31319 : Add telemetry customer category, customer name, and environment name to Content Analytics events#31459
Merged
jcastro-dotcms merged 10 commits intomainfrom Feb 26, 2025
Conversation
…tomer name, and environment name to Content Analytics events
|
Please use a Conventional Commit title format for this PR. For more information, see https://www.conventionalcommits.org/en/v1.0.0/ |
victoralfaro-dotcms
approved these changes
Feb 25, 2025
jdotcms
approved these changes
Feb 25, 2025
freddyDOTCMS
approved these changes
Feb 25, 2025
…customer-name-and-environment-name-to-content-analytics-events
…customer-name-and-environment-name-to-content-analytics-events
…customer-name-and-environment-name-to-content-analytics-events
…customer-name-and-environment-name-to-content-analytics-events
jcastro-dotcms
deleted the
issue-31319-Add-telemetry-customer-category-customer-name-and-environment-name-to-content-analytics-events
branch
fmontes
pushed a commit
that referenced
this pull request
Feb 26, 2025
…tomer name, and environment name to Content Analytics events (#31459) ### Proposed Changes * Adding four more attributes to a Customer Analytics Event: * Customer category. * Customer name. * Environment name. * Environment version. * The schema and database table was updated in order to reflect this. * The code changes were added to the `BasicProfileCollector` class. This means that absolutely all Data Collectors will have access to these new attributes, no matter where they're being triggered from.
spbolton
pushed a commit
that referenced
this pull request
Jun 20, 2025
…tomer name, and environment name to Content Analytics events (#31459) ### Proposed Changes * Adding four more attributes to a Customer Analytics Event: * Customer category. * Customer name. * Environment name. * Environment version. * The schema and database table was updated in order to reflect this. * The code changes were added to the `BasicProfileCollector` class. This means that absolutely all Data Collectors will have access to these new attributes, no matter where they're being triggered from.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
BasicProfileCollectorclass. This means that absolutely all Data Collectors will have access to these new attributes, no matter where they're being triggered from.This PR fixes: #31319