OliviaWeb

Hello there! This is a site that is meant to showcase an OpenWeb SSO experience.

OpenWeb can support one of two types of registration flows:

OpenWeb's Built-in Registration Flow (nonSSO)

• Conversation will come with an out-of-the-box registration solution for publishers who do not have their own user management or registration systems.
• No additional development work needed, built in registration flow that works once Conversation is implemented.

Here are some examples of OpenWeb's nonSSO registration flow:

• OliviaWeb (Olivia's nonSSO test site)
• The Drive
• Refinery29

Notice the behavior when a user goes to log in or register with OpenWeb. On publisher sites with OpenWeb's built-in registration flow (nonSSO), the user is presented with the same OpenWeb popup modal for all sites. This is how the registration flow will appear for all sites using this method because OpenWeb is providing the functionality.

Integrate with Publisher's Existing Registration Flow (SSO)

• Conversation will come without a registration flow, and the publisher is expected to connect/integrate their own user management & registration system with OpenWeb.
• Additional development work needed, this can add anywhere from 1-4 weeks to the estimated implementation time depending on the publisher, so please reach out to sales engineering for proper expecations.

Here are some examples of publisher's SSO registration flow:

• OliviaWeb SSO (📍You are here)
• Yahoo!
• Fox News
• New York Post

Now, notice the difference in behavior when a user logs in or registers with OpenWeb. On publisher sites where they've integrated OpenWeb with their own user management system (SSO), the user is instead presented with the publisher's sign in and sign up flow. This means the registration modal (or separate page) will appear different for each of these sites because the publisher owns and manages the functionality.

Important things to remember:

• The publisher will always own their user data, or be able to access it at any time, no matter the registration method. This is in compliance with GDPR & CCPR regulations.
  • If they are nonSSO, we can get them their user data via scheduled or manual reports.
  • If they are SSO, the publisher can use our Export and Delete User Data API.

Feel free to visit my article pages and check it out for yourself: