Notification templates

Reusable push copy with variables.

#What a notification template is

A notification template is a single push title + body pair drawn from a curated corpus of real push notifications documented from growth-stage apps. Templates give you a starting point — tested copy patterns you can adapt to your brand — without writing from scratch.

The corpus contains 180 entries spanning habit-forming, win-back, trial conversion, social, and transactional patterns. Each entry carries attribution (the real app it was documented from), a verbatim flag, and links to the public sources used to verify the copy.

#Categories

Templates are organised into ten categories:

Category	What it covers
habit	Daily reminders and routine-building nudges.
streak	Streak protection, milestone celebration, and loss-aversion warnings.
winback	Re-engagement after extended inactivity — escalating emotional tone.
reactivation	Return prompts for recently lapsed users (shorter lapse than win-back).
trial	Trial start, midpoint, expiry warning, and post-expiry upgrade prompts.
promo	Time-limited offers, discount codes, and event-based promotions.
social	Friend activity, kudos, league standings, and community events.
progress	Milestone completions, goal achievements, and metric summaries.
transactional	Confirmations, payment receipts, and status updates.
onboarding	First-session, feature discovery, and account setup prompts.

#Variables and placeholders

Notification body and title text uses two placeholder conventions:

Syntax	Meaning
`{{ variable_name }}`	Known chip variable — interpolated automatically from the user's attributes at send time. The five supported variables are first_name, days_left, plan, country, and lifetime_value.
`[bracket text]`	Literal placeholder — rendered exactly as written. Replace it with your own value before activating (e.g. [product_name], [Feature X]).

Examples

// Chip variable — interpolated automatically
"Welcome, {{ first_name }}! Your trial ends in {{ days_left }} days."

// Bracket placeholder — you fill this in
"Your {{ plan }} subscription includes [Feature X] — tap to explore."

Heads up

A {{ variable }} that does not match one of the five known chip names is rendered as-is (the literal string {{ unknown }}) rather than being interpolated. Use bracket notation for tenant-specific values that Pushlane does not know about.

#Verbatim vs. reconstructed

Each template carries a verbatim flag:

Flag	Meaning
verbatim: true	The copy was confirmed word-for-word by at least one public source (linked in the sources field). Use as-is or adapt.
verbatim: false	The copy was reconstructed from a documented notification pattern. The tone and structure are accurate but the exact wording may differ from the original.

The sourceApp field names the real app the template was documented from. This is attribution only — no app logos are displayed.

#Using a template

Notification templates surface in two places in the product:

Message editor — "Use as template": Open a Message node in the flow builder and click the template library icon. Browse by category, select a template, and its title and body are loaded into the editor. Edit the copy before saving.
New flow seed — "Start from this notification": From the template library, start a new single-step flow pre-populated with the chosen notification. Add delays, branches, or additional messages around it.

Note

Templates set the message channel to push. Pushlane is a push-only platform — in-app and SMS channels are not available.

#Deeplinks

Some templates carry a deeplink hint — a URL scheme or universal link to a specific screen in your app. When present it populates the deeplink field of the message variant. Replace the hint with your own scheme before activating.

Message variant — deeplink field

{
  "content": {
    "title": "Your streak ends in 10 minutes",
    "body": "One lesson saves your {{ days_left }}-day streak.",
    "deeplink": "myapp://lesson/daily"
  }
}

The deeplink is passed through to the APNs payload as-is. Your app must register the scheme or associated domain and handle the URL in your notification delegate.

Next: Audiences — build the segment of users a flow targets.