Skip to content
  • There are no suggestions because the search field is empty.

How can I test Widgets 2.0 Before the automatic migration

Table of Content

 

Overview

Widgets 2.0 are the next generation of Feefo display tools, built to be lighter, more compliant, and more accessible. Whether you've already enabled 2.0 or are still preparing to migrate, you can start testing the widgets ahead of our end-of-August migration.

 

What should I know before testing

  • If your site uses fully bespoke, non-Feefo widgets, the toggle will not update those displays. In that case, direct implementation of Feefo widget code is required before Widgets 2.0 can be tested.

  • Testing is mainly intended to validate front-end behaviour such as layout, spacing, styling, responsiveness, and how the widgets fit within your site design.

  • Changes usually appear quickly, typically between immediate and 5 minutes after enabling the toggle. In a small number of cases, caching can take longer.

Important: Custom CSS built for older widgets will not carry across to Widgets 2.0. If a client has heavily customised legacy widgets, the test should focus on identifying styling differences and deciding whether the standard 2.0 design is acceptable.

 


How clients can test Widgets 2.0

Option 1:  If you use the Feefo widgets and have not toggled on

The following instructions would allow you to check all of the settings in the staging environment first and then promote to production when you are happy.

Note, additional customisations will be available for all of the widgets in hub.

 

Firstly, add this script alongside the existing bootstrap script

New bootstrap;

<script src="https://api.feefo.com/feefo-widgets-data/loader/widgets/{merchant id}" type="text/javascript"></script>

Exiting bootstrap;

<script type="text/javascript" src="https://api.feefo.com/api/javascript/{merchant identifier}" async=""></script>

 

 

Then test the new widgets by using the following code snippets:

On Page

Product:

<feefo-product-reviews sku="product-sku" version="20"></feefo-product-reviews>

Service:

<feefo-brand-reviews version="20"></feefo-brand-reviews>

 

Slide-out

<feefo-slideout></feefo-slideout>

 

Score Badge

<feefo-score-badge></feefo-score-badge>

 

Service Carousel

<feefo-service-carousel></feefo-service-carousel>

 

Product Stars

<feefo-product-stars sku="product-sku"></feefo-product-stars>

 

Pop-up

Product:

<feefo-product-pop-up sku="product-sku" version="20"></feefo-product-pop-up>

Service:

<feefo-pop-up version="20"></feefo-pop-up>

 

 

Option 2: If you use the feefo legacy or optimised widgets and have already toggled on they can test the new widgets by using the following code snippets:

Score Badge

<feefo-score-badge></feefo-score-badge>

 

Service Carousel

<feefo-service-carousel></feefo-service-carousel>

 

Product Stars

<feefo-product-stars sku="product-sku"></feefo-product-stars>

 

Pop-up

Product:

<feefo-product-pop-up sku="product-sku" version="20"></feefo-product-pop-up>

Service:

<feefo-pop-up version="20"></feefo-pop-up>

 

What clients should test on their website

When testing Widgets 2.0, you should review both appearance and behaviour. We encourage you to check the following:

  • Desktop, tablet, and mobile layouts

  • Page spacing and container fit

  • Font size and readability

  • Review expansion and collapse behaviour

  • Modal behaviour for pop-ups and overlays

  • Scroll behaviour, especially for pages with sticky headers

  • Attribute display where many review attributes are shown

  • Locale behaviour if the account uses restricted locales or translated content

  • Badge and product star behaviour if these are in use alongside the main review widgets

Note, if there are any issues with the above, additional customisations will be available for all of the widgets in hub.

 

When to contact Support

You should contact Support if:

  • The widget does not change after enabling the toggle

  • The widget appears broken on mobile or within a custom container

  • The current widget relies on heavy CSS customisation

  • You need to revert to the old display 

Test early, review your key pages on mobile and desktop, and let Support know about any styling or rendering concerns before the end-of-August migration so they can be addressed in advance