LogoLogo
Developers
  • Welcome
  • Introduction
  • Getting Started
    • Overview
    • What can we do?
    • Features & Packages
    • SDKs
  • SERVICES
    • Introduction about services
    • Identity
      • Brand
        • Examples
        • How to identify a brand
        • What default values when a brand is created?
        • How to be a reseller
        • Multiple Brand Management
      • User *
        • User Type
        • Username
        • User Status
        • Username vs. Login Name
        • Password
          • User-defined options
          • Built-in policies
        • Authentication Methods
          • Traditional Login
          • External Login
          • Login with Email link
        • Referral (Invite Friends)
          • Example
        • Password Policy
        • Login with Google
      • Device
        • Type
        • Device Identifier (Device Code)
        • Device Registering
        • Access Limit
    • Subscription
      • What is Package?
      • Package (Pricing Plan)
      • Plans & Pricing *
        • Licensing *
        • Subscription Type *
        • Feature
          • Examples
        • Package
        • Price *
        • Coupon
        • License
          • License Status
          • License Delivery Type
          • License Source
        • Pseudo Flow *
          • Licensing Flow *
          • Pricing Flow *
          • Coupon Application Flow *
    • Billing
      • Payment
        • Payment Status
        • Commission
        • Instant Payment Notification (IPN) *
          • Payment Gateway
          • Supported Gateways
        • Payment Transaction Overview
      • Transaction *
      • Invoice *
    • Wallet
      • Wallet *
        • Secure Practices *
        • ✔️Pseudo Flow *
      • Redeem *
    • Security
      • Black List
      • Risk Levels
    • Community
      • Issue
        • Examples
        • Pseudo Flow
      • Organization
    • Content Delivery Network (CDN)
      • CDN
        • CDN Storage
        • Uploading files to a CDN
        • Downloading files from a CDN
        • Are There Any Limitations?
        • Best Practices
    • Analytics
      • Tracking
        • Tracking Activity
        • Tracking Email
        • Tracking Notification
      • Log & Debug
      • Notification
    • Integration
      • Authentication
      • Payment Gateways
      • Push Notification
      • SMS Provider
      • SMTP Provider
      • Gitbook
    • Brand Settings (Branding)
      • What are Permissions and Roles?
        • System permissions & brand-based permissions
          • A (6 resources)
          • B (7 resources)
          • C (4 resources)
          • D (3 resources)
          • E (2 resources)
          • F (1 resource)
          • I (3 resources)
          • L (1 resource)
          • O (1 organization)
          • P (4 resources)
          • R (1 resource)
          • S (2 resources)
          • T (4 resources)
          • U (7 resources)
          • W (1 resource)
        • System Roles & Brand-based Roles
        • Granting Permissions
        • Assigning Roles
        • Best Practices
        • Pseudo Flow
        • Conclusion
      • What is Issue Category
      • What is Feature?
      • What is Subscription Type?
      • What is Subscription?
      • What is Commission Rate?
      • Events & Patterns
        • Event
          • Events for Community (Organization) (4)
          • Events for Device (3)
          • Events for License (2)
          • Events for Payment (8)
          • Events for System (9)
          • Events for Ticket (Issue) (6)
          • Events for User (47)
            • User.Account_ (5)
            • User.Coupon_ (1)
            • User.Email_ (5)
            • User.Expiration_ (3)
            • User.Inactive_ (2)
            • User.Invoice_ (1)
            • User.License_ (1)
            • User.Logged_ (3)
            • User.Password_ (3)
            • User.Phone_ (2)
            • User.Profile_ (2)
            • User.Receipt_ (1)
            • User.Referee_ (1)
            • User.Registered (2)
            • User.Reward_ (3)
            • User.Service_ (1)
            • User.SMS_ (1)
            • User.Status_ (5)
            • User.Suspicious_ (4)
            • User.Ticket_ (1)
          • Events for Wallet (4)
          • (Missing Events) *
        • WalletEarningEvent
          • Earning.User_ (8)
          • Earning.Wallet_ (2)
        • Email Templates *
        • SMS Templates *
      • Tags
      • Domains
      • Email templates
    • System Constants (Read-only)
      • Country
      • State
      • City
      • Time Zone
      • Currency
      • Language
      • Exchange Rate
  • Other concepts
    • Built-in resource
      • Built-in roles
        • Best practice
      • Built-in permissions
    • JFW Status
    • Default data
    • System data
    • Soft deletion data
    • Cryptography
    • Mailing
      • Examples
      • Email Sender
      • Email Template
    • Scheduler
      • Examples
      • Schedulers Used In JFW
    • Tracking Level
  • Versioning
  • Workflows
  • References
    • Internal references
    • External references
      • MailKit
      • MIME Type
  • Changelog
