Firetip | HTML Template Engine Specification

FULL DOCUMENTATION & SYNTAX GUIDE

Firetip HTML Template Engine Specification

Complete technical documentation for formatting templates, implementing conditional injections, and handling database attributes through Firetips campaign node.

Documentation Index

PROPRIETARY HTML EMAIL BUILDER

Launch visual template suite, code generator & Faigen AI to help build amazing email templates.

SECTION 1

Core Syntax Rules

The Firetip engine parses raw HTML strings prior to SMTP queue delivery. All replacement tags must adhere strictly to the bracket format to be recognized by Firetip's parsing parser.

[parameter_name]

SECTION 2

Complete Parameter Reference

The following parameters are compiled dynamically from your audience list and system environment variables during every transmission cycle:

Tag Syntax	Data Source	Description & Output Format
[username]	Audience list	Recovers the registered audience handle string.
[name]	Audience list	Inserts the recipient's first name.
[surname]	Audience list	Inserts the recipient's surname or family name.
[email]	Audience list	Target recipient's active email destination string.
[phone]	Audience list	Recovers the contact phone number string.
[lang]	Audience list	Language localization code (e.g. en, fr, es).
[date]	system clock	Exact ISO timestamp generated at dispatch time (YYYY-MM-DD).
[id]	Audience list	Unique primary key identification number (integer).
[account_type]	Audience list	Tier classification integer (e.g. 3 for Pro accounts).
[node]	environment	Active routing node identifier (`sc01`).
[node_id]	environment	Specific hardware identifier for the executing node block.
[company_name]	Audience list	Corporate entity or organization name string associated with the profile.
[unsubscribe]	gateway handler	Injects the secure opt-out URL link for list compliance.
[tracking_pixel]	gateway handler	Renders the invisible 1x1 tracking beacon for open detection.
[t_link]	gateway handler	Generated target link wrapped for engagement metrics.
[click_link]	gateway handler	Click-through tracking redirect URL for inbound response logging.
[v_link]	gateway handler	Verification link used for authenticating message interaction or list opt-in.

SECTION 3

Conditional Account Type Display

You can render customized sections based on user privilege levels (such as distinguishing between Free Tier and Pro Subscribers using account type parameters).

<!-- If Account Type is Pro -->
<div style="display: [IF_PRO]block; display: none; color: #dc3545;">
    <p>Thank you for maintaining a Pro subscription on the sc01 node.</p>
</div>

SECTION 4

Null & Fallback Handling

If a database record returns an empty value for an injected parameter, the Firetip engine automatically replaces the tag with a safe default string (Valued audience) to prevent broken markup or blank display spaces in the final inbox delivery.

SECTION 5

Live Test Dispatch

Ready to test your template layout? Send a mock transaction trigger directly through the sovereign gateway.

Run Test Transmission Gateway: smtp.firetip.pro

SECTION 6

Pre-Configured Dashboard & API Values

Certain campaign variables—such as tracking links, target destinations, and redirect behaviors—can be pre-configured directly inside your account dashboard or injected dynamically via API calls prior to queue execution.

// Example: API payload parameter pre-assignment
$payload = [
"t_link" => "https://scloud.live/r/target",
"click_link" => "https://scloud.live/click"
];

SECTION 7

Custom Metadata & Extended Tags

You can append custom key-value pairs to your dispatch payloads for advanced campaign segmentation and internal tracking through the sc01 node.

// Example: Custom metadata injection tag syntax
[custom_tag_name]

SECTION 8

RFC Compliance Standards

All messages dispatched through the sc01 node and Firetip campaign engine adhere strictly to Internet Engineering Task Force (IETF) standards to ensure optimal deliverability, header formatting, and MTA compatibility.

Standard	Specification	Implementation Note
RFC 5322	Internet Message Format	Enforces strict header structuring, date formatting, and line-length limits (78 characters max per line).
RFC 2045-2049	Multipurpose Internet Mail Extensions (MIME)	Manages multipart alternative boundaries separating plain text and HTML payloads correctly.
RFC 2369	List Header Fields	Injects explicit `List-Unsubscribe` and `List-Help` headers for automated audience processing.

// Example: RFC 2369 compliant unsubscribe header injection
List-Unsubscribe: <[unsubscribe]>
List-Unsubscribe-Post: List-Unsubscribe=One-Click