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
Figure why the behaviour flow of Google Analytics revealed that we're tracking pages both with and without trailing slashes while users browse the site:
/styles and /styles/
/patterns and /patterns/
/component and /components/
This distinction would be fine for landing pages, as we don't control how other websites link to us. However, during navigation between pages of the design system, we should only see one format for the paths.
Why
We likely have some form of redirect in place to make this transparent to users (at the price of an extra request, which would be great to avoid). However, in the analytics, it muddies the data as:
both URLs are the same page
this doubling of pages pushes other pages out of the top X of the data, making it harder to review how users browse the Design System site
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
We know why we're seeing both URLs on Google Analytics
We've chosen and implemented a fix so we only track a single page
The text was updated successfully, but these errors were encountered:
What
Figure why the behaviour flow of Google Analytics revealed that we're tracking pages both with and without trailing slashes while users browse the site:
/styles
and/styles/
/patterns
and/patterns/
/component
and/components/
This distinction would be fine for landing pages, as we don't control how other websites link to us. However, during navigation between pages of the design system, we should only see one format for the paths.
Why
We likely have some form of redirect in place to make this transparent to users (at the price of an extra request, which would be great to avoid). However, in the analytics, it muddies the data as:
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
The text was updated successfully, but these errors were encountered: