> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/configure-widget-actions-and-validation.md). # Configure widget actions and validation Configure what happens when users click a widget element. Use actions to navigate users, collect data, update profiles, or trigger events. Use validation to block incomplete or invalid form submissions. Build the structure first in [Design widget layout](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/design-widget-layout.md). Choose elements in [Widget elements reference](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/widget-elements-reference.md). {% hint style="info" %} Set clear, stable identifiers before mapping values, conditions, or custom events. {% endhint %} ### Before you start Click actions are available for **Buttons** and **Images**. Set identifiers for every element used in mappings or conditions. ### Configure an action 1. Select a button or image. 2. Click the ⚡ **lightning** icon in the toolbar. 3. Choose an action. 4. Add conditions or validation when needed. 5. Preview every path before saving.

Click Actions panel — Choose an action for the selected button or image.

### Choose an action Use the action that matches the outcome you need: * **User Update**: save a profile attribute or form response. * **Redirect to URL**: open a web page. * **Go to View**: move to another screen within the widget. * **Send Data**: send values to an endpoint. * **Close Widget**: dismiss the current widget. * **Open Widget**: launch another saved widget. * **Get Web Push Permission**: request browser notification permission. * **Fire Event**: record a custom event. * **Android Background Location Permission**: open Android location permission settings. * **Deep Link**: open an in-app destination. * **Manage App**: let your app handle the action result. ### 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: 1. Select the button or image. 2. Choose **User Update**. 3. Pick the field you want to update. 4. Map the value from a widget component if needed. {% hint style="success" %} #### Matching components with attributes To access subcategories of the target profile attribute: * **Windows:** `CTRL + ALT + 7` * **Mac:** `FN + Option + 7` {% endhint %}

User Update attribute options — Open attribute subcategories to select the update method.

User Update action settings — Choose the profile field and its value source.

**Example** To update a user’s email through a button: 1. Assign an identifier to the button. 2. Select **User Update**. 3. Open the subcategory and choose the update method. 4. Select **Content** if the value comes from another widget component. 5. Match the content with the component you want to use, such as `emailattributebutton`.

Map the value from the relevant widget component.

User Update mapping example — Confirm the mapped component before saving.

#### 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: 1. Enter the destination URL. 2. Add a condition if the redirect should run only in a specific case.

Redirect to URL action settings — Enter the destination and add conditions when required.

#### 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: 1. Choose **Go to View**. 2. Select the target view. 3. Add **Action Conditions** if the target should depend on user input.

Go to View action — Use this action for navigation inside the widget.

Go to View target selection — Select the destination view and optional conditions.

#### 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: 1. Define the data or parameters to send. 2. Enter the endpoint URL. 3. Add conditions if the send action should be limited.

Send Data action settings — Configure the endpoint and values to send.

#### 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`.

Close Widget action — Close the widget after the user dismisses it.

#### 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: 1. Choose **Open Widget**. 2. Select the target widget. 3. Make sure the target widget already exists.

Open Widget action settings — Select an existing widget to open next.

#### Get Web Push Permission Use **Get Web Push Permission** to request browser notification permission from the user. This action supports onboarding, subscription prompts, and well-timed opt-in requests.

Get Web Push Permission action settings — Assign the permission request to a button or image.

When users click the assigned element: 1. The browser displays its native permission prompt. 2. Users choose whether to allow notifications. 3. Their decision is reflected in Netmera automatically.

Widget asking users to enable web push notifications — Explain the value of notifications before requesting permission.

Browser notification permission prompt — The browser presents the final permission choice.

#### 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: 1. Create the event first in [Create Custom Events](/netmera-user-guide/panel-settings/settings/app-configuration/events.md). 2. Assign **Fire Event** to the button or image. 3. Select the event from the list. {% hint style="success" %} #### Matching widget components with events To access subcategories: * **Windows:** `CTRL + ALT + 7` * **Mac:** `FN + Option + 7` {% endhint %}

Fire Event action settings — Select the event to record when users click.

Fire Event mapping options — Open event subcategories to configure mapped values.

**Example** To fire an event from an image click: 1. Assign an identifier to the image. 2. Select **Fire Event**. 3. Open the subcategory and choose the method. 4. Select **Content** if the mapping comes from a widget component. 5. Match the event with the right component, such as pairing `LikeEvent` with the image identifier.

Mapping a widget component to a custom event — Use the identifier to map the relevant component.

Fire Event mapping example — Review the event mapping before saving.

#### Android Background Location Permission Use this action when the widget should guide Android users to allow or deny background location access.

Android background location permission action — Use this action only for Android mobile widgets.

Android background location permission settings — Assign the appropriate permission action to each button.

How to set it up: 1. Add buttons such as **Allow Permission** and **Deny Permission**. 2. Assign the matching background location action to each button. 3. 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.

Deep Link action settings — Enter the in-app destination for the selected platform.

#### Manage App Use **Manage App** when the app should handle the action itself. This action is commonly used for app-level deep link behavior.

Manage App action settings — Use this action when your app handles the result.

### Validations Validations prevent incomplete or invalid input before an action runs. Set an input type first. Then add the rules and error messages users need.

Validation settings for a widget field — Configure validation on the field that collects user input.

#### Input types The input type controls how users enter a value and which checks apply automatically. Choose the type that matches the expected data, then add validation rules for any additional requirements.

Input type	Behavior	Use it for
Text	Supports required, length, and regex rules.	Names, labels, and formatted text values.
Number	Supports numeric ranges and percentage constraints.	Quantities, ages, and scores.
Date	Shows `DD/MM/YYYY` and a calendar picker. Blocks invalid dates and formats.	Registrations, reservations, and appointments.
Email	Checks standard email formatting as users type. Blocks submission until corrected.	Sign-up and contact forms.
Phone	Shows a telephone keyboard on mobile. It does not enforce a format.	Phone number collection. Use Regex for country codes or digit counts.
Password	Masks entered characters. It does not enforce complexity rules.	Password creation or confirmation. Use Regex for requirements.
URL	Checks standard URL formatting. Blocks submission for invalid values.	Websites, deep links, and other URL values.

Input type selection for validation — Choose the input type that matches the value users enter.

#### 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.

Validation rule settings — Add a rule and write the error message users see.

Rule	Description
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.
Email	Validates that the entered value matches standard email address format. Blocks submission if the value is missing an `@` sign or domain.

#### Run validation before the action Enable **Check Form Validations Before Performing This Action** on the form action. The widget checks validation first. Passing values run the action. Failed values show the related error and block the action. {% hint style="warning" %} #### 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. {% endhint %}

Check Form Validations Before Performing This Action setting — Enable this setting on the action that submits the form.

### Action Conditions Use **Action Conditions** to run an action only for a matching user choice or value. Each condition evaluates an element identifier against an expected value. 1. Choose the identifier to evaluate. 2. Select the condition. 3. Enter the expected value. 4. Save the action. {% columns %} {% column %}

Action Conditions settings — Select the identifier, condition, and expected value.

{% endcolumn %} {% column %}

Configured action condition — The action runs only when the condition matches.

{% endcolumn %} {% endcolumns %} ### Example: route users by rating This flow asks users for a five-star rating. Ratings of **1 to 3** open **Feedback**. Ratings of **4 to 5** open **Thank You**. #### Build the views 1. Add a rating element and a submit button to the first view. 2. Set the rating element identifier to `rating`. 3. Add **View 2** for **Feedback**. 4. Add **View 3** for **Thank You**. Identifiers appear at the top-right of the selected element. Replace generated names before configuring actions. {% columns %} {% column %}

Rating element identifier — Assign a clear identifier to the rating element.

Feedback view in the rating flow — View 2 collects feedback from lower ratings.

{% endcolumn %} {% column %}

Identifier field in element settings — Use the identifier in the button action conditions.

Thank You view in the rating flow — View 3 thanks users with higher ratings.

{% endcolumn %} {% endcolumns %} #### Configure the outcomes Add two **Go to View** actions to the submit button: | Action | Target view | Condition | | -------------- | --------------------- | ------------- | | **Go to View** | **View 2: Feedback** | `rating <= 3` | | **Go to View** | **View 3: Thank You** | `rating >= 4` | Select **+ Add Action** before configuring the second outcome. Add further actions when the flow also sends data, redirects users, or fires an event. {% columns %} {% column %}

Go to View condition for ratings of three or below — Ratings of three or below open the Feedback view.

{% endcolumn %} {% column %}

Go to View condition for ratings of four or above — Ratings of four or above open the Thank You view.

{% endcolumn %} {% endcolumns %}

Action selection menu — Select an additional action when the flow needs it.

Preview both rating paths. Then click **Save Widget and Return**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/configure-widget-actions-and-validation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.