LogoLogo
PlatformsPricingRessources
  • Home
  • Onboarding
  • User documentation
  • Release Notes
  • Help Center
  • User documentation
  • Dashboard
    • Global Experience Dashboard discovery
    • How to filter the Global Experience Dashboard
    • How to customize your Global Experience Dashboard
    • Uplift card
  • Web Experimentation and Personalization
    • Campaign creation and dashboard
      • Types of campaigns
        • Choosing the right type of campaign with Ally, our assistant
      • How to create a campaign
        • Experimentations
          • How to create an A/B Test
          • How to create a Multipage Test
          • How to create a Split Test/Test by Redirection
          • How to create an A/A Test
          • How to create a Patch / Multipage Patch
          • How to create a Multivariate Test
        • Personalizations
          • How to create a Multi-Experience Personalization
          • How to create a Multipage Personalization
          • How to create a Simple Personalization
      • Campaign duplication
        • How to duplicate a campaign
      • How to set-up Main Information step
      • Understanding campaign duration
      • Campaign loading (deferred/ instant)
      • The "Comment" section of the campaign creation flow
      • Campaign statuses
      • How to exclude IP addresses from your campaigns
      • How to use MDE Calculator
      • Campaigns Dashboard
      • Campaign Scheduler
      • Mutually Exclusive Experiments
      • How to use Campaign Prioritization
        • Prioritization of Personalizations
    • Editors and Widget
      • How to create and edit content in the visual editor
      • How to use our Visual Editor - Interactive demo
      • Discovering the Visual Editor
      • Visual editor - History and review of modifications
      • Code Editor
      • Using the Editor Copilot
      • Prompt Inspiration library for Visual Editor Copilot
      • How to create an Action Tracker in the editor
      • How to use redirection option
      • How to create trackers in the editor
      • Widgets
        • Widgets configuration in the visual editor
        • AB Tasty prebuilt Widgets
          • Action Button Widget
          • Banner Widget
          • Before-After Image Widget
          • CSAT Widget
          • Celebrate Widget
          • Countdown widget
          • Drawer Widget
          • Dwell Time Tracking Widget
          • Element Visible Tracking Widget
          • Iframe Click Tracking Widget
          • IFrame Widget
          • Image Pop-in Widget
          • NPS® (Net Promoter Score) Widget
          • Progress Bar Widget
          • Scratch card Widget
          • Scroll Rate Tracking Widget
          • Search & Replace Widget
          • Simple Popin Widget
          • Snowflake Animation Widget
          • Social proof Widget
          • Social Sharing Widget
          • Spotlight Widget
          • Sticky Element Widget
          • Tooltip Widget
          • Video Pop-in Widget
          • Virtual Click Widget
        • Custom widget
          • Custom Widgets: List of propname Fields and Their Specificities
          • Custom widgets: Global usage and information
        • Custom code widget
      • Chrome extension
      • Shadow DOMs & iFrames
        • Understanding Shadow DOM
        • How to edit Shadow DOM in the visual editor
        • Understanding iframes
        • How to edit Iframes in the visual editor
    • Goals step
    • Targeting step
      • How to set up a campaign Targeting
      • How to create a Segment (Who section)
        • Segments Recommendations
        • Inspiration with Engagement Level segmentation
      • How to define Targeted Pages (Where section)
      • How to create a Trigger (How section)
        • Geolocation criterion
        • Device criterion
        • Screen size criterion
        • IP address criterion
        • Weather criterion
        • Landing Page criterion
        • Source & source type criterion
        • Previous Page criterion
        • URL Parameter criterion
        • Minimum Pages viewed criterion
        • Visited Pages criterion
        • Same day visit criterion
        • Browser language criterion
        • Browser criterion
        • Adblocker criterion
        • JS Variable criterion
        • Code-based criterion
        • CSS Selector criterion
        • DataLayer criterion
        • Visitor attributes criterion
      • How to define a Targeting Frequency (When section)
      • How to set-up targeting verifications
      • How to use the replicate targeting option
      • How to use URL operators to build URL patterns
    • Traffic allocation step
      • Campaign flow: Traffic Allocation step
      • Dynamic allocation
      • Even allocation
    • Advanced Options step
      • Sequential Testing Alerts
    • QA step
      • QA Mode & QA Assistant
        • How to use the QA mode
        • How to use the QA Assistant on desktop
        • How to use the QA Assistant on mobile
      • How to use the browser console to QA a campaign
  • Feature Experimentation & Roll-Out
    • How to create server-side A/B tests
    • How to create feature toggles and manage rollouts
    • How to create server-side personalization
    • FE&R Glossary
    • Managing Flags
    • Managing Context Keys
  • Recommendations & Merchandising
    • Recommendations
      • Web recommendation
        • Most popular recommendation filters
        • Variables by placement
        • Placement
        • Products groups
        • Filters
        • Exceptions
        • Options
      • Recommendation Banner
        • Recommendation banner with tag and custom JS
          • Adding Recos Tag to a website
          • Enriching Recommendations Banner HTML to send events to DataLayer through Recos Tag
          • Setting up GTM to send Recos Datalayer Events
          • Connect Tag Assistant from GTM
          • Check that the events arrive correctly in GA
          • Check the display of recommendations
          • Retrieving recos products from a RECO_ID with Recos Tag
        • Deploying a Recommendations Banner Custom Widget
        • Retrieving a Recommendation RECO_ID
        • How to push recommendations with Adobe Campaign
        • How to build recommendations (recommendation builder variant)
      • Mail recommendations
        • How to push recommendations into your Brevo emails
        • Brevo Feed
        • Products groups
        • Filters
        • Products highlights
        • Exceptions
        • Options
        • Parameters
        • Preview
        • Most popular recommendation filters
    • Merchandising
      • Introduction
      • Category
      • Products groups
      • Filters
      • Products highlights
      • Exceptions
      • Result to refine
      • How to deploy a merchandised product list through Algolia
    • Recos & Merch analytics
      • How to track performances
      • Recos Analytics Event format
      • The impact of BigQuery exports in terms of cost
      • Setup analytics retrieve events with Recos Tag
      • Key indicators over the period & Segment
      • Overview data
      • Evolution metrics
    • Recos & Merch API
      • Getting a product list
      • Accessing Recos API (endpoint)
      • Accessing Recommendations API (only specific accounts)
    • Recos & Merch account management
      • How to manage users in Recommandation & Merchandising module
      • How to manage roles
      • How to manage synchronisations
      • How to manage invoices
    • Security and GDPR
      • Procedure for Reporting Personal Data Breaches
      • Backup Policy
      • Security Configuration of Our Servers
      • PSSI
    • Recos & Merch Algorythms
      • How to manage algorithms
      • How to create your algorithms
      • Better understanding
      • Default algorithms
      • Data used to train Algorithms
    • Recos & Merch integrations
      • Integrations with Recos & Merch
      • Brevo Integration
      • Analytic integrations
        • Google Analytics integration
        • Matomo integration
        • Random data integration
      • Recos & Merch CMS integration
        • PrestaShop integration
        • Shopify Integration
        • Custom integration
  • Emotions AI
    • Understand EmotionsAI
      • EmotionsAI in a nutshell
      • Leverage EmotionsAI to get more value from A/B tests
      • Leverage EmotionsAI to get high-potential A/B test ideas
    • First steps with EmotionsAI
      • Onboarding
      • EmotionsAI functioning
      • Navigating the interface
      • FAQ about EmotionsAI
    • Using EmotionsAI
      • How to activate EmotionsAI features
      • EmotionsAI Website Mapping configuration
      • EmotionsAI Journey Analysis
      • EmotionsAI Page Analysis
      • Target EmotionsAI segments
      • QA a campaign on Desktop with EmotionsAI Chrome Extension
      • Use EmotionsAI targeting on hard-coded personalizations
      • Usage of EmotionsAI in some Push integrations
    • Read EmotionsAI campaigns’ report
  • Library
    • How to set-up your libraries
    • Widget library
      • Creating and managing Widgets
      • How to create a preset Widget
      • How to create a Custom Widget
        • How to configure Custom Widgets Custom Forms
      • How to declare your Widget Theme
    • Assets Library
    • Trackers library
      • Action Trackers
        • How to create and manage Action Trackers
      • How to create a Custom Tracker with custom JavaScript code
      • How to create a Custom Tracker via the DataLayer
    • Creating and managing Segments
      • List of Segment criteria
        • CSAT criterion (Customer Satisfaction)
        • NPS® criterion (Customer Satisfaction)
        • Engagement Level criterion
        • EmotionsAI criterion
        • Content Interest criterion
        • Page interest criterion
        • Device criterion
        • Cookie criterion
        • New/Returning visitors criterion
        • Campaign Exposure criterion
        • Number of sessions criterion
        • Day(s) Since Last Session criterion
        • Day(s) Since First Session criterion
        • Action Tracker criterion
        • Cart Abandonment criterion
        • Last Purchase criterion
        • Purchase Frequency criterion
        • Geolocation criterion
        • DMP, CDP, rd party tool criterion
      • Segments Library - Metrics
    • Creating and managing Triggers
      • List of Trigger criteria
    • Creating and managing Saved Pages
  • Integrations
    • Integrations general information
    • Push integrations
      • Adobe Analytics
      • Air
      • Amplitude (analytics browser)
      • Amplitude
      • AT Internet Smart Tag
      • Contentsquare
      • Google Analytics (Audience creation)
      • Google Analytics (UA)
      • Google Analytics (event only)
      • FullStory
      • Heap Analytics
      • Hubspot
      • Matomo
      • Mixpanel
      • Piano Analytics
      • SalesForce Marketing Cloud (Push)
      • Segment
      • Tealium
    • Pull integrations
      • Air
      • Commander Act
      • EmotionsAI
      • Fullstory
      • Google Analytics
      • Heap Analytics
      • Mixpanel
      • mParticle
      • Piano Analytics (Pull)
      • SalesForce Marketing Cloud (Pull)
      • Segment
      • Tealium : Import Audiences
      • Weborama
    • Other integrations
      • Productivity
        • Microsoft Dynamics Commerce
        • Setting up Microsoft Clarity Integration with AB Tasty
        • Didomi
        • How to Set Up the AB Tasty Connector with Notion
        • How to connect AB Tasty to Google Sheets
        • Connect your Slack Workspace to AB Tasty
      • Data Warehouse
        • Data Warehouse integrations: General information
        • Big Query - Daily exports from AB Tasty to Big Query
        • Snowflake - Daily exports from AB Tasty to Snowflake
        • Redshift - Daily exports from AB Tasty to Redshift
    • Custom integrations
      • Universal Data Connector
      • Custom Integration Connector with a rd party tool (Push data)
      • AB Tasty public API
  • Reporting & Performances
    • Data Explorer
      • How to analyze page traffic via Data Explorer
      • How to get metrics breakdown by multiple dimensions via Data Explorer
      • How to get a list of recent hits via Data Explorer
      • Data Explorer - List of Metrics and Dimensions
    • ROI dashboard
    • Performance Center
      • List of Performance Guidelines
    • Reporting
      • Campaign reporting
        • Reporting Copilot
        • Analysis Copilot
      • Data & reports: generalities and definitions
      • AB Tasty reports Metrics
        • Live hits of the reporting
        • Metrics based on tracking widgets
        • Navigation metrics
        • Metrics based on pageviews
        • Metrics based on clicks
        • Metrics based on transactions
      • Reporting Filters
        • General Reporting filters
        • EmotionsAI Reporting filter templates
      • Using the NPS®️ report
        • How does Feedback Analysis Copilot work
      • Sample ratio mismatch
      • Refresh reporting data using Refresh On Demand
      • Data export from the reporting
      • Frequentist Analysis mode
      • Understand the statistics behind your Reports
        • Statistics for the reporting
        • Statistical metrics
        • Avoiding Pitfalls in AOV Analysis for Conversion Rate optimization
        • Conversion mechanisms & concepts
        • Reporting Readiness
  • Account
    • Tag integration
      • All About Tags
      • How to implement the Generic Tag
        • AB Tasty hosted tag implementation
        • Tag Domain Delegation
          • Tag domain delegation implementation
      • How-to QA the Generic Tag
      • How to implement the Generic Tag via Google Tag Manager
      • How-to join the Next tag program
      • AB Tasty integration with Shopify
        • Understanding Shopify App features
        • How to implement the AB Tasty tag via Shopify
        • How to set-up Shopify Custom Pixel App
      • AB Tasty tag compilation
      • How the AB Tasty tag is designed to handle Single Page Apps (SPA)
    • Technical implementation
      • How to choose your cookies deposit method
      • How to declare my Account Domain?
      • JavaScript in AB Tasty
        • How to configure JavaScript
        • Javascript files execution
        • Campaign JavaScript Execution
      • How to configure jQuery loading
      • How to integrate Product hits
      • Product Hits integration principles
        • How to set-up segment criteria "Content Interest" and "Cart Abandonment"
    • Transaction Tag integration
      • How to implement the Transaction tag
      • How to create a Transaction Tracker via DataLayer
      • How to use the Transaction Tag Generator
      • How to QA the Transaction tag
    • Performance and security
      • How to manage visitor identity
      • How to deactivate AB Tasty
      • Consent policy - cookies, storage and privacy
    • Account management
      • The organization page
      • Subscription page
      • How to manage users?
