CONNECTIONS / MariaDB / MariaDB to TikTok Custom Audience
MariaDB tables into TikTok, built for TikTok audience targeting.
Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB tables you name, then delivers first-party segments to TikTok as match-ready custom audiences so TikTok sees match-ready audiences without an export.
- ● mariadb → tiktok.audience :: live
- > read segments rows=64,665
- hash sha256(email,phone) consent=filtered
- route tiktok deliver
- ✓ delivered · 53,025 matched
WHAT THIS ENABLES
MariaDB to TikTok Custom Audience
TikTok Custom Audience for MariaDB: Signals delivers first-party segments to TikTok as match-ready custom audiences straight from your MariaDB tables, hashed and consent-screened each time the read runs.
- Signals delivers first-party segments to TikTok as match-ready custom audiences, reading your MariaDB tables each time the read runs.
- Targeting that mirrors your live segment, with no export step out of your MariaDB tables.
WHAT FLOWS WHERE
MariaDB to Custom Audience, mapped.
Each sync hands the customer segments from your MariaDB tables to Signals, which hashes and filters every record, then TikTok's Custom Audience API logs the match-ready audiences for match quality on TikTok.
Each sync hands the customer segments from your MariaDB tables to Signals, which hashes and filters every record, then TikTok's Custom Audience API logs the match-ready audiences for match quality on TikTok.
Built for the teams that own the number.
Engineering teams running MariaDB who need TikTok custom audiences mirroring the segment your data team publishes out of MariaDB tables.
From kickoff to verified events.
-
Connect
A read-only database user scoped to the MariaDB tables you name, mapped to TikTok's Custom Audience API and tuned for match quality on TikTok.
-
Map
Columns from your MariaDB tables align to TikTok's Custom Audience API in the visual mapper, hashed as the read runs and checked for match quality on TikTok.
-
Deliver
Each time the read runs, Signals reads your MariaDB tables and delivers first-party segments to TikTok as match-ready custom audiences, reads only the records changed since the last run, with match quality on TikTok watched in the debugger.
What ships with this use case.
TikTok custom audiences mirroring the segment your data team publishes from your MariaDB tables, delivered each time the read runs.
Targeting that mirrors your live segment out of your MariaDB tables, delivered each time the read runs without read load on the database climbing.
Match feedback on match quality on TikTok from TikTok's Custom Audience API each run, tied back to your MariaDB tables.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /dmp/custom_audience source=mariadb.segments
- id_schema ["EMAIL_SHA256","PHONE_SHA256"]
- action "add" · audience_id "aud_48011"
- id_list_size 64,665 · matched 53,025
- ✓ accepted match=82%
Adjacent moves on the same stack.
from MariaDB
MariaDB to Meta Custom Audience
Meta Custom Audience for MariaDB: Signals keeps Meta audiences synced as adds and removals…
Learn more
from MariaDB
MariaDB to Google Customer Match
Google Customer Match for MariaDB: Signals projects your segments into Google Ads as…
Learn more
same use case
ActiveCampaign to TikTok Custom Audience
ActiveCampaign to TikTok Custom Audience: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
TikTok Custom Audience
Datahash syncs hashed customer audiences from your CRM, warehouse, or files to TikTok for…
Learn moreAsked on almost every call.
How often does the MariaDB TikTok Custom Audience sync run?
You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB tables into TikTok. Since Signals reads only the records changed since the last run, TikTok custom audiences mirroring the segment your data team publishes keeps pace and engineering teams running MariaDB watch match quality on TikTok. One scoped connection sets it up, cadence adjustable later.
What match rate should a MariaDB-sourced TikTok Custom Audience batch expect?
Match rate follows identifier coverage in your MariaDB tables, which engineering teams running MariaDB control, not MariaDB itself. A record with a current hashed email or phone matches for TikTok; one missing both cannot. First-run feedback from Custom Audience API pinpoints match quality on TikTok, the number engineering teams running MariaDB tune against.
NEXT STEP