@tsteur opened this Issue on May 7th 2020 Member

Reported in https://wordpress.org/support/topic/some-minor-ui-tips/#post-12794720

You can reproduce it eg using this HTML

<a target="_blank"  href="https://foo.bar/wp-content/plugins/test.php?api_user_id=123455&dlkey=49849494&content_type=application/pdf">PDF</a>
or 
<a target="_blank"  href="https://foo.bar/wp-content/plugins/test.php?api_user_id=123455&amp;dlkey=49849494&amp;content_type=application/pdf">PDF</a>

resulting in a false link in visitor log (reports itself seem to be fine)

https://foo.bar/wp-content/plugins/test.php?api_user_id=123455&amp;dlkey=49849494&amp;content_type=application/pdf

instead of

https://foo.bar/wp-content/plugins/test.php?api_user_id=123455&dlkey=49849494&content_type=application/pdf

Quick test shows the tracker might send the correct value, but might be some escaping issue.

@mattab commented on May 7th 2020 Member
@tsteur commented on May 7th 2020 Member

It's not related to any segmenting or so.

@tsteur commented on April 5th 2021 Member

there's more insights here https://wordpress.org/support/topic/some-user-facing-logs-have-a-url-encoding-issue-for-ampersands-in-links/

Basically, it seems to work in Downloads reports but not in Visits log and real time widget meaning it is likely indeed an escaping issue.

@tsteur commented on July 22nd 2021 Member

This might be fixed meanwhile. Need to first reproduce it before looking into it.

@sgiehl commented on June 24th 2022 Member

I'm actually not able to reproduce the tracking issue. If I have a page with the links mentioned in the issue description, both are tracked with the same url. Maybe the browser already removes the encoded ampersands.
Nevertheless: If I manually trigger tracking a download with an encoded url like:

_paq.push(['trackLink', 'https://foo.bar/wp-content/plugins/test.php?api_user_id=132&amp;dlkey=132&amp;content_type=application/pdf', 'download']);

That url is displayed encoded in the visitor log, while it works when it's tracked as outlink. Will check why that is the case...

This Issue was closed on June 28th 2022
Powered by GitHub Issue Mirror