Skip to main content
All CollectionsGetting Started
How Can I Set up a Single Sign-On to Access Outbrain DSP?
How Can I Set up a Single Sign-On to Access Outbrain DSP?
Updated over a month ago

NOTE: Beginning on August 6, 2024, Outbrain is unifying the login experience for both users using Outbrain's native DSP (formerly Zemanta) and Ad Manager, Amplify. This update eliminates the need for separate login credentials across both the Outbrain DSP and Amplify platforms. Consequently, some accounts may need to update their credentials to continue accessing the platforms after the release of SSO. The detailed instructions for the transition from separate logins to a single sign-on (SSO) authentication process and the two-factor authentication setup are outlined below.

Unlock Simplified Campaign Management with Outbrain's Single Sign-On (SSO)

Outbrain offers multi-channel advertising on the open web, allowing you to easily buy directly from Outbrain Amplify or use your preferred DSP, including our native DSP solution.

The use of Single Sign-On (SSO) authentication simplifies access for advertisers using both Outbrain Ad Manager, Amplify, and native Outbrain DSP (previously Zemanta) by requiring only a single set of login credentials. This unified access not only saves you time; it also streamlines your cross-funnel buying and empowers you to scale campaigns more effectively across the open web.

Additionally, we have implemented mandatory two-factor authentication to ensure your campaigns and data remain protected with the highest level of security.

Transitioning to Single Sign-On:

If you are a user with access to both Amplify and DSP (previously Zemanta):

  • Login credentials: Clients with access to both Amplify and DSP (previously Zemanta) platforms used to have separate login credentials for each. With the release of a single-sign-on authentication process, you will use only your Amplify credentials to access both platforms.

  • 2FA: As an Amplify user, you should already have two-factor authentication (2FA) established.

If you are a user of DSP (previously Zemanta):

  • Login credentials: As a result of the unifying sign-on experience, DSP (previously Zemanta) only users are required to update their passwords via the link received in the “Forgot password?” email sent from our dashboard.

  • 2FA: To strengthen security measures, Outbrain DSP users are also required to set up two-factor authentication (2FA) to access the platform. Detailed instructions for implementing 2FA are provided in the second section of this article.

If you are a user of only Amplify:

  • Login credentials: Users who only access Amplify and do not use Zemanta (Outbrian DSP) should continue logging in using their existing Amplify passwords.

  • 2FA: All Amplify users should also already have the 2FA set up.

If you are an API User:

  • Login credentials: API users act as two-in-one; users to access the dashboard and user to access the API pipelines.
    - API tokens and passwords are not changing, there is no change in API behavior, links, or access.
    - If the User is used to access the dashboard, one of the above examples applies based on access permissions (Amplify and Zemanta, Zemanta/DSP only).

Q&A:

What if the link I received in the Forgot password email is not working?

If you tried to reset the password via the link received in the Forgot Password email and the link is not valid, simply go to dsp.outbrain.com (or my.outbrain.com/login) and click 'Forgot password'. By following this simple step, you'll receive a new, valid link to access the platform without any hassle.


How to set up Two-Factor Authentication?

What is two-factor authentication?

Two-factor authentication is an account verification method that requires users to prove their identity in two steps before gaining access to the dashboard (such as logging in plus verifying via email). This differs from standard one-step authentication, which simply requires the user to enter their login credentials.

Why did we add two-factor authentication to Outrain DSP?

We decided to add two-factor authentication to the dashboard (and later make it mandatory for all users) as part of an ongoing effort to increase account security and privacy. Two-factor authentication adds a protective layer to users’ accounts and makes it much more difficult for online predators to steal login credentials or other information. Two-factor authentication is also standard across the SaaS space and is a very common means of identity verification used by big players like Google and Facebook.

Who uses two-factor authentication?

All external users are required to set up two-factor authentication in order to gain access to the dashboard.

What authentication methods are available, and how do they work?

Users can choose from two authentication methods:

  1. Email verification: Upon logging in, a unique code will be sent to the user’s dedicated email address. They will need to enter that code on the dashboard to prove their identity and complete the login process.

  2. *RECOMMENDED* Preferred authenticator app, e.g. Google Authenticator: Upon logging in, a unique code will be sent to the user’s dedicated authenticator app. They will need to enter that code on the dashboard to prove their identity and complete the login process. This method requires an additional integration process when the user first sets up their two-factor authentication. Users who select the authenticator app as their preferred method will also have the option to set up two-factor authentication by scanning a QR code.

How often will users need to verify their identity via two-factor authentication?

External users will need to verify their identity with two-factor authentication whenever they log in, however, a login is only forced every 7 days; the dashboard can be open on a browser for up to one week before the authentication process is reinitiated. There is a “Trust this Device” checkbox for users to select if they’d like to extend this period to a month.

Is there anything users should keep in mind regarding login credentials?

We strongly recommend that each dashboard contributor have their own unique login tied to their dedicated email address. This not only reduces the potential risk of login information exposure to online predators but also enables them to select email verification as their preferred method of two-step authentication if they so choose.

Did this answer your question?