{{ }} — for tokens, conditionals, and dynamic content throughout the platform. Here's a quick breakdown of how it works:
Knowledge Base
GPTWeb Templating: Handlebars Syntax
Great question! GPTWeb uses Handlebars-style templating syntax — double curly braces
| Feature | Syntax | Example Output |
|---|---|---|
| Basic Token | `{{raw:visitor.first_name}}` | Alex |
| Formatter | `{{raw:visitor.last_seen|relative}}` | 2 days ago |
| Fallback Value | `{{raw:visitor.first_name || "there"}}` | Alex or "there" |
| Conditional | `{{raw:#if known}}...{{raw:/if}}` | Renders if visitor is known |
| Negation | `{{raw:#unless anonymous}}...{{raw:/unless}}` | Renders if NOT anonymous |
| AI Zone | `{{raw:ai_zone:greeting}}` | AI-generated personalized greeting |
You'll find this syntax used across welcome messages, email templates, agent workflows, campaign content, and system prompts. The
raw: prefix inside the braces is a GPTWeb convention that tells the rendering engine to process and replace the token — and it also lets you display token syntax literally in documentation without it being evaluated. It's a clean, readable templating approach that makes personalization accessible without requiring any coding knowledge. Want to dive deeper into getting started with templates or explore specific use cases?GPTWeb is the future of engagement — websites and marketing automation combined, built for the AI era, built for now.