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

    CONNECTIONS / Close / Close to Meta Custom Audience

    Close smart-view opportunities into Meta, built for Meta lookalike and suppression seeds.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, 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

    close -> meta-custom-audience :: live

    1. ● close → meta.audience :: live
    2. > read segments rows=26,812
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 22,254 matched

    WHAT THIS ENABLES

    Close to Meta Custom Audience

    Close to Meta Custom Audience: your Close smart-view opportunities, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift as records change.

    • Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your Close smart-view opportunities as records change.
    • Always-current lookalike seeds and exclusions, with no export step out of your Close smart-view opportunities.

    WHAT FLOWS WHERE

    Close to Custom Audience, mapped.

    Each sync hands the customer segments from your Close smart-view opportunities 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 Close smart-view opportunities to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs 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 Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need lookalike seeds and suppression lists that track your live customer base out of Close smart-view opportunities.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Close, reading only your Close smart-view opportunities, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.

    2. Map

      Columns from your Close smart-view opportunities align to Meta's Custom Audiences API in the visual mapper, hashed as the sync runs and checked for audience refresh cadence.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and keeps Meta audiences synced as adds and removals so lists never drift, sends only the records that changed, 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 Close smart-view opportunities, delivered as records change.

    Always-current lookalike seeds and exclusions out of your Close smart-view opportunities, delivered as records change without API call volume climbing.

    Match feedback on audience refresh cadence from Meta's Custom Audiences API each run, tied back to your Close smart-view opportunities.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /customaudiences source=close.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 26,812 · num_invalid_entries -21
    5. audience_id "1694444" · session "upsert"
    6. ✓ accepted match=83%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Close

    Close to Google Customer Match

    Close to Google Customer Match: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to TikTok Custom Audience

    Close to TikTok Custom Audience: your Close smart-view opportunities, hashed and…

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

    The pace follows your Close smart-view opportunities: Signals sends changes from Close 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 inside-sales teams running Close keep audience refresh cadence in view. Delivery needs no export and no manual upload.

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

    In Close, match rate tracks the email and phone quality your Close smart-view opportunities carry. Clean identifiers land for Meta; blank ones never will. The first Custom Audiences API report shows inside-sales teams running Close where audience refresh cadence needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to Meta Custom Audience, in production this week.

    Talk to our team All Close use cases