CONNECTIONS / MySQL
MySQL + Datahash: web and order data become conversions.
Order history, account records, and event tables usually sit in MySQL, often behind an ecommerce or web application. Signals reads them from a replica on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.
- ● mysql :: signals live
- > SELECT * FROM orders WHERE id > :last_id rows=54,912
- > read customers user=signals_ro@replica
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 84%
The signal MySQL yields, and receives.
Every kind of signal that moves between MySQL and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A query runs on the cadence you set against a replica, so an orders table leaves MySQL as events without touching your primary database.
- Lead conversions
- Change detection tracks primary key or updated_at values, so each run reads only the rows that changed since the last one.
- Custom audiences
- Identifiers are SHA-256 hashed as the replica read runs, so no plaintext email or phone from your tables ever reaches an ad platform.
- Lead generation inbound
- The visual mapper aligns whatever column names your application uses, so tables built for checkout or account flows still become clean conversion signals.
Pick your platform. Every use case for it, in one place.
Every way MySQL data moves, grouped by platform and ranked by how many use cases MySQL 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 MySQL with a read-only user, scoped to a replica where one exists, over an encrypted connection.
-
Select
Choose the tables or views 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.
MySQL questions, answered.
Does Datahash write to my database?
No, the connection uses a read-only user, ideally pointed at a replica, so Signals can query only the tables and views you allow and can never insert, update, or delete a row. You choose the scope of that user, and revoking it at any time leaves the rest of your MySQL instance untouched.
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 ever matched to a platform. A self-hosted Core deployment is available when records cannot leave your perimeter, in which case hashing happens inside your own MySQL environment first.
How often does the sync run?
On a schedule you choose, from every few minutes to daily batches, with incremental extraction so each run touches only changed rows. That keeps load on your MySQL instance low even during traffic spikes, and reading from a replica means production queries are never affected.
NEXT STEP
See your MySQL data working in every ad platform.
Ready to enable a use case, or still mapping what MySQL data could do? Our team helps you find the right place to start.
