CDP Microsoft Ads w/ Enhanced Conversions

Feature request

Is your feature request related to a problem?

Yes, the lack of a Microsoft Ads destination in PostHog’s data pipeline means we cannot seamlessly send user event data (e.g., enhanced conversions) to Microsoft Ads for better ad attribution and targeting. While a Google Ads destination exists, this limits our ability to fully leverage PostHog’s potential across multiple advertising platforms.

Describe the solution you'd like

I would like a Microsoft Ads destination similar to the existing Google Ads destination. This would include:

• Support for sending hashed user identifiers (e.g., email, phone) to Microsoft Ads for enhanced conversions.
• Easy integration with PostHog events, allowing selected events to be forwarded to Microsoft Ads.
• Configurable mapping of PostHog properties to Microsoft Ads’ required fields.

Describe alternatives you've considered

• Manual Uploads: Exporting user data from PostHog, formatting it, and uploading it manually to Microsoft Ads. This is time-consuming and error-prone.
• Third-Party Tools: Using external platforms like Zapier or Segment to bridge the gap. However, these add complexity and cost to the workflow.
• Custom Scripts: Building custom integrations via the Microsoft Ads API, but this requires significant development effort and maintenance.
• Google Tag Manager: We currently use GTM to send events to Microsoft Ads. We'd rather use PostHog as our source of truth for this rather than managing an integration in multiple places.

Debug info

- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

The issue does not identify implementation files, tests, or an entry point; begin by locating the existing Google Ads destination and PostHog data-pipeline integrations. Done means Microsoft Ads can receive selected PostHog events with hashed identifiers and configurable mappings for enhanced conversions.