TryGhost
OSS
Ghost
Added Gift source attribution for gift-link signups no ref - gift-link visits (`{post_url}?gift={token}`) unlock a single gated post; when the reader signs up they're attributed to whatever channel the link was shared through (usually Direct), so gift-derived signups are invisible as a distinct source in the Growth tab - gift links leave no server-side trace tying a signup to the gift (unlike gift subscriptions, which set member.status='gift'): the gift-links service only validates tokens and the `_gift` token is surfaced to Tinybird for visit analytics only - so at signup the gift signal exists solely as the `?gift` param on the unlocked post's URL in the browser - the history recorder ignores that param (it only reads ref/source/utm), so tag a `?gift` visit with referrer source 'Gift' (medium 'gift') there; it then flows through the normal referrer pipeline into members_created_events.referrer_source. The real referrer url is kept and an explicit ref/source/utm on the link still wins - a valid token renders in place (invalid tokens are 301-stripped pre-render), so a `?gift` present when the recorder runs is always a genuine gift view
nx run ghost:build:assets
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx run ghost:build:assets
Click to copy
Linux
4 CPU cores
read-write
access token used
7d69f373
28896