How to Add a Custom Field in Systeme.io Forms and Contacts
Create custom fields only for information you will actually use. Systeme.io lets you add a named field with a unique key, place it on a form and store the submitted value on the contact record.
Create a custom field only when the answer will change what happens next
Extra form fields create friction, so collect information only when it will affect segmentation, qualification, personalization or a later operational step. Asking for data without a defined use makes the form longer without improving the customer journey.
Start with one or two fields that have a clear purpose. Examples include business type, goal, experience level or a customer reference that will be used by a workflow, filter or support process.
Create the field from a contact record and give it a stable key
Systeme.io's current help guide creates a custom field from CRM, Contacts, then an individual contact record. Choose Add new custom field, enter a clear name and assign the unique key used to identify that field technically.
Treat the key as a long-term identifier. Use a predictable naming convention so the field remains understandable when it later appears in automations, integrations or exported data.
Add the custom field to the form as an input type
Open the page editor, drag in a Form input element and choose the custom data type you created from the Input Type setting. Systeme.io's form element can also group inputs, checkboxes and the submit button into one form container.
Set the label, placeholder and required status according to the value of the information. Do not make a field mandatory simply because the option exists; require it only when the next step genuinely depends on the answer.
Keep simple lead-capture forms lighter than qualification forms
An email opt-in usually benefits from very few fields because the visitor is making a small commitment. A quote request, application or onboarding form can justify more questions because the value of the next step is higher.
Match the amount of information requested to the user's motivation at that stage. If you need deeper qualification later, collect it after the first conversion rather than forcing every visitor to complete a long form upfront.
Use stored data only in automations you can explain and verify
Once the value is stored on the contact, it can support filters, segmentation and integrations. Connect it to tags or automation only when the rule has a clear business purpose and you can predict the outcome for each possible value.
Avoid building a large automation tree around untested fields. First confirm that the data is captured consistently, then add the smallest rule that improves the follow-up or routing of the contact.
Submit a real test and inspect the contact record before launch
Use a recognizable test value, submit the published form and open the resulting contact record in the CRM. Confirm that the custom field contains exactly the value you expected and that no standard field was accidentally overwritten.
This end-to-end test is more useful than checking only the editor. It proves that the visitor-facing input, field mapping and stored contact data all work before you send meaningful traffic to the page.
Check these four signals.
✓Each field has a defined segmentation or workflow purpose
✓The unique key follows a stable naming convention
✓Only necessary fields are marked as required
✓A test submission stores the expected value on the contact
Need the bigger picture before choosing a plan?
Open the current offer and check Systeme.io pricing, limits and features before deciding on a subscription.
Official sources for this guide
Software pricing and features can change. Review the official documentation below before choosing a product or plan.
