• 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-paste the single-line integration code that we provide you in the Workbench
  See example: https://www.excentos.com/de/how-it-works-integration
• existing Quick Test possibility that allows you to run a test in your website if and how the Product Guide will integrate.
  See Quick Test documentation: https://www.excentos.com/en/documentation/site-integration#quicktest

there are no "real serious" disadvantages.

However, please be aware of the following:

• in very rare cases, we encountered conflicts of the website's CSS or JavaScript with excentos CSS and JavaScript classes. We then had to 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)

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 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)