Skip to main content

Forms: Settings

Page title, width, colours, validation, and Hidden Values for automatic Profile enrichment

Updated this week

Forms: Settings

Once you've created a Form, the Settings in the bottom bar are where you fine-tune how it looks, how it behaves when visitors make mistakes, and what data it quietly adds to every Profile that submits.

Most of what's here feels like small stuff — width, colours, error messages — but this is the layer that separates a Form that looks like "a form someone bolted onto our site" from a Form that looks like part of your brand. It's worth the ten minutes.


In this article


Form

In the Form Settings section you can adjust the working name and the page title.

Working name

Internal only — this is what you see in your Activity list. Use it to find the Form later. Good naming conventions become gold when you have dozens of Forms in the system.

Page title

The Page title is the text displayed in the browser tab when visitors open your Form. Visitors will see this — in their browser tab, in bookmarks, and in search results if the Form is ever indexed.

Don't leave it blank or generic. A title like "Subscribe to [Your brand] weekly" or "Download the guide – [Your brand]" reinforces the promise and looks far more professional than "Untitled Form".

Language

Configure language settings to enhance accessibility. Select the language the content is written in so that screen readers know how to read the text. This setting does not affect your content — it's purely a signal to assistive technologies.

💡 Tip. If you run Forms across Nordic or European markets in multiple languages, set this per Form so Swedish content is read as Swedish, Dutch as Dutch, French as French, and so on. It's a small accessibility investment with real impact for users who rely on screen readers.


Design

This is where the Form starts to feel like part of your brand.

Form width

Adjust the width of the Form. Maximum width is 1500px.

💡 Tip. A narrower Form (around 500–700px) almost always feels more focused and converts better than a Form that stretches across the full screen. Wide Forms tend to look like spreadsheets. Narrow Forms look like a conversation.

Body colour

Set the Body colour with a hex code, RGB values, or the colour picker.

To make the body colour transparent, click the X icon next to the colour code. The preview shows a white circle crossed with a red line.

Your Form body is now transparent:

Transparent backgrounds are particularly useful when embedding the Form as an iFrame on a page where you want it to inherit the surrounding colour.

Background image

Set the background colour with a hex code, RGB values, or the colour picker.

Upload a background image if you prefer. When uploading, select how the image should be displayed and enter an Alt text.

Option

Behaviour

Tile

Standard setting, works everywhere where background image is supported. The image repeats in both x and y directions.

Fill

Fills up the background, rescales the image, keeps dimensions and crops to fit.

Fit

Shows the whole background image once, rescales, but does not crop.

Stretch

Fills up the background, rescales by stretching the image instead of cropping.

💡 Tip. Use "Fill" for photography-style backgrounds (landscapes, product shots), "Tile" for subtle patterns, and "Stretch" only when you know the image was designed for exactly that behaviour — stretching tends to distort photos.

Border

Adjust border width and radius (roundness of corners). Set border colour with hex code, RGB, or the colour picker.

A soft border radius (around 8–12px) and a subtle border colour give the Form a "card" feel that separates it visually from the page background. It's a small visual cue that says "fill me in".


Validation

Validation controls what happens when a visitor makes a mistake — either leaving a required field empty, or typing the wrong format into a field (for example, letters in a phone number).

Good validation is invisible when everything goes right and genuinely helpful when something goes wrong. Frustrated visitors don't submit Forms.

Highlight missed field

Tick the Highlight missed field checkbox to change the colour of the input field the visitor missed. Adjust the Highlight colour with hex code, RGB or the colour picker.

A warm red is conventional, but any colour that contrasts clearly with your Form background works. Avoid using your brand's primary colour for errors — it confuses visual hierarchy.

Missed field message

Enter a Missed field message to display under an empty required input field when the visitor tries to submit.

This error message only appears if the field is set as required, or in the event of a confirmation field not matching the original.

Write the message in plain, friendly language. "Please enter your email address" is better than "This field is required". Tell the visitor what to do, not what they did wrong.

Wrong format message

