Within a landing page, you can use buttons or CTAs (Call To Action) designed only for navigation, for example to take the user to a link or another page. In these cases, there is no form involved, so no post-submission actions are available.
When you use the submit button of a form, instead, the Actions tab comes into play.
After the landing page or survey is submitted, you can decide which actions to trigger using the Add action button. In this scenario, there is a next step to manage, and this is where actions become available, allowing you to direct the contact to another page, convert goals, start an automated flow and more.
On this page you’ll find the full list of available actions, with examples to help you understand when to use them and how to combine them.
Landing page actions
Complete response
This action marks the response as completed.
It’s added automatically to post-submission actions and is enabled by default.
Navigate
Allows you to send the contact to another page after submission.
You can choose the previous page, the next page, the final page, a specific page, or reload the current page. You can also open the destination in a new browser tab or force the participant to log out. By default, this action navigates to the final page.
Check an entered value
Lets you check the content of an answer before moving forward. For example, you can require the contact to select “I accept” on the privacy policy question for the questionnaire to be considered valid.
This action uses a placeholder, available in the Code tab for each question.
You can also define what format counts as valid by choosing whether to accept or reject specific values, or by checking that the answer is an email address, a phone number, or a number.
Convert a goal
Allows you to link survey completion to a conversion goal.
If you’ve already set up goals, you can choose which one should increase when the questionnaire is completed, and see the result in the platform dashboard. You can also set one or more conversion parameters to enrich tracking.
Contact actions
Add/remove from audience
Lets you manage a contact’s membership in a static audience after submission.
- If you choose Remove, the contact is removed from the selected static audience, if they’re in it
- If you choose Add, the contact is added to the selected static audience, as long as the contact and the audience belong to the same database, or the static audience belongs to the global database
Save linked fields on the contact
Lets you update the fields of the contact who submitted based on the answers provided in the questionnaire.
You can decide how to handle fields linked to questions hidden by visibility conditions: you can update fields linked to hidden questions as well, or update only fields linked to questions that were actually shown.
If updating the contact adds new contact details, you can also decide whether to always enable them for receiving. If you choose No, new contact details are enabled only when explicitly allowed by the page form fields.
Set a field value
Lets you assign a value to a contact field in one of the available databases.
You can choose which field to update and which value to set.
For text or number fields, you can also use the placeholder of a landing page question
Assign expression result to a field
Lets you set a field using the result of an expression.
After you select the field from the ones available in your databases, you can define the expression to apply.
Inside the expression you can use a landing page question placeholder or apply filters to contact fields. Alternatively, you can pick an expression that’s already in your library.
Increment a number field
Lets you increase or decrease the value of a numeric field.
After you select the contact field, define how much to change it by: the increment can only be a positive integer, even if the selected field is a decimal type.
If you enter a negative value, the result will be a decrease of the selected field value.
Subscribe contact
Lets you add the contact to a database after submission.
First, choose the destination database. If you select Source database, the system tries to identify the correct database automatically. For example, if the contact comes from a forwarded communication, the database of the contact who forwarded the email is used. If the database can’t be determined, the subscription won’t be performed.
You can specify the contact’s source by choosing one of the default options or any custom sources available in your account.
Then define what should happen if the contact is already in the database:
Update data without updating status: the contact keeps their current status, but their data is updated
Return an error without updating: no changes are applied and the contact sees an error
Update data and status: both data and status are updated, and the status becomes the value specified in the next field
Finally, choose which status the contact should have in the database:
Unconfirmed: the contact is added with an unconfirmed status and will need to confirm their subscription
Subscribed: the contact is added directly with a subscribed status
Unsubscribe contact
Lets you manage a contact’s unsubscription from the database.
You can specify the unsubscribe reason by choosing one of the default options or any custom sources available in your account.
You can also enable Generate unsubscription without changing status. In that case, an unsubscribe event is recorded, but the contact’s status doesn’t change, meaning a subscribed contact stays subscribed.
This option is useful when contacts are subscribed to multiple communications or brands and you use a preference center. If a contact chooses not to receive a specific communication, you can exclude them only from that one, without fully unsubscribing them from the database. Reports will still show the unsubscribe request, so you can manage their preferences more effectively.
Confirm contact subscription
Lets you confirm a contact’s subscription by moving them from the "Unconfirmed" status to "Subscribed".
You can also enable an option to avoid showing an error if the contact is already subscribed.
Other actions
Start automated flow
Lets you automatically add the contact to an automated flow right after submission. For example, with a signup form you can start the welcome flow right away.
To use this action, select an automated flow that includes a Button action node (available automated flows appear with the name set in the node configuration).
Selectable automated flows belong to the same journey as the landing page, or can come from other journeys if the node was set as available to all journeys.
Send email
Allows you to send a transactional email immediately after submission.
You can create a new message or use an existing one and choose whether to send it to the contact who submitted the form or to an external recipient.
For example, you can use this action to send a thank-you email with a discount code to a contact after they complete the form and click the Submit button.
Send SMS
Allows you to send a transactional SMS immediately after submission.
You can create a new message or use an existing one, and choose whether to send it to the contact who submitted the form or to an external recipient.
For example, you can use this action to send a summary SMS with the details of the appointment booked by the contact.
Actions and apps
Depending on the apps and connectors active in your account, you may also see additional post-submission actions. These extra actions let you integrate the landing page with other tools and services available in your environment.
Advanced actions
Run API request
Lets you send a REST API request to an external endpoint. For example, you can use it to send collected data to a CRM, update a ticketing system, or trigger custom processes on third-party platforms right after submission.
The API call requires an URL and, if supported, you can include an OAuth token using a placeholder.
The request supports multiple HTTP methods, including POST, GET, PUT, DELETE, HEAD, and PATCH, so it can work with most REST endpoints.
You can add custom headers to provide additional information to the endpoint. Headers can include variables or placeholders, for example for an authentication token or to pass values from landing page fields.
The request body, when applicable, is always JSON and can include dynamic values using variables and placeholders from landing page questions.
If the endpoint requires OAuth authentication, you can associate a Server OAuth digital certificate from the ones available to you. The token can be placed manually where required or, if not specified, it’s added automatically in the header. If the endpoint doesn’t require authentication, you can leave this empty.
This action can also reach endpoints with expired or unverifiable SSL certificates through a dedicated option, useful in controlled or test environments.
If you get a 401 Unauthorized error, the call can automatically retry with a new OAuth token. This second attempt is the only retry: if it fails, the request is considered definitively unsuccessful.