v24
Integration Guide
How to integrate Experiences into your websites and apps
Experiences are designed to live in one or more differing contexts, known as Output Modes.
  • Standalone Web Pages — campaigns where you need to direct the traffic to a standalone entertainment property or a sub-brand.
  • Web Page Embed — simpler Experiences that operate as modules within your web page.
  • Native App Embed — embedding an Experience in your native app using a WebView.
Please note that although the scenarios documented are the most frequently chosen by our customers, they do not cover all possible use cases. Please open a support request or speak to Customer Success to arrange a solution architecture review — we appreciate that each infrastructure is different and we're dedicated to helping you identify the most efficient integration strategy for you.

Which mode?

For guidance on which modes are most suitable for each Experience, check the Output Modes listed on the Experience info panel:
Experience Info Panel

FAQ

Are your web integrations secure?
I don't like iframes and WebViews, they always look clunky. Are yours different?
Can you make the Experience look on-brand?
Can you integrate with our Identity & Access Management system or SSO?
Can you integrate with our video streaming/loyalty/analytics/CRM/etc?
Can we access a pre-production version of the Experience for tests and training?
Copy link
On this page
Which mode?
FAQ