Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Custom event `referrer` property in payload not overriding Plausible's internal referrer

Abierto
  • ¿Algo no está bien?
#5,564 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
elixir, next.js
Área
analytics, api, backend

Línea de trabajo

Start by tracing how the https://plausible.io/api/event endpoint handles the supplied referrer when events arrive from a session managed by next-plausible. Verify whether the explicit payload value is discarded in favor of the session referrer, and confirm that the provided referrer is used for attribution on delayed custom events.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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:

  1. Automatic Tracking: Using next-plausible for standard pageview tracking and other automatic events.
  2. Custom Events: Sending specific custom events by directly calling the https://plausible.io/api/event endpoint from our server-side using a fetch 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:
Lenguaje dominante
Elixir
Estrellas
29.7k
Forks
1.9k
Merge medio
3 d 22 h
PR fusionados (30 d)
50

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de plausible/analytics

Todos los issues de plausible/analytics

Issues similares

Más issues de Elixir

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.