Note: This help article documents how to use custom fields when you’re writing your campaign message. To learn how to create them via CSV Upload, "Creating Custom Fields via CSV Upload.".
Custom Fields enable you to dynamically insert personalized contact information in your campaign messages. They help your messages feel more relevant to your customers while also helping the text look and read like a one-to-one conversation.
For example, an auto shop wants to include the make and model information for their customers in their campaign messages. When uploading a CSV, they create a custom field labeled “Make/Model” and include their customers’ car data in the file. The auto shop can then use that field in their promotional texts (i.e. “Hey :contact:! It’s time to service your :make_model:..”). Each of their customers in that audience will only see their own make/model reflected in the body of the campaign, making the message much more relevant and personal to each individual.
For an illustrated walkthrough of how to use custom fields in your campaign messages, follow these steps after you’ve created your custom fields.
1. Open the campaign form, and click Edit next to the message section.
2. Start typing your message into the text box. When you get to a point where you want to include one of your custom fields, click the :a: icon.
3. You’ll see a list of all the personalized fields you can use in this campaign. In this example, the auto shop will select “Make/Model.” Once selected, the field will populate in the text box in a grey bubble.
4. You can add as many personalized fields as you like. Once you’re done writing your message, click Finish.
5. When your campaign is ready, you can schedule, send, or test it out. If you test your campaign and send it to anyone (including yourself) who are not included in the CSV upload, and therefore don’t have custom field data assigned to you, then the test message will populate the fields with the first row of valid data. In this example, that would be “Honda CRV” for :make_model: and “1 / 3” for :due_date:.