Skip to main content

Documentation Index

Fetch the complete documentation index at: https://documentation.outpost.pub/llms.txt

Use this file to discover all available pages before exploring further.

Outpost automatically applies labels to members as they move through subscription lifecycle events, interact with your conversion tools, and sync with integrations. These labels are visible in your member list and Ghost, and can be used as triggers and conditions in email flows and the rules engine.
Labels prefixed with ZZZ_ sort to the bottom of Ghost’s label list — this is intentional to keep system tracking labels out of the way. Labels prefixed with # are behavior flags.Several labels use dynamic suffixes (dates, IDs, GUIDs, slugs) to carry extra data within the label name itself.

Email & Marketing

LabelApplied when…
#Unsubscribe_Via_Outpost_EmailMember unsubscribes via an Outpost email
Marketing_OkayMember has opted in to marketing emails (applied automatically after the welcome action)
Marketing_OptOutMember has opted out of marketing through Outpost (e.g., unsubscribed from a marketing email). Treated as a marketing opt-out signal.
No_MarketingMember has opted out of marketing in Shopify and was synced over. Treated as a marketing opt-out signal.
#Ignore_WelcomeSkips the welcome email flow for this member
#Ignore_AdvancedSkips advanced autoresponder emails
#Ignore_UpgradeSkips upgrade email sequences

Subscription Lifecycle

LabelApplied when…
Active_ClientMember has an active paid subscription
Former_Paid_SubscriberMember was previously paid and is now free
Former_Comp_SubscriberMember’s complimentary subscription has ended
Plan_Renewal_[date]Tracks the member’s subscription renewal date (e.g., Plan_Renewal_15-02-2026)

Payment & Checkout

LabelApplied when…
Started_CheckoutMember started the checkout process
Payment_StartedMember clicked an offer or payment CTA
Payment_PendingMember initiated checkout but hasn’t completed payment
CouponMember used a coupon or discount code

Donations

LabelApplied when…
Gave_A_DonationMember made a donation via Stripe or PayPal
ZZZ_Donation_[date]_[amount]_[provider]Dated donation record with amount and payment provider. Date format is dd-mm-YYYY (e.g., ZZZ_Donation_15-03-2026_50_Stripe)

Gifts & Group Subscriptions

LabelApplied when…
Bought_Gift_SubscriptionMember purchased a gift subscription for someone else
Received_Gift_SubscriptionMember received a gift subscription
Group_BuyerMember purchased a group subscription
Group_Member_[GUID]Member is part of a group subscription (GUID identifies the group)
Institutional_Group_SubscriptionMember is part of an institutional group subscription

Retention

LabelApplied when…
Saved_By_Retention_OfferMember was retained through a retention offer
ZZZ_Retention_Offer_[ID]Tracks which specific retention offer was used
ZZZ_Retention_Offer_Date_[date]Tracks when the retention offer was applied
ZZZ_Failed_Payment_Ended_Subscription_[date]A payment failure ended this subscription
ZZZ_Retention_Payment_Continue_Subscription_[date]A retention payment continued this subscription

Paywalls & CTAs

LabelApplied when…
#ZZZ_Soft_Registration_Wall_SignupMember signed up via a registration paywall
#ZZZ_Soft_Registration_Wall_DisplayMember was shown a registration paywall
#ZZZ_Soft_Upgrade_Wall_SignupMember upgraded via an upgrade paywall
#ZZZ_Soft_Upgrade_Wall_DisplayMember was shown an upgrade paywall
#ZZZ_Signup_CTA_[ID]Member clicked a specific signup CTA (ID identifies the CTA)
#ZZZ_Signup_Post_[ID]Member signed up via a CTA on a specific post (ID identifies the post)
#ZZZ_Signup_Session_[GUID]Tracks the signup session for attribution

UTM & Traffic Attribution

These labels are applied automatically at signup when UTM parameters or referral values are present in the URL. All five can be applied to the same member if all parameters are present.
LabelApplied when…URL parameters captured
source:[value]Member arrived via a tracked sourceutm_source, source, or ref
medium:[value]Member arrived via a tracked medium (channel type)utm_medium
campaign:[value]Member arrived via a tracked campaignutm_campaign
content:[value]Member arrived via a tracked creative or content variantutm_content
term:[value]Member arrived via a tracked search term or audience segmentutm_term
Examples:
  • A member who arrives from ?utm_source=twitter&utm_campaign=launch gets: source:twitter, campaign:launch
  • A member who arrives from ?ref=newsletter-partner gets: source:newsletter-partner
  • A member who arrives from a full UTM URL gets up to five attribution labels
See CTAs & Auto Display for full details and examples.

Gated Content

LabelApplied when…
Gated_Download_[slug]Member downloaded a gated PDF (slug identifies the PDF)
Signup_Via_Gated_Download_[slug]Member signed up through a gated PDF download

Subscription Schedules

LabelApplied when…
Subscription_ScheduleMember is enrolled in a subscription schedule
Sub_Sched_[GUID]Identifies the specific subscription schedule the member is on

Shipping (for sites with shipping enabled)

LabelApplied when…
Address_AddedMember has added a shipping/mailing address

Integrations

LabelApplied when…
Webflow_Form_SubmissionMember signed up via a Webflow form
HubspotMember has been synced to HubSpot CRM
SalesforceMember has been synced to Salesforce
FeedPressMember is linked to a FeedPress podcast feed
SupercastMember is linked to a Supercast private podcast feed
ShopifyMember has been synced from Shopify

Recharge

LabelApplied when…
Magazine_SubscriberMember is an active Recharge subscriber (label name is configurable per site)
Former_Magazine_SubscriberMember was a Recharge subscriber (label name is configurable)
Issues_Remaining_[count]Tracks how many Recharge issues the member has remaining

Using system labels in automation

System labels can be used as triggers and conditions in Email Flows and the Rules Engine just like any other label. Examples:
  • Trigger a win-back flow when Former_Paid_Subscriber is applied
  • Send a confirmation email when Gave_A_Donation is applied
  • Start an onboarding sequence when Received_Gift_Subscription is applied
  • Exclude #Ignore_Upgrade members from upgrade campaigns