Feedback
Help Center

Trigger-based Forms

Trigger-based forms are behavior-based forms that appear automatically when a visitor meets specific criteria. Unlike the standard always-on Feedback Button, these forms are standalone and don’t require a visible button on your page.

To start your form: 

  1. From any section of the dashboard, select Create on the right side of the page header. A How should feedback appear? modal pops up.
  2. Select Trigger-Based Form, and select Continue.
  3. Choose a Slide-Out Form or a Full-Screen Form to open the builder.
  • Slide-out Form: A subtle widget that slides in from the edge of the screen—good for quick check-ins without interrupting the user journey.
  • Full-screen Form: A high-impact modal that overlays the page. Full-screen forms can also be accessed using their own direct URL (visible in the Trigger-based Form overview), useful for linking in emails or support content.

Once you open the Build form view, you see a dynamic multi-page editor. Use the question menu on the left to add components to your active page.

The builder uses tabs at the top of the workspace to separate your pages: 

  • Start Page: The first thing users see. Unlike other structures, Trigger-Based Forms don’t force a specific mandated question type here.
  • Intermediary Pages: Custom pages used to dive deeper into follow-up topics. Select the + (plus) icon next to the tabs to add new pages.
  • End Page: The final validation screen. When you go to the End page, the question toolkit limits your options to Format elements (Header and Paragraph) and Advanced Settings, which lets you build a streamlined thank-you screen.

Build your form fields using the Add questions menu on the left side of the dashboard. Click any item to add it to your page:

  • Feedback: NPS, Rating, or Mood.
  • Input: Input Text, Text area, or Email.
  • Choice: Drop-down, Checkbox, or Radio buttons.
  • Format: Header and Paragraph.
  • Advanced Settings: Toggle Store IP address and Store user location directly below the question menu.

Page logic lets you jump to specific pages based on the answers given in the current page. Control visibility lets you show questions on the same page based on the answer to a previous question. To add page logic:

  1. Select the three dots (...) next to the page title.
  2. Select Edit.
  3. Select Add Rule in the Page Logic section.

To add control visibility:

  1. Hover over a question and select the gear icon. The control visibility options appear along the bottom.

Targeting rules let you control exactly when and to whom your form appears. From the Launch tab, go to the Targeting view to set your conditions. Targeting rules work as AND logic—a visitor must meet all enabled criteria for the form to be triggered.

  • Visitors on a particular page: Restricts delivery to a specific URL.
  • Visitor Status: Target New or Returning visitors.
  • Time on Page: Delays the form until a user has been active on the current page layout for a specific amount of time (e.g., 5 seconds).
  • Scroll Depth: Triggers the form when a visitor scrolls down to the bottom of the page.
  • % of visitors: Limits exposure to a specific percentage of your visitors (e.g., 10%).
  • Exit Intent: Triggers the form when the system detects a user is exiting the page (e.g., within 5 seconds of exit trajectory). This is a Desktop-only option.
  • Page Views: Displays the form only after a visitor views a specific number of pages (e.g., at least 3 pages).
  • Browser Cookies: Targets or excludes audiences based on specific browser cookies.
  • Device Type: Limits form delivery to audiences using a specific hardware profile (such as mobile devices or desktop displays).

Modern websites engineered on modern frontend routing stacks (like React, Angular, or Vue) don’t fire native global browser document hard-refreshes when a user switches between path views. For Trigger-based forms, our code snippet checks targeting rules (like URL matches) on the initial page load, so you must simulate a page refresh when a virtual page change occurs.

Add the following JavaScript call to your application's router or navigation logic to run every time the path modifications update:

window.usabilla_live('virtual_pageview');

  • Refreshes Targeting: It tells the script to re-check if a Trigger-based form should show on the new URL parameters.
  • Data Accuracy: It ensures your analytics and behavioral triggers (like Time on Page) reset correctly for the new view layout.

In the Launch, the Schedule lets you control the campaign lifecycle:

  • Activation: Activate immediately, schedule a start date, or save the campaign as Off to be toggled manually later.
  • Deactivation: Automatically stop the campaign on a specific date or after a certain number of responses (e.g., stop after 500 entries).
  • Reset Campaign: Define how often a user should see the form again (e.g., every 30 days).
  • Do Not Bother: By default, our Trigger-Based Forms don’t show again interacts with them. However, this option uses local storage to ensure a visitor only sees the form once until the next reset, whether they interact with it or not. This persists even if the user closes the tab, but will be cleared if they wipe their browser cache.

Once you save your form, you see the Install page. To collect behavioral insights, deploy the GetFeedback JavaScript snippet onto your website. This snippet acts as a container code—once it is active, you can manage campaigns from your dashboard without touching your website's code again.

If you have direct access to your website's source code, follow these steps to place the snippet:

  1. From the final tab of the builder, select View code to open the tracking window. 
  2. Copy your unique snippet string.
  3. Open your website's global header template or layout file.
  4. Paste the copied snippet into the document's tracking layout blocks, ensuring it resides within the <body> tags. For the best performance, place the code right before the closing </body> tag on every page where targeting conditions are monitored.
  5. Content Security Policy (CSP) Notice: If your infrastructure runs strict security profiles, toggle the Include CSP Hash controls directly inside this script code modal to pull down your required cryptographic tags. For full tracking rules documentation, see our Configuring Content Security Policy (CSP) guide.

If you configure your campaign using the Full-screen layout, you will get a unique, standalone Form URL. You can use this link outside your main website, such as embedding it directly into outbound transactional emails or customer service email signatures.

  • Use the Preview button in the builder to test your Page Logic and design before launching.
  • Don't trigger multiple campaigns at the exact same moment on the same page, as it can cause a poor user experience and data conflicts.
  • If you only want to show Form B to users who finishes Form A, use a custom cookie dropped on the Success event of Form A.

After launching, go to How to Analyze Your Results to track campaign performance.