Router macros for the ingest endpoint and the dashboard.

defmodule MyAppWeb.Router do
  use MyAppWeb, :router
  import Pixelex.Router

  # the browser's way in: POST /px/e, GET /px/px.gif, GET /px/pixelex.js
  pixelex_ingest "/px"

  scope "/admin" do
    pipe_through [:browser, :require_admin]
    pixelex_dashboard "/analytics"
  end
end

The ingest endpoint takes no pipeline

pixelex_ingest/2 deliberately forwards outside the :browser pipeline. Session fetching, flash and CSRF protection are all wrong here: the endpoint is called by a beacon on pages the visitor is not signed in to, and a CSRF token would have to be embedded in the tracker for every page, which is not protection, it is ceremony. What actually bounds it is the per-site event allowlist, the consent gate, bot filtering and the rate limiter — see Pixelex.Plug.Ingest.

The dashboard takes yours

pixelex_dashboard/2 mounts a LiveView and inherits whatever pipeline it is scoped inside. It has no authentication of its own. Put it behind yours. A site's full traffic, sources and funnels are not public data, and a library that shipped its own auth would be a second login for you to maintain and a first one for an attacker to find.