Define the pattern
Name the reusable message and write the stable title, body, and payload.
Notification templates
Move at LiveOps speed without losing your voice.
Give teams reusable message foundations with dynamic variables, platform context, lifecycle controls, and a direct path into automation.
Illustrative template editorActive template
Overview
Audience
Messages
Delivery
Settings
Live workspace
Guild invitation
Variables
03Used by
02 triggersPlatform
iOS + AndroidCurrent flow
Title{{guildName}} needs you
BodyA new raid begins in {{minutes}}
Datascreen: guild_raid
Example data for product illustration. Not customer performance.
A template should create consistency, not sameness.
PushHub keeps the approved structure stable while allowing the player and event context to make each notification relevant.
How it works
Create once, personalize at the right boundary.
Declare variables
Use readable placeholders for player, game, or event context.
Connect the trigger
Reference the template from an active event automation.
Manage the lifecycle
Edit, inspect, activate, or retire templates without losing ownership.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Reusable content
Create app-scoped templates for recurring player moments.
Dynamic placeholders
Resolve template variables from authenticated event input at dispatch.
Trigger connection
Attach a template to an event trigger with optional delay and conditions.
Localization sets
Planned locale variants will manage translated content under one template identity.
In the game
Reusable foundations for recurring moments.
Social request
Personalize a guild, friend, or team invitation from event context.
Reward ready
Insert the reward name and relevant claim window without rewriting the pattern.
Store rotation
Reuse a governed offer format while changing bundle and expiry context.
Governance begins with visible ownership.
Templates remain app-scoped, keep stable identities for triggers, and separate content reuse from provider credentials or raw device tokens.
App boundary
A template cannot silently cross into another app.
Validated references
Triggers require an existing template identity.
Honest localization
Managed translation sets are not advertised as Live.
Questions teams ask before they commit.
Template placeholders are resolved from the variables submitted with a matching event.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.