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
Perhaps I'm missing something, but it seems like unless you track the page path as part of the event name, there isn't a way to see on which pages a given event fired?
A hack solution for now could be to set the referrer to the current page using goatcounter_referrer, and use the referrer list to identify the pages on which the event ran. But this doesn't work for events fired by JS.
As a possible simple addition(?) that would allow the above hack to work universally, could we be allowed to specify the referrer in JS events as well? e.g.
Internally events are "just" pageviews, but with event=true and without the requirement that the "path" (event name) starts with /. Other than that, it's treated pretty much identical.
There isn't really any way to do what you want other than using the referrer. Maybe it should be doing that by default and/or the UI could be clarified on this 🤔
@arp242 Yes, what do you think, perhaps the default for an event's referrer should be the current page? In many ways that makes more sense.
Either way, it would still help if there was feature parity between JS events and data parameter events, so that the referrer can be overridden in both methods.
Perhaps I'm missing something, but it seems like unless you track the page path as part of the event name, there isn't a way to see on which pages a given event fired?
A hack solution for now could be to set the referrer to the current page using
goatcounter_referrer
, and use the referrer list to identify the pages on which the event ran. But this doesn't work for events fired by JS.As a possible simple addition(?) that would allow the above hack to work universally, could we be allowed to specify the referrer in JS events as well? e.g.
Arguably, this ISN'T a hack – as quite arguably the page on which the event fires IS its "referrer".
The text was updated successfully, but these errors were encountered: