When using StructuredWeb, one of the key benefits for you and your partners is the multitude of merge fields available. Merge fields allow you to automatically add information into tactics without manually adding it yourself. All merge fields in the platform follow this format: [MergeField]. Note how the merge field itself is in brackets. Additionally, there are not spaces and each word is capitalized. The case and spelling of merge fields need to be exact for the merge field to properly work.



Account-specific merge fields - Market Assets

Market Assets are merge fields that are populated directly by partners. The specific market assets are custom for each client, but commonly used market assets include Company Name, Company Logo, and Website Address. All Market assets are in the following format: [MarketAsset####] Market assets are to be used ONLY when setting up content at the program level. Market assets are replaced with the value when a tactic is copied into a partner account, and so the market asset merge field cannot be added directly into a tactic already created in the partner's account.


To learn more about how to create additional market assets, view the support article here.


While not technically a Market Asset, another important partner-specific merge field that functions very similarly is [MyWebAddress]. This merge field is used frequently when linking from a tactic like an email to a landing page. This merge field is replaced when the email is copied into the partner account and replaced with a unique domain in their StructuredWeb account. This is how the system keeps each partner copy of the landing page separate.



User-Specific Merge Fields

Beyond market assets, tactics can also use merge fields to pull in information for the person sending an email. This will use the record owner of the contact to determine which user to populate with the merge field. Popular uses for the user-specific merge fields include an email signature or the sender name and email address. These merge fields can be found in the editor by selecting Merge Fields and then User Information.

  • [MyFirstName] - The user's first name.
  • [MyLastName] - The user's last name.
  • [MyCompany] - The company name for the user.
  • [MyEmail] - The user's email address.
  • [MyPhone] - The phone number of the user.
  • [MyWebAddress] - the web address for the user.


When using user merge fields, these can be added in the program setup or by the account-level user. The merge fields are replaced in the preview or when the final campaign is sent.



Contact Merge Fields

Contact merge fields allow you to merge information about the email recipient into the email. A classic example of this would be to have a greeting at the begging of the email address to "Dear [FirstName]," to add personalization. These merge fields can be found in the editor by selecting Merge Fields and then Contact Information.

  • [FirstName] - first name of the email recipient
  • [LastName] - Last name of the email recipient
  • [Company] - company name of the email recipient
  • [Email] - email address of the recipient
  • [Salutation] - salutation of the recipient (e.g. Mr. or Mrs.)
  • [Phone] - phone number of the recipient


When using contact merge fields, these can be added in the program setup or by the account-level user. The merge fields are replaced in the preview or when the final campaign is sent.


As a best practice we advise against using too many contact merge fields when setting up templates. Partners often have different levels of contact information when importing and requiring a merge field that the partner doesn't have can cause the output not to display properly.


In addition to normal contact merge fields, advanced accounts can also utilize Profile Merge Fields. If an account has imported custom profile information into the CRM along with the basic contact details they can use profile merge fields to add this information into emails. Profile merge fields should NOT be setup at the program level as profiles are uniquely set for each account. To learn more about using profile merge fields click here.