Outseta across multiple domains | Outseta Knowledge Base

It is possible to use Outseta across domains such as mydomain.com, app.mydomain.com, and learn.mydomain.com.

However, there are things to look out for regarding Protected Content and Authentication.

Protected Content

Protected content will apply across all domains. If you add a protected content group using the rule "starting with the-course" you cannot have a public sales page on mydomain.com/the-course as it will be protected on both domains.

When working across domains, it's worth taking some time to develop a URL structure that makes sense across domains for your use case.

The above example could be solved by having the course sales pages nested under courses.

If you are looking to protect an entire domain, a common scenario is when hosting an app on app.mydomain.com and the marketing site on my domain.com that is also possible with a custom snippet.

Authentication

By default, authentication does not persist across domains, meaning your users must log in for every domain.

To change that, configure Outseta to use a cookie for the token storage method in your head script, and your users' auth state will persist authentication across domains.

<script>
<!-- Outseta Script Options -->
  var o_options = {
    domain: "<your domain>.outseta.com",
    tokenStorage: "cookie",
    // the rest of your configuration //
  };
</script>

<!-- Outseta Script (doing all the magic) -->
<script src="https://cdn.outseta.com/outseta.min.js" data-options="o_options"></script>