The UID2 framework enables publishers to integrate in either of the following ways:
- Via the standard integration workflow, using the UID2 SDK for JavaScript (also known as the UID2 SDK).
- Via the server-only (custom) integration workflow, by building a direct integration without using the UID2 SDK.
If you are a content publisher interested in generating UID2 tokens for the real-time bidding (RTB) bid stream and want to see how you can use the UID2 services and which integration fits your needs best, you can build and run an example application for each integration.
The following table summarizes both examples and provides links to the example applications, their documentation, and the respective step-by-step integration guides.
| Environment | Documentation | Description | Primary Audience | Integration Guide |
|---|---|---|---|---|
| Node.js | UID2 SDK Integration Example | Demonstrates how to use the UID2 services with the UID2 client SDK to implement the standard UID2 integration workflow. | Publishers with web assets | Client SDK Integration Guide |
| Node.js | Server-Only UID2 Integration Example | Demonstrates how to use the UID2 services to implement a custom (server-only) UID2 integration workflow without relying on an SDK for establishing client UID2 identity and retrieving advertising tokens. | App developers and CTV broadcasters | Server-Only UID2 Integration Guide |
| Java | Java SDK Integration Example | Demonstrates use of the UID2 Java SDK for both a server-only UID2 integration, and a standard (client SDK and server SDK) integration. | Publishers with web assets, app developers, CTV broadcasters | Server-Only; Client SDK |
The example applications illustrate the basic steps that you need to consider for your integration. For example, you need to decide how to do the following:
- Implement user login and logout.
- Manage UID2 identity information and use it for targeted advertising.
- Refresh tokens.
- Deal with missing identities.
- Handle user opt-outs.