| JavaScript | | there are no "real serious" disadvantages. However, please be aware of the following: - in very rare some cases, we encountered 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)
- We then implement a workaround to rename our 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, we encountered conflicts of the website's JavaScript with excentos JavaScript.
- we then find the conflict and clarify how to solve it
| yes | we recommend using the JavaScript integration |
| iFrame | We 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 (e.g. different height for question cards than for recommendation list)
- the excentos Analytics does not know the referrer / website that integrated the Product Guide, so we 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 to only use an iFrame if you encountered CSS / JavaScript collisions and if we could not easily solve them |