Assign Click Actions
Use this page to define what happens when a user clicks a widget element.
This page focuses on behavior. If you are still building the widget layout, start with Customize Components. If you need help choosing the right element first, see Widget Elements Reference.
Quick workflow
Click action types
User Update
Use User Update when a click should update profile data or user properties.
This is useful for saving form responses, updating user fields, or writing back preference data.
How to set it up:
Select the button or image.
Choose User Update.
Pick the field you want to update.
Map the value from a widget component if needed.
Matching components with attributes
To access subcategories of the target profile attribute:
Windows:
CTRL + ALT + 7Mac:
FN + Option + 7
Example
To update a user’s email through a button:
Assign an identifier to the button.
Select User Update.
Open the subcategory and choose the update method.
Select Content if the value comes from another widget component.
Match the content with the component you want to use, such as
emailattributebutton.
Redirect to URL
Use Redirect to URL when a click should open a web page.
Best for external websites, landing pages, product pages, and campaign detail pages.
How to set it up:
Enter the destination URL.
Add a condition if the redirect should run only in a specific case.
Go to View
Use Go to View to move users to another screen inside the same widget.
This is the main action for multi-step flows such as rating → thank you or form → success.
How to set it up:
Choose Go to View.
Select the target view.
Add Action Conditions if the target should depend on user input.
Send Data
Use Send Data when the click should send form or interaction data to an endpoint.
This is useful for custom data collection and server-side workflows.
How to set it up:
Define the data or parameters to send.
Enter the endpoint URL.
Add conditions if the send action should be limited.
Close Widget
Use Close Widget when the interaction should simply dismiss the widget.
This works well for actions such as Dismiss, Maybe later, or No thanks.
Open Widget
Use Open Widget when one widget should launch another widget.
This is useful for chained flows such as summary widget → detailed widget.
How to set it up:
Choose Open Widget.
Select the target widget.
Make sure the target widget already exists.
Fire Event
Use Fire Event when a click should trigger a custom event inside your app or tracking setup.
This is useful when another workflow, report, or integration depends on the interaction.
How to set it up:
Create the event first in Create Custom Events.
Assign Fire Event to the button or image.
Select the event from the list.
Matching widget components with events
To access subcategories:
Windows:
CTRL + ALT + 7Mac:
FN + Option + 7
Example
To fire an event from an image click:
Assign an identifier to the image.
Select Fire Event.
Open the subcategory and choose the method.
Select Content if the mapping comes from a widget component.
Match the event with the right component, such as pairing
LikeEventwith the image identifier.
Android Background Location Permission
Use this action when the widget should guide Android users to allow or deny background location access.
Choose Mobile Blank Widget in the Widget Gallery to use this feature. This action is only available for mobile widgets.
How to set it up:
Add buttons such as Allow Permission and Deny Permission.
Assign the matching background location action to each button.
After the click, the user is directed to the Android Settings screen.
Deep Link
Use Deep Link when the click should open a specific destination inside the app.
This is useful for product pages, article detail pages, feature screens, or campaign destinations.
Validations
Validations help you prevent bad or incomplete input before an action runs. By adding validation rules to form fields, you can ensure that only properly formatted, complete data is submitted — reducing errors and improving data quality across campaigns.
Validation Types
Text Validation
Applies string-based rules to text input fields. You can require that the field is not empty, enforce a minimum or maximum character length, or use a regex pattern to match a specific format.
Number Validation
Applies numeric rules to number input fields. You can require a value within a defined range or validate against percentage constraints. Useful for quantity fields, age inputs, or score-based forms.
Date Validation
When the input type is set to Date, the field displays a DD/MM/YYYY placeholder and opens a calendar picker on interaction. The form blocks submission if an invalid date (e.g., 31/02/2025) or incorrect format (e.g., 2025-12-17) is entered. Use this type for registration, reservation, or appointment date fields where unstructured text input would otherwise introduce inconsistent data.
Email Validation
When the input type is set to Email, the entered value is automatically checked against standard email format on every keystroke. If the format is invalid, form submission is blocked until the value is corrected. Use this for sign-up forms, contact forms, or any scenario where collecting a malformed email address would break downstream communication flows.
Phone Validation
When the input type is set to Phone, mobile devices automatically switch to a numeric/telephone keyboard when the field is focused. This reduces input errors and speeds up entry for users on mobile. Note: Phone type does not enforce a specific format or pattern — it only changes the keyboard behavior. If format validation is required (e.g., country code, digit count), use the Regex rule in combination.
Password Validation
When the input type is set to Password, the entered characters are masked and not displayed in plain text. Use this for widgets or survey forms that include a password creation or confirmation step. This type does not enforce complexity rules by default — combine it with a Regex rule if minimum length or character requirements are needed.
URL Validation
When the input type is set to URL, the entered value is checked against standard URL format. Submission is blocked if the value does not match a valid URL structure. Use this for fields that collect website addresses, deep links, or any input that must be a properly formed URL.
Validation rules
Validation rules define the specific condition a field value must meet before the form can be submitted. Each rule requires an error message that is shown to the user when the condition is not met.
Not Empty
Ensures the field is not left blank. Use for any required field.
String Length
Enforces a minimum and/or maximum character count on text input.
Number
Validates that the entered value falls within a defined numeric range.
Percentage
Validates that the value is a valid percentage (0–100).
Regex
Validates the value against a custom regular expression pattern. Use for formats not covered by built-in types, such as national ID numbers, postal codes, or phone number patterns.
Valid Date
Ensures the entered date is a real, calendar-valid date. Blocks submission if the value is an impossible date such as 31/02/2025.
Date - Minimum
Requires the entered date to be on or after a specified date. Use for scenarios where past dates are not acceptable, such as future appointment scheduling.
Date - Maximum
Requires the entered date to be on or before a specified date. Use for scenarios where future dates are not acceptable, such as birth date fields.
Validates that the entered value matches standard email address format. Blocks submission if the value is missing an @ sign or domain.
Important step
Do not forget Check Form Validations Before Performing This Action.
This ensures that all validation rules run before the click action is executed.
Check Form Validations Before Performing This Action
When enabled, the widget checks validations first. If validation passes, the action runs. If validation fails, the action is blocked and the user sees the related error message.
Manage App
Use Manage App when the action should be handled by the app itself. This is commonly needed for app-level deep link behavior.
Action Conditions
Use Action Conditions to control when a click action should run.
How it works:
Choose the identifier to evaluate.
Select the condition.
Enter the expected value.
Run the action only when the condition is matched.
Example scenario: rating flow
This example creates a simple feedback flow with conditions.
Goal
Ask for a 5-star rating. Users who rate 4-5 go to a Thank You page. Users who rate 1-3 go to a Feedback page.
Step 1: Add the rating element and identifiers
Design the widget first. Add the rating element and the button users will click after rating.
Then assign a clear identifier to the rating element, such as rating.
Identifiers are usually shown at the top-right of the selected component. Replace random defaults with clear names before you start action setup.
Step 2: Create the views
Add the extra views needed for the flow:
View 2: Feedback
View 3: Thank You
Step 3: Add conditional actions to the button
Add two Go to View actions to the same button.
First action:
choose Go to View
select View 2
add the condition
rating <= 3
Second action:
click + Add Action
choose Go to View
select View 3
add the condition
rating >= 4
You can add more actions later if the flow needs data send, redirect, or event trigger steps.
After testing the logic, click Save Widget and Return.
Last updated
Was this helpful?