Powered by GitBook
LogoLogo

For developers

  • Developers

For users

  • Admin & cPanel

Examples

  • BoostPTE

Copyright @2018-2025

On this page
  • What is an Email Template?
  • How are Email Templates Used in JFW?
  • Placeholder
  • Entity Placeholders

Was this helpful?

  1. Other concepts
  2. Mailing

Email Template

Last updated 1 year ago

Was this helpful?

Note: This section provides an overview of email templates and how they are used in JFW. It also provides a list of placeholders that you can use in your email templates. We store email templates in TrackingEmailPattern table. The table includes columns for the email template ID, brand ID, email subject, email body, and the user who created or last modified the record, along with the corresponding date and time.

What is an Email Template?

An email template is a preformatted email that you can use to send to your contacts. It is a reusable HTML file that you can use to send emails to your contacts. You can use email templates to send emails to your contacts, such as newsletters, promotions, and other marketing emails.

How are Email Templates Used in JFW?

In JFW, once an is triggered, the system sends an email to the contact using the email template associated with the event. The email template contains placeholders that you can use to personalize the email for each contact. When the system sends the email, it replaces the placeholders with the contact-specific information.

Placeholder

The email template can contain placeholders that you can use to personalize the email for each contact. You can use placeholders to insert contact-specific information, such as the contact's name, email address, and other contact details. In JFW, Handlebars syntax defines placeholders in the email template. Example: {{brand.product_name}}, {{user.first_name}}.

Entity Placeholders

Brand
  • {{brand.brand_code}} - The placeholder key for the [Brand_Code] property.

  • {{brand.email_support}} - The placeholder key for the [Email_Support] property.

  • {{brand.email_support_title}} - The placeholder key for the [Email_Support_Title] property.

  • {{brand.system_email}} - The placeholder key for the [System_Email] property.

  • {{brand.system_email_title}} - The placeholder key for the [System_Email_Title] property.

  • {{brand.product_website}} - The placeholder key for the [Product_Website] property.

  • {{brand.product_name}} - The placeholder key for the [Product_Name] property.

  • {{brand.product_alias}} - The placeholder key for the [Product_Alias] property.

  • {{brand.product_prefix_name}} - The placeholder key for the [Product_Prefix_Name] property.

  • {{brand.website_cpanel}} - The placeholder key for the [Website_CPanel] property.

  • {{brand.website_admin_tool}} - The placeholder key for the [Website_Admin_Tool] property.

  • {{brand.website_admin_tool2}} - The placeholder key for the [Website_Admin_Tool2] property.

  • {{brand.website_admin_tool3}} - The placeholder key for the [Website_Admin_Tool3] property.

  • {{brand.website_protocol}} - The placeholder key for the [Website_Protocol] property.

  • {{brand.domain_white_list}} - The placeholder key for the [Domain_White_List] property.

  • {{brand.bundle_identifier}} - The placeholder key for the [Bundle_Identifier] property.

  • {{brand.author_name}} - The placeholder key for the [Author_Name] property.

  • {{brand.app_description}} - The placeholder key for the [App_Description] property.

  • {{brand.app_version}} - The placeholder key for the [App_Version] property.

  • {{brand.access_code}} - The placeholder key for the [Access_Code] property.

  • {{brand.company_name}} - The placeholder key for the [Company_Name] property.

  • {{brand.website}} - The placeholder key for the [Website] property.

  • {{brand.logo_image_path}} - The placeholder key for the [Logo_Image_Path] property.

  • {{brand.shortcut_icon_path}} - The placeholder key for the [Shortcut_Icon_Path] property.

  • {{brand.description}} - The placeholder key for the [Description] property.

User
  • {{user.first_name}} - The placeholder key for the [First_Name] property.

  • {{user.last_name}} - The placeholder key for the [Last_Name] property.

  • {{user.nick_name}} - The placeholder key for the [Nick_Name] property.

event