-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Past Issues Searched
- I have searched open and closed issues to make sure that the bug has not yet been reported
Issue is a Bug Report
- This is a bug report and not a feature request, nor asking for self-hosted support
Using official Plausible Cloud hosting or self-hosting?
Plausible Cloud from plausible.io
Describe the bug
We are experiencing an issue where the referrer
property, explicitly sent within the payload of our custom events via a direct call to Plausible's API, is not consistently used for attribution. This occurs even when we provide a specific referrer value, which is stored in our database (original referred from his first login).
Instead, Plausible's dashboard often displays the internal referrer you got from his active session (first pageview from that session), particularly for events happening within an active session managed by next-plausible
.
Our setup involves:
- Automatic Tracking: Using
next-plausible
for standard pageview tracking and other automatic events. - Custom Events: Sending specific custom events by directly calling the
https://plausible.io/api/event
endpoint from our server-side using afetch
request.
We are trying to do this because our Goals are usually happening hours or days after the first interaction with the page, so we want to track the original referrer as referrer for those events in Plausible.
As a workaround we are registering them now as Custom Properties, but finding some issue with that workaround too.
Expected behavior
We'd expect the referrer sent by our api call to override Plausible's internal referrer and the custom event to be linked with the referrer we are providing.
Screenshots
No response
Environment
- OS:
- Browser:
- Browser Version: