CONNECTIONS / Cloudian
Cloudian + Datahash: HyperStore exports become signals.
Cloudian HyperStore runs S3-compatible object storage inside your own data center, giving compliance-heavy teams full control over where conversion data lives. Signals connects to that private endpoint, reads files as they land, and delivers hashed events to your ad platforms.
- ● cloudian :: signals live
- > object arrived s3://hyperstore-prod/orders/2026-07-18.csv
- > parse rows=64,890 schema=orders
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 82%
The signal Cloudian yields, and receives.
Every kind of signal that moves between Cloudian and the platforms, through one hashed, deduplicated route.
- Offline conversions
- HyperStore sits inside your own data center, so scheduled pickup points at your private S3-compatible endpoint rather than a public cloud bucket, and each new export is picked up on the same schedule regardless of where it is hosted.
- Lead conversions
- Enterprise export jobs often carry legacy column names from internal systems, so the mapper translates whatever a HyperStore bucket contains into consistent event fields without asking your team to reformat anything upstream.
- Custom audiences
- Identifiers are SHA-256 hashed as each file is read from your private endpoint, and the file itself is discarded after processing, which matters for teams running Cloudian specifically to keep data off public infrastructure.
- Lead generation inbound
- Row-level status is reported back per file, so a compliance team auditing what left the private endpoint can see exactly what was processed and what was quarantined.
Pick your platform. Every use case for it, in one place.
Every way Cloudian data moves, grouped by platform and ranked by how many use cases Cloudian supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Cloudian with scoped, read-only credentials to your HyperStore endpoint.
-
Watch
Choose the bucket and file pattern on your private endpoint to watch.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
Cloudian questions, answered.
Which file formats are supported?
Delimited files such as CSV and TSV with configurable headers are the common case, and fixed-width exports from legacy internal systems can be handled through the column mapper. You point Signals at a bucket and file pattern on your HyperStore endpoint, and any matching object is parsed as it lands.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud, with the source file discarded once processed. Since Cloudian is often chosen to keep storage inside a private data center, a self-hosted Core deployment is available so hashing itself happens on your own infrastructure.
Does data ever leave our private HyperStore endpoint?
Signals connects directly to the endpoint you configure and reads only the files matching the prefix and pattern you set. Rows are hashed on read and the object is discarded after processing, so nothing from your HyperStore cluster is retained. Self-hosted Core keeps the entire pipeline inside your own environment if required.
NEXT STEP
See your Cloudian data working in every ad platform.
Ready to enable a use case, or still mapping what Cloudian data could do? Our team helps you find the right place to start.
