Design the event instrumentation for Experience Cloud at scale at global scale

Problem Statement Description

Product context: Adobe is a creative, document, and marketing software company; its products include Creative Cloud, Photoshop, Illustrator, Acrobat, Adobe Express, Firefly, and Experience Cloud.

Adobe Experience Cloud serves enterprise marketing teams and agencies that manage campaigns, audiences, assets, journeys, analytics, and personalization across many clients, regions, brands, and channels. In this interview, you are asked to design the event instrumentation approach that would let Experience Cloud capture, process, and make product and customer-interaction events useful at global scale.

Assume the instrumentation must support multiple Experience Cloud products and workflows, including campaign setup, audience management, content personalization, reporting, collaboration, AI-assisted marketing tasks, and agency-client account structures. Events may come from web apps, APIs, SDKs, integrations, and backend services, and they must be reliable enough for analytics, experimentation, billing-adjacent insights, customer success, compliance, and operational monitoring.

The challenge is not to design a single tracking pixel or analytics dashboard. It is to define how a large enterprise platform should model, collect, validate, govern, transmit, store, observe, and evolve events while balancing latency, data quality, privacy, cost, developer usability, and global regulatory constraints.

The instrumentation design should consider:

- Core event taxonomy, naming conventions, schemas, required fields, versioning, and ownership across Experience Cloud products

- User, account, agency, brand, workspace, campaign, and tenant identifiers, including how identity should work across products and integrations

- Collection paths across client-side, server-side, SDK, API, and third-party integration events, including offline or delayed events

- Reliability requirements such as delivery guarantees, deduplication, ordering, retries, backpressure, and data loss detection

- Privacy, consent, regional data residency, sensitive-data handling, access control, retention, and enterprise auditability

- Data quality mechanisms including validation, schema enforcement, monitoring, anomaly detection, and debugging tools for internal teams

- Rollout and migration approach for existing products, including developer adoption, backward compatibility, documentation, and governance

- Observability and decision usefulness for downstream consumers such as product analytics, experimentation, customer success, security, and platform operations

Your goal is to frame the technical product requirements and trade-offs for an instrumentation platform that can scale across Adobe’s enterprise marketing ecosystem, support agency workflows, and maintain trust with global customers while enabling teams to make better product, operational, and customer decisions.