Actions

Actions are predefined events within your app that prompt Formbricks to display a survey when triggered. These are detected by the Formbricks widget, which then presents the appropriate survey based on your predefined settings.

How Do Actions Work?

Actions in Formbricks App Surveys are deeply integrated with user activities within your app. When a user performs a specified action, the Formbricks widget detects this activity and can present a survey to that specific user if the trigger conditions match for that survey. This capability ensures that surveys are triggered at the right time. You can set up these actions through a user-friendly No-Code interface within the Formbricks dashboard.

Why Are Actions Useful?

Actions are invaluable for enhancing survey relevance and effectiveness:

• Personalized Engagement: Surveys triggered by user actions ensure content is highly relevant and engaging, matching each user’s current context.
• User Attributes: By tying surveys to specific user attributes, such as activity levels or feature usage, you can customize the survey experience to reflect individual user profiles.
• User Targeting: Precise targeting based on user attributes ensures that surveys are shown only to users who meet certain criteria, enhancing the relevance and effectiveness of each survey.

Setting Up No-Code Actions

Formbricks offers an intuitive No-Code interface that allows you to configure actions without needing to write any code.

To add a No-Code Action:

1. Visit the Formbricks Dashboard & switch to the Actions tab:

2. Now click on “Add Action”

Here are four types of No-Code actions you can set up:

1. Click Action

Click Action is triggered when a user clicks on a specific element within your application. You can define the element's inner text or CSS selector to trigger the survey.

• Inner Text: Checks if the innerText of a clicked HTML element, like a button label, matches a specific text. This action allows you to display a survey based on text interactions within your application.

• CSS Selector: Verifies if a clicked HTML element matches a provided CSS selector, such as a class, ID, or any other CSS selector used in your website. It enables survey triggers based on element interactions.

2. Page view Action

This action is triggered when a user visits a page within your application.

3. Exit Intent Action

This action is triggered when a user is about to leave your application. It helps capture user feedback before they exit, providing valuable insights into user experiences and potential improvements.

4. 50% Scroll Action

This action is triggered when a user scrolls through 50% of a page within your application. It helps capture user feedback at a specific point in their journey, enabling you to gather insights based on user interactions.

This action is triggered when a user visits a specific page within your application. You can define the URL match conditions as follows:

Setting Up Code Actions

For more granular control, you can implement actions directly in your codebase:

1. Configure the Action: First, add the action via the Formbricks web interface to make it available for survey configuration. After that you can fire an action using formbricks.track()

2. Track an Action: Use formbricks.track() to send an action event to Formbricks.

formbricks.track("Action Name");

Here is an example of how to fire an action when a user clicks a button:

const handleClick = () => {
  formbricks.track("Button Clicked");
};

return <button onClick={handleClick}>Click Me</button>;