Skip to main content

UID2 Overview for Private Operators

Own the process of generating UID2s from DII in a private environment.

Private Operators

Private Operators of UID2 send first-party directly identifying information (DII) to a secure environment for translation, and control the destinations for those identifiers. A participant that chooses to become a private Operator (previously known as closed Operator) can generate and manage UID2s, running a UID2 Operator service in a private environment.

Learn about what the UID2 framework offers to private Operators, including benefits, hosting options, documentation and other resources, and how to get started.


Here are some of the intended benefits of participating in UID2 as a private Operator:

  • You can maintain privacy-conscious workflows for your customer data to be encrypted and activated across chosen partners.
  • You can participate in UID2 using your own first-party directly identifying information (DII) without sharing it.
  • You have full control of resources, performance, and latency for UID2.
  • You can plan to minimize network hops with a service that can provide regional proximity.
  • You can implement processes and policies that you control, as opposed to taking part in a shared service.

For more information, see The UID2 Operator.

Hosting Options for Private Operators

If you choose to be a private Operator, several implementation options are available. You can do any of the following:

  • Use a cloud services setup. UID2 supports hosting UID2 in an enclave on the following cloud service providers (medium level of effort to implement):
    • Amazon Web Services (AWS)
    • Microsoft Azure
    • Google Cloud Platform (GCP)
  • Use your own machines to generate and manage UID2s (greater level of effort to implement).

Getting Started

  1. Request access to UID2 by filling out the form on the Request Access page.

  2. Decide which implementation option you want to use.

  3. If you're using an SDK, download the SDK. Refer to the applicable SDK guide.

  4. Follow the instructions in the implementation guide for the option you chose.


    Be sure to encrypt request messages to UID2. For details, see Encrypting Requests and Decrypting Responses.

  5. Test.

  6. Go live.

Implementation Resources

The following documentation resources are available for private Operators to implement UID2.

Integration TypeDocumentationContent Description
AWSUID2 Private Operator for AWS Integration GuideInstructions for setting up a Private Operator service for AWS Marketplace.
GCP Confidential SpaceUID2 Private Operator for GCP Integration GuideInformation for setting up the UID2 Operator Service in Confidential Space, a confidential computing option from Google Cloud Platform.
AzureUID2 Private Operator for Azure Integration GuideInstructions for setting up the UID2 Operator Service in a Confidential Container, a confidential computing option from Microsoft Azure.


For a list of frequently asked questions regarding the UID2 framework, see Frequently Asked Questions.