To get started, head over to Admin > Customers > Customer Custom Fields. From here, you'll want to create a new field type.
After creating a new field type, you'll want to populate it with answers. There are different options that you can test, including drop downs, check boxes, and text fields. In this example you'll see the drop down used to determine customer type.
You'll first name the field, and then determine the type. You can then populate the options depending on which type you've selected. Using the drop down type, you can apply icons when this option is selected. This is covered in more detail in the Customer Badges article.
Once complete, click Update Customer field. This new Customer Custom field will be available for future editing/reference on the Customer Custom field page.
Now you will be able to access this on new customers when you create them. Just use the Additional Fields tab.
You'll see the new Customer Custom fields there.
In this example. the customer was set to Business.
You can use or update Custom Fields on existing customers by editing the customer > Additional Fields. Or you can bulk update them via CSV. That is covered in more detail at the bottom of our Customer Import article.
If you need to edit or add new Custom Field options, you can do so from the customer record itself when you're editing it, or back in Admin > Customer Custom fields.
You will also be able to build customer lists based off these answers. Just head over to Admin > Customer Lists to target your Custom Fields. Once you target them, you can generate a list to send a Marketr email to.
For example, if you're having a sale specifically for your business clients, you could set up a Customer List to pull as "Business" customers, then send a targeted email blast to them through Marketr.
Looking to create a pop up alert for a customer? Here's our Feature Friday video on how to do that!
You can also add custom fields for tickets, for more instruction, click here.
** PLEASE NOTE ** Special characters such as / and ? are not allowed in the names of custom fields.