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

    CONNECTIONS / Microsoft SQL Server / SQL Server to Meta Custom Audience

    Your SQL Server tables, wired to Meta lookalike and suppression seeds.

    Connect SQL Server and point Signals at your SQL Server tables; it keeps Meta audiences synced as adds and removals so lists never drift each time the read runs, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    microsoft-sql-server -> meta-custom-audience :: live

    1. ● sql server → meta.audience :: live
    2. > read segments rows=13,897
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 11,118 matched

    WHAT THIS ENABLES

    SQL Server to Meta Custom Audience

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

    • Customer segments from your SQL Server tables activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
    • Lookalike seeds and suppression lists that track your live customer base, drawn from your SQL Server tables by data teams running SQL Server.

    WHAT FLOWS WHERE

    Microsoft SQL Server to Custom Audience, mapped.

    Signals reads the customer segments from your SQL Server 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 SQL Server 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, with the records already in SQL Server tables, views, and indexed views.

    Data teams running SQL Server activating Meta lookalike and suppression seeds straight from SQL Server tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the SQL Server tables you name to feed Meta's Custom Audiences API, sized for audience refresh cadence.

    2. Map

      A scheduled read pulls your SQL Server tables, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.

    3. Deliver

      On each run, Signals pulls your SQL Server tables, keeps Meta audiences synced as adds and removals so lists never drift, and reads only the records changed since the last run, with audience refresh cadence in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your SQL Server tables and reads only the records changed since the last run.

    Always-current lookalike seeds and exclusions from your SQL Server tables, with read load on the database steady because Signals reads only the records changed since the last run.

    A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your SQL Server tables.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: microsoft-sql-server.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=microsoft-sql-server.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 13,897 · num_invalid_entries -249
    5. audience_id "1668951" · session "upsert"
    6. ✓ accepted match=80%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Microsoft SQL Server

    SQL Server to Google Customer Match

    SQL Server to Google Customer Match: Signals reads your SQL Server tables and projects your…

    Learn more

    from Microsoft SQL Server

    SQL Server to TikTok Custom Audience

    SQL Server to TikTok Custom Audience: Signals reads your SQL Server tables and delivers…

    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 SQL Server Meta Custom Audience sync run?

    Delivery tracks SQL Server, run by data teams running SQL Server: a near-real-time or scheduled sync of your SQL Server 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 SQL Server-sourced Meta Custom Audience batch expect?

    Match rate follows identifier coverage in your SQL Server tables, which data teams running SQL Server control, not SQL Server 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 data teams running SQL Server tune against.

    NEXT STEP

    SQL Server to Meta Custom Audience, in production this week.

    Talk to our team All Microsoft SQL Server use cases