Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
28896
bd86772d 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
by Kevin Ansf...
Succeeded
28896
bd86772d 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
by Kevin Ansf...
Succeeded
28896
e551dc14 Added Gift source attribution for gift-link signups no ref - gift-link visits (`{post_url}?gift={token}`) were attributed to whatever channel the link happened to be shared through (usually Direct), so gift-derived signups were invisible as a distinct source in the Growth tab - the gift token never reaches member attribution: it's stripped before the history recorder runs, and member.status='gift' is a member property that the attribution-event analytics don't aggregate over - tag a `?gift` visit with referrer source 'Gift' (medium 'gift') in the frontend history recorder so it 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 - channel is the right attribution dimension here (it composes with the gifted post's content attribution rather than replacing it), but sourcing it from client history is the debatable choice vs setting it server-side at redemption where the validated token already lives - opening as a draft to discuss
by Kevin Ansf...