Analytics treats in-page anchor jumps as pageviews about analytics

[tobiaslins]

We just rolled out a new version that now doesn't track same-page hash navigations anymore!
This should work now as expected without any changes on your side!

Thanks 🙏

[tobiaslins]

Hey @Justineo :)

We consider adding a way to disable automatic page view collection (and triggering them manually).
For now you will need to use beforeSend to skip tracking page views with # in the URL.

<Analytics beforeSend={function (event) {
    if(event.url.includes("#")) return 
    return event;
}} />

Something like that would work, but sadly there is no way to find out if it was a crosspage navigation or same page hash navigation.
https://vercel.com/docs/concepts/analytics/audiences/redacting-sensitive-data

[Justineo]

I think this workaround won't work as the page view event does not expose enough information. The page view from /foo to /bar#baz shouldn't be skipped.

We need both the URL before navigation and after it to see if history change is caused by in-page anchors but in current implementation we only got url.

analytics/packages/web/src/types.ts

Lines 1 to 4 in 73e33e7

	interface PageViewEvent {
	type: 'pageview';
	url: string;
	}

[Justineo]

Hello, I'm following up on the status of this issue. Has there been any progress?

[tobiaslins]

@Justineo
You could keep the previous page in useRef and only skip the event when its a same page navigation! What do you think?

[Justineo]

I think this is a common use case and shouldn’t require such workaround. Technically we can rewrite any client side logic but I think it should be handled by the analytics SDK itself.