Treasure Data CDP,
fed by server-side events.
Treasure Data is the enterprise CDP that unifies customer data across every channel — web, mobile, CRM, point-of-sale, and more. But the web data flowing in through browser-side SDKs is increasingly incomplete. Ad blockers strip events. ITP fragments identities. Consent banners gate the JavaScript before it loads.
Ingest Labs streams events to Treasure Data server-side — enriched with first-party identity, delivered in real time, and gated by user consent. Your CDP gets complete, identified event streams without browser dependencies, so customer profiles are richer and audience segments are accurate.
Why Treasure Data + Ingest Labs
A CDP is only as valuable as the data it ingests. Treasure Data excels at unification, segmentation, and activation — but those capabilities are undermined when the web event stream is full of holes. Missing events create incomplete profiles. Fragmented cookies produce duplicate records. Blocked scripts mean entire user sessions never reach the CDP at all.
Server-side event collection solves these problems at the source. Instead of depending on a browser-side SDK to collect and transmit events, Ingest Labs captures events at the server edge — before ad blockers, ITP, or consent banners can interfere. Every event is enriched with a persistent first-party identity that Treasure Data can use as a unification key.
The result: fewer orphaned profiles, more complete customer journeys, and audience segments built on the full picture — not the shrinking subset that survives the browser.
Integration resources
Setup guide for the Treasure Data destination, including event schema mapping and identity configuration.
Contact for setup guide
Treasure Data — where your customer profiles, audience segments, and activation workflows are managed.
Visit Treasure DataTreasure Data's official API and SDK documentation — ingestion, schema, and integration reference.
Treasure Data docsKey benefits
Complete, identity-resolved event streams flowing into your CDP — no browser dependencies, no data gaps.
- Stream events to Treasure Data in real time via server-to-server API — no browser SDK required
- Enrich every event with persistent first-party identity for cleaner profile unification
- Eliminate orphaned profiles caused by ITP cookie expiration and cross-device fragmentation
- Capture web events that ad blockers and privacy browsers strip from client-side collection
- Enforce GDPR, CCPA, and custom consent policies at the server level before data reaches the CDP
- Normalize event schemas before ingestion — clean, queryable tables without manual ETL
Frequently Asked Questions
How does Ingest Labs send data to Treasure Data?
Ingest Labs streams events to Treasure Data's ingestion API in real time, server-to-server. Every event is enriched with first-party identity — hashed email, user ID, device fingerprint — before delivery. This means your CDP receives identified, structured events without depending on browser-side JavaScript or third-party cookies.
What types of events can I send?
Any event your site or app generates — page views, purchases, sign-ups, form submissions, product interactions, and custom events. Ingest Labs normalizes the event schema before delivery so your Treasure Data tables stay clean and queryable without manual ETL.
Does this replace Treasure Data's JavaScript SDK?
It can. Treasure Data's browser SDK is subject to ad blockers, ITP, and consent restrictions. Ingest Labs collects events server-side and delivers them to Treasure Data's API, bypassing browser limitations entirely. You can also run both in parallel during migration.
How does first-party identity improve my CDP data?
CDPs are only as powerful as the identities they can resolve. When browser cookies expire or are blocked, visitor profiles fragment — the same person appears as multiple anonymous records. Ingest Labs maintains a persistent first-party identity that Treasure Data can use as a unification key, producing fewer duplicates and richer customer profiles.
Is this GDPR and CCPA compliant?
Yes. Ingest Labs enforces consent at the server level. Events are only streamed to Treasure Data when the user has granted the appropriate consent. Consent decisions are logged for audit, and data can be partitioned by consent status for downstream compliance workflows.
How long does setup take?
Most customers are streaming events to Treasure Data within 24 hours. You connect your Treasure Data API credentials in the Ingest Labs dashboard, configure your event mapping, and real-time server-side delivery begins immediately.
Ingest Labs Treasure Data integration: Server-side event streaming into Treasure Data's enterprise CDP. First-party identity resolution for cleaner profile unification. Real-time delivery without browser dependencies. Eliminates data gaps from ad blockers and ITP. GDPR and CCPA compliant. Live in under 24 hours.
Feed Treasure Data complete, identity-resolved events — in real time.
Server-side event streaming, first-party identity, and consent-aware delivery for your enterprise CDP.