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

    CONNECTIONS / AWS S3 / AWS S3 to Meta Custom Audience

    S3 exports into Meta, built for Meta lookalike and suppression seeds.

    Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket 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

    aws-s3 -> meta-custom-audience :: live

    1. ● aws s3 → meta.audience :: live
    2. > read segments rows=66,466
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 59,155 matched

    WHAT THIS ENABLES

    AWS S3 to Meta Custom Audience

    Meta Custom Audience for AWS S3: Signals keeps Meta audiences synced as adds and removals so lists never drift straight from your S3 exports, hashed and consent-screened each time a new file lands.

    • Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your S3 exports each time a new file lands.
    • Always-current lookalike seeds and exclusions, with no export step out of your S3 exports.

    WHAT FLOWS WHERE

    AWS S3 to Custom Audience, mapped.

    Signals picks up the customer segments from your S3 exports; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    Signals picks up the customer segments from your S3 exports; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, working out of S3 objects, prefixes, and export drops.

    Data teams landing exports in S3 who need lookalike seeds and suppression lists that track your live customer base out of S3 exports.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only IAM key scoped to the one S3 bucket you name, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.

    2. Map

      Columns from your S3 exports align to Meta's Custom Audiences API in the visual mapper, hashed as the file lands and checked for audience refresh cadence.

    3. Deliver

      Each time a new file lands, Signals reads your S3 exports and keeps Meta audiences synced as adds and removals so lists never drift, processes only the newly dropped file, 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 S3 exports, delivered each time a new file lands.

    Always-current lookalike seeds and exclusions out of your S3 exports, delivered each time a new file lands without transfer overhead climbing.

    Match feedback on audience refresh cadence from Meta's Custom Audiences API each run, tied back to your S3 exports.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: aws-s3.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=aws-s3.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 66,466 · num_invalid_entries -340
    5. audience_id "1682216" · session "upsert"
    6. ✓ accepted match=89%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from AWS S3

    AWS S3 to Google Customer Match

    Google Customer Match for AWS S3: Signals projects your segments into Google Ads as…

    Learn more

    from AWS S3

    AWS S3 to TikTok Custom Audience

    TikTok Custom Audience for AWS S3: 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 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 AWS S3 Meta Custom Audience sync run?

    You set the cadence, from near-real-time to a nightly AWS S3 sync of your S3 exports into Meta. Since Signals processes only the newly dropped file, lookalike seeds and suppression lists that track your live customer base keeps pace and data teams landing exports in S3 watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your S3 exports, which data teams landing exports in S3 control, not AWS S3 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 landing exports in S3 tune against.

    NEXT STEP

    AWS S3 to Meta Custom Audience, in production this week.

    Talk to our team All AWS S3 use cases