CONNECTIONS / MariaDB / MariaDB to Meta Custom Audience
MariaDB tables into Meta, built for Meta lookalike and suppression seeds.
Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB tables you name, then keeps Meta audiences synced as adds and removals so lists never drift so Meta sees match-ready audiences without an export.
- ● mariadb → meta.audience :: live
- > read segments rows=24,259
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 20,135 matched
WHAT THIS ENABLES
MariaDB to Meta Custom Audience
Meta Custom Audience for MariaDB: Signals keeps Meta audiences synced as adds and removals so lists never drift straight from your MariaDB tables, hashed and consent-screened each time the read runs.
- Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your MariaDB tables each time the read runs.
- Always-current lookalike seeds and exclusions, 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 Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.
Each sync hands the customer segments from your MariaDB tables to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.
Built for the teams that own the number.
Engineering teams running MariaDB who need lookalike seeds and suppression lists that track your live customer base out of MariaDB tables.
From kickoff to verified events.
-
Connect
A read-only database user scoped to the MariaDB tables you name, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.
-
Map
Columns from your MariaDB tables align to Meta's Custom Audiences API in the visual mapper, hashed as the read runs and checked for audience refresh cadence.
-
Deliver
Each time the read runs, Signals reads your MariaDB tables and keeps Meta audiences synced as adds and removals so lists never drift, reads only the records changed since the last run, with audience refresh cadence watched in the debugger.
What ships with this use case.
Lookalike seeds and suppression lists that track your live customer base from your MariaDB tables, delivered each time the read runs.
Always-current lookalike seeds and exclusions out of your MariaDB tables, delivered each time the read runs without read load on the database climbing.
Match feedback on audience refresh cadence from Meta's Custom Audiences API each run, tied back to your MariaDB tables.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=mariadb.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 24,259 · num_invalid_entries 133
- audience_id "1664580" · session "upsert"
- ✓ accepted match=83%
Adjacent moves on the same stack.
from MariaDB
MariaDB to Google Customer Match
Google Customer Match for MariaDB: Signals projects your segments into Google Ads as…
Learn more
from MariaDB
MariaDB to TikTok Custom Audience
TikTok Custom Audience for MariaDB: Signals delivers first-party segments to TikTok as…
Learn more
same use case
ActiveCampaign to Meta Custom Audience
ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Custom Audience
Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…
Learn moreAsked on almost every call.
How often does the MariaDB Meta Custom Audience sync run?
You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB tables into Meta. Since Signals reads only the records changed since the last run, lookalike seeds and suppression lists that track your live customer base keeps pace and engineering teams running MariaDB watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.
What match rate should a MariaDB-sourced Meta 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 Meta; one missing both cannot. First-run feedback from Custom Audiences API pinpoints audience refresh cadence, the number engineering teams running MariaDB tune against.
NEXT STEP