Powered by GitBook
LogoLogo

AB Tasty Website

  • Home page AB Tasty
  • Blog
  • Sample size calculator
  • Release note

AB Tasty Plateform

  • Login

© Copyright 2025 AB Tasty, Inc, All rights reserved

On this page
  • Introduction
  • Configuration
  • Layout tab
  • Content tab
  • Style tab
  • Conditions tab

Was this helpful?

Edit on GitLab
Export as PDF
  1. Web Experimentation and Personalization
  2. Editors and Widget
  3. Widgets
  4. AB Tasty prebuilt Widgets

CSAT Widget

PreviousBefore-After Image WidgetNextCelebrate Widget

Last updated 9 days ago

Was this helpful?

The CSAT widget is part of the Promotional Content widget category. For more information on the widgets, please refer to .

Introduction

CSAT stands for “Customer Satisfaction”. This widget allows your visitors to rate, on a scale defined by you, how satisfied/happy they are with your website, services or products. AB Tasty’s default example of a CSAT widget:

Configuration

Layout tab

The layout tab lets you choose the position of the CSAT widget on the website. There are 4 options:

  • Modal

  • Top banner

  • Bottom banner

  • Free placement

Top and bottom banner will anchor the widget either to the top or to the bottom of the screen.

Free placement will allow you to choose the HTML element of the page in which you want to place the widget. This requires basic knowledge of HTML and knowledge of how your website is designed.

