CONNECTIONS / MariaDB
MariaDB + Datahash: tables become ad-platform events.
Orders and customer records sit in MariaDB tables, often standing in for MySQL on the same schema and tooling. Signals reads them on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.
- ● mariadb :: signals live
- > SELECT * FROM orders WHERE updated_at > :cursor rows=45,112
- > read customers role=readonly
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 85%
The signal MariaDB yields, and receives.
Every kind of signal that moves between MariaDB and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A query runs on the cadence you set, so a table of orders or customer records leaves MariaDB as events without anyone building an export.
- Lead conversions
- Change detection reads only the rows that moved since the last cursor, keeping load on the database low even on large tables.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed at ingestion, so no plaintext identifier from a MariaDB table ever reaches a destination.
- Lead generation inbound
- The visual mapper aligns whatever column names your schema uses to each platform's event fields, the same mapping process teams already run against MySQL, so an unusual table shape still becomes clean conversion signals.
Pick your platform. Every use case for it, in one place.
Every way MariaDB data moves, grouped by platform and ranked by how many use cases MariaDB 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 MariaDB with read-only credentials over an encrypted channel.
-
Select
Point Signals at the tables or views that hold conversion data.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
MariaDB questions, answered.
Does Datahash write to my database?
No. Signals connects with a read-only database user granted SELECT on the tables you name, so it can query MariaDB but never insert, update, or delete a row. You scope the grant to exactly the schema you want read, and it can be revoked at any time without affecting any other application on the server.
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. A self-hosted Core deployment is available when data cannot leave your perimeter, in which case hashing happens inside your own environment before delivery.
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. Because MariaDB is wire-compatible with the tools most teams already run against MySQL, the same read-replica setup you use today works for this connection too.
NEXT STEP
See your MariaDB data working in every ad platform.
Ready to enable a use case, or still mapping what MariaDB data could do? Our team helps you find the right place to start.
