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

    CONNECTIONS / Attio / Attio to Meta Custom Audience

    Your Attio workspace lists, wired to Meta lookalike and suppression seeds.

    Connect Attio and point Signals at your Attio workspace lists; it keeps Meta audiences synced as adds and removals so lists never drift as records change, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    attio -> meta-custom-audience :: live

    1. ● attio → meta.audience :: live
    2. > read segments rows=39,342
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 32,260 matched

    WHAT THIS ENABLES

    Attio to Meta Custom Audience

    Meta Custom Audience for Attio: Signals keeps Meta audiences synced as adds and removals so lists never drift straight from your Attio workspace lists, hashed and consent-screened as records change.

    • Customer segments from your Attio workspace lists 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 Attio workspace lists by RevOps teams running Attio.

    WHAT FLOWS WHERE

    Attio to Custom Audience, mapped.

    Signals reads the customer segments from your Attio workspace lists as records change, 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 Attio workspace lists as records change, 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 Attio records, lists, and workspace objects.

    RevOps teams running Attio activating Meta lookalike and suppression seeds straight from Attio workspace lists.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Attio, reading only your Attio workspace lists to feed Meta's Custom Audiences API, sized for audience refresh cadence.

    2. Map

      Signals reads your Attio workspace lists, 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 Attio workspace lists, keeps Meta audiences synced as adds and removals so lists never drift, and sends only the records that changed, 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 Attio workspace lists and sends only the records that changed.

    Always-current lookalike seeds and exclusions from your Attio workspace lists, with API call volume steady because Signals sends only the records that changed.

    A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Attio workspace lists.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /customaudiences source=attio.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 39,342 · num_invalid_entries -139
    5. audience_id "1674753" · session "upsert"
    6. ✓ accepted match=82%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Attio

    Attio to Google Customer Match

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

    Learn more

    from Attio

    Attio to TikTok Custom Audience

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

    The pace follows your Attio workspace lists: Signals sends changes from Attio to Meta as records change. Because it sends only the records that changed, lookalike seeds and suppression lists that track your live customer base stays current while RevOps teams running Attio keep audience refresh cadence in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    Attio to Meta Custom Audience, in production this week.

    Talk to our team All Attio use cases