Brands have historically faced challenges connecting fragmented customer data with third-party identity systems due to privacy, compliance, and data-sharing hurdles. Stagwell’s deployment of a privacy-preserving identity matching application on Databricks Marketplace changes this by allowing brands to run secure matching workflows directly within their own cloud infrastructure.

  • Deploy identity matching apps in minutes without exporting sensitive data
  • Leverage Databricks governance and clean room tech for privacy-safe workflows
  • Reduce compliance bottlenecks and improve developer efficiency

Infrastructure signal

The introduction of Databricks Marketplace Apps represents a key shift in cloud data infrastructure by enabling containerized applications to run entirely within a brand’s own Databricks environment. This eliminates the need to move raw customer data to third parties, significantly mitigating privacy and compliance risks while preserving data governance using Unity Catalog’s access controls.

Stagwell’s identity matching application uses this architecture to integrate clean rooms for secure data collaboration, allowing brands to connect their first-party data to Stagwell’s identity spine without network data leakage. This approach decreases deployment time from months to minutes and facilitates streamlined, standardized identity workflows that scale efficiently across cloud compute resources.

Developer impact

Developers benefit from simplified workflows because the app runs where the data resides, eliminating the need for complex data export processes and bespoke secure data pipelines. The containerized app model abstracts proprietary matching algorithms, protecting intellectual property while providing a consistent interface via React and Express layers to interact with identity matching processes.

The use of multiple scoped identity tokens—covering brand user authentication, app-level operations, and backend API calls—supports granular security and auditability. Databricks Jobs and Notebooks serve as the execution backbone for the matching algorithms, giving developers an integrated environment to customize and monitor workflows without compromising data privacy.

What teams should watch

Teams responsible for cloud cost management should anticipate reduced overhead in long-running data transfers and manual compliance reviews, given the faster deployment and embedded governance model. Identity and data governance teams need to evaluate the implications of deploying containerized apps within Unity Catalog boundaries to ensure proper access controls and audit trails remain intact.

Product and engineering units should monitor this shift towards in-place data processing models for identity graph matching as it may redefine partner integration strategies and accelerate time-to-value for audience segmentation and activation. Observability metrics around clean room lifecycle, app telemetry, and user token usage will become critical to maintain confidence in data privacy and operational reliability.

Source assisted: This briefing began from a discovered source item from Databricks Blog. Open the original source.
How SignalDesk reports: feeds and outside sources are used for discovery. Public briefings are edited to add context, buyer relevance and attribution before they are published. Read the standards

Related briefings