Embedded and OEM integrations
In partner-to-partner OEM or "Powered by" integrations, where one Connected Partner's product is integrated through another partner's platform, the host platform must preserve or append the embedded partner's User-Agent identifier in outbound Databricks requests so telemetry can be attributed to the correct partner.
Requirements
| Requirement | Description |
|---|---|
| Host Platform Support | The host platform must preserve or append the embedded partner's identifier in outbound Databricks requests |
| Embedded Partner Attribution | Embedded partners are responsible for coordinating with the host platform or OEM provider to ensure their Partner-specific User-Agent identifier is preserved or appended in outbound Databricks requests |
| User-Agent Format | Use the standard format described in the User-Agent format guidance |
What's next
- Review User-Agent format: Understand the required format and guidelines.
- Validate implementation: Verify User-Agent attribution using Query History or system tables.
- Review integration requirements: See Integration Requirements for all Connected Partner onboarding requirements.