CONNECTIONS / Linode
Linode + Datahash: Object Storage exports become signals.
Linode Object Storage, now part of Akamai's cloud, gives developers a straightforward S3-compatible bucket for exports. Signals watches that bucket, hashes each row on arrival, and routes matched events to your ad platforms.
- ● linode :: signals live
- > object arrived s3://media-store.linodeobjects.com/customers/2026-07-18.csv
- > parse rows=27,556 schema=customers
- hash sha256(email,phone)
- route meta · google
- ✓ 2 destinations synced · match 71%
The signal Linode yields, and receives.
Every kind of signal that moves between Linode and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A bucket on Linode's Object Storage gets watched the same way any S3-compatible bucket would, so an export job running alongside your app needs no separate integration to reach Signals.
- Lead conversions
- The column mapper translates whatever header layout your export uses into consistent event fields, so a schema change on your app's side does not require a change on Signals' side.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed as the file is read, and the object is discarded after processing, so a customer export never lingers past that run.
- Lead generation inbound
- Every row returns a per-destination delivery status, so a formatting issue in one export is caught and reported without blocking the rest of the batch.
Pick your platform. Every use case for it, in one place.
Every way Linode data moves, grouped by platform and ranked by how many use cases Linode 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 Linode with scoped, read-only access to your Object Storage bucket.
-
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.
Linode questions, answered.
Which file formats are supported?
Delimited files such as CSV and TSV with configurable headers are the common case, and fixed-width layouts can be handled through the column mapper. You point Signals at a bucket and file pattern on your Linode Object Storage cluster, and any matching file is parsed on arrival, so an existing export job needs no changes.
Is customer PII stored by Datahash?
No raw identifier sits on host servers in Datahash Cloud: emails and phone numbers are SHA-256 hashed the moment a file is read, and the object pulled from your Linode bucket is discarded right after. Teams that cannot let data leave their own infrastructure at all can run a self-hosted Core deployment instead, where hashing happens on their side.
Is Linode Object Storage compatible with the same setup as AWS S3?
Yes. Linode Object Storage implements the S3 API, so pointing Signals at your Linode endpoint uses the same read-only, scoped-access pattern as any other S3-compatible provider. If a workload later moves to a different provider, the same bucket-and-pattern configuration carries over without a change to how events are hashed or routed.
NEXT STEP
See your Linode data working in every ad platform.
Ready to enable a use case, or still mapping what Linode data could do? Our team helps you find the right place to start.
