CONNECTIONS / OVHcloud
OVHcloud + Datahash: EU-hosted files become ad signals.
Conversion and CRM exports land in your OVHcloud object storage container, hosted under European jurisdiction. Signals reads each file as it arrives, hashes the identifiers, and routes the rows to every connected ad platform.
- ● ovhcloud :: signals live
- > object arrived ovh://eu-west-rbx/exports/leads-2026-07-18.csv
- > parse rows=18,340 schema=leads
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 76%
The signal OVHcloud yields, and receives.
Every kind of signal that moves between OVHcloud and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A file dropped into the watched OVHcloud container is picked up on its schedule and parsed as it lands, so an export job pointed at Roubaix or Gravelines needs no separate delivery step to reach the platforms.
- Lead conversions
- The column mapper aligns whatever headers an OVHcloud export uses to each platform's event fields, so a European back-office system with its own naming convention still maps cleanly.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed as the file is read, and the file itself is discarded after processing, keeping the data path inside the EU region the container is provisioned in.
- Lead generation inbound
- Every row returns with a per-destination status, so a malformed record from a regional export is flagged and quarantined instead of failing the whole batch.
Pick your platform. Every use case for it, in one place.
Every way OVHcloud data moves, grouped by platform and ranked by how many use cases OVHcloud 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 OVHcloud object storage with scoped, read-only access.
-
Watch
Choose the container, region, and file pattern 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.
OVHcloud questions, answered.
Which file formats are supported?
The common formats are delimited files such as CSV and TSV with configurable headers, and fixed-width layouts run through the column mapper. Signals watches an OVHcloud container and file pattern that you specify, so once a European back-office job is pointed at that location, no further change is needed to keep it feeding the platforms.
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. Because an OVHcloud container can be pinned to an EU region, the read path stays inside that jurisdiction throughout. A self-hosted Core deployment is available when hashing must happen entirely inside your own environment before delivery.
How often are files picked up?
The pickup schedule is one you configure, anywhere from a few minutes apart to once a day, and Signals processes each file exactly once with a per-row report. Because a container can sit in a specific OVHcloud region, the schedule set there runs independently of anything in another region, so a French export job and one running elsewhere each keep their own cadence.
NEXT STEP
See your OVHcloud data working in every ad platform.
Ready to enable a use case, or still mapping what OVHcloud data could do? Our team helps you find the right place to start.
