Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / MySQL / MySQL to Meta Custom Audience

    From MySQL tables to Meta lookalike and suppression seeds.

    Signals reads your MySQL tables through a read-only database user scoped to the MySQL 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.

    Talk to our team Explore the setup

    mysql -> meta-custom-audience :: live

    1. ● mysql → meta.audience :: live
    2. > read segments rows=49,278
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 35,973 matched

    WHAT THIS ENABLES

    MySQL to Meta Custom Audience

    MySQL to Meta Custom Audience: Signals reads your MySQL tables and keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked each time the read runs.

    • Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your MySQL tables each time the read runs.
    • Always-current lookalike seeds and exclusions, with no export step out of your MySQL tables.

    WHAT FLOWS WHERE

    MySQL to Custom Audience, mapped.

    Signals reads the customer segments from your MySQL tables each time the read runs, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.

    Signals reads the customer segments from your MySQL tables each time the read runs, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, working out of MySQL tables and views.

    Application teams on MySQL who need lookalike seeds and suppression lists that track your live customer base out of MySQL tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MySQL tables you name, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.

    2. Map

      Columns from your MySQL tables align to Meta's Custom Audiences API in the visual mapper, hashed as the read runs and checked for audience refresh cadence.

    3. Deliver

      Each time the read runs, Signals reads your MySQL 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 YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base from your MySQL tables, delivered each time the read runs.

    Always-current lookalike seeds and exclusions out of your MySQL 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 MySQL tables.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: mysql.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=mysql.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 49,278 · num_invalid_entries -335
    5. audience_id "1693090" · session "upsert"
    6. ✓ accepted match=73%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MySQL

    MySQL to Google Customer Match

    MySQL to Google Customer Match: Signals reads your MySQL tables and projects your segments…

    Learn more

    from MySQL

    MySQL to TikTok Custom Audience

    MySQL to TikTok Custom Audience: Signals reads your MySQL tables and delivers first-party…

    Learn more

    same use case

    ActiveCampaign to Meta Custom Audience

    ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Custom Audience

    Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MySQL Meta Custom Audience sync run?

    Delivery tracks MySQL, run by application teams on MySQL: a near-real-time or scheduled sync of your MySQL tables feeds Meta on that cadence. Each run reads only the records changed since the last run, so always-current lookalike seeds and exclusions holds up on audience refresh cadence. The live debugger confirms every delivery inline.

    What match rate should a MySQL-sourced Meta Custom Audience batch expect?

    Coverage of hashed identifiers across your MySQL tables decides it, and application teams on MySQL own that inside MySQL. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags audience refresh cadence, which application teams on MySQL then raise inside your MySQL tables.

    NEXT STEP

    MySQL to Meta Custom Audience, in production this week.

    Talk to our team All MySQL use cases