As a modal, the widget will appear as a pop-up displayed on top of the website. When it is chosen, you are allowed to choose its position on the page:

The layer options allow you to choose the z-index of the widget (whether it is above or below your website’s content, perpendicular to your screen).

For example, this is what Above means:

This is what Under means:

All the contents of a website are usually on the same level as each other (they have the same z-index of 0) The custom option allows you to choose the value of the z-index of the widget. That value can take positive or negative values and whichever element has a higher z-index will appear above elements with a lower z-index, if they happen to overlap on the screen.

Widget dimensions

The widget dimensions can be set to automatically expand or contract according to the amount of content it has, if you toggle it on.

The “Width” section contains 2 boxes:

  • The value of the width

  • The unit of the width

Description of each unit and value:

  • vw (% of viewport width)

    • The percentage of the window’s width. The value inserted will be the percentage. 100% will occupy the whole width of the window.

  • px

    • Stands for pixels. The value will specify the number of pixels the width of the widget will be

  • em

    • Em is a unit of measurement which indicates size relative to the size of the font. 1em means "equal to the current font size", and 2em means 2 times the current font size

  • vh (% of viewport height)

    • Similar to vw - the percentage of the window’s height. The value inserted will be the percentage of the height that you want the width to be equal to.

  • vmin (% of viewport minimum)

    • This unit is based on the smaller dimension of the viewport. If the viewport height is smaller than the width, the value of 1 vmin will be equal to 1% of the viewport height. Similarly, if the viewport width is smaller than the height, the value of 1 vmin will be equal to 1% of the viewport width.

  • vmax (% of viewport maximum)

    • This unit is based on the larger dimension of the viewport. If the viewport height is larger than the width, the value of 1 vmax will be equal to 1% of viewport height. Similarly, if the viewport width is larger than the height, the value of 1 vmax will be equal to 1% of the viewport width.

