How can PubMatic improve its Identity Hub to better unify fragmented user IDs across platforms?

Introduction

To improve PubMatic's Identity Hub and better unify fragmented user IDs across platforms, we need to dive deep into the current state of the product, understand user pain points, and develop innovative solutions. I'll approach this challenge by first clarifying key aspects of the product, then analyzing user segments and their pain points, before proposing and evaluating potential solutions.

Step 1

Clarifying Questions

• Looking at the product context, I'm thinking about the primary use cases for PubMatic's Identity Hub. Could you help me understand the main scenarios where publishers and advertisers are using this tool to unify user IDs?

Why it matters: This will help us focus our improvements on the most critical functionalities. Expected answer: Identity Hub is primarily used for cross-device targeting and frequency capping. Impact on approach: We'd prioritize solutions that enhance these core use cases.

• Considering user behavior, I'm curious about the current success rate of ID unification. What percentage of user IDs are we currently able to successfully unify across platforms?

Why it matters: This will help us gauge the scale of the problem and set realistic improvement targets. Expected answer: Currently achieving 60-70% unification rate. Impact on approach: If low, we'd focus on improving the core matching algorithm; if high, we'd look at edge cases and expanding coverage.

• Regarding product lifecycle and company alignment, where does improving the Identity Hub fit into PubMatic's broader strategy? Are we looking to differentiate ourselves in the market or catch up to competitors?

Why it matters: This will help us align our solution with the company's strategic goals. Expected answer: We're aiming to differentiate and become the market leader in identity resolution. Impact on approach: We'd focus on innovative, unique solutions rather than just matching competitor features.

• Considering external factors, how has the recent focus on user privacy and regulations like GDPR and CCPA affected our ability to unify user IDs? What constraints are we working within?

Why it matters: This will help us ensure our solutions are compliant and future-proof. Expected answer: We're limited in the types of data we can use and how long we can store it. Impact on approach: We'd need to focus on privacy-preserving techniques and consider first-party data strategies.