---
title: "Form Mail Template"
description: "An E-Mail Template is an HTML Template that can be used for sending an E-Mail using Mailjet. Each E-Mail from a Form Submit will then look like defined in the Template."
path: https://www.eonshowroom.eon.com/en/specials/form-mail-template.html
lastModified: 2026-04-23T07:19:32.661Z
---
# Form Mail Template
# Form Mail Template
An E-Mail Template is an HTML-based file used to define the layout and design of emails sent via **Mailjet** after a form submission. It ensures that every notification or confirmation mail follows a professional and consistent brand design.
### Headline Features
- Custom HTML/CSS: Full control over the visual appearance of the email.
- Dynamic Placeholders: Insert user data directly from form fields.
- Iterative Content: Automatically list all form inputs using a single tag.
- Timestamping: Log the exact moment of submission in various timezones.
- Attachment Handling: Support files are automatically attached (no setup needed).
- Anchor ID support for internal linking
## Configuration
### Headline editing in a nutshell
Main configuration options of the Headline component
- Template Source:Edit directly in DAM or upload an external HTML file.
- Form Integration:Added via the Form Container Dialog (not in the grid).
- Data Mapping:Use ${elementname} to link form fields to the email.
- Design Assets: Adjust E.ON logos and legal info in the provided example.
### In this how to
Here is a qucik overwiev on the relevant topics:
- Creating & Adjusting Templates
- Using Form Data (Placeholders)
- The mailContent Feature
- Timestamps & Timezones
- Element Name Rules
- Troubleshooting
#### Creating & Adjusting Templates
Editors can find a base example using the E.ON Brand Design in the DAM at: /dam/project-name/mail-template
**How to edit:**
1. **Direct Edit:** Modify the HTML directly in the DAM.
2. **External Edit:** Download the file, use an HTML editor of your choice, and re-upload.
3. **Customization:** You **must** adjust legal information, logos, and links to your specific needs.
#### Using Form Data (Placeholders)
To display values that the user entered into the form, use the following structure: ${elementname}
The ${elementname} will be replaced by the actual input value when the email is sent.
- **Example:** If your input field is named firstname, use ${firstname} in the template.
- **Note on Files:** Uploaded files are attached to the **Support Mail** automatically; no placeholder is required.
#### The mailContent Feature
If you don't want to specify each element manually, use the reserved *${mailContent}* placeholder. It automatically creates an HTML table of all submitted data.
**Advanced Parameters:**
You can modify the table by adding parameters in parentheses: *${mailContent(parameter)*}.
| Parameter | Function / Effect |
| --- | --- |
| border | Adds basic CSS styles (borders & padding). Exclusive to custom styles. |
| **emptyfields** | ****Shows all configured input elements, even if the user left them blank. |
| html | Disables sanitization (Warning: Use only if absolutely necessary). |
| nolabel | Uses technical element names instead of field labels. |
#### Server Timestamp
Use *${homerTimestamp}* to record exactly when the server accepted the submission.
- **Default (UTC):** *${homerTimestamp}* outputs ISO 8601 format (e.g., 2026-04-10T14:25:30Z).
- **Custom Format:** *${homerTimestamp(format:de)}* for German conventions or *${homerTimestamp(format:dd.MM.yyyy)}*.
- **Timezones:** *${homerTimestamp(timezone:Europe/Berlin)}*.
- **Combined:** *${homerTimestamp(format:de,timezone:Europe/Berlin)}.*
[Timezone ID List](https://docs.oracle.com/cd/E72987_01/wcs/tag-ref/MISC/TimeZones.html)
##### Useful Hint:
Never use a **comma ,** inside your custom format pattern. Commas are reserved as separators for the parameters. Use **dots .** or **colons :** instead.
#### Technical Rules for Element Names
The "Element Name" of your form fields must follow strict rules to work with placeholders:
1. **Unique:** No two fields can have the same name.
2. **Lowercase:** Use small letters only.
3. **No Specials:** No signs, blanks, or special characters.
4. **No Numbers:** Use letters only.
##### Useful Hint:
Always double-check the "Element Name" field in the Component Dialog of your Form Input (e.g., Textfield, Checkbox). If the name there is emailaddress, your placeholder in the HTML must be *${emailaddress*}.
#### Technical Rules for Element Names
The "Element Name" of your form fields must follow strict rules to work with placeholders:
1. **Unique:** No two fields can have the same name.
2. **Lowercase:** Use small letters only.
3. **No Specials:** No signs, blanks, or special characters.
4. **No Numbers:** Use letters only.
##### Useful Hint:
Always double-check the "Element Name" field in the Component Dialog of your Form Input (e.g., Textfield, Checkbox). If the name there is emailaddress, your placeholder in the HTML must be *${emailaddress*}.
#### Troubleshooting: Why is my Mail blank?
If your placeholders are visible in the received mail (e.g., it literally says "${firstname}"), check the following:
## Typo in Element Name
Is it *firstname* in the form but *${first_name}* in the HTML?
## Case Sensitivity
Did you use a capital letter in the HTML Template?
## DAM Sync
Did you forget to activate/publish the HTML Template after editing it in the DAM?
## Form Container
Is the correct and latest version of the Mail Template selected in the Form Container settings?
## Does, Don'ts and Grid Usage
### What you should do
- Use Inline CSS: Ensure your custom HTML template uses inline styles for maximum mail client compatibility
- Match Names: Ensure the ${placeholder} exactly matches the "Element Name" in the form container.
- Attach to Container: Always link your template within the Form Container Dialog.
- Update Legal: Always verify the footer, imprint, and logo are correct for your specific project.
### What you shouldn't do
- No JavaScript: Email clients will block templates containing