The preserve ratio toggled on will set the widget’s height automatically.

Content tab

The content tab allows you to customize the contents displayed in the CSAT widget. There are 3 aspects that you can customize:

  • The question and emojis

  • The open-ended questions

  • The “Thank you” message

The main message and the emojis for representing the rating of satisfaction

AB Tasty has a default one: “How satisfied are you with your experience on AB Tasty?”. This can be customized to be any other version that you prefer, with the restriction being 10,000 characters maximum

Having 2 emojis only is suitable if you are only looking for a binary rating from your customers (Satisfied/Unsatisfied or Good/Bad). Having 3 and above gives a broader spectrum of ratings and thus a more precise rating from customers, if this is what you are after. The emojis can be the AB Tasty default ones representing different levels of satisfaction:

These emojis can be customized to be any icon you want by choosing to have “Custom Emojis” and uploading a new one for each emotion using the Image Upload option. Or you can paste the link of an icon hosted somewhere external to AB Tasty, by choosing the Image Path option.

The standard text emojis allow you to use the regular emojis that people usually use on phones.

To be able to put emojis in these text boxes, you can simply search for the emojis online, and copy & paste them. It is also possible to simply input raw text, if this is something you want.

Open-ended question

You can choose whether you want open-ended questions to the visitors for each type of rating that they give. From the customers’ point of view, they will first have a choice of ratings to give (the emojis). Then, whichever rating they give will cause a different question to be asked to them. First, you have to toggle on that you want open-ended questions.

