Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: wording, grammar

...

Info

This page describes the different frontend front end technologies of integrating the Product Guide into your website or applications.

(smile) If you don't want to get into the details, just follow our recommendation to use the JavaScript integration.


Introduction

excentos supports various technologies to integrate the Product Guide into your website or applications.

This overview describes the commonly used default functionalities only; please contact excentos if you want to inquire other ways of integrating the Product Guides as there are far more possibilities.


integrationadvantagesdisadvantagessupported by excentoscomments
JavaScript
  • very flexible integration
excentos is 100% responsible for that look and feel is identical to what you saw in the Workbench's preview
  • you just need to copy
-
  • and paste the single-line integration code that
we provide

there are no "real serious" disadvantages.

However, please be aware of the following:

  • in
very rare
  • some cases,
we encountered
  • there where conflicts of the website's CSS
or JavaScript
  • with excentos CSS
and JavaScript classes. We then had to
  • (especially if the customer's website assigned styles to HTML identifiers instead of using class names)
    • solution: implement a workaround to rename
our
    • excentos CSS classes

(we thus now use "xc" prefix for all CSS classes so CSS conflicts should really be a very rare case)
    • or resolve other conflicts
  • in very rare cases, there were conflicts of the website's JavaScript with excentos JavaScript.
    • solution: excentos will find the conflict and clarify how to solve it
yesit is recommended using the JavaScript integration
iFrame

There is not a significant advantage over using JavaScript. The

yeswe recommend you using JavaScript integrationiFrameWe don't really see any significant advantages. From our point of view, the

only reason to use iFrame integration would be

  • 100% safe against CSS and JavaScript collisions (but see comments on JavaScript integration above)
    • You are thus 100% sure that the look&feel corresponds to what you see in the Workbench preview (unless the iFrame does not use dynamic height)
  • you or excentos will need to provide an iFrame that dynamically adapts to the size of the Product Guide, also in responsive
behaviour
  • behavior (e.g. different height for question cards than for recommendation list)
  • the excentos Analytics do not detect the referrer / website that integrated the Product Guide, so it cannot analyze traffic generation within the excentos Analytics. Also for you as our customer, you will be able analyzing the traffic within the webpage that contains the iFrame, but not be able analyzing the traffic within the iFrame
yes, but may require initial support / customization
we would advice
excentos advises to only use an iFrame if you encountered CSS / JavaScript collisions and if
we
it could not be solved easily
solve them


Further

...

Integration Technologies

If you want to use another integration (e.g. web components, build your own user interface based on our API) please contact our support.