CONNECTIONS / Datahash API
Datahash API: post events from your backend to every ad platform.
Send server-side events to Signals over a documented REST API from any backend, in any language. Signals hashes the identifiers, validates each payload, and delivers the conversions to Meta, Google, TikTok, and Snap, with no pixel and no warehouse read.
- ● datahash-api :: signals live
- > POST /v1/events type=purchase value=214.00
- > 202 accepted id=evt_9f2a
- hash sha256(email,phone) server-side
- route meta · google · tiktok · snap
- ✓ forwarded · match 82%
The signal Datahash API yields, and receives.
Every kind of signal that moves between Datahash API and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Every event type, a purchase, a lead, or a custom action, posts to one documented endpoint, and schema validation rejects a malformed event instead of failing the batch.
- Lead conversions
- Emails and phone numbers are SHA-256 hashed the moment an event is received, or you send them pre-hashed, so no plaintext identifier is ever stored.
- Custom audiences
- The client examples show how to batch and retry, so a backend can post events in near real time or in periodic groups without losing any.
- Lead generation inbound
- Every request appears in the live debugger with its full payload and per-destination status, so a failed match is visible at the exact event that caused it.
Pick your platform. Every use case for it, in one place.
Every way Datahash API data moves, grouped by platform and ranked by how many use cases Datahash API supports.
- 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.
-
Create a key
Create an API key in the Signals console.
-
Send
Send a test event from your backend following the API reference.
-
Map
Map custom fields to the signal schema if needed.
-
Go live
Verify events in the live debugger and go live.
Datahash API questions, answered.
Which languages are supported?
Any language that can make an HTTPS request works, since the API is a documented REST endpoint that takes JSON payloads. Examples cover common backend stacks, and because there is no SDK to install, a service written in Go, Python, Node, or anything else posts events the same way and reaches every mapped ad platform.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud, so only hashed values are matched to a platform. You can also send values pre-hashed, and a self-hosted Core deployment is available when data cannot leave your perimeter, in which case hashing happens inside your own environment.
How are failures handled?
Every request returns a clear status code, and the live debugger shows validation errors per event, so a retry can target only the events that failed rather than resending a whole batch. Schema validation catches a malformed payload before it reaches a platform, so one bad event never blocks the rest of the request.
NEXT STEP
See your Datahash API data working in every ad platform.
Ready to enable a use case, or still mapping what Datahash API data could do? Our team helps you find the right place to start.