A custom field allows you to collect subscriber information beyond the standard fields of first name and email address. An example would be a custom field called last name so you can get the full names of your subscribers. You create a custom field, and then you’re able to use that in your forms or with the API (see the Subscribers endpoint for adding custom field values to a subscriber.)Note that you must create a custom field before you can use it with the subscribe methods on the forms, sequences, and tags endpoints.
Create a custom field for your account. The label field must be unique to your account. Whitespace will be removed from the beginning and the end of your label.Additionally, a key field and a name field will be generated for you. The key is an ASCII-only, lowercased, underscored representation of your label. This key must be unique to your account. Keys are used in personalization tags in sequences and broadcasts. Names are unique identifiers for use in the HTML of custom forms. They are made up of a combination of ID and the key of the custom field prefixed with “ck_field”.A maximum of 140 custom fields are allowed. Requests that exceed this limit will return a response of 400.
Updates a custom field label (see Create field above for more information on labels). Note that the key will change but the name remains the same when the label is updated.
An update to a custom field will break all of the liquid personalization tags in emails that reference it - e.g. if you update a Zip_Code custom field to Post_Code, all liquid tags referencing {{ subscriber.Zip_Code }} would no longer work and need to be replaced with {{ subscriber.Post_Code }}.
The API response returned when updating custom fields is dependent on the number of custom fields in the request, as shown by the examples below. A maximum of 140 custom fields are allowed. Requests that exceed this limit will return a response of 400.