---
title: "Data pipelines: CDP integrations"
source: PostHog Documentation
source_url: https://github.com/PostHog/posthog.com
licence: MIT
domain: data-and-analysis
subdomain: posthog-docs
date_added: 2026-04-25
---

Data pipeline provides a full-featured customer data platform (CDP) in PostHog, with full-service integrations for ingesting, transforming, and sending data to destinations:

- **Transformations** extend PostHog's functionality by filtering and transforming analytics data. 

- **Sources** let you [ingest data](/docs/cdp/sources) from your existing systems, and join them to existing person and event data using [data warehouse](/docs/data-warehouse). 

- **Destinations** send PostHog data to other sources in [realtime](/docs/cdp/destinations) or as [batch exports](/docs/cdp/batch-exports) which reliably send data to a destination on a schedule.

## Billing for data pipelines

For information about data pipeline pricing and billing, please visit our [pricing page](https://posthog.com/pricing).

## Use cases

Pipelines can be used for a wide variety of use cases, such as:

- **Send event data to a data warehouse.** If you have a data lake or data warehouse, you can use destinations to send PostHog event data there, while ensuring you still have that data in PostHog to perform your analytics processes.

- **Send event data via webhooks.** You can use our realtime destinations to send event data to external services through [webhooks](/docs/cdp/destinations/webhook). This is useful when you want to push event data to tools like [Slack](/docs/cdp/destinations/slack), [Hubspot](/docs/cdp/destinations/hubspot), or [Intercom](/docs/cdp/destinations/intercom).

- **Enforce event schemas.** By default, PostHog does not enforce schemas on events it receives. However, a transformation could do so, preventing ingestion of events that do not match the specified schema in order to keep your data clean and following specific guidelines you need it to follow.

- **Label events.** To facilitate sorting through your events, you can use transformations to determine arbitrary logic to label an event (e.g. by setting a `label` property). This can help you tailor your metrics in PostHog, as well as facilitate data ordering if you ever use PostHog data elsewhere.

- **Correlate costs with impact.** You can [use the data warehouse](/blog/data-warehouse-at-posthog) to import cost data from sources like ads and cloud infrastructure platforms, and then use it in queries alongside product data to understand the impact and ROI of your spend. 

For a full list of transformations and destinations currently available, see the [destinations](https://app.posthog.com/data-management/destinations) and [transformations](https://app.posthog.com/data-management/transformations) tabs under data pipeline in-app.
