With UseItBetter, the site owners can add additional logic to their website that enables them to interact with users, change user experience or just collect more information about their journeys based on behaviors and metadata already tracked with UseItBetter.

Such functionality is delivered using Triggers and Responses set up for a specified Segment in the Analytics Panel.


A Response is a predefined module designed to deliver a specific site functionality with little or no coding effort from the website owner. Just to list a few examples, with Responses you can survey the users (e.g. open questions, likert-scale), add users to remarketing lists (e.g. Google Remarketing), extract data from the content users are confronted with (e.g. product price, error messages) or add JavaScript tags (e.g. live chat tag, tracking tag).

Responses are also capable of making changes in a front-end layer of a website: replace or add HTML content, modify CSS and execute JavaScript code. This opens the door to creating even the most complex A/B and multivariate tests and site personalizations.


A segment defined in UseItBetter can be used as a Trigger to fire a Response during a user visit if the user meets the criteria defined in a Segment for which the Trigger was set up. Such criteria can include a combination of specific user interactions (e.g. users who did or didn’t click an element) and metadata about content (e.g. viewed pages) or purchase (e.g. basket value, products in basket), traffic source (e.g. google), user demographics (e.g. age, gender), etc.

Responses can be fired for all users in the segment or for a percentage of users (a test group) while experience of the rest of users (a control group) remains unaffected.

How are users assigned to Trigger’s control and test groups?

When a user starts a visit on a website, the UseItBetter script loads the user’s assignment history from the browser’s LocalStorage. If the history is missing or it contains no information about assignment for one or more enabled triggers, then the user is randomly assigned to a control or a test group based on the trigger’s sampling definition and the assignment is saved in the assignment history in LocalStorage. If the user was previously assigned to a control or a test group, the group assignment is retrieved from the history. This means, that every time the user visits a website using the same browser, he or she will always be assigned to the same group (control or test) as long as the LocalStorage is not cleared.

Previewing Triggered Responses

You can test any Response in the Preview Mode before making it public. To access the Preview Mode, add the:




parameter to the website’s URL.

Ask a Question

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>