1. Home
  2. Getting Started
  3. Publish Your assistants/filters

Publish Your assistants/filters

Now that you have finished editing your assistants and filters, you are ready to publish the solutions and integrate them into your webshop. On the UI tab make sure that you have chosen the right design for your assistant & filter. 

Now go to the “Integrate” Tab:

Click on the button “Activate all Localizations” to take your assistant/filter live. 

After this step, the warning signs will be greyed-out and the publish button will become active – see the turquoise action buttons in the top navigation.

After publishing the assistant/filter, the “Go Live” button will then appear on the right side of the page.  

The assistant is now also locked in this current state – in case you want to make further edits, you will need to create a new draft – again, see turquoise actions buttons in the top navigation.

Click on “Go Live” to take the assistant/filter live. After this step you will be able to retrieve the Javascript integration code by clicking on the respective language:

You will find one Javascript integration code per assistant/filter category. Note, each assistant and filter has its own unique integration code (the code follows the same structure, but each assistant or filter has a different code to identify the solution within the Javascript code)

Please repeat the steps above to publish your assistants/filters for each of your assistant/filter categories. 

If you are utilizing the new Miele brand corner provided by Loadbee your work in the Zoovu platform is now completed. Your assistants and filters will automatically be displayed within the brand corner, as soon as you integrate the Loadbee brand corner integration code into your web-shop. 

 If you are NOT utilizing the Miele brand corner provided by Loadbee please proceed with the steps described in 2.3.1a) below to learn how to integrate the assistants and filters into your website. 

Integrate assistants/filters into Your webshop

The integration of Miele assistants/filters can be completed by copying and pasting a short JavaScript integration code onto a landing page in your web-shop environment. The structure of the integration code remains the same – only the “advisorCode” differs for every individual assistant or filter. 

<script type="text/javascript" src="//api-st.smartassistant.com/api/v1/advisors/advisorCode/js-loader"></script>


<div id="smartassistant-advisor"></div>

div id – the name of the integration container – the custom html element where an assistant/filter will be loaded /rendered. The html content of this element will be replaced with the assistant/filter content. You need to replace ${ADVISOR_INTEGRATION_CONTAINER} with the element’s id.

advisorCode – specifies the assistant code, replace ${ADVISOR_CODE} with the assistant code

Excusus: Javascript  integration vs. iFrame integration

In the “Integrate”-Tab in the zoovu platform you can find both the Javascript and iFrame integration code for each assistant and filter. It is strongly recommended to integrate the assistants/filters using the Javascript code, as it offers several benefits over the iFrame integration method (please see ‘Disadvantages of iFrame integration section below for more details)

Benefits of Javascript integration:

  • Assistants / Filters integrated via Javascript adapt to the browser window size and the device which is used to view the solution. This means an assistant/filter that is integrated via Javascript will behave responsively. A mobile device would be recognized immediately and a mobile-optimized version of the assistant/filter will be displayed.

  • Design elements adapt dynamically to the space available on the webpage where you integrate it. Depending on the available space an infotext may, for example, be displayed differently in two different webshops.

Disadvantages of iFrame integration:

  • No adaptions to different screen and device sizes.
  • No dynamic adaptation of design elements – infotexts can overlap with other elements on your webpage or be cut off due to iFrame windows which are not big enough.
  • No dynamic adaptation of the space needed to display the full assistant/filter – e.g. if you adapt the iFrame size based on questions with only one row of answers, the window could be too small for a longer subsequent question. This may result in the hiding of other elements in the assistant/filter (e.g. Next button, which would prevent the user from completing the assistant journey).
Updated on October 14, 2019

Was this article helpful?

Related Articles