Hosting an Experience on your domain
How to host a Monterosa Experience on your website seamlessly
When embedding an Experience via an iframe, modern browsers may treat the embedded webpage as "" and limit its functionality. That is because the web domain of the parent page (your website) is different to the web domain of the embedded Experience, so from the browser perspective it looks "foreign".
This may cause various undesirable effects, e.g. disable analytics functionality in Apple Safari due to its ITP (Intelligent Tracking Prevention) initiative or block the Experience's ability to keep its state in Google Chrome's Incognito Mode due to its default Third-Party Cookies settings.
Google plans to extend Chrome's limitations for Third-Party Cookies to a normal (i.e. non-Incognito) browsing mode by the end of 2024. Other browsers are likely to follow the suit.
Solution
To ensure these and other issues are prevented, we recommend hosting the Monterosa embedded Experience on the same domain as its parent page using either a sub-domain or a sub-page.
Sub-domain
This is typically the simplest solution to set up.
If your website's domain is "yourwebsite.com" then we will liaise with your IT team to make our Experience available at a URL that may look like this: "https://interact.yourwebsite.com/experiences/1.0.0/".
As you are the owner of the domain, your IT team will have to "allow" this setup by adding two records to your DNS configuration at our request: one to allow the domain "redirect" (CNAME to our CloudFront distribution) and another to enable HTTPS (ACM's DNS validation).
Sub-page
This is the preferred option if DNS manipulations are impossible for technical or policy reasons.
If your website's domain is "yourwebsite.com" then we will liaise with your IT team to make our Experience available at a URL that may look like this: "https://interact.yourwebsite.com/experiences/1.0.0/".
This configuration requires a more complicated setup on your end and its details depend on the content delivery technology you use. In most cases we will work with your IT team to add a "rule" or "behaviour" to your CDN configuration that will pass the traffic that reaches your website via a specific path — e.g. "/experiences/*" — to our infrastructure.