CONNECTIONS / Microsoft SQL Server
Microsoft SQL Server + Datahash: your database drives every campaign.
Conversion data and customer records sit in Microsoft SQL Server tables, often behind a .NET application or reporting layer. Signals reads them on a schedule through a read-only login and delivers hashed events and audiences to every major ad platform, with no export.
- ● mssql :: signals live
- > SELECT * FROM dbo.Orders WHERE ModifiedDate > @cursor rows=38,204
- > read dbo.Customers role=db_datareader
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 81%
The signal Microsoft SQL Server yields, and receives.
Every kind of signal that moves between Microsoft SQL Server and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A query runs on the SQL Server Agent job's cadence, so an Orders table leaves your dbo schema as events without a manual export.
- Lead conversions
- Change tracking or a ModifiedDate column limits each run to rows updated since the last cursor, keeping load on the instance low even as tables grow.
- Custom audiences
- Email and phone values are SHA-256 hashed as each row leaves SQL Server, so no plaintext identifier from the tables you exposed ever reaches a destination.
- Lead generation inbound
- The visual mapper aligns whatever column names your schema uses, so tables built for reporting or a .NET application still become clean conversion signals.
Pick your platform. Every use case for it, in one place.
Every way Microsoft SQL Server data moves, grouped by platform and ranked by how many use cases Microsoft SQL Server 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 Microsoft SQL Server with a read-only login, scoped to the db_datareader role, over an encrypted connection.
-
Select
Choose the tables or views in your schema that hold conversion and customer data.
-
Map
Map columns to event and identifier fields in the visual mapper.
-
Go live
Check sample rows in the live debugger, then go live.
Microsoft SQL Server questions, answered.
Does Datahash write to my database?
No, the connection uses a read-only login scoped to the db_datareader role, so Signals can query only the tables and views you allow and can never insert, update, or delete a row. You control which schema the login can see, and revoking access at any time does not affect the rest of your SQL Server instance.
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 ever reach a destination. A self-hosted Core deployment is available when records cannot leave your perimeter, in which case hashing happens inside your own SQL Server environment before anything is delivered.
How often does the sync run?
On a schedule you choose, from every few minutes to daily batches, with incremental extraction so each run reads only rows changed since the last cursor. That keeps load on your SQL Server instance low even as tables grow, and different tables can run on different cadences within the same connection.
NEXT STEP
See your Microsoft SQL Server data working in every ad platform.
Ready to enable a use case, or still mapping what Microsoft SQL Server data could do? Our team helps you find the right place to start.
