matomo-org/matomo

Clarify "Keep Page URL fragments when tracking Page URLs" Option in Measurable Settings

Open

#22,791 opened on Nov 22, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)PHP (2,847 forks)batch import
EnhancementHelp wantedtriaged

Repository metrics

Stars
 (21,513 stars)
PR merge metrics
 (Avg merge 8d 11h) (106 merged PRs in 30d)

Description

Within the configuration of a measurable there is an option "Keep Page URL fragments when tracking Page URLs", this option is not super clear, could we precise that this is about #. Screenshot from 2024-11-22 10-51-13

Steps to reproduce

  1. Open the Matomo settings and navigate to the configuration of a Measurable.
  2. Locate the option labeled "Keep Page URL fragments when tracking Page URLs".
  3. Review the description or functionality associated with this option.

What I got:

The option "Keep Page URL fragments when tracking Page URLs" lacks clarity. It is not immediately clear that it refers to tracking the fragment identifier (#) in the URL, which can affect how analytics handle single-page applications or anchor-based navigation.

What I expected instead:

A more precise explanation for the option, such as:
"This setting determines whether the fragment identifier (e.g., #section) in URLs is included when tracking page views. Enable this if you want analytics to differentiate between sections of a page identified by # fragments."

Contributor guide

Research direction
Update the description of the option 'Keep Page URL fragments when tracking Page URLs' to clarify that it refers to the fragment identifier (#) in URLs. Provide a clearer explanation as suggested in the issue.
Tech stack
php
Domain
analytics
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90