Enter a Wrong format message to display when a visitor types information that doesn't match the format of the input field — for example, letters in a number field, or an incomplete email.

Preview and test error messages

Toggle Preview error messages to see in the editor how the errors will look.

To test messages, click on the Input Field element and write an incorrect response directly in the editor — for example, letters in a field set to number type.

Note: Error messages and styling only appear if you set up the input field as required, or in the event of the confirmation field not matching the original.


Hidden values

Hidden values are one of the most powerful — and underused — features in the Forms tool. They let you automatically add data to every Profile that completes your Form, without the visitor seeing or typing anything.

Use hidden values to enrich Profiles with specific data depending on which Form they filled in. The values are the same for every visitor who completes the Form.

Three types of hidden values

Profile Attribute

Set the value of an Attribute for every visitor who completes the Form.

Example: if your campaign targets a specific country, set the Country Attribute value to "Sweden" as a hidden value on your Swedish Form. Every Profile who fills in that Form automatically gets Country = Sweden, without needing to type it. Perfect for segmentation and personalisation down the line.

Profile Tags

Use a Profile Tag to differentiate Profiles who opt in via a particular Form.

Example: a Form shared only from a trade show might add the tag source:tradeshow-2025. A Form shared via a partner's newsletter might add source:partner-X. You can then build Segments by source and measure downstream engagement by channel.

Event Property

Add a custom field to the Event data of the Form – Submit Event. Use this to further personalise how you collect and act on Event data.


💡 Tip. Event Properties are perfect for data you want to analyse but don't necessarily want to store permanently on the Profile — useful for A/B testing, seasonal offers, or tracking which Form version performed better without cluttering your Attributes.


Use cases

Lead nurturing — tag the source, trigger the right flow

You have three Forms for the same download — one embedded on the blog, one on the landing page, one on a partner's site. Use hidden values to tag each submission with its source. Your Marketing Automation welcome flow can then branch based on source: bloggers get content recommendations, landing-page visitors get product-focused nurturing, partner visitors get co-branded content.

Retention — route preference updates to the right Subscription

A preference centre Form shared only with customers (not prospects) can carry a hidden tag like audience:customer. Every Profile who updates preferences via that Form is automatically flagged, which lets you segment "customers who recently updated preferences" — your most engaged, data-fresh audience.

Brand building — campaign attribution without extra fields

Running a seasonal campaign? Add a hidden Event Property like campaign:spring-2026 to the Form. You can report on exactly how many Profiles signed up from the campaign without asking visitors to fill in an extra "how did you hear about us?" dropdown. Less friction, better data.

Loyalty — silently promote your best leads

If a Form is shared only with VIPs or long-standing customers (for example, an exclusive event registration), a hidden tag like tier:vip adds an invisible layer of segmentation. These Profiles can then receive differentiated communications forever after.


Preview

Preview your Form under the Preview tab. Switch between Mobile and Desktop to see how it looks on different devices.


Check mobile before you publish. Most Form views happen on a phone, and issues that are invisible on a 27-inch monitor (cramped fields, too-small buttons, awkward line breaks) are very visible on a 5-inch screen.


Go through the Form as a visitor would. Can you tap the button easily? Are labels readable? Does the headline explain what you're signing up for? If anything feels off, go back and adjust before publishing.


💡 Tips & tricks

  • Design settings are reusable. Once you've locked in width, colours, and border style you're happy with, save the Form as a template. Every new Form inherits your standards.

  • Accessible error messages matter. Clear, calm error language prevents abandonment. Avoid technical-sounding phrases.

  • Use hidden values generously. Every Form you build should probably carry at least one hidden value — source, campaign, or audience type. It's free data that makes later analysis much easier.

  • Don't over-style. If your Form looks dramatically different from your main website, embedded placements feel jarring. Match your site's typography and spacing where you can.

  • Preview the actual environment. If the Form will be embedded on a dark-background page, preview it with the transparent body colour toggled on — otherwise you'll publish a Form with a jarring white block.


Next steps

Settings done — now decide what happens after submit:

Did this answer your question?