Stop gating the referral beacon, and report the visit properly

Fixkamo-marketing
Shipped
August 20, 2026 at 1:58 AM UTC
Author
Kamo
Commit
48493ae

Two corrections to what shipped, both restoring the behaviour this feature was asked for. The beacon was gating itself on the analytics consent record. That reads like a privacy win and is not one: the referral record is what a partner is PAID against, so declining analytics did not shrink the numbers, it made the visits unattributable — the visit still happened, the signup still converted, and the partner simply went unpaid for traffic they really sent. It is ungated now, and what keeps that proportionate is unchanged and stronger: a visitor who never followed a partner link is never cookied and never measured at all. Our own product analytics stays gated, as it should. check-mrt-cookie now pins the ungated beacon and the no-cookie-no-beacon rule so neither drifts back. Page title, time zone and screen size ride along again. They were dropped as undisclosed, which was the right instinct and the wrong fix — the visitor drawer has fields for all three and showed em dashes forever. They are bounded here, clipped again server-side against their column widths, and now actually described in the cookie and privacy disclosures rather than collected quietly.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing