usabilla FAQs

The Usabilla - Clicktale integration allows you to directly connect your users' feedbackitems to Clicktale session recordings. The integration can easily be set up by pushing the Clicktale session recording to Usabilla through our JavaScript API. Please follow the below steps to set up the integration.

Please note:This integration is set up per feedback button. If you are using multiple feedback buttons, the integration will have to be enabled for each button in your account.

1. Log into your Usabilla account and navigate to theintegrations page.

http://subs07.app.clicktale.com/

2. Click the Clicktalelogo at the top of the page. This will open the below modal window. The Clicktaleintegration can beset up per feedback button.It is possible to use the integration for multiple feedback buttons.

3. Add your Clicktale partition number. You can find this by logging into your Clicktale account and looking at the URL. For example: If your Clicktale URL is ‘’, your partition would be ‘07’.

4. Use your integration. Your Clicktale account is automatically paired with any Usabilla feedback item, for which a recording is available. Simply find afeedback item for which a recording is available and click the Clicktale integration. It's that simple!

Have you ever looked for a solution where you can compare customer data points in an omnichannel approach? Look no further. Our new analysis platform, Workspaces, enables you to combine survey responses from different digital touchpoints.Ranging from feedback received through websites, emails, and mobile applications. Thus enabling you to get a holistic view and pulse of your key metrics.

This Guide consists of:

Create a chart in 4 easy steps:

Give your chart a title and description

Select the type of chart you would like to create

Select the questions you want to visualize in your chart

Choose your visualization options

Edit a chart

Delete a chart

Creating your first chart in 4 easy steps

Once you've created your workspace, select the 'Add New Tile' button to add a chart to your workspace:

here

Step 1: Give your chart a title and description

When you create a chart, you will be asked to give the chart a name (140 characters, mandatory) and a description (140 characters, not mandatory). We would advise you to think about a short title that quickly sums up what you are visualizing and use the description to provide more detail so that your colleagues are clear about what data you are visualizing in your chart. Don’t worry if you’re not sure what to call your chart, because both the name and description are editable:

Step 2: Select the type of chart you would like to create

In this step, you simply choose the type of data you would like to display in your chart. Currently, you can select between NPS, Mood, Rating, and Open text answers:

Step 3: Select the questions that you want to visualize in your chart

Now it's time to select the surveys which you want to include data from. If you've chosen an NPS chart in your previous step, you will be presented with all the surveys which have an NPS question included in the survey. This essentially means that we only display surveys which entail questions that are relevant to the chart type you selected.

Note: When creating a Mood chart, please note that you can only combine forms that have the same scale. So, mood ratings with a scale of 5 can only be combined with other mood ratings with the same scale. The same goes for Rating charts.

Step 4: Choose your visualization options

Based on your needs, we provide different options to visualize your data. At this point, we're offering two, of the eventual four, visualization options for the chart types with closed questions (Mood, NPS, and Rating) and one visualization option for the "Open test answers". For the chart types with closed questions you have the option between "Score over time" to see a trendline of your data or "Single Score" to see the average number of a specific period:

Tip: Each of the "Visualization options" come with their own additional "Display options". To fill you in about all the possibilities we have in our wonderful world of "Visualization" and additional "Display options", we have created this article.

Edit a chart

Created your chart but there's still something missing? Have no fear, the edit menu is here! The title, description, selected data, and selected visualization can be edited at any time. To use one of these, simply open the menu by selecting the three dots in the top right of your chart:

Note: Charts can be edited by both Administrators and Users who have access to the workspace the chart is in.

Delete a chart

Just like every piece of quality software, we have a reset button for the charts as well! In Usabilla Workspaces this comes in the form of the "Delete chart" option. This option can be found in the edit menu which can be opened by clicking the three dots in the top right of your chart:

Click on the three dots (1.)

Select "Delete chart" (2.)

Note: Charts can be deleted by both Administrators and Users who have access to the workspace the chart is in.

Success

Awesome: By completing this guide you have a great understanding of how charts can be created, edited and deleted in Usabilla Workspaces. Don't let us stop you there! Click to see an overview of all the available Support articles we have created for Usabilla Workspaces. Whether you'd like to know how to create a workspace, how to use the filters in your workspace or if you'd like to know more about the visualization options we have available for your charts, we got you covered!

If Salesforce Lightning is the CRM system of your choice, we have the possibility to enrich the information about your users by adding the Feedback that's given by them in Usabilla. With their Feedback in Salesforce Lightning, you can start taking advantage of the options to interact with your users Salesforce gives you. Have I sparked your interest? Great, allow me to continue!

Apart from Salesforce Lightning, this integration is compatible with:

Salesforce Sales Cloud

Salesforce Service Cloud

Salesforce Platform (force.com)

Salesforce Core (Professional, Enterprise, Unlimited and Performance Edition)

This guide consists out of two parts:

The essentials for your setup

The setup in Salesforce Lightning

What do you need:

- A Usabilla account with an Administrator role

- Your Salesforce Admin

Essentials

Let's start by making sure we have the essentials, the Usabilla app for Salesforce Lightning. We've created a Usabilla app that can be found on the Salesforce AppExchange. The app can be found by simply searching for Usabilla and once it has shown its face, you can install it.

Next up are the Usabilla Public API credentials. These credentials consist out of the Access Key and Secret Key. With these credentials, you're able to retrieve Feedback from your Usabilla account. Have a look at this article to see how and where you can retrieve your Public API credentials.

Last but not least, in order to match the Feedback items to a contact in Salesforce, a specific lookup field has to be created by your Salesforce Admin. I'll go over the specific steps that are required to create this specific fields as well, so if you are the Salesforce Admin than follow these steps.

Note: In this example, we'll be using the email address that's collected in the Feedback as a lookup field. But it's also possible to use data that is retrieved in the form of Custom Variables. When using Custom Variables there's are a couple of additional steps required, click here to have a look at these steps.

- In your Salesforce environment, open the 'Object Manager':

https://data.usabilla.com:

- From the 'Object Manager', select 'Feedback Item':

- Select 'Fields & Relationships':

- Select 'New':

- In the following screen, we're going to specify that we're trying to create a Lookup field by selecting 'Lookup Relationship' and select 'Next':

- Next, we're going to specify that this object will be related to a Contact by selecting '' and select 'Next':

- Then it's time to specify the 'Field Label', 'Field Name' and 'Child Relationship Name' as the following:

- In step 4 you can modify the Field-Level Security for Profile settings, there's no specific setting from Usabilla needed for this, so this can be set up according to your preference.

- In the following step we're going to specify that this field should be included in the 'Feedback Item' and the 'Feedback Item Layout' page layouts:

- Last but certainly not least, we're going to specify the title for the related list and save the changes we've made:

Setup in Salesforce Lightning

Now that we've covered the essentials, it's time to configure Salesforce Lightning the Usabilla app is installed successfully, we're going to configure the necessary settings that are needed to make sure Feedback is retrieved from Usabilla.

- Navigate to the 'Usabilla Setup' page by clicking the 'Setup' icon:

- Search for 'usabilla' and you should be able to find the shortcut to 'Usabilla Setup':

- Once 'Usabilla Setup' is clicked, you will be presented with the screen containing all the necessary information to set up the integration and it will look like the following screen:

- In the 'Data Endpoint' field, we're going to specify the following URL:

- Next up, the Access Key and Secret Key fields. The credentials you've retrieved from your Usabilla account can be inserted here:

- In the 'Fetch Feedback Items From x Days' you can specify how far we should go back to retrieve historical data. This option only affects sources that have not been fetched. Sources that have been fetched will use the last fetched feedback property to determine what feedback items should be fetched:

- The 'Schedule Sources' section allows you to configure how often a call is made to our Public API to retrieve Feedback per Product (Usabilla for Websites/Email/Apps).

There are three options here:

Use hour interval (by selecting this option, the field next to 'Schedule Source hours' becomes configurable which gives you the possibility to define the interval in hours eg 1 hour, 2 hours, 2,5 hours, 3,25 hours, etc.)

Every 15 minutes

Every 30 minutes

- The 'Schedule feedback items' section allows you to configure how often a call is made to our Public API to retrieve Feedback per Feedback source.

There are three options here:

Use hour interval (by selecting this option, the field next to 'Schedule Source hours' becomes configurable which gives you the possibility to define the interval in hours eg 1 hour, 2 hours, 2,5 hours, 3,25 hours etc.)

Every 15 minutes

Every 30 minutes

- In the 'Link Feedback and Contact' section, we're going to configure what information in the feedback item we can use to identify the user. To clarify what the function of the fields in this section do, I'll name them below and give a brief description of them:

Contact's Email API field name: This defines what information in Salesforce should be used to match the information of the user coming in through the Feedback (in this case, the email address)

Feedback's Email API field name: This defines the source for the email address in the Feedback item

Feedback's Contact API field name: This will link the Feedback item to the contact in Salesforce based on the 'Feedback's Email API field name'

Note: Please keep in mind that Feedback will only be attached to existing contacts if the email address in the Feedback item is known in your Salesforce environment. If the Feedback item contains a new email address, the Feedback will not be linked to a contact.

Custom Variables as Lookup field

In order to communicate the Custom Variables to Salesforce, we have set up 5 integration fields that can be used to make sure the Custom Variables will be available in Salesforce. These are the 5 integration fields:

integration_sf_id

integration_sf_01

integration_sf_02

integration_sf_03

integration_sf_04

By using these integration fields as the Name of your Custom Variables, the value that is pushed through will become available in Salesforce, which in turn can be used to link the Feedback to a specific user.

Allow me to explain the complicated text above with an example. If you're currently retrieving the ID of your users and it is displayed like this in Usabilla under Custom Variables:

User ID : 123456AB

In this example, the 'Name' of the Custom Variable is 'User ID' and the 'Value' is '123456AB'. To make sure this ID is available in Salesforce and can be used to link Feedback with a user in Salesforce, the 'Name' of the Custom Variable has to be adjusted to one of the five integration Fields:

integration_sf_id : 123456AB

Alternatively, you could also send the same ID once more, but with a different name. This would be helpful for colleagues who are reviewing Feedback in Usabilla and would like to have context about the Custom Variables they're seeing in the Feedback items. The result of this will be:

User ID : 123456AB

integration_sf_id : 123456AB

Next steps

Now that the Salesforce Lightning integration has been set up, it's time to take advantage of all the opportunities you've unlocked in Salesforce. Get in touch with your Salesforce Administrator to get an idea what awesome things you can do with Usabilla and Salesforce Lightning combined!

Our Usabilla Google Analytics integration uses the default tracking code that runs on the page on which the user leaves feedback. This allows you to quickly and easily set up the integration inyour Usabilla account. This works very well for the commonly used defaultGoogle Analytics implementation. However, if your implementation is more complex and you work with multiple tracking codes or if you implemented Google Analytics through a Tag Management System, the default integration might not work for you. In this case, you will have to ensure that your Usabilla Events are pushed to the right Google Analytics tracking codes.

In order to manage the tracking code to which Usabilla events are pushed, you can replace the integration with one of the below JavaScript snippet. Simply disable the integration in your Usabilla account and then insert one of the below JavaScript snippet underneath your existing Usabilla code.

Send events to all Google Analytics tracking codes

If you are using multiple Google Analytics tracking codes or if you do not know the name of the tracking code to which you'd like to send data you can use the below snippet. This JavaScript snippet will look for all Google Analytics tracking codes that run on your webpage. If a user providesfeedback through Usabilla, events will be pushed out to all tracking codes running on the website.

window.usabilla_live('setEventCallback', function(category, action, label, value) {

ga(function() {

var trackers = ga.getAll();

for (var i = 0; i < trackers.length; i++) {

var trackerName = trackers[i].get('name');

ga(trackerName + '.send', 'event', 'Usabilla Live', action, label, value, {nonInteraction: true});

}

})

})

Send events to one specified tracking code

If you are using multiple Google Analytics tracking codes, but you would like to send your events to one specific tracking code you can use the below JavaScript snippet. Insert the name of your tracking code as indicated and place the snippet below your existing Usabilla code. Whenever a user then leaves feedback through Usabilla, the events will be sent to your specified tracking code.

window.usabilla_live('setEventCallback', function(category, action, label, value) {

ga(function() {

var trackerName = 'Insert your tracker name here';

ga(trackerName + '.send', 'event', 'Usabilla Live', action, label, value, {nonInteraction: true});

})

})

Finding the name of your tracking code

The name of your tracking codeis either specified by your developers in the Google Analytics implementation or by your tag management system. Please find more information about tracker names here.There are a number of browser extensions available that help you to find the name of your tracking code, for instance, Google Analytics Debugger for Chrome.

In the below example we use the name that Google Tag Manager allocated to our Google Analytics tag.

window.usabilla_live('setEventCallback', function(category, action, label, value) {

ga(function() {

var trackerName = 'gtm1477995090429';

ga(trackerName + '.send', 'event', 'Usabilla Live', action, label, value, {nonInteraction: true});

)}

})

Any questions? Please feel free to reach out to our friendly support team.

In this article, we're going to cover how to create your (first) workspace. We're going to start with the definition of a workspace and will end with the creation of a workspace plus editing options of your workspace.

But before we start, we would like to highlight a few things:

Currently, the Feedback that is available is Feedback gathered by the Usabilla for Websites Campaigns and the Usabilla for Apps Campaigns.

You do not need to create new campaigns for them to appear in Usabilla Workspaces. Usabilla Workspaces will sync all of your campaigns from Usabilla. Note: currently, feedback data is only available from April 5th, 2019 in Usabilla Workspaces

A workspace can - for the time being - only be created and deleted by users with the role of Administrator. For now, you will have to be an Administrator within your current Usabilla-account to be an Administrator within Usabilla Workspaces. Also, an Administrator within Usabilla workspaces will have access to all workspaces, whereas, in the current Usabilla account, it's possible to give an Administrator only access to specific feedback buttons (and thus, campaigns). Anyone who is provided access to a workspace will be able to edit all of the charts within that workspace.

For now, nothing that you do in Usabilla Workspaces will affect any of your campaigns or data in Usabilla.

This Guide consists of:

What is a workspace?

How to structure a workspace?

Create a workspace in 4 easy steps:

Create a new workspace

Give your workspace a title and description

Select the campaign forms that you want to use in your workspace

Set your permissions

Edit a workspace

Delete a workspace

What is a workspace?

So, what is a workspace? A workspace is an environment that allows you to combine and segment responses in any way that fits your organization. You can create a workspace based on a structure that is appropriate to your teams, your goals and the insights that you want to share with your stakeholders. Want to combine the Responses coming from different channels? No problem. Different languages? No problem. Different platforms? No problem! In a workspace, you can select the data, add visualizations, filter the data, read the relevant responses and act upon the responses.

How to structure a workspace?

Before you create a workspace, we recommend thinking about how you best want to visualize your data from the existing campaigns that you are running in Usabilla. Think of what the key goal is and have this in mind as the title of your workspace. See more tips about how to structure your workspace.

Create a workspace in 4 easy steps

Step 1: Create a new workspace

You create a workspace by clicking on "New Workspace" on the top-left of your screen:

here

Step 2: Give your workspace a title and description

Then, you will be asked to enter the name and description of the workspace. The name is mandatory and can contain a maximum of 70 characters. The description is not mandatory, but advised, and can contain a maximum of 500 characters. We would advise you to think about a naming convention that works for you and that will make sure you and your colleagues easily recognize what data is in the workspace. Everyone who is using the workspace should know what's in there. Don't worry if you are unsure about what to call your workspace, both the name and description are editable. Please see below:

Step 3: Select the campaign forms that you want to use in your workspace

Now, click on "Continue". There, you will be able to select the Usabilla for Websites campaign forms you want to use in your workspace:

1. Search bar to quickly find the campaign forms you want to use in your workspace. It's also possible to sort the different forms alphabetically (ascending and descending).

2. Indicates which Usabilla product your form was created with within Usabilla.

3. Sort your forms based on creation dates.

4. Sort your forms based on status (inactive or active).

Step 4: Set your permissions

Once you’ve chosen the forms that you want to analyze in your workspace, the next step is to select who you want to provide access to your workspace. By default, a workspace will be made public to all Usabilla users within your organization, whether these users are an Administrator or not. So, by default, non-admins will also have access to any workspaces that are created in Usabilla Workspaces. When new users are added to Usabilla (such as when a new employee joins your company), they will also automatically have access to any public workspaces within Usabilla Workspaces.

However, the choice is yours. If you would like users to only have access to data that is relevant to them, you can apply restricted permissions to specific users in a workspace. When you decide to restrict access, only the creator of the workspace will have the right to edit the title, forms, and permissions within the workspace. For now, you can apply "Can edit data" rights to users that you would like to provide access to your workspace. Please see below:

Great stuff! If you made it up until here, you have created your workspace. Now, let's populate it with data by following our guide on "How to create a chart".

Edit a workspace

Let's say you have created your workspace, but, there's something missing. That one thing. That one campaign form you wanted to select isn't in your selection or maybe the description is not clear enough. This is where the editing options of the workspace come in.

To view the available editing options of your workspace, click on the three dots in the top right corner:

Administrators of your account will have the following options after opening the edit menu:

Edit form selections: want to add or exclude specific forms from your workspace? As an administrator, you can either select the "Edit Form Selection" option from the "Forms" filter or select the "Edit form selections" option by clicking on the three dots. Either option will take you back to the relevant step in the workspace creation wizard.

Edit title and description: if you want to change the title or description of your workspace, select the "Edit name and description" option from the three dots. This will take you back to the relevant step in the workspace creation wizard.

Edit permissions: if you want to change who has access to the workspace, select the "Edit permissions" option from the three dots. This will take you back to the relevant step in the workspace creation wizard, where you can either restrict access or provide access to all Usabilla users in your company by selecting "Public" access option.

Note: Only an Administrator can edit a workspace.

Delete a workspace

Oh, snap, the workspace you created is not correct and you would like a reset? Not to worry, for this and other scenarios where you'd want to delete the workspace you have created, we have the "Delete workspace" option.

The "Delete workspace" option can be found under the three dots in the top right corner of your workspace:

Click on the three dots (1.)

Select "Delete workspace" (2.)

Note: Only an Administrator can delete a workspace.

Success

Awesome: By completing this guide you have a great understanding of how workspaces can be created, edited and deleted. Don't let us stop you there! Click to see an overview of all the available Support articles we have created for Usabilla Workspaces. Whether you'd like to know how to create a chart in workspaces, how to use the filters in your workspace or if you'd like to know more about the visualization options we have available for your charts, we got you covered!

When you've created your Workspace and added a chart to it, we have some awesome filters you can use to drill down on the Feedback you're seeing in your Workspace. In this article, we'll be highlighting each of the filters to explain and show you how they work.

This guide consists of:

The Form filter

The Unsubmitted Responses filter

The URL filter

The Forms filter

In the creation process of your Workspace, a set of Forms has been selected. The Feedback of these Forms is being shown in the Charts in your Workspace. By default, you will be seeing the Feedback of all selected Forms in the Charts. But if you'd like to decide for yourselves Feedback from what Form should be displayed, then the Form filter can help you out.

To use the Form filter, click on the button that indicates what number of Forms are included in your Workspace:

here

Once you've clicked the button, a list will appear with the names of the Forms that are supplying Feedback to your Charts. To see what your Charts would look like without a Feedback of a specific Form, simply click on the name to deactivate it:

The Unsubmitted Responses filter

By default, the Feedback shown in your charts are from users who have completed the Campaign they have seen. Per definition, we define a user who has completed a Campaign, a user who has seen the "Thank You" page of a Campaign. But, what about the users who dropped off before seeing the "Thank You" page? We have got those responses covered as well with the "Unsubmitted responses" filter. By enabling this filter, you will see the responses of users who have started the Campaign, submitted one page of your Campaign but didn't reach the "Thank You" page.

To use the "Unsubmitted responses" filter, click on the button that indicates what number of Forms are included in your Workspace:

Click on the slider next to "Include unsubmitted response":

How does this work? When a user navigates from one page in a Campaign to another, their response is sent to Usabilla Workspaces. The page switch is essential for this. If the user does not navigate from one page to the other, because they leave when seeing the first page, we will not be able to gather the unsubmitted response.

The URL filter

After creating your workspace and adding one or multiple charts to your workspace, you'd might want to segment your metrics by URL. This can help you to better understand the performance across different business units, locations and/or customer journeys.

To use the URL filter, click on the "Add Filter" button under the name of your workspace:

When the Filter menu opens, select "URL":

After selecting "URL", you will be presented with the option to set a rule for the filter (1.) and the field where you can specify a part of or the full URL/Path (2.):

To help you filter as specific as possible, we have the following rules to choose from:

Does not contain: Will display all feedback that was left on a URL not containing the input in the next field.

Is exactly: Will display all feedback that was left on a URL exactly matching the input in the next field.

Is exactly not: Will display all feedback that was left on a URL exactly not matching the input in the next field.

Once you have selected the rule for the entry in the input field for the URL, hit "Enter" to activate the filter. When your filter has been activated successfully, the filter will be displayed like this:

Success

Awesome: By completing this guide you will be able to use the filters in Usabilla Workspaces. Don't let us stop you there! Click to see an overview of all the available Support articles we have created for Usabilla Workspaces. Whether you'd like to know how to create a workspace, how to create a chart in your workspace or if you'd like to know more about the visualization options we have available for your charts, we got you covered!

For charts in Usabilla Workspaces, we give you the ability to configure a visualization option. Each of the visualization options we provide will display the feedback differently. Along with each visualization option, we also provide some additional settings that can help finetune your charts. In this article, we will help you understand the visualization options we provide, the additional settings per visualization option and show you examples of each of the visualization options.

Since the visualization options you will be seeing depends on the chart type you select, we have split the visualization options up in two groups. When a NPS, Mood, and Rating chart is created, you will see a set of visualization options. When a "Open text answers" chart is created, you will see a different option. To keep things clear, this article is divided in the same way.

This guide consists of:

Visualization options for NPS, Mood and Rating charts:

The "Score over time" visualization option

The "Single score" visualization option

Visualization option for Open text answers:

The "List view" visualization option

The "Score over time" visualization option

The "Score over time" visualization option will provide you with a graph displaying how the score of the selected question(s) in your chart changed during the selected time period. This is an example of how the "Score over time" visualization option can be displayed:

here

The "Score over time" visualization option comes with some additional options:

"Hey Rakesh, what do these options actually do?" Great question, allow me to elaborate.

One trend line per question: Enabling this will display a trend line per question. When disabled one trend line will be displayed with the average score of the questions in your chart combined.

Different colors: Enabling this will give each trend line a different color. Only applicable when more than one trend line will be shown in the chart.

Overall results trend line: Enabling this will display a trend line with the average score of the questions in your chart combined.

Margin of error: Enabling this will display a margin for your trend line(s) that represents the maximum amount by which the sample results are expected to differ from those of the actual population. We do not display a margin of error for questions with less than 30 feedback items.

Mood score line for the period: Enabling this will display a dotted line representing the average score over the period.

The "Single score" visualization option

The "Single score" visualization option will provide you with a single-digit average score for the selected questions over the selected period. This is an example of how the "Single score" visualization option can be displayed:

The "Single score" visualization option comes with an additional option:

"But Rakesh, what does this option do?" Another great question, allow me to elaborate.

Show comparison to last period: Enabling this option will inform you in percentages how much the score changed over the previously selected time frame. If you have configured the data range to show data over a week, this percentage will calculate the change compared to the week before the current week. If you have configured the data range to show data over a month, this percentage will calculate the change compared to the month before the current month.

The "List view" visualization option

The "List view" visualization option will be available when the "Open text answers" chart type is selected. When this chart type and visualization option is selected, you will be able to see the responses left in open text field by your users:

Success

Awesome: By completing this guide you will be able to understand the visualization options we provide in Usabilla Workspaces. Don't let us stop you there! Click to see an overview of all the available Support articles we have created for Usabilla Workspaces. Whether you'd like to know how to create a workspace, how to create a chart in your workspace or if you'd like to know more about the filter options we have available for your workspaces, we got you covered!

Usabilla builds SaaS solutions, empowering brands to improve their UX, increase conversion on their marketing emails or make their mobile apps more user friendly.Currently we offer fourdifferent products:

Usabilla for Websites:Collect visual feedback on your website.

Usabilla for Email:Receive valuable feedback on your marketing or personal emails.

Usabilla In-Page:Ask your users about a certain element and collect this feedback in the very same page.

Usabilla for Apps:Gain insights in your users' feedback about your mobile applications.

Our two-way integration with FullStory allows you to push FullStory data together with Feedback from a Form or Campaign to Usabilla and push Usabilla Feedback to FullStory. This will help you and your team to quickly learn what happened in the session before the user gave Feedback or submitted a Campaign response. In turn, this will allow you to get more context when researching or analyzing the Feedback in Usabilla or when analyzing the user's behavior in FullStory.

In this article, we will be covering both types of integrations and help you set them up. After reading this article you will have a general understanding of the methods we have used to set up the integration and you will be able to set it up yourself.

Note: The FullStory integration is not an out-of-the-box integration. For setting up the integration you need some basic understanding of JavaScript.

This Guide consists of:

How to push FullStory data to Usabilla

How to push Usabilla Feedback to FullStory

What do you need?

- A Usabilla account

- A FullStory account

- Basic understanding of Custom Variables in Usabilla for Websites

- Basic understanding of the Usabilla Event Callback

How to push FullStory data to Usabilla

To push FullStory data to Usabilla we will be using Custom Variables. Custom Variables are data points you define and communicate to Usabilla. Some examples of Custom Variables are the Customer ID, the basket value, the tier, etc. The only requirement for converting a data point to a Custom Variable is that it's available on your website. Since the FullStory runs on your website, the data is available on your website and it can be converted in Custom Variables.

Converting the FullStory data to Custom Variables requires adding some JavaScript to your website. We've added an example code below that gathers the session data from FullStory, adds it to a JavaScript object and pushes that object to Usabilla as a Custom Variable object. The JavaScript has some prerequisites to work, the most important thing is the JavaScript below is executed after the FullStory code and Usabilla Installation Snippet are loaded in. An easy way of achieving this is by using a tag management system with tag sequencing. If you prefer you can also make sure of the _fs_ready function that is available in the FullStory script if you don't run FullStory on all your web pages.

When the integration is set up correctly you will be able to see the FullStory SessionID and Session Link with every Feedback item and Campaign response in Usabilla. Only when FullStory was running at the moment the user gave feedback will you see the data show up. Keep in mind that you're free to change the integration code used in this article. So you can change the name of the custom variables if you see fit.

Usabilla Support

Because we're using Custom Variables to push the FullStory data to Usabilla, we'll need to make sure that we don't overwrite existing values. Therefore, we recommend using the JavaScript object method shown in the example code to initialize and manage the Custom Variables. This method makes sure that you can simply push any updated data by reinitializing the JavaScript Object instead of redefining all values. You can use the usblUpdateCustom function for this.

How to push Usabilla Feedback to FullStory

To push the Feedback given by your users in a Usabilla Form or Campaign, we will be using our Event Callback function. The Event Callback function allows you to follow up an interaction between the user and Usabilla with another action. In this case, we will follow up the interactions "a Feedback Form being submitted successfully" and "a Campaign being submitted successfully" with the action "sending a Custom Event to FullStory". The Custom Event that is sent to FullStory will contain the Feedback and all additional data.

Including the Custom FullStory Event in an Event Callback function requires adding some JavaScript code to your website. The example code below triggers the Custom FullStory Event when a Feedback Form is submitted and when a Campaign has been submitted. Within the Custom FullStory Event, we're sending some parameters of our Event Callback that contain specific pieces of information. Feel free to change the example code to push parameters containing pieces of information that is relevant to you. For a full description of what information each parameter contains, have a look at our Article about the Event Callback.

Once the integration is set up correctly, you will be able to see the Custom Events in FullStory under the name that has been selected for it. Open the Event to see the details of the Feedback given by your users.

Success

Awesome: We hope this article helps you set up the integration with FullStory. If you have any questions or Feedback for us, feel free to reach out to !

In this article, we will focus on saved searches. We will talk about what they are and how you can set them up. We’ll also talk about how to set up email notifications based on these saved searches.

In this guide we’ll go over:

What are saved searches?

How do I set them up?

Managing your saved searches

Enabling the feature 'Send me an email for every new feedback response'

What are saved searches?

When you apply filtering options to your feedback items, you’re actually searching for specific feedback items. You might not have thought about it like that before, but in essence, that’s what filtering means. This also means that when you then save that filter, you end up with a saved filter. Here at Usabilla, we call this a saved search.

You can then use this saved search to quickly filter out the relevant feedback the next time you log into your Usabilla account. It simply makes sure you don’t have to apply the same filtering options every time you want to look at specific feedback. Feedback from a specific button, for example.

When setting up a saved search, you are given the option of receiving an email whenever a new feedback item is created that matches your search criteria. Administrators can also assign this saved search to the account of (several) team member(s) with an own Usabilla account. Non-administrators cannot do that on behalf of team members.

How do I set them up?

Now that you know what a saved search is, let’s take a look at setting them up. Please follow the following steps.

Log into your Usabilla account, select Websites in the top-left navigation and open the Feedback section.

Now filter your feedback by relevant criteria. For example: show all feedback items received via a specific feedback button. Or all feedback items with a negative mood rating. It’s totally up to you.

Now click on “New Save Filter”.

Please see below:

here

You’ll now be presented with the following pop-up:

Give your saved search a unique name.

Decide if you want to assign the saved search to your account or to your account and the team account of a team member. Administrators can also assign this saved search to the account of (several) team member(s) with an own Usabilla account. Non-administrators cannot do that on behalf of team members. It's possible to assign the saved search to multiple team members by adding multiple email addresses, divided by a comma. Mind you: if you decide to assign a saved search to a Usabilla account of a team member, that team member will also receive a saved search under her/his account. Should you decide to delete that saved search, this saved search will also need to be deleted under the account of the team member.

Decide if you (and, if chosen, your team member) want to receive email updates for your search. If not, then your saved searches will simply function as handy tools to quickly filter your feedback items (see paragraph 1). In that case, you can save your saved search now.

If you want to receive email updates, decide if you want to receive extended emails in HTML or minimalistic emails in plain text.

If you chose for extended emails, decide if you want to receive public links in these emails. Public links are hyperlinks which you can share with people without a Usabilla account. These public links will contain information about the feedback item(s).

Decide how many feedback items you want to receive per email. You can choose between 1 email per feedback item received within the frequency chosen under point 7 or simply all feedback items received within that frequency.

Select the frequency.

Don’t forget to save!

Managing your saved searches

To manage your saved searches, click on your username in the top right corner and go to “Account Settings”.

Select “Live Mail Settings”. Click on any of your saved searches to edit the name, frequency, and the time when the email update is sent. You can also delete your saved search if you no longer need them.

Enabling the feature 'Send me an email for every new feedback response'

Under this tab ("Live Mail Settings"), you can also enable the option ‘Send me an email for every new feedback response’. This feature is not related to the saved searches. It simply makes sure that you’ll receive a separate email for every new feedback item coming through your feedback buttons, regardless of any of your saved searches. These emails will be sent to the email address of your account. Also: looking for information on exporting your feedback items? Please go .

In this article, we will focus on Usabilla In-Page. We will talk about what they are, how you can set them up and how you can implement them on your website.

In this guide we’ll go over:

What is Usabilla In-Page?

Setting up In-Page

Implementing your In-Page widget

What is Usabilla In-Page?

With Usabilla In-Page, you can integrate our feedback widget right in the middle of the content of your website. This allows you to gather very specific element- or content-related feedback.

An In-Page widget looks like this:

here

After clicking on ‘YES’ (or ‘NO’), your visitor will be asked to explain his or her answer in an open text field:

But mind you: there are a lot more options than just ‘Yes’ and ‘No’ and a simple follow-up question! More on that below under ‘Setting up In-Page’.

Setting up In-Page

In-Page actually consists of 2 elements: a widget and a script. The widget is the actual piece of software your visitors will get to see. The script simply makes sure the widget can be shown on a website.

- First, go to your Usabilla account and click on ‘Setup’ under ‘In-Page widget’ and ‘Websites’. Please see below:

If you don’t have access to In-Page, please contact your Customer Success Manager.

- Click on ‘New widget'

- Give it a name

- You’ll be asked to select an existing script to install the widget on or add a new script. But what is a script? As said, you’ll use the script to make sure your widget can be shown on your website. But scripts also allow you to group multiple widgets according to your organisational needs. You could, for example, use a different scripts for each of your websites or different scripts for each of your departments. Please see below:

- After this, you’ll be presented with all of the In-Page options we offer. There are quite a lot of options, so take your time to familiarize yourself with the product. You could, for example, only ask ‘Did you find this useful’ and then use the ending page or add different follow-up questions. Please see below:

Tip: If you have a custom theme from Usabilla for Websites (for Forms or Campaigns) these can be selected under ‘Advanced’. The In-Page widget will automatically have your colors and style. If you don’t have a custom theme request one .

Implementing your In-Page widget

Now that you have a shiny, new In-Page widget, you’ll want to use it of course. To implement the widget, you'll have to add two pieces of code to your web page. We will start by adding the Javascript code and finish with the code for the widget itself.

- To see the two pieces of code, click the install icon next to the name of your widget:

(If you’ve just finished creating a new widget, you’ll be automatically directed to this page.)

- Select the code under ‘Script snippet’ and copy it:

- Paste the code into the bottom of every page you want the widget to appear, just before the closing body tag (</body>)

- Select the code under ‘Widget code’ and copy it:

- Paste the code in the section of the HTML where the widget should appear. You will have to do this on every page you want the widget to appear.

Make sure that the HTML container for the widget is defined before you execute the script. If you're using a Tag Management system then make sure that the firing rules is set correctly. First execute the HTML container, then execute the script.

Tip: when you are using a CMS make sure the Script snippet is installed in your main page template. Be consistent when implementing the scripts. So if you use GTM to implement your feedback button make sure you use GTM as well for the Script snippet.

Usabilla In-Pagefeedback can be supplemented with information you already acquired about your user or your website. This information can be passed on to Usabilla through Custom Variablesso every new In-Page feedback item will include yourcustom variables.

Please follow these steps to include Custom Variablesin yourUsabilla In-Page feedback.

1. Define the data you would like to pass on to Usabilla.Examples of Custom Variables are: usernames, session IDs, A/B-testing variablesfrom other tools, demographic data and membership statuses.

2. Add an id attribute to your In-Page div element.Find the div elementof Usabilla In-Page on your website and add an id attribute to the div. This id will be used to append an attribute containing your custom variable to the div. Your divwill then resemble the below div.

<div id="in-page-id" ub-in-page="5757d2dd980232864f94990e"></div>

3. Find the Usabilla In-Page script on your page and add the belowcode.Ensure that this code is positioned directly beneath the Usabilla In-Page script on your webpage.Replace "in-page-id" by the ID you are using and replace "key" with the name you would like to use in Usabilla for your custom variable. Lastly, replace "customVar" with your custom variable.

document.getElementById('in-page-id').setAttribute("ub-in-page-key", customVar);

4. Test your custom variable. Simply leave feedback through your In-Page widget and check your variable in Usabilla. The variable will be accessible by the feedback page's left-hand filter panel and included in the .csv exports.

Welcome to Usabilla Workspaces! We are excited for you to get your hands on Usabilla Workspaces and help you get much more out of the Feedback you have retrieved with Usabilla. What better way to help you get started than a Support article that covers the basics? So let's get started!

This guide consists of:

What is Usabilla Workspaces?

How do I access Usabilla Workspaces?

How do I use Usabilla Workspaces?

What is Usabilla Workspaces?

Usabilla Workspaces is our new Analysis feature that places a wide variety of ways to analyze your Usabilla Feedback in the palms of your hands, literally:

In Usabilla Workspaces you can:

Create and share charts based on NPS, Mood or Rating questions

Merge or compare different Campaign form results in order to track and report on your main KPIs

Filter and manipulate the data to uncover opportunities

Share a story that is meaningful and impactful to your organization

Awesome, right?

Note: Usabilla Workspaces is a new feature in Usabilla, this means that Usabilla as you know it will not change. The analysis features that you are used to are still accessible and the trusty way of creating Forms, Campaigns and Widgets will not change.

How do I access Usabilla Workspaces?

Usabilla Workspaces can be accessed through this link. Once you have opened the link or went to the URL, you will be welcomed by a very special login screen. To make things super easy, you can use your existing Usabilla credentials to log in to Usabilla Workspaces:

Your Usabilla Workspaces username = the email address of your Usabilla account

Your Usabilla Workspaces password = the password of your Usabilla account

Tip: Bookmark this URL for ultra-easy access to Usabilla Workspaces.

If you have added an additional layer of security to your Usabilla account in the form of Two-Factor Authentication (2FA), first of all, compliments from our Security team, secondly, we also encourage you to enable this for Usabilla Workspaces. To do this, simply scan the QR code that is shown and this will create a new entry in your Authenticator app specifically for Usabilla Workspaces. If you don't have 2FA setup for your Usabilla account, we strongly encourage you to set it up for both your Usabilla and Usabilla Workspaces accounts.

So now that we've got you into Usabilla Workspaces, let's talk about the things you can do in this beautiful new environment. In Usabilla Workspaces we have two types of user roles, Admins and Users. Below you will find an overview of what Admins can do and what Users can do.

Admins can...

Users can...

Create a workspace

Create new workspaces

Invite users to a new workspace

Not create new workspaces

Edit an existing workspace

Edit existing workspaces

Manage the access to existing workspaces

Not edit existing workspaces

Delete a workspace

Delete workspaces

Not delete workspaces

View workspace

View all the workspaces

View the workspaces they have access to

Create a chart

Create new charts

Only create charts for the workspaces they have access to

Edit an existing chart

Edit any existing chart

Only edit charts for the workspaces they have access to

Note: If you are an Administrator in Usabilla, you will be an Admin in Usabilla Workspaces.

If you are not an Administrator in Usabilla, you will be a User in Usabilla Workspaces.

How do I use Usabilla Workspaces?

You've seen the word "Workspaces" being mentioned multiple times in this article, but what is this thing we call "Workspaces"? A workspace is an environment that allows you to combine and segment feedback. Admins can create as many workspaces as they would like. Users with other Usabilla roles will need to be invited to a workspace, where they will be able to create charts. Within a single workspace, you will be able to create as many charts as you want and share that workspace with as many Usabilla users in your organization as you want.

Tip: Click here to go to the article we've written to help you create a workspace.

Within a workspace, you have the ability to create a chart based on a question type (e.g. NPS, Mood and Rating) from campaigns forms created in Usabilla. You can choose a question type from different campaigns and combine the data from these campaigns to visualize it in different ways. For example, combine NPS scores from multiple campaigns and visualize them in a trendline to uncover key insights over time, then allow the relevant people within your organization to see these results

Tip: Click here to go to the article we've written to help you create a chart in a workspace.

Before jumping in the fun, it is important to think about how you'd like to structure your workspaces. To help you get started we'd like to suggest a couple of points that can help in setting up a structure in your Usabilla Workspaces environment. Before setting up your workspace, think about the following points:

Who should have access to all/a specific workspace(s)?

What is the key objective that will be monitored in a specific workspace?

What kind of charts will be created in a workspace?

What goal do you have in mind when creating a workspace?

Use a naming convention for your workspaces and charts to ensure that everyone in your team can understand it.

Success

Awesome: You have finished the Getting Started with Usabilla Workspaces guide. Please have a look at the other articles we've written about Usabilla Workspaces here.

In this article, we will cover how you can integrate your own chat functionality with your Usabilla Feedback Button.When you're creating your Usabilla feedback form, you can give the user several options at the intro screen of the feedback form. This includes the option for specific & generic feedback and a third custom option:

Usabilla Support

Before we get started, let's look at some requirements to set this up:

Requirements

Access to edit the button form in your Usabilla account

A chat functionality which can be triggered with JavaScript

A Tag Management System (recommended)

Some level of JavaScript knowledge

Table of Content

Setting up your custom chat option

Create JavaScript code for chat functionality

Implement code through your Tag Management System

1. Setting up your custom chat option

First, go to Setup --> Edit default form:

To activate the custom option, you have to click the edit link at the top right corner in the intro screen editor:

Then add the custom option by activating it and choosing "execute script" in the "On click" field:

2. Create JavaScript code for chat functionality

To make this work, you have to create some JavaScript that will execute the chat functionality once a user clicks on the custom option. By using our JavaScript API, we can hook onto the event when a user clicks the custom option.When you add the custom option, make sure you first place the function you want to run into a variable.

<script type='text/javascript'>

function liveChatUsblFunc(){SCRIPT TO ACTIVATE CHAT HERE};

window.usabilla_live("setCustomOptionClick", liveChatUsblFunc)

</script>

In this script, you will have to append the JavaScript code that will trigger the chat functionality. The specific location for this script is commented in the code.

3. Implement JavaScript code through Tag Management System

Once the code has been modified to suit your specific chat functionality, you have to append it to your website. Most 3rd party scripts today are installed through a Tag Management System. If you don't use one, we highly recommend using one as it gives you a good overview of all the code snippets installed on your pages. It also gives you control over the dependencies between different scripts/tags.

I'll walk through the implementation in Google Tag Manager, which is one of the most used Tag Management Systems out there. If you happen to use another one, the same configurations apply.

1. Start to create a new tag for the custom script:

2. Select Custom HTML Tag:

3. Copy & paste your script snippet into the HTML section:

4. Set up the correct triggering rules for the tag:

In all cases where you will do JavaScript API calls towards Usabilla, the feedback button code has to be executed/triggered first. If the triggering sequence is not set up correctly, the custom option won't work.

5. Set up triggering configuration

This tag should follow the same triggering configuration as you have for the Usabilla Feedback Button

Congratulations! You just achieved a new level of customer centricity. If you have any questions, feel free to reach out to .

Note: This article only applies to Optimizely X. If you are using Optimizely Classic, just message us at [email protected].

If you use Optimizely to perform A/B tests on your website, user feedback can add valuable insightsto these A/B tests.

By integrating Optimizely and Usabilla you will be able to segment and analyze Usabilla feedback items or campaign results according to your Optimizely experiments. You will also be able tocompare feedback from different test variations within one experiment.

In this guide, we will walk you through the setup of sending the Optimizely information to Usabilla in the form of Custom Variables. This will result in the Optimizely data being available when reviewing feedback but also giving you the opportunity to target Campaigns on users in specific Variations.

The Setup

We will use the Optimizely X Javascript API toaccess the information on the running Optimizely experiments or personalisation campaigns and the corresponding variations and then send these to Usabillathrough custom variables with thescript below.This script needs to run after the regular Usabilla for Websites button script has been loaded.

usblCustomVars = {};

//Potentially define other custom variables here by adding them to the usblCustomVars object:

//usblCustomVars['Variable X'] = 'value A';

//usblCustomVars['Variable Y'] = 'value B';

//usblCustomVars['Variable Z'] = 'value C';

function updateUsblCustomVar() {

window.usabilla_live('data', {

'custom': usblCustomVars

});

}

function checkOptimizely() {

if (typeof optimizely !== 'undefined' && optimizely !== null) {

var campaign_data;

// Get Optimizely state

var state = optimizely.get('state');

// Return all active campaigns

campaign_data = state.getCampaignStates({ "isActive": true });

// Loop through Optimizely Campaigns

for (var campaign_id in campaign_data) {

if (campaign_data.hasOwnProperty(campaign_id)) {

// Get all data

var data = state.getDecisionObject({ "campaignId": campaign_id });

// Get variation

var variation = data.variation;

// Get experiment

var experiment = data.experiment;

// Append experiment and variation to Usabilla custom object

usblCustomVars['Optimizely_Experiment_Name: ' + experiment] = variation;

}

}

}

updateUsblCustomVar();

}

function onCampaignDecided(event) {

checkOptimizely();

}

if (typeof optimizely !== 'undefined' && optimizely !== null) {

window["optimizely"] = window["optimizely"] || [];

window["optimizely"].push({

type: "addListener",

filter: {

type: "lifecycle",

name: "campaignDecided"

},

handler: onCampaignDecided

});

}

checkOptimizely();

Optimizely data in your feedback

Once this has been implemented the Optimizely experiment name or ID and the corresponding variation name or IDwill be added to each Usabillafeedback items and campaign result, deriving from a page on which Optimizely is running. The following data will be shown:

Each active experiment that is running on the page a user gave feedback on.

The data will appear as follows: Optimizely_Experiment_Name: 'experiment'.

If the name for an experiment or variation is not specified within Optimizely, the ID will appear instead.

friendly support team

Through this added data, you will be able to filter and segmentyour feedback items or campaign results according to Optimizely experiments. The appropriate filter option to use is the Custom Variable filter:

Target Usabilla campaigns to a specific test variant

After pushing theOptimizely data to Usabilla you will be able to show a survey tovisitors that are in a certainexperiment or even see a specific variation. You can achieve this by activating the Custom javascript value trigger targeting option.

Any questions? Reach out to our !

At Usabilla, security is always a top priority. In an era where digital threats are significantly widespread, a SaaS company cannot fail to have adequate security controls in place to deliver a trustworthy product. Every day, our security team operates with the goal of providing a secure and reliable service to our customers, and achieving peak security accreditation is a team effort.

We are therefore pleased to share that, as of July 10th, 2019, Usabilla is officially ISO 27001:2013 certified.

What is ISO 27001?

The ISO 27001 certificate is the most globally recognized information security standard defined by the International Organization for Standardization (ISO).

As the top certification for Information Security Management Systems (ISMS), it prescribes a set of rules on how organizations should manage and handle information in a secure way to safeguard its integrity, confidentiality and availability.

What does this mean for you as a customer?

We take the security of your information seriously and have implemented sophisticated security measures to safeguard it. We want our customers to rely on and fully trust our technology and services.

Achieving the ISO 27001 certification is a great milestone for Usabilla. For us, information security is also a question of company culture. With everyone’s daily contribution we always aim to not only maintain, but to further improve our high security standards. The maturity of our processes is now also officially attested by an independent party.

Lucas Garzarolli, Security Officer, Usabilla

By complying with information security best practices and internationally recognized standards, you can have this assurance. The ISO 27001 certificate is proof that Usabilla has properly implemented processes and organizational structures to:

manage all risks related to information security,

protect information assets, and

achieve compliance with international best practices and legislation.

In closing

Our mission to security doesn’t end here. Information security is an ongoing process and we will keep working hard to maintain and exceed our standards to protect both company and customer data. Yearly audits will be performed by an external auditor to attest to our continuous compliance as we continue to develop and grow our business.

Reach out to your CSM to request a copy of the certificate or learn more by chatting with us.

Our Usabilla API for Usabilla allows various additional actions to be performed on our Feedback button. Through this API you can, for instance, alter the position, appearance or trigger of your feedback buttons and forms. The JavaScript API is only used for interacting with the Usabilla Buttons and Forms. If you want to use data collecting with Usabilla, use it in your own application, or want to integrate Usabilla data with another platform then check out our Public API. More information on using our Public API can be found on http://developers.usabilla.com.

To use our API calls, insert your command anywhere below the code for the original button widget as follows:

<script type='text/javascript'>

window.usabilla_live("Enter your Command here");

</script>

Available API Calls

add custom variables

Custom variables add information that you collect about your user to your feedback items and campaign results. Add the below API call to your web page in order to include this information in Usabilla. You can replace "server_name: s.server" by your own custom variable name and value. If you want to find out more about Custom variables in Usabilla for Websites, check this article.

<script type='text/javascript'>

window.usabilla_live("data", {custom: {server_name: s.server }});

</script>

click

Simulates a user clicking on the button. ie. once the click command has been triggered, the feedback process begins. This command allows you to trigger the feedback form from any element of your website.

<script type='text/javascript'>

window.usabilla_live("click");

</script>

hide

Hides the button from view. By default, the button is shown but calling this command prevents this.

<script type='text/javascript'>

window.usabilla_live("hide");

</script>

show

Shows the button on the site. Shown by default, but can make the button reappear after a hide.

<script type='text/javascript'>

window.usabilla_live("show");

</script>

setForm

Allows you to specify which custom feedback form you would like to be shown. Note: The form name must exactly match a form associated with the button in use.

<script type='text/javascript'>

window.usabilla_live("setForm","Enter the exact custom form name here");

</script>

setInterfaceZIndex

Controls the depth of the feedback form interface on the web page. Allowing you to configure around other elements. To ensure that your feedback form appears on top, ensure that the Z-index is higher than the Z-index of other elements on your website.

<script type='text/javascript'>

window.usabilla_live("setInterfaceZIndex", "99999");

</script>

setButtonZIndex

Controls the depth of the button on the web page. Allowing you to configure around other elements.

<script type='text/javascript'>

window.usabilla_live("setButtonZIndex", "99999");

</script>

setCustomOptionClick

Allows you to add a script to the optional third option in your feedback form's introduction screen. Enable the script in the feedback editing form before installing this API call. When you add the option make sure you first place the function you want to run into a variable.

<script type='text/javascript'>

window.usabilla_live("setCustomOptionClick", "Add third option here");

</script>

<script type='text/javascript'>

var livechatUsblFunc = function(){console.log("Do something")};

window.usabilla_live("setCustomOptionClick", livechatUsblFunc);

</script>

virtualPageView

When running Usabilla in a Single Page Application (SPA) it will be necessary to fire virtual pageviews to let Usabilla know that a user switched from one "page" to another. Please find more information here.

window.usabilla_live("virtualPageView");

UsabillaCampaignscan be set up to very accurately target specific users. The followingtargeting, settings are at your disposal to ensure that your campaign will show to the right users at the right time. They can be foundin the step 2 of your campaign editor and are available for all campaign types. Simply enable each targeting option and fill in the details to use it.

Note that targeting options always work together as AND-conditions. This means that all targeting options need to be matched in order for the campaign to be shown.

Visitors on a specific page

here

Show your campaign to specific visitors by defining the URL(s) on which your campaign should show or should not show. Please note that you can only show the campaign on pages that have the Usabilla feedback button installed.

Using the URL targeting you will first have to define whether you'd like to use the page's pathorfull URL. Select "full URL" if you'd only like totarget anything up to and including your top-level domain (for instance ".com" or ".nl"). Otherwise, select "Path".More information about "Full URL versus Path targeting" is available here.

Whenever your target URL contains a question mark or hash-sign ("?" or "#"), it's important to select the first checkbox. If you would like to show your survey on all URL excluding the target URL, select the second checkbox.

Next, choose the condition. The available conditions are "contains", "starts with", "ends with", "match exactly" or "matches regular expression". Generally speaking, the first options should suffice. If you have a very specific needs for targeting you can also use targeting based on regular expressions (Regex).

Regular expressions are widely used in programming and analytics tools. They offer a lot of flexibility in your targeting. There are some great resources available online for learning regular expressions.

Show a campaign after X amount of seconds on a page

Show the campaign to visitors who are on a page for a certain amount of time. You can show a survey after a few seconds, but you can also set the survey to appear a bit later. In the latter case, we recommend you to check your Analytics suite for the average amount of time your users spend on certain pages. This will allow you to target near the middle or end of their page visits.

Please note that the amount of seconds always works on a page level.

Tip! It is always advised to use the time targeting, so when the page has fully loaded a couple of seconds later the campaign triggers. This attracts more attention to the campaign.

Visitors potentially exiting the website

This will trigger visitors who move with their mouse pointer outside the active browser window after the defined time. Moving outside the active browser window potentially could mean visitors would like to exit the website/browser tab.

Note: This targeting works based on the mouse pointer. This means that the targeting option does not work for visitors accessing your website with a mobile device.

Returning / new visitors targeting

Here you can set if you only want to target visitors who are new on your site or only visitors who return to your site. By not enabling this targeting rule you will target both new and returning visitors.

Visitor percentage targeting

Here you can set that only a certain percentage of your visitors will see the campaign.

Website scrolling targeting

Here you can set to trigger the campaign when a user has reached the bottom of the site when scrolling down. You can set the number of pixels from the bottom when it should be triggered.

Pages visited targeting

Here you can set the number of pages the visitor at least needs to have visited before the campaign is triggered.

Tip! It helps when people browse your site first and give feedback when they know the page a bit. Therefore it is advised to set this targeting rule for most campaigns.

[Advanced] Manual targeting with javascript

Campaigns can also be triggered manually. This requires technical knowledge and access to the production website code or a tag management system. Every campaign can be triggered with it's unique trigger name. Set then name in the campaign editor and then copy the javascript snippet that appears. Add the javascript snippet to your website code in order to trigger the campaign in question.

window.usabilla_live("trigger", "campaign-name");

An example of when the manual trigger comes in handy is when wanting to show the campaign to a user on a button click. More information about the manual trigger is available here.

Targeting Cookies

Step 1 - Scroll down the targeting options to the visitors who have a specific browser cookie section and click the off button to switch it on.

Step 2 - Type in the name of the cookie and choose how you want it to relate it to the browser from the drop-down menu. You can also choose whether to make the cookie case insensitive by clicking the tick box underneath.

Step 3 - If you want to add another cookie to target just click the Add button and another box will appear directly underneath. This will also reveal two trash can icons which you can use to remove a cookie.

Cookies are widely used to set dependencies between different campaigns. A detailed explanation is available .

Target Specific Devices

In this section, you can specify which devices you wish to target with your campaign. The three options are Mobile, Tablet, and Desktop. The mobile and tablet options have several sub-categories to allow you to be more specific with the devices you wish to target e.g. you could choose to only target Android rather than all mobiles.

When you select a device all of the subcategories are automatically selected but can be removed by clicking on the tick box next to them.

You can let Usabilla for Websitesautomatically push feedback responses to your Zendesk.com setup. This way you can directly reply and manage Usabilla for Websitesfeedback responses in your customer support environment. To integrate Usabilla for Websiteswith Zendesk.com, please follow the steps below.

Getting Zendesk ready for the integration

1. Go to your Zendesk.com admin environment: https://[your sub domain].zendesk.com/home.

2. Go to “Settings” -> "Channels" -> "API".

let us know 3. Enable the token access API by checking the box. You'll see that a token will be generated for you. Make sure you save that page by clicking the black save button in the bottom right corner.

4. Open a new browser window and go to your Usabilla account settings.

5. Go to the live integrations tab

6. Click on the Zendesk.com logo to create a new integration. You can create an integration per button

Setting up the integration with Usabilla

Select the button you would like to create the zendesk.com integration for

Select when you would like Usabilla Live to push the feedback response:

When the feedback response has an email address

When the feedback response has a comment

When the feedback response has an email address or comment

Send all feedback responses

Enter your zendesk.com subdomain (e.g. https://[subdomain].zendesk.com).

Enter the email address you used at zendesk.com to sign up (use the email address that is listed in the exampleAPI call on the API page).

Enter the token of the zendesk.com API. If you are setting up the integration for multiple feedback buttons, it's possible to use the same Zendesk tokens for all buttons.

Check "Enable" to activate the zendesk.com integration for the selected button. You can always disable it later.

Click "Save" to finalizeyour zendesk.com integration.

Once the integration has been enabled you shall see tickets in Zendesk created like this:

If you've selected manual push as an integration option then you will have to manually push the feedback item from the feedback details page:

You can always edit your integration later to change the configuration or disable / enable the integration. If you have any other questions, please.

We are happy to announce a new partnership with ContentSquare which is on top of the game in UX analytics and customer insight. With the powerful combination of UX analytics and customer feedback, you will gain a true customer centricity insight of where to improve your customer experience.

What you need:

A Usabilla account with access to relevant buttons and campaigns

A Usabilla Feedback button installed

An account with ContentSquare

A Tag Management System

How the integration works:

This integration offers two methods. One method includes sending Usabilla data to ContentSquare and the other method also includes sending the ContentSquare ID to Usabilla. This allows you to find session replays in ContentSquare for specific feedback. The integration is enabled by placing a script on your web pages that will take care of the data acquisition for you.

What data points will be integrated:

A pageview will be tracked in ContentSquare each time the Usabilla pop-in appears for feedback or a campaign.

The mood score will be sent to ContentSquare dynamic variables for both feedback and campaigns.

The NPS score (if configured in Usabilla) will be sent to Contentsquare dynamic variables for both feedback and campaigns

The rating score for the first rating question in campaigns will be sent to Contentsquare dynamic variables.

Optional: The ContentSquare ID can be sent to a ContentSquare dynamic variable and to a Usabilla custom variable.

How does it look:

Within ContentSquare you can create custom segments in relation to Usabilla. Some segmentation examples would be:

Anybody that triggers the Feedback Button

Anybody that saw a Usabilla Campaign

Visitors that give a specific mood, rating or NPS score

You can apply any of the segments you create to the journey analysis module. In the below example we apply a SeenUsabillaFeedback segment to the sunburst. Here we can see where visitors choose to give feedback in their journeys:

https://docs.contentsquare.com/thirdparties/#usabilla

If we reverse the journey and select the UsabillaFeedbackWidget segment as the end point, we can see the most popular journeys that end up with visitor deciding to give feedback:

If we apply the segment for visitors that gave us 5/5 we can see the journeys that result in happy customers. We can do the inverse with unhappy customers too:

You can also view session recordings from specific feedback. A unique ID will be attached to every feedback item which you will then use in ContentSquare to find a session recording for the specific feedback.

(GDPR/PII): If you push the ContentSquare ID to Usabilla you should make sure that you also mask any sensitive information, such as an email address or a phone number. Without masking PII you would have the potential to find session replays for identified individuals rather than anonymous session replays. Reach out to Usabilla Support if you need guidance on how to mask PII before it’s sent to Usabilla.

Benefits:

Contentsquare’s AI-powered digital experience insights make it fast and seamless for everyone on your team to visualize web and app behaviors so you can improve engagement, conversion, and revenue. While optimizing your customers journey, it’s complicated to create a full overview of what is happening and why. By utilizing Usabilla and Contentsquare you are able to visualize the what and the why of your website that will uncover your customers friction points.

Next steps:

For more information on how the integration can be set up, please have a look at ContentSquare’s integration article that covers the implementation process:

Important: If your website is already using another Usabilla integration that makes use of the event callback window.usabilla_live, then please contact Usabilla Support for information on how to proceed.

Our integration with the project tracking tool, Jira, enables feedback items to be automatically or manually pushed to a specific project. This means you can easily push bugs or feature requests identified by your users to the teams responsible for solving them.

Pushing feedback to your Jira project can also be very helpful for filling your Kanban board and prioritizing stories.

Note: At the moment, this integration can only be set up for Usabilla for Websites and for the Feedback retrieved by your Feedback buttons.

This guide consists of:

Requesting an Atlassian API token

Setting up the Jira integration in Usabilla

How to manually push Feedback from Usabilla to Jira

Integration with Jira on-premise/self-hosted instances

Troubleshooting

An example

What do you need:

- A Usabilla account with an Administrator/Power User role

- An active Usabilla Button

- An Atlassian API token

Requesting an Atlassian API token

Let's start with requesting the API token you'll need to enable this integration:

- Log in to https://id.atlassian.com/manage/api-tokens

- Select "Create API token"

- Enter a name for the token you're about to create that will help you remember what the token will be used for

- Click the "Copy to clipboard" button and store it somewhere safe so we can use it in the next step of the setup

Setting up the Jira integration in Usabilla

Note: Let's start by making sure you're using Jira Cloud, if you are, continue with following these steps. If you're trying to set up the integration for a Jira on-premise instance, click here.

- Open a new browser taband go to http://app.usabilla.com

- Login into Usabilla with your credentials.

- Click on your username in the top-right corner (1.) and click on"Account Settings" in the drop-down (2.): support team

- In the Account Setting,navigate to the Live integrations tab (1.) and select the Jira logo (2.):

- Next, you will be prompted with a window for setting up your Jira integration with the following options:

Button: Select the button you would like to create the Jira integration for.

Push Feedback: Select when you would like Usabilla to push the feedback response. The options are:

- When the feedback response has an email address

- When the feedback response has a comment

- When the feedback response has an email address or comment

- Send all feedback responses

- Manual push

Url: Enter your Jira subdomain (e.g. https://[subdomain].atlassian.net).

- You do not need to include "https://" and ".atlassian.net".

Token Access: Click on our tool to generate a token, after clicking this enter the following credentials:

- Username: Enter your Jira username, in most cases, this will be an email address

- Password: Enter the API token that was requested at the beginnning of this article here.

Issue Type: Enter the preferred issue type (by default it's "Improvement").

- Issue types can be managed in Jira here:https://[subdomain].atlassian.net/secure/admin/ViewIssueTypes.jspa

Project Key: Enter the Jira project key.

- This is the project name found capitalized on the top left, after logging in.

Check "Enable" to activate the Jira integration for the selected button.

- You can always disable it later.

Click save and your Jira integration is ready.

How to manually push Feedback from Usabilla to Jira

When you have selected manual push, you can find the Jira integration on every feedback details page (that belongs to the button you have activated the integration for). Click the "Jira" link like displayed in the image below and a bug will be issued in Jira for this feedback item.All necessary data will be included in the ticket.

Note: Each Feedback item can be pushed to Jira once. Feedback items that were pushed to Jira can be recognized by a green checkmark.

You can always edit your integration later to change the configuration or to disable/enable the integration. Don't hesitate to reach out to our if you run into any questions or issues.

Integration with Jira on-premise/self-hosted instances

If you are usingJira on-premise you will need to provide access to the Usabilla servers in order to make the integration work. In many cases, your JIRA on-premise instance will be cut-off from the internet and will only be available when you are connected to the company network e.g. you can only access it when connected with the company VPN or when you are at the office.

To allow the Usabilla servers to connect to your Jira instance you will need to whitelist the IP addresses of the Usabilla Server. The Usabilla Server uses 3 IP addresses. You'll likely need to contact your network administrator to have these IP addresses whitelisted. Please contact your Usabilla contact person for the exact IP addresses and Ports that need to be whitelisted.

Troubleshooting

When setting up the integration you'll need to watch out for a couple of things. First, you'll need to make sure that you fill out all the fields correctly. In the screenshot below we highlight how each of the fields needs to be filled out. It's important that all the fields are filled out correctly since having the incorrect values can result in either the authentication for the integration being rejected or the push of the feedback being rejected.

Example

Awesome, if all went well you've just set up an integration between your Jira instance and you Usabilla feedback button. To give you a basic idea of how the integration will look like we've added two screenshots below. One show you how the manually pushing of feedback within Usabilla will look like and one screenshot show you how feedback will look in your Jira environment that has been pushed to a Jira business project. The pushing of feedback works for both business- as well as software projects.

Tip: When setting up the integration you have several options for pushing feedback. In order to achieve the right amount of granularity in the pushed feedback, make sure you select a method for pushing feedback to Jira that fits the needs of your organization.

Usabilla for Apps allows youto collect feedback inside your mobile app. Generally, you will learn most from your negative feedback. However, focusing on positive feedback can also be worth your while. Users that leave positive feedback are your brand's or your app's advocates. They are the ones to spread the positive word about your app.

In this article, you will learnhow you can turn your positive feedback-givers into your app's promoters, by asking them to leave a review in your app. Apple now offers a seamless experience to prompting your users for a review. We expect this implementation to show a higher conversion rate.

Before we start, you will need the following:

User on iOS 10.3+ ( over 70\% adoption rate )

Usabilla SDK version 3.6.0+

Access to your company's Usabilla account

Access to the code of your app

How does it work?

Whenever users decide to leave feedback in your app, they will start the feedback process by answering a mood rating question.The mood rating is a 5-point rating scale question that uses images, such as smileys or stars. Most users use the question "How do you like our app?", but you are free to alter this as you like. This question providesan easy way to measure the sentiment of your user at that moment.

When the userleaves feedback, you will have the option to show them an Apple App Store rating prompt. We recommend to only prompt for a review when the submitted feedback is positive (meaning the 4th or5th smiley or star).

friendly support team

How do I use it?

Enabling the review prompt in your app can be done, by opening your form in the editor in your Usabilla account. Navigate to the Usabilla for Apps setup page in your account, find your app and click "edit" to open the editor.

Then click the "Advanced" button at the top-right and flip the "Show rating prompt after feedback submit" toggle switch. Save your settings and you are ready.

When a user leaves positive feedback, you can decide whether or not to prompt the user for a rating. You can read the information regarding the user's activity passed in the Submission callback.

This does not mean that a user will automatically see a review prompt. The SDK will send the relevant data to your app and you can use that to decide whether to prompt for a review. There are a few restrictions to keep in mind when it comes to users seeing the review prompt:

A user can disable the prompts all together in their phone's settings.

A user will not see the prompt more than 3 times in the period of one year.

A user that already rated the current version of your app, will not see the prompt again.

Since weuse Apple's built-in review prompt, users will not have to leave your app at all to review your app in the App Store. The user can choose to only provide a star-rating and additionally, they can also decide to leave a comment. Overall, this provides a very user-friendly way to ask your promoters to rate your app in the App Store.

We expect the new App Store review feature to show better conversion rates as it lowers the barrier for the user to rate your app.

NoteAs, from iOS 11.0 onwards, Apple discourages the usage of custom rating prompts, we strongly recommend you to use the version described in this article.

Any questions? Please feel free to reach out to our .

In Usabilla for Apps, you have the option to include open text fields in your Forms and Campaigns. These open text fields allow your users to give you valuable Feedback. For example, if you'd like to know why your users have selected an unhappy rating or gave a low score, an open text field is a perfect way of asking for context. The open text fields we have in Usabilla for Apps are the 'Text Input' field and the 'Text Area' field. However, since this is an open text field, users are not restricted from typing in personal data in these fields. When the information left by the user could be used to identify a particular person, this is classified as Personal Identifiable Information (PII), this can be their full name, bank account number, etc. To make sure this information is not sent to Usabilla, we have a way of masking the PII that is left in the 'Text Input' and 'Text Area' fields. In this article, I'll explain how this feature works and where to find this awesome feature.

This article consists of 3 parts:

The Regular Expressions to find the PII

The character that is used to mask the PII

Where to find the full code

What do you need

- A form or Campaign with an open text field, a 'Text Input' and/or a 'Text Area' element

- A Mobile Developer who can help you implement the code in your App

- Usabilla SDK 6.2.0 and above

The Regular Expression (RegEx)

In order to find the Personal Identifiable Information in the open text fields, a set of RegExes needs to be included. This RegEx will go through the open text fields in the Forms and Campaigns and when it finds a match, the matched content will be masked. By default, the Usabilla SDK provides you with RegExes for email addresses and numbers with 4 digits and more. However, you have the option to include your own RegEx as well. So let's say you would like to mask Dutch zipcodes which consist out of 4 numbers and two letters, a RegEx can be created for this and included in the SDK. It's also possible to include multiple RegExes, for example, besides the default RegEx we provide also have a separate RegEx for the Dutch zipcodes.

RegEx: A regular expression (in short RegEx) is a sequence of characters that define a search pattern. This pattern is used to find specific keywords, numbers or other characters in an input field.

In the code we have created for the masking feature, the RegEx part can be identified as:

iOS: Usabilla.setDataMasking(masks: [String]), maskCharacter: Character)

Android: Usabilla.setDataMasking(List<String> masks, char maskCharacter);

The character

When the RegEx has found a match, the matched content will be masked. But, what will it be masked with? It will be masked with a character you can define yourself. By default, the matched content will be masked with 'X's. However, if you'd like to mask the matched content with '#'s, '*'s or any other character, you are free to do so. Just make sure this character is specified in the SDK.

In the code we have created for the masking feature, the character that has to be used to mask the matched content can be identified as:

iOS: Usabilla.setDataMasking(masks: [String]), maskCharacter: Character)

Android: Usabilla.setDataMasking(List<String> masks, char maskCharacter);

Github

To help you start using this great feature, we have included the full code that's needed for this on our Github pages:

iOS

Android

Please share these with your Mobile Developers so they can start the fun immediately.

That's it!

Success: With this feature implemented, the Usabilla for Apps Feedback collected in your Usabilla account will not contain any Personal Identifiable Information!

At Usabilla we believe that our solution must be available to as many users as possible. If you have a native App (iOS or Android), our native SDK's (iOS & Android) are the ones you're looking for. However, what if your App is written using a different framework? Can you still use Usabilla for Apps? Yes, you can! This article will help you get a general understanding on the solutions that we have created for supporting the most common app development frameworks. We'll be going over why it's necessary in some cases and how it can help you use Usabilla in your own App.

Tip: Click here to go straight to the list of supported app development frameworks.

Let's start with the basics. Nearly all mobile Apps are built to run on two platforms; iOS and Android. Both platforms have their own programming language of preference. iOS apps are written in Swift and Android Apps are written in Java/Kotlin. Whenever Apps are written in these native languages we call them native Apps. The two Usabilla for Apps Software Development Kits (SDK's) are also written in native languages.

But as always, there are more options. Besides using native languages, Apps can also be written using frameworks such as React Native. The main difference between native apps and for example a React Native App is that React Native Apps are written using JavaScript. A great argument for creating an App using different framework is having two native apps in the development time of one!

So what now, our SDKs are written in Swift and Java (native languages) but the app is written using a framework like React Native. Have no fear, our translators are here. Well...our bridges are here! These bridges will make sure that the functionalities from our SDK can be called and used by your App using the language of the framework that has been used to create your App.

App development frameworks

Below you'll find a list of our current bridges including the links to the resources to get you started.

React Native bridge:

- npm module

- Github page

Cordova bridge:

- npmmodule

- Github page

Xamarin bridge:

- NuGet package

- Github page

Is the bridge you're looking for not in the list above? Feel free to contact your Custom Success Manager and share the bridge you're looking for or the framework your App has been build with.

Bridges built! Let our bridges help you bridge the gap between you and the feedback-less Apps!

Visitors may become annoyed and irritated if they are continually seeing your campaigns popping up all over your website, especially when they have already completed the campaign. This is why we have the option to only show a campaign once.

The "Do not bother more than once" optionensures that a specific campaign will only be shown to the visitor one time. This is regardless of how many pages the campaign has been attached to.

Setting up the "Do not bother visitors more than once" option

You can enable the "Do not bother visitors more than once" option by editing your campaign and changing the "Scheduling". Below you will find a step by step guide for enabling the "Do not both more than once" option:

Go to http://app.usabilla.com

Login into Usabilla with your Usabilla Account.

In the left side menu click on "Setup" which can be found under "Campaigns".

Find and click on the campaign for which you want to enable the option.

The campaign info fold out, click on "Edit" which will take you to the Campaign Editor.

In the CampaignEditor navigate to the third "Scheduling" step.

To do so click on"Next".

In the "Scheduling" step go to the last option.

Tick the checkbox saying "Do no bother visitors more than once".

Hit the green "Save" button in the top-right corner to save your changes.

Your campaign will now only show once to your visitors. The “Do not bother visitors more than once” feature uses a local storage object to see if a visitorshould not be bothered. If the visitor of your pagedoes not allow for local storage objects, moves to a different device or when the earlier created local storage object is deleted the visitorwill be botheredlong as thevisitor matches the visitor targeting of your campaign. Disabling cookies in your browser can in somecases block the creation of a local storage object.

Campaign surveys in Usabilla for Apps are event-based. This means that a campaign is triggered when an event is fired. In order to provide you with a basic understanding of events, we will answer the following questions in this article:

What is an event?

Why use event-based targeting?

How are events created?

How can I connect my campaign to an event?

Can you give any examples?

Note: While this article intends to provide a non-technical overview, the actual implementation of events will require technical knowledge. Most likely, you will need a programmer to help you out.

What is an event?

An event signifies that an action occurred in your app. This action can be anything, from making a purchase to opening or closing the app menu. The event can be initiated by the user (e.g. clicking a button) or by the app (e.g. the user's flight has just arrived).

The events that are available for targeting are defined by the app in question. Once you identified the moment(s) in which you'd like to survey your users, it's best to speak to your technical team to see which events allow you to target on this specific moment.

Why use event-based targeting?

Since events are defined by the app itself, event-based targeting allows for ultimate flexibility. It allows you to target on any action occurring in the app. This means that Usabilla for Apps surveys are very customizable and can be shown to the user at exactly the right time. This benefits the user experience and has a positive effect on your campaign's conversion rate.

How are events created?

To help you in the process of defining what events could be interesting for your Campaigns, we've split this process up into four steps. The goal of these four steps is to help you create events and Campaigns that are relevant to you, help you get a clear overview of where you could trigger a Campaign and alignment between you and the developers who will be creating the events.

Example: To clarify each of these steps, let's set up a test scenario we can apply each of these steps to: "A new version of my app has been released with a new feature and I would like to retrieve Feedback from the users who have been using it to see if and how we can improve this functionality. The new functionality lets users display locations of candy stores in their vicinity."

What are you trying to achieve with your Campaign?

Before thinking of any event, let's start with the goal you have in mind for your Campaign. Do you want to set up a Campaign to measure the KPIs that are set or do you want to notify users about a new feature in your app? By having a clear goal, you'll also be able to think about what type of Campaign to use and what type of question elements to use. For example, is a notification Campaign the best option or do you need to set up a Campaign of 4/5 pages?

Example: Let's go back to the example scenario and apply this step to see what the outcome would be. The goal of my Campaign is: "Ask the users that have used the new feature how they would rate the feature on a scale from 1 to 5. When they respond to this question with a rating from 1 to 3, it will be followed up with a comment element where users can provide additional comments on how the feature can be improved. Since I would like to know how we can improve this feature, I would like to target users who have used the feature more than 5 times."

Where should the Campaign be displayed?

Once you have your goal clear and you have an idea what you want to ask in your Campaign, it's time to think about where the Campaign should be triggered. A great point to start is mapping out the Customer journeys in your app. By having a clear overview of the different routes users can take to achieve their goal, you'll know exactly what the sweet spot is for your Campaign.

Example: So, what would be the best moment to display our test scenario Campaign? "The Campaign should be displayed after the user has used the feature successfully. This means, trigger the new functionality and either let the App use their location or manually enter their location. Once the App has their location, it will display all of the stores sorted from near to far. Once this list is shown, the Campaign should trigger."

What are the events for me?

Once you have a clear picture of what you would like to achieve with your Campaigns and what the best place is to display your Campaign, the next step is combining these two things with the Events you would like to use. To help you define the Events, these questions can help:

What action should trigger the Event?

Is it something the user does or is it something that the app does?

What name describes the Event best?

Example: Finally, let's apply this step for our test scenario as well:

What action should trigger the Event?

The Event should be triggered when the list of stores near the user is shown.

Is it something the user does or is it something that the app does?

This event should be fired by the app as a result of the user giving their location.

What name describes the Event best?

The name of the Event is "LocationShown".

To keep everything in a clear overview, we advise creating an Event Library with the result of each of the previous steps. This document can be the reference point for everyone in your team that will be creating Campaigns in Usabilla for Apps. A completed Event Library contains at least 3 columns with the following information:

What is the Goal of the Campaign?

Where in the App should the Campaign be displayed?

What Event should trigger the Campaign and when is it triggered?

Example: I've also created an Event Library for the steps and answers we just gave in our test scenario Campaign. To give you an idea what this can look like, I've added a screenshot: these guidelines

Connect with development

Last but certainly not least, creating the events. In most cases, this will be done by the developers. Before handing the baton over to the devs, we recommend sitting down together and share the outcome of the previous three steps by sharing the Event Library. You can see this as a moment of calibration where you can share your thoughts and vision you have and where the devs can react on them. Since there is a chance your app is already using events from a different SDK than Usabilla, there is a chance that certain events are already defined. This calibration session is the perfect opportunity to find things like these and make sure everyone is on the same page.

Apart from finding Events that have been created already, it can also help in estimating how long it will take to implement the Events and when you can start using these Events in your Campaigns. Whenever there's doubt about when or what should trigger an Event, refer to the Event Library for context.

How can I connect my campaign to an event?

After your developers have implemented the event, you can simply enter your Usabilla account and create a new in-app survey. Create the survey as you normally would and then specify the event in campaign targeting. You can show a campaign to your users as soon as an event is fired, or only after an event has been fired a number of times.

Make sure that the targeted event is identical to the event that your developer specified in your app. Events are case sensitive.

After specifying the event in your campaign targeting, it's time to activate and test your campaign. As soon as the Usabilla SDK has been implemented in your app and your events have been added, you can activate and deactivate new campaigns without making any code changes. It's important to note that your campaign will be live as soon as it's activated.

Since the event is the immediate trigger for your campaign, a campaign cannot be shown without specifying the trigger event.

Event examples

When using event-based targeting, the possibilities are endless. Events are highly customizable and closely follow the behavior of your users in your app. Some examples of possible events are:

Learning more about your users

When the user opens the app

When the user performs a number of searches in your app

When your user leave a certain flow (for instance, when they move from the booking page back to another section of the app)

When clicking a button

Measuring specific metrics

After opening the app a number of times

After taking an offline event such as taking a flight or receiving an order has occurred.

After completing an action in the app

After using the search functionality in your app

Now that you are familiar with the concept of an event it's time to get started. Follow to create your first campaigns.

Slide-out survey campaigns allow you to easily and subtly survey visitors via a small slide-out on your web page. Slide-out surveys are intuitive, with the ability to respond to a visitor'sanswers byshowing or hiding further questions, information, or slide-out pages.

Create a Slide-out Campaign

In the CampaignsOverview page choose 'New campaign'.

After clicking 'New campaign' you will be prompted to select a campaign type. To create a slide-out survey select 'Slide-out survey'. This will open the Slide-out survey creator.

Form Pages

Initially, you will be prompted with a dialog to define the title of your campaign. You can also changethe titleby clicking on the 'New Slide-out Survey Campaign' title.

In the initial dialog, you'll also be able to change the language and apply templates. Default templates are templates that Usabilla provides. Whereas Custom templates are templates which are maintained by you as an Usabilla user.

After confirming your title you can start building your Slide-out Campaign. The building of the slide-out campaign consists out of 4 steps:

Widget

Form pages

Visitor targeting

Scheduling

1. Widget

In the first step, you will be asked toassign your new campaign to a feedback button. In this step, you can select one or multiple buttons to which the campaign will become associated. This means that the campaign will appear on any page that the chosen button(s)appearson (even if your button is invisible) unless visitor targeting states otherwise.

To select the feedback buttons for association simply tick the checkboxes for the corresponding feedback buttons and click on 'next' to continue to step 2.

Note: Your campaign will only show on a pageif you have a button (& its relevant code)on that web page.

Form pages

In the form pages section, you will be able to set up the content of the slide-out survey. The form pages section consists out of multiple sub-sections which allow you to customize the survey to your liking.

The top panel shows how many pages you have active within your campaign, and it is here that you can add further pages. There are two types of pages: a form pageand an ending page. You can read more on Page types, and how they workin Page Types.

Form Editor and Canvas

The Form Editor and canvas are the mainobjects of the Form pages section. It is here where you build your Slide-out campaign. On the left, you'll see the Form Editor which allows you to add form elements. To do so simply click on the preferred element within the Form Editor you would like to add. After clicking, the element will be added to your canvas on the right. Within the canvas, you can drag-and-drop the element to change the order of the element using the drag-handle on the right.

To edit the element simply click the element itself or mouseoverthe element and click on the options cogwheel.

This will open the appropriate EditDialogfor each element. You can delete elements by clicking the bin icon which also appears on mouseover.

The Edit Dialog will differ from element to element but generally allowsyou tochangethe name of the element's title, and any other text on that element. For some, it is possible to edit the scale(eg. Rating) or orientation (eg. Radio Buttons).

At the endof the Edit Dialog, you can set visibility criteria for the element. You can for example, only show a text input when the user selects a specific answer from a previous question.More information on this can be found in How to Control Visibility.

In addition to the visibility criteria, you also have the option to make asurvey even more responsivebased on a visitor's inputs by adding rules forpage jumps. BycombiningVisibility Options and Page Jumpsyou can create responsive surveys for your visitors.

Note:To preserve the structure of the Usabilla for Website Campaign form, after saving the campaign form, you will no longer be able to change the name of a question or the value of an answer of the elements in you campaign.

We have created notifications in the campaign form to help you with the new settings. When you create a Usabilla for Website Campaign form, before saving your Campaign form for the first time, you’ll be asked to confirm that you’re done creating your form. We’ve put this extra step in place to confirm that you’re satisfied with campaign structure at that time and that you’re aware of the limited editing options in the future.

When you edit a Usabilla for Websites Campaign form that was already saved, the changes you can make to this form and question(s) will be limited to help preserve the integrity of the form structure and the data that is collected.

Previewing your Campaign

You can preview your campaign by hitting the 'Open Preview' button. This provides you with a previewof how your campaign will appear to your visitors. With the preview you can test any visibility options, the page jumps, andensure the campaign is placed in a convenient location. Depending on the elements you're using within your campaign you will need to change the size and position of your Slide-out campaign. To do so go to the Advanced Settings.

Advanced Settings

The Advanced Settings dialog can be opened by clicking on the 'Advanced' button left of the 'Open preview' button. Within the Advanced Settings dialog, you will be able to change several settings like theme and position. For the Position settings you can set the position (where the slide-out appears), the offset percentage (where the Slide-out will appear on the axis), and the width in pixels (how with the slide-out will be).

In the Advanced Settings dialog, you will also have the option to add one of yourCustom Themesto your campaign. Read more aboutTheminghere.

Visitor Targeting

In the third step of building your Slide-out campaign, you can set the visitor targeting. The visitor targeting allows you set which visitors of your website will see the Slide-out campaign. By default, the targeting will be set to show the campaign to all visitors of your page. Then you change the targeting to 'Show your survey to certain visitors.' you'll see all the options for the targeting.

You can find more information aboutVisitorTargetingin thetargeting section. Once you have set your visitor targeting, click on 'Next'to continue with scheduling.

Scheduling

Scheduling allows you to change a variety of setting for activating, deactivating and resetting your campaign.You can read more aboutscheduling your campaigns here.

Once all options have been set to your liking, click 'Save'your campaign and begin surveying your visitors!

Full Page Surveysallow you to survey visitors either via a screen overlayon your web page or with a full page survey via a custom URL. Less subtle than a slide out, they are more likely to invoke a reaction.Full Page surveys can be intuitive, with the ability to respond to a visitor'sanswers byshowing or hiding further questions, information, orpages.

Create a Full Survey Campaign

On the Campaigns Overview page choose 'New Campaign'.

scheduling your campaigns here

After clicking 'New Campaign' you will be prompted to select a campaign type. To create a FullSurvey select 'Full Survey'. This will open the FullSurvey creator.

Form Pages

Initially, you will be prompted to add a name to your campaign and optionally add a language or template.

In the initial dialog, you'll also be able to change the language and apply templates. Default templates are templates that Usabilla provides. Whereas Custom templates are templates which are maintained by you as an Usabilla user.

You can always change the name of your surveyby clicking on the 'New Survey Campaign' title. After the firstdialogue, you will startbuilding your Full Survey.

Widget

In the first step, you will be asked toassign your new campaign to a feedback button. In this step, you can select one or multiple buttons to which the campaign will become associated. This means that the campaign will appear on any page that the chosen button(s)appearson (even if your button is invisible) unless visitor targeting states otherwise.

To select the feedback buttons for association simply tick the checkboxes for the corresponding feedback buttons and click on 'next' to continue to step 2.

Note: Your campaign will only show on a pageif you have a button (and its relevant code)on that web page.

Form Editor and Canvas

The Form Editor and canvas are the mainobjects of the Form pages section. It is here where you build your Full-Screen campaign. On the left, you'll see the Form Editor which allows you to add form elements. To do so simply click on the preferred element within the Form Editor you would like to add. After clicking, the element will be added to your canvas on the right. Within the canvas, you can drag-and-drop the element to change the order of the element using the drag-handle on the right.

To edit the element simply click the element itself or mouseoverthe element and click on the cogwheels.

Note:To preserve the structure of the Usabilla for Website Campaign form, after saving the campaign form, you will no longer be able to change the name of a question or the value of an answer of the elements in you campaign.

We have created notifications in the campaign form to help you with the new settings. When you create a Usabilla for Website Campaign form, before saving your Campaign form for the first time, you’ll be asked to confirm that you’re done creating your form. We’ve put this extra step in place to confirm that you’re satisfied with campaign structure at that time and that you’re aware of the limited editing options in the future.

When you edit a Usabilla for Websites Campaign form that was already saved, the changes you can make to this form and question(s) will be limited to help preserve the integrity of the form structure and the data that is collected.

Form pages

In the form pages section, you will be able to set up the content of the slide-out survey. The form pages section consists out of multiple sub-sections which allow you to customize the survey to your liking.

The top panel shows how many pages you have active within your campaign, and it is here that you can add further pages. There are two types of pages: a form pageand an ending page. You can read more on Page types, and how they workin Page Types.

This will open the appropriate EditDialogfor each element. You can delete elements by clicking the bin icon which also appears on mouseover.

The Edit Dialog will differ from element to element but generally allowsyou tochangethe name of the element's title, and any other text on that element. For some, it is possible to edit the scale(eg. Rating) or orientation (eg. Radio Buttons).

At the endof the Edit Dialog, you can set visibility criteria for the element. You can for example, only show a text input when the user selects a specific answer from a previous question.More information on this can be found in How to Control Visibility.

In addition to the visibility criteria, you also have the option to make asurvey even more responsivebased on a visitor's inputs by adding rules forpage jumps. Bycombining Visibility Options and Page Jumps you can create responsive surveys for your visitors.

Previewing your Campaign

You can preview your campaign by hitting the 'Open Preview' button. This provides you with a previewof how your campaign will appear to your visitors. With the preview you can test any visibility options, the page jumps, andensure the campaign meets your needs and those of your users. This is also a great way to see how your campaign will look with a certain theme.

Advanced Settings

The Advanced Settings dialog can be opened by clicking on the 'Advanced' button left of the 'Open preview' button. Within the Advanced Settings dialog, you will be able to change several settings like them, privacy policy, and the showing of a progress bar. When you're creating a full survey campaign you'll also see that there is the option to 'Use website as a background'. When you check this box you'll be able to provide a URL that will be used to set a background website when people access you Fully Survey Campaign using a manual link.

Custom Themes

On this screen, you also have the option to add one of yourCustom Themesto your campaign. Read more aboutTheming here.

Visitor Targeting

In the visitor targeting section, you will be able to select the targeting criteria, but also the type of Full Survey you want to use. There are two types of Full Surveys:

An in-page full survey which overlays your site content,

or a full page survey with its own URL, reachable only through that URL.

These two Full Survey types have their own pros and cons:

In-page Full Survey: Will prevent the user from being able to interact with the content, until the user dismisses the survey or completes it;Can be set to appear automatically.

Manual Link Full Survey: Can only be reached by going to the Survey's URL; Doesn't interfere with any other content (other than opening a new tab, or replacing an URL entirely); Can have custom variables passed to it via the URL (Read more about these in Custom Variables ).

If you opt for the in-page Full Survey, you can further manage which visitors will see your survey.Read more aboutVisitorTargetingin the targeting section.

If you opt-in for the Manual link instead option you'll won't have the option to set any targeting options. The reason for this is that the targeting in that case solely lies in the sharing of the link to the campaign. As soon as you've saved a Full Survey Campaign with a manual link you'll see the manual link show up after saving the campaign.

After you're done setting theUser targeting you can move to the next step by clicking onNext again.

Step 3 - Scheduling

Finally, you have to set your campaignScheduling.You can read more about.

Once all options have been set to your liking, click 'Save'your campaign and begin surveying your visitors!

When creating a Usabilla Campaign survey, you will want to keep a few things in mind, to make your campaign analysis as easy as possible. One of the ways in which you can do this is by using descriptive and clear values in your campaign. In this article we will clarify what the Campaign values are and how they work.

What are Campaign values?

If you add a closed question to your Campaign, you will have to both define the answer options from which your respondent can choose as well as a value. They help you to:

create a better overview of your Campaign results as they are shorter and more descriptive than your actual campaign responses.

aggregate data from the same Campaigns in multiple languages.

Campaign values are not visible to your participant, but they are shown to you in the Results section of your campaign.

In your Campaign, you will find two types of values. The first represents the actual question itself and it's called the "name" of a campaign. Then there are also values for each answer option in closed questions. These values will represent the longer answer options when analyzing your Campaign results.

Note:For some question types it's not possible to set the name of this question as they will always have default names. These are the NPS-element and the Mood-rating element. Their names are "NPS" and "mood".

Can Campaign values be changed?

To preserve the structure of the Usabilla for Website Campaign form, after saving the campaign form, you will no longer be able to change the name of a question or the value of an answer.

We have created notifications in the campaign form to help you with the new settings.

When you create a Usabilla for Website Campaign form, before saving your Campaign form for the first time, you’ll be asked to confirm that you’re done creating your form. We’ve put this extra step in place to confirm that you’re satisfied with campaign structure at that time and that you’re aware of the limited editing options in the future.

When you edit a Usabilla for Websites Campaign form that was already saved, the changes you can make to this form and question(s) will be limited to help preserve the integrity of the form structure and the data that is collected.

Where are the Campaign values used?

The Campaign values are used in all Campaign results export files of Usabilla for Websites and Usabilla for Apps Campaigns. This allows you to export results from the same campaign in different languages and combine the results in one file.

Furthermore, the Campaign values are used in the filter section of your campaign results. For instance, if you want to filter your campaign results according to a response given to a question, you will be able to locate this question through the value.

The Usabilla for Apps dashboard allows you to quickly gain a high-level overview of the feedback coming in through your application. In this article, we explain which information is available in the Usabilla for Apps dashboard and how you can use it.

1. Filter options

At the top-right of the dashboard, you will find filter options that allow you to segment your feedback according to:

date by default the dashboard shows the last 30 days.

feedback form the feedback form in Usabilla through which the user provided feedback

platform Android or iOS

app the app (version) in which the feedback was given

2. General graphs

Next three general graphs will provide you with a quick overview of how your app is performing. These graphs represent the emotional score your user submitted, the feedback item frequency and if you are collecting an NPS, also the NPS.

3. Emotional trendline

The Emotional Trendline provides a timeline of the average mood rating. Hover over the individual data points, to see a breakdown per day.

4. Feedback items

The feedback items graph shows you the number of incoming items per day, over the date range you specified. Hover over the individual days to see the number of feedback items that have been left on a specific day. If your selected date range exceeds 30 days, the graph will provide you with a weekly amount of feedback items, rather than a daily amount.

5. Net Promoter Score

If at least one of your forms contain a Net Promoter Score(NPS) question you will see twoNPS chartsin your dashboard.These charts consist of a timeline and a breakdown of the current NPS score per rating point. When measuring the NPS score in your Usabilla for Apps feedback form, it's important to note that feedback through this form is only given when the user often has a (negative) incentive to do so. Therefore we advise you to be careful when comparing the Usabilla NPS to a score measured through other sources.

6. Technical Meta Data

In the next chart, we show charts for the following technical metadata. This information is collected whenever a user submits feedback through the Usabilla feedback form in your app. You will find the average mood score for each of the available specifications as well as the number of items that have been left. This breakdown tells you a lot about the happiness of your users across different devices, operating systems, and apps.

app version This is specified by your developers in the implementation of Usabilla for Apps

os version

device

manufacturer

7. Device Language

The device language is the language set up in the device specifications. In this chart, we also break down the number of items in a certain language as well as the average mood score.

8. Label

Labels are added on the feedback management page by you and they can be used to group yourfeedback, define the status of a feedback item or assign the feedback item to a specific team member. The dashboard chart shows you which labels have been applied most often and what their average mood score is.

9. Geographical engagement

The geographical engagement tile tellsyou where your users left feedback. The location is based on the user's IP address and segmented per country. If your users left feedback in the United States, you will also be able to see the feedback per state.

The Usabilla for Apps feedback form can be createdin the Usabilla interface. Thecustomizable elements are the questions,colors, the App Store redirect and wordings of the various buttons and elements in your website. In this article, we will create a new Usabilla for Apps feedback form from scratch, taking you through all options.

We'll start on the Usabilla for Apps setup page to create our new feedback form. Click "New Form" on the top-right to open the form editor. We will first change the name and settings of your form.

At the top-left of your form, you will find the text "New untitled app" the current name of your form. Click the name to change your form name. An overlay will appear in which you can edit your form's name.

here

1. Formsettings

After changing the name of the form, it's time to dive into the advanced settings.Click the "Advanced" button at the top-right of the editor to open the following modal window. We can break the advanced settings down to three topics; general settings, text settings, and color settings.

General settings

Here, you will find four switches that allow you to change the following settings:

Screenshot Activate the possibility to add a screenshot to the form.

Progress bar Add a progress bar at the top of the page.

Store IP address Store the IP address of each user leaving feedback and add it to each feedback item

App Store re-direct Direct users that select one of the two most positive mood rating elements.

Email notifications By selecting the email notifications, every feedback item will be emailed to an email address as specified by you. Please do note that the provided email address must have an account in Usabilla.

If the toggle switches are deactivated for screenshots orthe App Store redirect, the setting specified in the app itself will be overwritten. Iffor instance, you deactivate the toggle switch, but your app implementation specifies that a screenshot should be included, the feedback will not contain a screenshot.

Text settings

The second step in your advanced settings is editing the text of the standard non-question elements in your form. The customizable elements are:

Form title

Screenshot title

Error message

Next button

Cancel button

Submit button

Colorsettings

In the last section of the advanced settings, you will be able to specify the colors ofyour feedback form. A detailed explanation of the different elements that can be styled, can be found here.

Page settings

Apart from the advanced settings, you can also add extra pages to your feedback form. Extra pages can be added by clicking the "Add page" icon at the top of the page. When adding a new page to your form, you will be able to select either a form page or an end page. A form page is a page that can contain actual questions, while an end page contains only a thank you note (or image). Furthermore, you can also copy questions from another page, which might be useful if you are working with repeated questions.

2.Creating your questions

Your feedback form will always start with a mood rating. This mood rating consists of stars, smileys or images as specified on your end. When opening the form editor, the mood rating will already be present. Click the mood rating questionto edit the text and indicate whether your form is using smileys or stars. As explained, your developer will be able tochange the images for the smileys in the app itself.

In this screen, you will also be able to change the default 5-point rating scale for a 2- or 3-point scale.

After editing the mood rating you will be able to add other question elements into your form. Simply click one of the elements on the left side of the screen to insert them into your form.

We recommend you to always insert at least an open comment field. It's good to keep in mind that your users are always the ones to take the incentive to leave feedback. By including the comment field, you allow them to share what they want to share.When editing the open comment field, you will notice two options that allow you to pre-fill the comment, to provide an example to the user. When inserting text into the "default" option, your example text will be regarded as actual content of the comment field. When using the placeholder instead, your text will be slightly greyed out and disappear the moment the user clicks the input field.

3. Control visibility and page jumps

When editing your comment question, you will notice a "control visibility" section for each question. This section allows you to show or hide certain questions depending on the answers that have been given to preceding closed questions.This allows you to adjust your question according to the mood rating score a user provides or for instance the NPS.

In order to use "control visibility" simply select the question on which the question you are editing is dependent, then select the answer options according to which you would like to show or hide. Then select whether the question should be hidden or shown according to the answer given.

Apart from the control visibility, you can also direct users to different pages in your feedback form depending on the answers they provide. In order to set this up, you can hover over the page of thefeedback form that you are currently working on. A little settings icon will appear and upon clicking this icon the page management modal window will open. Then click "add rule" at the right side of the screen and set the page jumps up in the same way as the control visibility.

After setting up your visibility controls, youare all good to go. Save your form through the "save" button at the top right and head over to the installation page, to preview your form.

Usabilla for Email is an excellent way of gathering Feedback on emails that are sent out. Whether it is to get insights into how well the last Newsletter scored or to get insights into how your Support team is doing. However, sometimes a little bit more context is very welcome. For example, which edition of the Newsletter did the Feedback come in for? Or, which client left Feedback for a particular Support agent? These questions can be answered by adding Custom Variables to your Usabilla for Email widget. In this article, I'll be informing you a little bit more about the different types of Custom Variables that can be used and how to set these up.

This guide consists of:

What are Custom Variables?

Static Custom Variables

Dynamic Custom Variables

The Setup

The Result

What do you need:

- A Usabilla account with access to Usabilla for Email

- Basic HTML knowledge

- A Text Editor (Atom, Visual Studio Code, etc.)

What are Custom Variables?

Custom Variables are essentially data points that can be used to gather additional information that can be added to a Feedback item. In general, these data points can give more context about the Feedback item, for example, the user who left Feedback, the tier the user is in, etc. Custom Variables consists of two elements, the name of the Custom Variable and the value of the Custom Variable. If we take the example of the tier, the name would be 'Tier' and the value would be the actual tier the user is in gold, silver, etc. Custom Variables come in two flavors, static and dynamic.

Note: To use Custom Variables in Usabilla for Email, the email client you're using has to support the implementation of HTML in your email template (footer, signature, etc.).

Static Custom Variables

The static variant of Custom Variables are the Variables where both the name and value are predefined. Let's take the tier as an example again, let's say you're sending out a newsletter to users in the 'Silver' tier. The name of your Custom Variable would be 'Tier' and the value would be 'Silver'

Dynamic Custom Variables

The dynamic variant of Custom Variables only has the name predefined. The value of the Custom Variable is not predefined, instead, a placeholder is configured that can be read by the email client you're using. By doing this, the value of the Custom Variable will be whatever information is supplied through the placeholder. For example, a newsletter is sent to all of your users which are in different tiers. When users from the 'Gold' tier give feedback, the value of the Custom Variable will be 'Gold' but when users from the 'Silver' tier give feedback, the value of the Custom Variable will be 'Silver'.

Note: In order to use dynamic Custom Variables, the email client you're using has to allow the use of variables as placeholders. To verify whether your email client allows this, contact your supplier who can provide you with this information.

Setup

Now that we know all there is to know about Custom Variables in Usabilla for Email, let's set them up. Whether you're about to set up static Custom Variables or dynamic Custom Variables, for the most part, the setup is the same.

Let's start by copying the HTML of our widget. Navigate to the 'Setup' page (1.) in the Usabilla for Email environment and select 'Widget installation instructions' (2.) of the widget you want to add Custom Variables to:

[email protected]

After clicking 'Widget installation instructions' you will be presented with 3 ways of installing the widget. Adding Custom Variables can only be done by editing the HTML of the widget, so we're going for option number 2. Simply click 'Select' and copy the selected HTML:

Once you've copied the HTML, open a Text/Source code Editor of your choice and past the HTML there. At first, the HTML will probably look like this:

To clean it up a bit, save the widget as a .html file and run a Format or Beautify command, which will result in something like this:

Right now, you might have a better clue of how our widgets are set up, it consists out of hyperlinks (<a href> tags) and images (<img> tags). The Custom Variables will be added to all of the links in your widget, in the case of my example, I have 6 of them:

Adding Custom Variables to your widget can be done by adding the following line to each of the links in your widget:

&<Variable Name>=<Value>

In the case of static Custom Variables, you're predefining both the name and the value of the Custom Variable. So if I would like to add the Silver tier as a static Custom Variable, the addition to the links in my widget would look like this:

&Tier=Silver

Tier, name of the Variable, defined by me.

Silver, value of the Variable defined by me.

However, if you'd like to go for dynamic Custom Variables, we would have to define the placeholder instead of the actual value. In Usabilla Support we use Frontapp as our email client. Frontapp identifies placeholder like this: {{Data}}. The placeholder for the recipient of my email is defined as {{recipient.email}}. If I would like to add the recipient of my email as dynamic Custom Variable to my widget, the HTML I would have to add to my widget would look like this:

&Recipient={{recipient.email}}

Recipient, name of the Variable, defined by me.

{{recipient.email}}, value of the Variable, will be replaced by the actual recipient of my email because the email client recognizes it.

The Result

Once you've successfully been able to add Custom Variables to your widget and you're starting to receive Feedback, the Custom Variables can be found by opening a Feedback item:

Success: I hope I was able to help you get a better understanding of Custom Variables in Usabilla for Email and help you set them up as well. Feel free to browse around and if you have any questions for us, reach out to .

Usabilla for Websites feedback can be supplemented with information you already acquired about your user or your website. This information can be passed on to Usabilla through Custom Variables so that it will be included in feedback itemsand campaign results.

Please follow these steps to include Custom Variablesin your feedback items and campaign results.

1. Define the data you would like to pass on to Usabilla.

Examples of Custom Variables are user names, session IDs, A/B-testing variablesfrom other tools, demographic data and membership statuses.

2. Include the variables withaJavaScript API call.

The following JavaScript API call can be included on every page on which you would like to include Custom Variables. Please ensure the call is installed on every page below the Usabilla code.

<script type="text/javascript">

window.usabilla_live("data", {"custom": {

"Username": username, "SessionID": session_id

}

});

</script>

In this example, "Username" and "SessionID" are the custom variables names that will appear in Usabilla, while the values indicate a reference to the variable.

If your website is JavaScript heavyit should be noted that the API call can be used multipletimes, any call replacing the data of the previous call. So thelast call’sdata will be used when thefeedback process is started.

Append and update Custom Variables

You can make the Custom Variables for Usabilla for Websites easily updateable by using a JavaScript Object for storing the Custom Variables. If you update the object and resend the Custom Variables using the JavaScript object you can easily keep custom variables up-to-date or even append values. Below you'll find an example of how you could achieve this:

Allowed values for Custom Variables

When you use our JavaScript API call for sending Custom Variables to usabilla you can pass onthe following 2 objects:

email: The user’s email address, if your button asks the user for his email address the field will be pre-filled with the data you set here, otherwise, the email address will be sent as is.

custom: A JavaScript object containing custom data. The below data typesare permittedin custom variables.

Boolean

Integer

Float

Double

String A string can include up to 500 characters.

Array

NULL

Object

Arrays and objectscan have a maximum depth of 2 and must consist of uniform values (only strings, only integers etc.).

Tip: We highly recommend that you don't use any object and or arrays. Using only uniform values allows to easily compare and export the feedback and campaign results that you gathered.

3. Success!

The Custom Variables will now be included inevery feedback item and campaign result. Also, you will be able to target campaigns to users that have certain Custom Variables.

You can create a new campaign by heading to the campaigns section of your Usabilla account. Navigate to Websites > Campaigns > Overview orfollow this link.

In the upper right hand corner you can click the blue "New Campaign" button to get started. Select the campaign type that you would like to use.

friendly support team

( Click here for an explanation of campaign types)

From here, select the campaign you would like to create. You will then be directed to the Campaign Editor where your campaign can be customized to your needs.

Any questions? Please reach out to our .

This glossary contains a list of terms and definitions you may come across as you interact with various Usabilla products.

Active Feedback

Active feedback concerns campaigns, that can be setup to target specific visitors on specific actions in order to collect feedback on certain topics.

Benchmark

A standard or average against which things can be compared

Boost Live Feedback Survey

Draw User’s attention to submit feedback via the feedback button with a small slide out survey asking to leave passive feedback about the website.

Campaign

Campaigns are surveys that collect “active feedback” by targeting a specific audience through certain behaviors, events, or specific pages.

Campaign Schedule

Definewhenyour campaign will be shown.

CES (Customer Effort Score)

Metric that measures customer satisfaction with the idea of creating loyal customers by reducing customer effort. An example could be,"How much do you agree with the following statement on a 1-5 scale?: The company made it easy for me to handle my issue.”

Conditional Forms

These forms contain questions that dynamically change based on the subject of the feedback. The Feedback Button’s default form has a drop down for User’s to select the subject, such as bug, compliment, or suggestion.

Control Visibility

You can control the visibility of certain elements based on answers to the previous questions. (If answer is X, show element Y.)

CSAT (Customer Satisfaction Score)

CSAT measures how products and services provided by a company meet or exceed a customer’s expectations and how satisfied they are in general with a product or a service.

Custom Form

Show a different feedback form to certain users based in the URL, country, or IP address. Can also be triggered with the Javascript API command.

Custom Third Option

When setting up the feedback form for the feedback button one can select to ask for specific or generic feedback. A custom third option can be added when noticing that the feedback button is used to leave feedback about things that do not concern the website, but e.g. rather feedback about customer service. With the third option you can add a link to the customer service contact page to keep receiving relevant feedback about the website through the feedback button.

Emotional/Mood Rating

The key metric offered by Usabilla. It is the first default element in your feedback forms that collects the general mood of the respondent.

Event Callbacks

Usabilla for Websites uses so-called Event Callbacks to signal that an interaction with Usabilla has taken place on a website. The Event Callbacks can be registered through a javascript function. They are the backbone of many of Usabilla's integrations and can be used to make feedback submitted through Usabilla available in the browser. Event callbacks make it possible to send information from Usabilla to other web optimization tools such as analytics tools, A/B testing tools or Data Management Platforms.

Exit Survey

A survey that gets triggered when the visitor of a website leaves the browser window. Useful when wanting to find out why the visitor would leave the website (e.g. while purchasing something).

Full Screen Survey

A full screen survey is rather intrusive as the survey will pop up in front of the page. That way you can encourage the user more to participate in the survey. It is used for longer surveys and e.g. exit surveys, newsletter sign ups, etc.

GDPR

TheGeneral Data Protection Regulation (GDPR) (Regulation (EU) 2016/679) is a regulation by which the European Parliament, the Council of the European Union, and the European Commission, intend to strengthen and unify data protection for all individuals within the European Union (EU).

Generic Feedback

In the feedback form you can ask for generic feedback meaning the feedback will be about the whole page instead of a specific part of the website. A screenshot of the whole page can be generated and saved with the feedback item to replicate the way the user has been through on that page.

Goal Completion Rate (GCR)

TheGoal Completion Rate(GCR) metric measures the number of people that complete a specificgoal, such as signing up for a trial or subscribing to a mailing list.(Goal Completion Rate= # of Web Visitors / # of Goals Completed)

In-Page

In-Page is part of Usabilla for Websites. It lets you create a widget which can be embedded in your website. You can, therefore, run surveys that seem to be integrated seamlessly into the web page.

Javascript API

Our Javascript API allows various additional actions to be performed on our Feedback button. Through this API you can, for instance, alter the position, appearance or trigger of your feedback buttons and forms. The JavaScript API is only used for interacting with the Usabilla Buttons and Forms.

Jump Rules

Define if or when the User should jump to another page based on the answers submitted on the current page. (If answer is X, jump to page Y, otherwise jump to the last page)

Key Insights

Summary of feedback items showing common trends, anomalies, and areas that need attention. In order to provide meaningful data, Key Insights will appear wit a minimum of 100 feedback items per month.

Labels

Labels help you organize the feedback items into meaningful categories. Feedback items can also be assigned to other relevant team members based on the label they are tagged with. You can also create labels manually or automatically.

NPS (Net Promoter Score)

Net Promoter Score is a number used to measure the loyalty of your users by asking how likely they are to recommend your business to someone. The score range typically runs from 0-10 whereby 0-6 are detractors, 7 & 8 are passives and 9 & 10 are promoters.

Passive Feedback

Passive feedback concerns the feedback button that you can place on the side of your website. It is considered “passive” because the website visitor has to take initiative to click on the website and provide feedback. This is used to collect feedback about the website itself & lets you take regional or full screenshots.

Public API

Our Public API is a RESTful API which allows customer to obtain their data directly using a script or a program that's running on their end.Please visit developers.usabilla.com for more information and documentation.

Recruit Participants Survey

This type of survey lets you redirect your users to an external questionnaire. It can be used find out more about your users.

Save Form Values

Save the values of form elements that are submitted into form fields when feedback is left. Password fields are never stored.

Saved Search

You can set up saved searches to save filters, retrieve it automatically, and receive the feedback relevant to you via email.

Screenshot/Visual Feedback

With Usabilla for Website you can collect visual feedback/ screenshots to reproduce what the user giving feedback saw. You can ask to leave feedback on a specific part of the website or on the whole website.

SDK

A Software Development Kit (SDK) a set of tools thatenables developers to implement the Usabilla solution in an application (Usabilla for Apps).

Slide Out Survey

Survey that slides out subtly from the side on a page. It does not interrupt the user too much from his action. Good to use when wanting to collect feedback about new features on a website, to ask ad hoc questions, short questionnaires, ask about the reason for visit, etc.

Specific Feedback

In the feedback form of the feedback button one can ask to collect feedback about specific parts of the website meaning that the user can click on one part of the website of which a screenshot is taken and left with the feedback item. Example: the button to make a reservation on a restaurant website does not work; with the specific feedback option the user can select that button and leave feedback informing that the button does not work.

Theme

A Theme is a design that can be selected as standard design for feedback forms and campaigns to adjust these to your own website design/ corporate identity.

Translate text to

Set up automatic translation of feedback comments to a certain language.

URL vs Path

URL is the whole web address of a website consisting of several parts.A path will usually refer to a file or folder (directory) on the web server (for example, /folder/file.html).

Usabilla for Apps

Usabilla for Apps allows you to capture feedback from within your native iOS and Android apps. Collect passive feedback by users trigger forms when they run into something they’d like to share with you. Collect active feedback by asking specific questions to your user at a moment where they are least biased. You can use this functionality if you - for instance - want to measure an NPS, find out how satisfied users are or to validate a business assumption with your users.

Usabilla for Email

Usabilla for Email lets you create a widget that can be placed in your email templates to collect feedback about the content of your emails, service of different employees, and to redirect to more extensive surveys.

Usabilla for Websites

Usabilla for Websites focuses on collecting feedback on and about your website in a smart way. It consists of several parts (active feedback, passive feedback and InPage).

User Targeting

Define to which specific visitors (who) your campaign will be shown.

Viewport

A User’s visible area of a web page. It varies with device (smaller on a mobile phone than on a computer screen).

In some situations, the design of your web page does not lend itself to a feedback button that lays on top of your web page. In those situations, it’s best if you, for example, have a link in a drop-down menu that trigger the Usabilla Feedback form. In this article, we’ll go over the steps for integrating Usabilla with our own feedback button.

For this guide, it’s recommended that you have basic knowledge of Usabilla, HTML, CSS, and JavaScript.

Adding a button or link to the web page

Firstly, you’ll need to make sure that you have an HTML element that you can use for triggering the Usabilla Feedback form. This HTML element will act as an alternative way of initiating the feedback process that you would normally start by clicking on the Usabilla Feedback Button. An example of this can be found below:

here

There are several types of HTML elements that you can add. For the sake of this guide, we’ll be using a standard <a> link with some text that can be clicked for leaving feedback. Add the HTML, CSS, and JavaScript for the HTML element that you’re going to use to the web page for initiating the feedback process.

<!--integrated feedback button -->

<a rel="noopener,nofollow" target="_blank" href="https://support.usabilla.com/hc/en-us/articles/115003173505-Integrate-Usabilla-with-your-own-feedback-button#" id="usbl-integrated-button">Give Feedback</a>

Using the JavaScript API Commands

When you have Usabilla installed on your web page you automatically have access to a set of JavaScript API commands. These JavaScript API commands can be used for interacting with the Usabilla Tool on your web page. Of those JavaScript API commands, you’ll two for this guide. These are the “hide” command and the “click” command.

The “hide” command is the command we’ll be using for hiding the default Usabilla Button. Because we’re creating our own feedback button we’ll need to hide the default one. Doing so makes sure we’re not adding multiple feedback buttons while we only need one.

The “click” command is the command that we’ll use for initiating the feedback process. The “click” command simulates the event that would normally occur when someone clicks on the feedback button.

To make your life a little bit easier we already made a piece of example code that you can add to your web page straight away to:

Add a link for initiating the feedback process.

Hide the default feedback button.

Enable the added link to initiate the feedback process.

<script>

//Hide Usabilla Default button

window.usabilla_live("hide");

//Find a Link and open the Usabilla Feedback form when the user clicks on the link

document.getElementById("usbl-integrated-button").addEventListener("click",function(){

window.usabilla_live("click");

});

</script>

When you add this code, you need to make sure that the code with the “hide” and “click” command is added after the Usabilla code is added to your page. This pre-requisite since the commands are only available if the Usabilla installation code was run.

After you’ve added the code with the commands you’ll be ready to use your integrated feedback button. With the JavaScript API commands, there are countless ways you can integrate Usabilla with your own website. Please go for more information on our JavaScript API commands.

Total example

<!--integrated feedback button -->

<a rel="noopener,nofollow" target="_blank" href="https://support.usabilla.com/hc/en-us/articles/115003173505-Integrate-Usabilla-with-your-own-feedback-button#" id="usbl-integrated-button">Give Feedback</a>

<!--ADD USABILLA INSTALLATION SNIPPET HERE -->

<script>

//Hide Usabilla Default button

window.usabilla_live("hide");

//Find a Link and open de Usabilla Feedback form when the user clicks on the link

document.getElementById("usbl-integrated-button").addEventListener("click",function(){

window.usabilla_live("click");

});

</script>

In case you've migrated to the Global analytics tag (gtag.js) tracking code, you will have to append a code snippet on your webpage instead of enabling the integration in your Usabilla account. This is due to the way this specific tracking code sends event parameters.

To be able to push Usabilla data using the Global analytics tag, you need to copy/paste the following code snippet under the Usabilla button code:

window.usabilla_live('setEventCallback', function(category,action,label,value){

if (typeof action !== 'undefined') {

gtag('event', action, {

'event_category': 'Usabilla',

'event_label': label,

'value': value,

});

}

});

You can see what kind of data is included in this integration and also how you set up your custom report in this article.

In Usabilla for Apps, we've set up some customization functionalities that can help give your Feedback Forms and Campaigns the look and feel of your App. These functionalities can be accessed straight from your Usabilla account and once you've set up your customization, it will be reflected in your App immediately, without having to release a new version of your App. In this article, we're going to dive deeper into these options to help you get started with customizing your Feedback Forms and Campaigns for Usabilla for Apps.

This article is split up in separate sections:

We'll start by helping you identify the Color Groups

Next, we're going to cover the Color Settings

Last but certainly not least, the Banner Position (only for Campaings)

Color Groups

To help you identify the different elements that can be used in Usabilla for Apps Feedback Forms and Campaigns, we've divided them into groups based on their role in the interface. Below you'll find an overview of these color groups for Android and for iOS.

Note: SDK 6.0.1+ for iOS and SDK 6.0+ for Android, will contain our new cards design for your Feedback Forms and Campaigns. Each question element will be placed on a different card, which makes it easier for your users to separate the different questions resulting in a more appealing Form/Campaign with improved readability.

Group 1, Title color:Changesthe color of all question titles and headers.

Group 2, Accent color:The color of interactive or otherwise important components like sliders, checkboxes and the submit button. This also includes the navigation bar of the feedback form.

Group 3, Text color:The color of general text, such as user input, paragraphs, checkbox options etc.

Group 4, Validation message color: The color that highlights fields which are either required and left blank or incorrectly filled.

Group 5, Background color: The color of the background.

Group 6, Text color on accent color elements: The color of the text displayed over elements in accent color, such as selected buttons and checkmarks in checkboxes.

Group 7, Card color: The color of the card design elements.

The following images display examples of how the elements are grouped for Android and for iOS.

The different color groups in Android apps

here

The different color groups in iOS apps

Color settings

Now that we've identified the different Color Groups and we know what elements these groups belong to, we can continue with configuring the colors we want to have in our Forms and Campaigns. Let's start by locating the place where these settings can be configured. The color settings can be found by opening the 'Advanced' settings in your Form or Campaign:

With the 'Advanced' options open, scroll down to enter the wonderful world of the 'Color Settings':

This is where you can go ahead and customize the colors of your Form and/or Campaign to give it the look and feel you want to go for. Want to see what your Form/Campaign looks like after changing some of the colors? Feel free to give the Usabilla Preview App a try! The Usabilla Preview App can be downloaded from the Google Play Store and the App Store and it allows you to scan the QR code that's shown after saving a Form and Campaign.

Banner position

Apart from the settings for colors, we also have one setting specifically for Campaigns. The initial screen in a Campaign in Usabilla for Apps is always a banner. This banner can be used as an invitation to participate in a Campaign, it can be used to measure the NPS, how a user is feeling or to simply display a notification. With the setting related to this banner, you can control whether the banner is shown at the bottom of the screen or at the top of the screen. By default, the banner will be displayed at the bottom of the screen.

Note: This setting is only available in the iOS SDK 6.0.1+ and Android SDK 6.0+.

The banner setting can be found by opening the 'Advanced' settings in your Campaign:

Et voila:

To give you an idea of how your Campaign will look when either 'Bottom' or 'Top' is selected, we've included these two images as examples:

Additional customization

This was a complete guide to help you manage the colors of the elements in your Forms and Campaigns, and the position of the banner of your Campaigns from Usabilla. But wait, there's more! It's also possible to customize the mood rating, the star rating, the font and the color of the Header. These specific elements can be customized from the SDK. The documentation regarding this for our Android SDK can be found here. For our iOS SDK, you can find it.

Success! You've finished the article and you're ready to take on the color customization screen in Usabilla, have fun!

At Usabilla, we recommend you to connect the feedback that your users provide to information that you have available elsewhere as much as possible. Usabilla's custom variables allow you to do just that. In this article, we aim to provide a basic explanation of custom variables as well as links to the implementation guides for each Usabilla product.

What are custom variables?

Custom variables are little bits of data that you can include when a user leaves feedback through Usabilla. They can derive from other 3rd party tools or from your own website.Custom variables are used to add extra information about your user or the website, email or mobile app about which the user left feedback. Custom variables are structuredin "key-value pairs", which means that they will be structured as demonstrated by the following examples:

Subscription: Enterprise

Tier: Gold

Current_shopping_basket_value: 49.95

Previous page: https://www.google.com

Once implemented, custom variables will be available in your Usabilla account for each feedback item to which they were added. Usabilla only stores custom variables when the user submits a response.

friendly support team

Every product in the Usabilla product suite allows you to utilize custom variables. However, the implementation, the way they are displayed and the analysis options differ for each product.

Note:A maximum of 488 characters can be included in a custom variable. This applies to both the feedback button and for campaigns

Why do I need custom variables?

Connecting user feedback to data from other sources helps you to:

add context to your feedback

quantify your user feedback

use feedback to understand your quantitative data

Custom variables allow you to enrich your feedback with data from other sources by passing these on data along with the feedback item. This means that you can add extra information such as usernames, customer types or A/B test variables to your feedback. Having these data in the same place as your feedback, will help you to connect the dots and analyze your feedback quicker and more extensively.

Besides enriching your feedback with more information, custom variables can also be used to very accurately target users with a Usabilla survey. For example, if you want to survey users that are between 25 and 40 years old and have purchased a specific product in the past, this is possible through custom variables. See this article for more details.

Which data can be used included in custom variables?

Custom variables can include any sort of data, provided that:

you already collected these data

the data are available for Usabilla

your company's privacy policies allow you to send these data to Usabilla

Furthermore, we also encourage you to only send data to Usabilla if you are actually planning to use them. This will help you to keep your feedback clean and to the point. Also, this will help you to meet data privacy requirements such as the General Data Protection Regulation (GDPR).

Tip: In case you would like to add data which could potentially be used to identify individuals (e.g. user IDs or usernames), you could consider including a hashed or encrypted version of the data. This way you will be able to recognize the user that left feedback, but no one outside your organization will be able to do so.

Lastly, we recommend you to keep the custom variables short and comprehensive. Keep in mind that custom variables can be used to filter and categorize your feedback when analyzing it.

How can I add custom variables?

Adding custom variables will require you to change a bit of code for most Usabilla products. Therefore we recommend you to already start thinking about custom variables during the initial implementation of the Usabilla. Implementation guides for the different products are available here:

Usabilla for Websites

Usabilla for Websites - standalone surveys

Usabilla In-Page

Usabilla for Email

Usabilla for Apps - iOS and Android

Advanced usage

Since custom variables allow for a lot of freedom, there are many things you can do through the usage of custom variables. Potential next steps are:

Connecting Usabilla and your data layer

Create a survey for users that come from one specific page

Collect feedback on your Zendeskcustomer support emails and connect it directly to the support agent in question

More ideas or questions about custom variables? Don't hesitate to reach out to our .

To ensure that your Feedback Buttons, Feedback Forms, In-Page Forms, Email Widgets, and Campaign Forms are aligned with the design of your website we allow you to set a Custom Theme. The Theme of a form or widget defines how it will look and feel for your users. In this article, we'll discuss how you can use Custom Themes and what can be customized.

How to use Custom Themes

We always recommend that you use a Custom Theme and more specifically, one that matches the design of yourwebsite. Doing so ensures that experience of Usabilla part matches the experience of your website, which in turn results in a fluent experience overall for your user. To make sure that the forms that you've created with Usabilla blend into your website your Customer Success Manager will create a Custom Theme for you that aligns with the design of your website.

As soon as you become a customer at Usabilla your Customer Success Manager will create a Custom Theme for you and make sure that the theme is ready before your Getting Started Training.

Making Changes to your Custom Themes

If you want to make changes to your Custom Theme or you, for example, want a seasonal Custom Theme for Christmas to be added, you can request a change to your existingTheme or a new Custom Theme through our Customization request form. When requesting themes always make sure to upload all resources in the recommended formats (font .WOFF, logo .PNG, color HEX)

Did you Know: Our Themes are platform agnostic, meaning that they can be used in any of our Web and Email products. We've also made sure that the basic design for our App product aligns with the themes.

What can be customized in the Themes?

In order to provide your users with the best possible experience for responsiveness, accessibility, performance, backward compatibility, and web design best practices there are some limitations in place. In order to provide you with a clear overview of what can be changed, we've created the reference down below. All the elements of the forms have been annotated with the possible customizations in the interface as described below (click to view in full-screen).

Customization

When you look at the overview you'll see that you can change the styling of the elements from the list below.

Base Style

Base Colors

Typography

Button

Banner

Mood rating

When you request a Custom Theme via our request form you'll be guided through all the possible customizations. After your themes have been created and added to your Usabilla Team Account you can apply the Theme to your forms. Changing the theme is very easy and can be done from the advanced settings of each form. You can change aTheme without changing the implementation itself, this applies to both the selected theme or the styles within the theme.

If you're keen on seeing some examples or if you have any questions specific questions about themes, please do not hesitate to get in touch with your Customer Success Manager or with our Support Team.

In this short article, I’ll show you how you can find the App ID in Usabilla for Apps. Before you can trigger a Usabilla for Apps Campaign, you need to create a campaign and an app, in your Usabilla account. The Campaign is connected to an App ID, and the App ID is further on connected to the SDK.

Campaign App ID SDK

When you want to trigger a certain Usabilla for Apps Campaign, you must initialize the Usabilla SDK with the corresponding App ID that’s connected to the specific campaign. To find this App ID, simply follow these steps:

1. Go to Apps Campaigns Overview

When you’re in the overview page, click on the specific campaign you want to find the App ID for. This shall expand the bar and reveal the name of the App it’s connected to.

2. Click on “New Campaign”

On the next page, our platform will ask you to type in a new campaign name, just ignore it and close the dialog box. You shall see a list of all the App’s created in your account on this page, including the specific App ID’s:

Can I upload my own button?

Yes! We have launched a Beta version of the "Button Creator". This tool allows you to upload an image as a new button. This means you no longer have to contact your Customer Success Manager to upload a new pretty button for you, you can do it yourself anytime. However, the minimum privilege right you need to have to be able to use the Button Creator is as a power user.

What does it do?

The Button Creator allows you upload a .png image as a button. This means you can design a button whichever way you want it to look.

Simply create the .png image of your button and upload it to our Button Creator tool. After uploading, you can indicate where the button should be positioned on the web page and adjust the size where needed. We recommedthat you upload an image that is twice thenumber of pixels of what you need. Thay way you'll be able downscale it to support high-resolution retina screens.

touch

Where to find it.

You can find the Button Creator under Usabilla for Websites. Once you’re logged into Usabilla make sure you have ‘Websites’ selected in the top left corner. Under "Buttons & Forms" you click on "Setup".

From Setup, go to "Create a New Button". On this page, you will find a banner on the top to get you to the Button Creator.

Your feedback is appreciated.

We would not be Usabilla if we were not collecting feedback for our new tools.

In the Button Creator, you will notice a feedback button asking to help us improve. Any remarks you might have about our new tool - please do not hesitate to share through the feedback button.

Useful tips

Where can I find my button after saving it?

Once you are sure your button looks the way you want it to and hit save, you will land on a page with both standard Usabilla buttons and your own custom buttons. Your newly created button will be under "custom buttons". With this newly uploaded image, you can create a new button code to implement on your website - the same way you're used to.

What if I want to edit or delete a button?

This Beta version of our Button Creator tool does not allow to edit or delete buttons. Your Customer Success Manager, however, has the ability to do this for you. So if you are not entirely satisfied with your saved button, then contact your Customer Success Manager or get in .

What kind of images can I upload?

To guarantee high-quality buttons, we allow only .png images to be uploaded in the Button Creator.

The maximum file size is 2MB.

What is Retina support?

In the Button Creator, you will see the option to "downscale image by 50\% (retina support)". We added this feature in order to secure quality images on high-resolution screens.

We recommend using this feature. Without downscaling the button will look fine on standard screens but could become pixelated on high-resolution retina screens.

In this article, we will show you how you can get started setting up an API call using the Python client library. We will cover the most basic steps you need to be able to set up an API call.

In some cases, you might want to extract data from Usabilla or structure the data in a certain way, different from the default Usabilla reports that you can generate from your Usabilla account. In that case, you can use our API to extract the data you need.

Requirements:

Basic understanding of the Terminal

Basic understanding of the concept of an API

A code editor (we will be using Visual Studio Code)

Table of content:

Check if Python 2.7 is already installed

Install Python 2.7

Test if everything works

Install Usabilla API

Execute Usabilla API calls

1. Check if Python 2.7 is already installed

To make anything work, we first need to make sure that Python is installed on your computer. Some computers already have Python pre-installed. Let’s first check if you already have Python installed:

Open Terminal on your computer

Type:python

https://github.com/usabilla/api-python/tree/master/example

Based on the output, we can see that Python 2.7 is installed. If you have version 2.7 (or 2.7.x), you’re lucky and you can continue to step 3! If not, we will have to install Python 2.7 before we can proceed.

If you’re on a Windows computer, you might first have to navigate to the folder where Python is installed for the Python interpreter to work.

2. Install Python 2.7

Navigate to www.python.org/downloads

Click on the download link for version 2.7

Follow the installation instructions

Open your Terminal and type the command python again. The Python interpreter should respond with the version number.

3. Test if everything works

Now, let’s create a Python file that we can use to test if everything is set up correctly.

1. Create a working directory (folder) we can store all our Python code in

2. Open Visual Studio Code and create a new file

3. In the Visual Studio Code editor for the new file type: print(“Hello World!”)

4. Save the file as test.py in your Python folder we created in step 1.

5. Open Terminal and move into the folder where we saved our Python test file

Note: You can move from one directory to another one by typing cd followed by the path to move into the specific folder: cd full_path

6. Execute the Python file by typing: python test.py

7. If everything has been set up correctly you should get Hello World! printed out in your terminal output:

4. Install Usabilla API

Now that you have Python installed, it’s time to install the Usabilla python library on your computer.

1. Open Terminal

2. Install pip on by runningeasy_install pip

3. Type pip install usabilla-api

Note: If you're using a Windows OS or have difficulties installing pip in step 2, then follow the guidelines here: https://pip.pypa.io/en/stable/installing. If you're running into issues in step 3, then type sudo pip install usabilla-api on Mac. For Windows, run the terminal as Administator and then try again.

5. Execute Usabilla API calls

To get you started with doing API calls towards our servers, we will walk you through an example on how you can retrieve all Usabilla buttons from your account.

1. Start by creating a file in your Python folder which we will name getAllButtons.py

2. In the code editor, paste this code into your file:

"Python API - List out all Usabilla buttons with ID and name"

import usabilla as ub

import json

# Create an API client with access key and secret key

api = ub.APIClient('ACCESS-KEY', 'SECRET_KEY')

# Get all buttons in account

buttons = api.get_resource(

api.SCOPE_LIVE, api.PRODUCT_WEBSITES, api.RESOURCE_BUTTON, '*', iterate=True)

parsed_json = json.loads(json.dumps([item for item in buttons]))

# Print out all buttons with ID and name

for record in parsed_json[:]:

btn_id = record['id']

btn_nm = record['name']

print("Button ID: " + btn_id + " || Button name: " + btn_nm)

3. Change the access key and secret key and then save the file.

4. Open Terminal and move into the Python folder by using cd

5. Once you’re in your python folder with the getAllButtons.py file, you can execute it from the Terminal by typing: python getAllButtons.py in the Terminal window.

Congratulations: Here's your trophy for making your API call! We have several example codes on our GitHub page that you now can start experimenting with:

Usabilla for Websites gives you great flexibility, especially when it comes down to the targeting of a Usabilla Campaign. One way of triggering a Usabilla Campaign is by using a Manual Trigger. A Manual Trigger allows you to trigger a campaign by initiating a Usabilla JavaScript API Command.

While you could use this to trigger a Campaign based on the click of a button or based on an event on your web page you could also use to trigger a campaign after a video has ended. A great use case for this is when you want to ask users for feedback regarding the video that they just watched.

First, we'll need to create a campaign that uses a Manual Trigger. In another article in our Support Center we outline the steps for creating a campaign that triggers using a manual trigger.

When you create your campaign you need to make sure you have set the manual trigger command "vjsEnded". By doing so your Campaign will only trigger when the following JavaScript API command is initiated:

window.usabilla_live('trigger', 'vjsEnded');

Next, we'll need to add some JavaScript to your web page that interacts with your HTML5 video. To make it a little easier for you, we've already made the script that shows the full example. In the Github Gist below you'll find an example that includes both theimplementing of theHTML5 video, as well as the setup for the manual trigger.

The script uses the HTML5 Video API to check for the event that is executed when the video has ended. More information about this can be found in the MDN web docs.

Using that event the script sends out a manual trigger to Usabilla which in turn will trigger the campaign. Prerequisite for implementing this is that your video is located on the same web page as where you have Usabilla implemented and that the video is played using HTML5 video player.

Note: The implementation explained in this article does not work with Youtube. If you want to trigger a Campaign after a Youtube video has ended you'll need to use the Youtube iFrame Player API.

Usabilla for Websitesoffers several ways in which you can combine user feedback with your data layer. A data layer is a layer of information about your user or your application, which is accessible from the browser during the user's visit. Please find more information about a data layer here.

During the user's stay on your website, you can exchange information between Usabilla and your data layer. This allows you to combine the input a user provides through Usabilla with data from other sources.

Addinginformation from your data layer toUsabilla feedback

One of the ways in which data can be exchanged between Usabilla and your data layer is by pushing data from your data layer to Usabilla through our JavaScript API.This is a JavaScript snippet, which can be addedto the existing Usabilla code on your website.

The information from your data layer will then be included in feedback and campaign results as custom variables. You will also be able to target campaigns according to the information from your data layer. For more information, please have a look at the following articles:

Push custom variables to Usabilla

Trigger campaigns on custom variables

Depending on the data layer implementation you're using, you're also able to assign your data layer as CustomVariable Object. By assigning the data layer as Custom Variable Object, you'll have *all* of the data layer information availablein Usabilla. Below, you'll find some of the compatible data layers which can be used as Custom Variable Object. Keep in mind that compatibility of your data layer as the Custom Variable Object depends on the implementation you have. Always make sure to thoroughly test the code before implementing.

//Send data to Usabilla using Google TagManager

window.usabilla_live('data', {

'custom': dataLayer[0]

});

//Send data to Usabilla using Tagman

window.usabilla_live('data', {

'custom': tmParam

});

//Send data to Usabilla using Dynamic Tag Manager

window.usabilla_live('data', {

'custom': _sattelite

});

//Send data to Usabilla using Qubit

window.usabilla_live('data', {

'custom': universal_variable

});

//Send data to Usabilla using Tealium

window.usabilla_live('data', {

'custom': utag_data

});

Push feedback and campaign results into your data layer

When a user leaves feedback on your website, the feedback can be sent to your data layer through our Event Callbacks. This way, you can connect the feedback a user provides to events measured in your quantitative analytics suite or pass the info on to other analytics tools. The following article provides an in-depth explanationon how you can make sure that your feedback is pushed to your data layer.

Send campaign results to third party tools

Tip: if you're using Relay42 as your tag management system, you may want to use our out-of-the-box integration to push information to Relay42's data layer, or even target Usabilla campaigns according to information from the data layer.

Next steps

Once you integrated Usabilla and your data layer, many doors are opened towards optimizing your users' experience on the website. You can use the information from your data layer to contextualizeyour users' feedback and make it even more valuable. Furthermore, you can act on an individual user's feedback immediately, making their experience more relevant and even more personalized.

You can easily export all of your feedback responses in the Feedback Overview. When you export your feedback responses, you can also decide to export only a subset of your feedback responses by applying filters. Exporting your feedback can be very useful when you want to use a program such asExcel or Google Sheets so that you can further analyze thisdata or combine it with other data sets. Below, you'll find the steps necessary for exporting your feedback responses.

Looking for information about Saved Searches instead? We covered those in a separate article. Please go here.

Exporting

1) Head to the Usabilla for Websites "Feedback"page.

Public API

2) In the "Feedback" page, you'll find the filters, your feedback graphs, and your feedback. In thetop righthand side of the page, you will find the "Export"button as shown below. Click on the "Export" button to open the export drop-down menu.

3) In the export drop-down, you'll see two options:

Export Now

Will export all feedback that is within the scope of your applied filters in a CSV file.Click on export now todownload your data in a .CSV file.

Automatic Export

Allows you to set up automated CSV exports via sending a CSV file via email, storing a CSV file on an FTP server, or storing a CSV file on an AWS s3 bucket.

Note: The automated exports will export all feedback and will not take into account any of your filters. If you require different formats for feedback data you can also pull it through our .

If you're struggling with the large amount of feedback that is getting in you can always reach out to your personal Usabilla Customer Success manager. Your Customer Success Manager will be able to offer you guidance and best practices on feedback management and share feedback within your organization using Usabilla.

In this article, we will cover how you can integrate Usabilla data into Google Analytics (GA) using Google Tag Manager’s (GTM) Data Layer.

This integration will work with the following Usabilla products:

Usabilla Button

Usabilla Campaigns

Table of content:

Understanding the Data Layer

Pushing Usabilla data to GTM Data Layer

Creating Data Layer Variables in GTM

Creating a trigger for a Usabilla action in GTM

Connecting data from Data Layer Variables to GA event tag

Setting up a custom report in GA

1. Understanding the Data Layer

First of all what is a Data Layer and what's the provided benefits of using it?

Technically speaking, a Data Layer is a JavaScript array that can store certain information. It functions as a simple database that lies on the website where you can store valuable information about your users or page content. The information collected in the Data Layer can be everything from key attributes of a website (URL, page title etc.) to key information for marketing or analytics tags, like campaign ID, purchase history or other user data.

The Data Layer gives you a single data point where you can store and access all your third-party data. It also enables you to easily integrate with other third-party technologies.

2. Pushing Usabilla data to GTM Data Layer

As a first step, we need to append a code snippet into a tag in Google Tag Manager. This code snippet will make sure that all feedback that's left, is getting pushed into the Data Layer.

In your main GTM view, click on“Tags”, then “New”, followed by clicking the box that says “Tag Configuration”.

Using our Event Callbacks

Choose the tag type “Custom HTML” and copy paste the code snippet below into the custom HTML tag:

window.usabilla_live('setEventCallback', function(category,action,label,value,userData){

if (typeof action !== 'undefined') {

//Append data to datalayer on all actions

window.dataLayer.push({

'event':'Usabilla',

'category': category,

'action': action,

'label': label,

'value': value,

'userData': userData

});

}

});

Your final tag setup should look like this:

Note: Make sure that you fire off this tag after the Usabilla button code has been fired off. If you have installed the Usabilla button code as a tag in GTM, then youcan easily achieve this by clicking on the “Tag Sequencing”tab and setting up your rules.

3. Creating Data Layer Variables in GTM

Now it's time to create some variables in Google Tag Manager. These variables will connect the data in the Data Layer with GTM.

In your main GTM view, go to “Variables” and click on “New”. In the variable configuration window, select“Data Layer Variable” as variable type:

The variables you will create in this step depends on what data you want to integrate into Google Analytics. In this example, we will use the standard variables "category", "action", "label" and "value" from our Event Callback Method. To get an overview of the data that's stored in these variables, then take a look at our support article. This article also maps out the information that’s accessible on the different actions with the Usabilla form; Open, Close, Submit etc.

Tip: If you want to map out the information in the userData object then you can get an overview of the data that’s accessible by using the preview function in GTM.

Now let’s get back to creating our variables. We will create 4 data layer variables in this example. Give each of them a descriptive name, but make sure that you give it the correct “Data Layer Variable Name”.

The different Data Layer Variable Names we will create in GTM can be found in the code snippet that we appended in step 1:

For category the Data Layer Variable Name will be "category", for action it will be "action", for label it will be "label" and for value, it will be "value".Go ahead and create these variables in your GTM account and follow the example below for all 4 of them:

Now, we shall have these Data Layer Variables created in our Google Tag Manager account:

4. Creating a trigger for a custom event in GTM

To be able to send the data layer variables further on to Google Analytics, we first need to define a trigger for the event when a user interacts with Usabilla.

Go to “Triggers” then select “New”. As a trigger type select “Custom Event”. As the “Event name” you have to enter “Usabilla” (without quotation marks). Last, but not least, you can select when the trigger should be fired. In our example, we will choose “All Custom Events”

5. Connecting data from Data Layer Variables to GA event tag

To do a recap and wrap our head around what you’ve done so far:

You’ve made sure that the Usabilla data is appended to the Data Layer

You’ve created Data Layer Variables that are connected to the Data Layer

You’ve created a trigger in GTM that fires off every time a Usabilla action is awakened from our Event Callback Method.

Feeling great? You’re almost ready to become a true Google Tag Manager Ninja. Now you need to connect the building blocks that you’ve created to make this kind of integration work.

Go to your main GTM view, click on “Tags”, then “New”. When clicking on Tag Type add a “Google Analytics - Universal Analytics” tag. As Track Type select“Event”. Connect the Data Layer Variables by mapping them out, one by one, from the slide-out menu that appears. Last, but not least, add the Usabilla trigger that we just created. Your final setup should look like this:

6. Creating a custom report in Google Analytics

You’ve justed accomplished to pull data all the way from the Data Layer and into Google Analytics. Give yourself a tap on the shoulder and prepare yourself for the last step: presenting the data in a custom report in Google Analytics.

How you create your custom report depends on which data you've pushed into Google Analytics. In our example we will make use of the information that's sent along with the variables category, action, label, and value:

1. Within Google Analytics click on the "Customization" tab, then "Custom Reports" and after that on the "New Custom Report" button.

2. Enter a title for your custom report and enter a name for your report tab.

3. Add the following four metrics: Users, Unique Events, Pages / Session, and Avg. Value.

4. Add the following Dimension drill-downs: Event category, Event action, Page, and Event label.

5. Optional: You can also add a filter to your custom report. E.g. filtering on the data in the "Event Category" with a Regex.

6. Click "Save" and your report should be ready. Please note that Google Analytics doesn't display their data in real time, so it can take a while before the report gets filled with data.

Congratulation! Here's a trophy for completing the integration.

Feedback? Do you have some feedback on this article? Feel free to leave feedback via our feedback button!

The Usabilla for Websites and Usabilla In-Page scripts can be implemented through Relay42. In order to implement Usabilla on your website through Relay42, please follow the below steps.

1. Within the Tag Management section of Relay42, go to Tags.

2. Click the 'New Tag' button:

this article

3.Look for Usabilla in the Search bar and select the Usabilla template tag from the results:

4.On the right hand side select the 'Button code' variant:

5. For the next step in Relay42 you will need the Usabilla button IDsof the mobile and desktop feedback button. You can find these in your Usabilla account in the Buttons & Forms Setup section. You can show the ID by click 'Show Javascript code' under each of the button:

6. Copy and paste the Usabilla button IDsfor mobile and desktop into Relay42:

It is possible to automatically push Usabilla campaign results into the Data Management Platform of Relay42 by checking the box 'Enable Relay42 feedback tracking'. Take a look at for more information on this part of the Usabilla / Relay42 integration.

7.In the final step of setting up the Usabilla tag, specify the tag name and tag firing rules (optional) and click save:

8.To finish you will need to publish the newly added tag to your production website.

The Feedback page is the place in Usabilla where you have an overview of allincoming feedback items. To use this page effectively, however, it's critical that every user only sees the feedback that's relevant for them.In this article we'll show you how you can:

Create a custom view of the Feedback page, only showing relevant items for you

Send an email notification every time a new Feedback Item comes in that's relevant for you

Filters

To make sure you see the feedback that is relevant for you, we need to start using the filters. In the Feedback Page, you can filter on the following Feedback Attributes:

Button:Select one, or multiple, buttons for which you want to see the Feedback Items

Date: The date range for which you want to see all items

Mood: Select one or multiple moodscores. You'll only see the items that have these scores

NPS: Select a range of NPS scores that you want to filter out. Only works if you ask an NPS question.

Status: Filter on the status of an item (New/Read/Archived)

Comment (includes or excludes): Enter a word or sentence and filter on items that contain/don't contain this word or sentence in the comment field.

Email: Only show feedback items where a visitors left their email address

Label(s) : filter on all items that include/exclude one or multiple labels

URL: Filter out all feedback that's generated from a particular section of your site based on URL

Device: Filter on device type(s) (mobile/tablet/desktop)

Browser: Filter on browser type(s)

Operating System: Filter on operation system(s)

Custom Variables (includes or excludes): Filter on items that contain/don't contain specific custom variable values.

Feedback ID: Filters on Feedback ID

Viewport: Filter on specific viewport ranges

IP address: Filter on feedback that includes/excludes certain IP addresses (e.g. used to filter out test items left from your own office)

Save Filters

Once you've used the filters to see only the relevant feedback for you. You can save these filter options by clicking 'New Save Filter'.

After this you can give a name to your saved filter, and assign it to your account and/or to the account of a team member. To also assign it to a team member account, simply enter his/her email address (they do need to have a Usabilla account).

If you click save, the Saved Filter will now be available in the dropdown menu on the top of the filters. You can save as many filters as you'd like.

If you want to receive automatic email notifications for each new feedback item that adheres to your saved filter, simply check the 'Send email updates for this search' checkbox when creating a saved filter. After you've set the Format and Frequency you can save the filter, and you'll receive automatic emails for this filter.

Note: If you've assigned a saved filter to a team member, and set up an email update, your team member will also receive the email update.

Want to remove a saved filter or email update from your account? You can do that from your Account Settings.

Example of Saved Filters for different user roles:

Customer Support

At Usabilla our support team wants to be updated every hourfor feedback that's left in our backend. That's why they've created a saved filter with the following settings:

Button: Usabilla backend

URL (starts with): https://app.usabilla.com

The email updates settings look like this:

Product Owner

Our product owner is not logging into the Usabilla backend on a daily basis. But he does want to receive feedback on bugs that occur in the backend on a daily basis. He's also interested in the suggestions that our users have for us, both on our public website and from ourbackend. His saved filter looks like this:

Buttons: Usabilla Backend, Usabilla.com - Desktop, Usabilla.com - Mobile

Label(s): Bug OR Suggestion

Since he just wants one update a day with an overview of feedback items, his settings look like this:

Recruiter

Our recruiter is very interested what people think about our Jobs pages. Do potential applicants like our job postings, do they have questions? She'd like to know. Because she receives automatic emails, she hardly ever has to log in to the Usabilla backend. She getsall the data she needs in her inbox.

Her saved filter looks like this:

Buttons: Usabilla.com - Desktop, Usabilla.com - Mobile

URL (starts with): https://jobs.usabilla.com/

Her saved search is saved like this:

Data analyst

Our data analyst doesn't work in Usabilla itself, but wants to receive periodical exports of all the feedback that we receive in Usabilla. He works with Automatic Exports. You can set these up by clicking the Export button, and pick 'automatic export'.

Next he configured the automatic export to arrive weekly on a Wednesday in the email settings:

Just a few examples of stakeholders within our teams, who use different filters to get the feedback that's relevant for them.

You can let Usabilla Live automatically push feedback responses to your Desk.com setup (formerly Assistly). This way you can directly reply and manage Usabilla Live feedback responses in your customer support environment. To integrate Usabilla for Websiteswith Desk.com, please follow the steps below.

Setting up Desk.com for Integration with Desk.com

Go to your Desk.com admin environment: https://[your sub domain].desk.com/admin.

Make sure you have admin rights in Desk.com.

Alternatively, ask your desk.com administrator to perform these steps.

Go to “Settings”.

Click on “API”.

Click on the “+ Add API Application” button.

Fill in the name form field, for example with “Usabilla Live” and the Website URL form field with “http://usabilla.com”.

The callback URL and Support URL can be left blank.

Then click the “Add” button.

The Usabilla Live API application with its credentials has been created in Desk.com. Now you have to fill in these credentials in the Usabilla Desk.com integration section. To enable and set up the Desk.com integration you will need to go to your Usabilla Account Setting. Please follow the steps below:

Open a new browser tab

Go to https://app.usabilla.com

Login with your credentials and click on your name in the top-right corner.

In the dropdown click on "Account settings"

In the account setting, you will see several tabs where you can change your settings

For setting up the integration click on the "Live Integrations" tab.

In the "Live Integration tab" click on the desk.com logo to create a new integration.

You can have multiple integrations set-up with the same feedback button. You are however only able to set up 1 integration of each type per button.

After clicking on the Desk.com logo you will be prompted with a window that contains al the settings that need to be set to get the Desk.com integration up and running. The steps below explain what need to be set for each of fields.

Setting up Usabilla for Integration with Desk.com

Select the button you would like to create the desk.com integration for

Select when you would like Usabilla Live to push the feedback response:

When the feedback response has an email address

When the feedback response has a comment

When the feedback response has an email address or comment

Send all feedback responses

Enter your desk.com subdomain (e.g. http://subdomain.desk.com).

Enter the key of your desk.com API application.

Enter the secret of your desk.com API application.

Enter the token of your desk.com API application (click in the desk.com admin on "Your access token").

Enter the token secret of your desk.com API application.

Check "Enable" to activate the desk.com integration for the selected button.

You can always disable it later.

Click save and your desk.com integration has been set up.

You can always edit your integration later to change the configuration or disable/enable the integration. If there is any other integration you are looking for, please let us know.