Custom fields
Short answer
A custom field is any detail you keep about a subscriber besides their name and address, like a company or a birthday. They come from your CSV columns, your forms, or Add custom field on a subscriber’s page, and most show on every subscriber’s page.
Jounce keeps three things about everyone by itself: their email address, their first name, and their last name. Anything else you want to remember is a custom field, such as their company, their city, or a birthday.
A field added on a subscriber’s page or in an import is a box on every subscriber’s page, empty until you fill it in. A field that came only from a form shows only on the people who have a value in it.
Where a field comes from
- A CSV import. On Match your columns, a column that isn’t a Jounce field can become one with Create new field…. See Add a custom field while importing.
- A form. An extra field on one of your signup forms saves as a custom field on each person who fills it in. If someone is already on your list, a form only fills in an empty field. It never changes or clears a saved one. See What happens when someone submits.
- A subscriber’s page. Add custom field names one and puts the cursor in it. See Add a custom field.
One field per name
Jounce matches fields by name. Capitals, spaces, hyphens, and underscores don’t make a name different: Job Title, job-title, and job_title are one field. So a form’s Job Title field and a CSV column called Job Title fill the same field.
Type a name you already have in Add custom field or Create new field…, and Jounce finds that field instead of making a second one.
A field made through the developer API can have an id that differs from its name; the API calls it the field’s key. Say the id is company and the name is Company Inc. Typing either one finds the field.
A custom field can’t take the name of something Jounce keeps by itself, such as Email, First name, Last name, or Status. Spaces, hyphens, underscores, and capitals don’t get around this: First name, first_name, and E-mail are all refused.
When you type one as a field’s name, Jounce says That name belongs to a built-in field — pick another under the name. The dialog stays open for a different one. If your workspace already has a field with such a name, it keeps working and stays on every subscriber’s page.
A form or the developer API can still send a field named like first name or E-mail. Jounce doesn’t save it as a custom field. A first or last name counts as the real one when none was sent with it, and anything else is left out.
A workspace keeps up to 25 custom fields. Past that, Jounce says You can keep up to 25 custom fields. Remove one to add another. To remove one, see Delete a custom field.
Where you can use them
- The filter builder’s Data field finds people by what a field holds, or by whether it’s empty. See The filter types.
- In the email editor, a link can be set to fill in a custom field for whoever clicks it.
An email’s text can show a person’s first name, last name, or address, but not a custom field.
Deleting a value or a field
On someone’s page, the three dots above a field with a value offer Delete value. It empties the field for that person alone. See Delete a custom field’s value.
For Admins and Managers, the same menu also holds Delete field. It takes the field off every subscriber’s page, with every value in it, and it can’t be undone. See Delete a custom field.
More in this topic
Updated