CONNECTIONS / Vultr
Vultr + Datahash: object storage becomes ad signals.
Conversion and CRM exports land in your Vultr Object Storage bucket alongside the rest of your infrastructure. Signals reads each file as it arrives, hashes the identifiers, and routes the rows to every connected ad platform.
- ● vultr :: signals live
- > object arrived vultr://blr1/exports/signups-2026-07-18.csv
- > parse rows=9,842 schema=signups
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 74%
The signal Vultr yields, and receives.
Every kind of signal that moves between Vultr and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A file written by a cron job or app server to the watched Vultr bucket is picked up on schedule and parsed as it lands, so a small export script needs no separate delivery step to reach the platforms.
- Lead conversions
- The column mapper aligns whatever headers your application writes to each platform's event fields, so a hand-rolled export from a lean stack still maps cleanly without a rewrite.
- Custom audiences
- Email and phone values are SHA-256 hashed as each file is parsed, and the object is discarded once processed, so a developer's export never leaves plaintext behind on our side.
- Lead generation inbound
- Every row comes back with a per-destination status, so a malformed record from a quick script is flagged and quarantined instead of failing the whole file.
Pick your platform. Every use case for it, in one place.
Every way Vultr data moves, grouped by platform and ranked by how many use cases Vultr 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 Vultr Object Storage with scoped, read-only access.
-
Watch
Choose the bucket 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.
Vultr questions, answered.
Which file formats are supported?
CSV, TSV, and other delimited exports work without extra setup, with headers you remap freely, and fixed-width output goes through the column mapper if that is what a script produces. A quick cron job or a small backend service can write straight into the watched Vultr bucket in whatever shape it already outputs, with no conversion step required beforehand.
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. This applies whether the export comes from a managed application or a single cron job. A self-hosted Core deployment is available when data cannot leave your own infrastructure, with hashing happening there instead.
How often are files picked up?
On a schedule you choose, from every few minutes to daily batches, and each file is processed exactly once and reported row by row. A new object landing in the watched Vultr bucket triggers the next run, so a lean setup with a single cron job fits the same cadence as a larger pipeline.
NEXT STEP
See your Vultr data working in every ad platform.
Ready to enable a use case, or still mapping what Vultr data could do? Our team helps you find the right place to start.
