| Doc. Number | Article Title | Effective Date | Version |
| FHC-TAG-2 | How to Use Tags | April 23, 2026 | 0.7 |
This article describes the Tags functionality within the Forth CRM. This article is broken down into the following sections.
Overview
Tags are placeholders used in templates, campaigns, emails, forms, etc.
{FULLNAME} is a default tag that comes with your CRM. It populates the value (full name of contact) stored for the First and Last Name fields. When a user generates a document containing placeholder tags, they are replaced with the information from the CRM.
Tags can be extremely helpful if you understand how to use them.
If you have an agreement, contract, etc. that you are going to use multiple times or a campaign that you are going to send out to multiple contacts, placing tags in your documents will save time by replacing the placeholder tags with actual contact information, so you don't have to manually type everything in. It also helps avoid typos, skipping, or duplicating contacts, and makes the document templates reusable.
Types of tags
There are two types of tags in the FORTH CRM:
- System - tags that come with your CRM and can be used right away.
- Custom - tags that you create yourself based on custom fields in your CRM.
Default tags
Default tags are divided into three categories. Click the category name to access appropriate Help Center articles on that topic.
Using tags
You can add Tags or replaceable fields to a template. Be sure to paste them as plain text. Any styling transferred from the source could cause issues when generating the document.
For a list of available tags, visit our comprehensive Tags article by clicking HERE.
1. First, locate an area of the template where a Tag needs to be added. A good indication is anywhere there is an open underlined area in the middle of a paragraph, like below.
2. To add the tags here, we suggest replacing the entire underlined section with the tag.
3. Once you’ve added the tag, add the underlined styling using the toolbar.
Doing it this way prevents a few issues. First, the empty underlined spaces are underscores “_” which is different than the actual style underline. See below how the underline of the tags does not line up with the underscores.
4. If you want to add extra empty space at the beginning or end of the tags like this, go into the HTML and add some space within the <span> element the tag is wrapped in.
A <span> is a way to add HTML styling around text or another element. We’ll go over those later but you can review https://www.w3schools.com/tags/tag_span.asp for more information.
5. To add the space, you need to specifically add a non-breaking space. There is a difference between just hitting the space bar vs when you use a non-breaking space. HTML readers will automatically ignore some spaces, the command used below tells the HTML reader (or the editor/doc gen system) in our case, that the spaces are intentional and you want them to appear in the output.
<span style="text-decoration: underline;"> {FULLNAME} </span>
Custom Company Tags
Users can create and use company-level tags like {COMPANY_CUSTOMFIELDNAME}.
The tags will look like this: {COMPANY_CUSTOMFIELDNAME}. The "COMPANY_CUSTOMFIELDNAMES" part must exactly match the name of the custom field.
- Tags will work in emails, templates, automations, and webhooks that involve company data.
- Users will only see and use tags for fields they're allows to access, based on their role and permissions.
- Tags will work with automations and webhook integrations, allowing company-specific data to trigger actions or populate information.
Troubleshooting
A common issue with tags is the tag's text like {FULLNAME} appearing, instead of being replaced with information from the contact. Most often, this is due to the <span> starting within the tags in the HTML instead of outside. There may be other issues like this where there is something in the HTML preventing the system from properly reading the tag. If you run into issues like this, first check the tag in the HTML.
You can see in this example below that there does not appear to be any issue based on what you see in the editor.
<span style="text-decoration: underline;"> { <span style="text-decoration: underline;">FULLNAME</span>} </span>