If toggled on, you will have the following choices:

Each of them can be customized, again with a restriction of 10,000 characters. If toggled off, open-ended questions will not be asked to customers after they submit their rating. The Button text section is simply text that will appear on the button that submits their answers to the open-ended question.

The Thank You Message

This toggle allows you to display a simple “Thank you” message to the customer after they have completed their rating. An example of a “Thank you” message is already provided. When toggled on, you will have the option to customize the message to your liking, again with a restriction of 10,000 messages.

Style tab

The style tab allows you to customize the general appearance of the CSAT widget including the:

  • Emoji colors and spacing

  • Text alignment in the box, color, font, font size

  • Margin, padding and background of the whole CSAT widget

  • Border style of the CSAT widget

  • Whether you want an underlay with the CSAT widget

  • Style of the close button (if you want a close button)

Emoji colors and spacing

The color and opacity of each emoji can be changed as shown in the screenshot above. The “Hex” box is simply the color’s hex code and can easily be found by a simple search online. The percentage box is the percentage opacity of the chosen color (0% meaning fully transparent and 100% being fully opaque) The emoji margin slider is the margin size on the left and right of the emoji, in pixels.

Text alignment, font, font color and font size

The text alignment options will allow you to horizontally position your text within the widget box. The text color and opacity can be changed as shown in the screenshot above. The “Hex” box is simply the color’s hex code and can easily be found by a simple search online. The percentage box is the percentage opacity of the chosen color (0% meaning fully transparent and 100% being fully opaque) The text font can also be chosen from a variety of different font styles.

One important option to note is the “Inherited from element” option - this means it will inherit the font of the HTML element the widget is found in. For example, if the widget is located in an element which already contains some text, the widget will have the same font as that element. If the widget is in no particular element, then it will inherit the default font set on that webpage.

The text style can be regular, bolded, italicized or underlined and the slider is for the font size.

Margin, padding and background of the CSAT widget

All the values are in pixels and you can see the values apply after setting the values and clicking on the page. The background color of the widget is also customizable. The color and opacity can be changed the same way:

There are 3 ways to upload the image:

  1. Drag and drop the image from your computer

  2. Click and open a dialog box to browse your computer and upload the image

  3. Use the “Image Path” option to paste the URL of an image hosted on another website.

The background fitting has 4 options:

  1. Cover - A snippet of the image will appear inside the widget.

  2. Contain - The whole image will fit inside the widget while preserving its aspect ratio

  3. Fill - the image will fill the widget without preserving the aspect ratio

  4. None - No restrictions will apply to the image

There is an option to add a shadow around the border of the widget as well, and can be turned on/off using a simple toggle:

Border style of the widget

The border thickness dictates the thickness of the widget’s border in pixels. The border color can also be changed. The “Hex” box is simply the color’s hex code and can easily be found by a simple search online. The percentage box is the percentage opacity of the chosen color (0% meaning fully transparent and 100% being fully opaque) The border radius dictates how round the corners of the widget will be. The smaller the radius, the sharper the corner.

Underlay

An underlay is a transparent and unclickable “cover” that appears in between the widget and the rest of the web page. This makes the widget focused to the user and forces them to notice and use it, or close it completely.

The underlay color can also be changed. The “Hex” box is simply the color’s hex code and can easily be found by a simple search online. The percentage box is the percentage opacity of the chosen color (0% meaning fully transparent and 100% being fully opaque). It is recommended that the opacity is set to a reasonable amount, and never 100% (40% - 60% is a reasonable amount). The “Underlay clickable to hide widget” will simply make clicking anywhere on the screen (except the widget) hide the widget.

Close button

You can choose to have a close button for your widget by toggling it on/off. And if you choose to have it, it can be either inside or outside the widget. The close button’s cross size can also be customized.

The cross size is in pixels and dictates the length (and height) of the cross’s container box. The “Hex” box is simply the color’s hex code and can easily be found by a simple search online. The percentage box is the percentage opacity of the chosen color (0% meaning fully transparent and 100% being fully opaque). The box containing the cross can also have its color and opacity changed in the same way.

The border radius dictates the sharpness of the corners of the close button’s border. The smaller the radius, the sharper the corners. The “Hex” box is simply the color’s hex code and can easily be found by a simple search online. The percentage box is the percentage opacity of the chosen color (0% meaning fully transparent and 100% being fully opaque).

Conditions tab

The Conditions tab allows you to decide 3 aspects of the widget:

  • Triggering - What causes its appearance and disappearance

  • Recurrency - How often it should appear to the customer

  • Animation - The animation with which it appears/disappears

Triggering

You can choose which event will cause the widget to appear on the screen of the customer. The list of events and what they mean is as follows:

  • When the page is loaded

    • When all the contents of the page have finished loading

  • As soon as possible

    • As soon as possible

  • At exit intent

    • When the customer intends to leave the page by switching tabs or closing the tab/browser

  • After x seconds of activity

    • The number of seconds after which the customer interacts with the page continuously

  • At click on element

    • When the user clicks on an element specified by you

  • When hovering over an element

    • When the customer’s mouse moves on an element specified by you

  • When an element is visible

    • When an element specified by you appears on the customer’s screen

  • When scrolling up

  • When a scroll percentage is reached

    • Scroll percentage here means how much of the total pages length has been reached by scrolling (E.g: 50% means the customer scrolled halfway down the whole page)

  • When the visitor has seen x pages

  • When a tracking is or has been sent

  • When the visitor rage clicks

    • When the customer repeatedly and very quickly clicks on the page (out of anger or dissatisfaction)

  • Custom trigger

All of the triggering events have a “Delay” option, which allows you to specify how much time after the event happens should the widget be displayed. The auto-hide toggle lets you choose whether to have the widget disappear by itself (toggled on) or not. If toggled on, you will be able to choose how many seconds after submitting the rating should the widget disappear.

Recurrence

The recurrence of 3 events can be customized:

  1. When the widget is displayed

  2. When the widget is displayed again after closure

  3. When the widget is displayed after submitting a rating

All 3 events have the same frequencies listed:

  1. Every time

  2. Every session

  3. Every x days

  4. Every x weeks

  5. Every x months

  6. Once only

Animation

The animation refers to the way the widget will appear to the customer. There are 3 animations:

  1. None

  2. Slide

  3. Fade

“None” will make the widget simply appear/disappear. “Slide”, as its name suggests, will cause the widget to slide into view. Choosing slide will give you some options about:

  1. How long the slide will last for

  2. The speeds at which the widget will slide (fast/slow at the start, middle and end)

“Fade” will have the widget slowly appear into view from completely transparent to full opacity. The options for “Fade” are similar to “Slide”, except that there is no direction to fade from.

If toggled off, then it will keep a fixed size that you can set it to keep.

Turning it off will provide you with more options to set up the widget’s height:

The emojis range from a minimum of 2 emojis to a maximum of 5 emojis.

The margin refers to the space between the widget border and other elements of the page outside it. The padding refers to the space between the widget border and the elements inside the widget. The margin and padding on all 4 sides of the widget can be customized with the following controls:

The “Hex” box is simply the color’s hex code and can easily be found by a simple search online. The percentage box is the percentage opacity of the chosen color (0% meaning fully transparent and 100% being fully opaque) A background image can also be inserted in the CSAT widget by toggling the background image toggle:

The close button can also have a customisable border. If the border thickness is set to 0px, then it will simply not exist. Otherwise, after setting the border thickness to a value greater than 0, the following options will appear:

The direction from which the widget will slide in

Widgets configuration in the visual editor