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

    CONNECTIONS / Freshsales / Freshsales to Meta Custom Audience

    Your Freshsales deals and lifecycle stages, wired to Meta lookalike and suppression seeds.

    Signals reads your Freshsales deals and lifecycle stages through scoped OAuth access to Freshsales, reading only your Freshsales deals and lifecycle stages, 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

    freshsales -> meta-custom-audience :: live

    1. ● freshsales → meta.audience :: live
    2. > read segments rows=68,012
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 51,009 matched

    WHAT THIS ENABLES

    Freshsales to Meta Custom Audience

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

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

    WHAT FLOWS WHERE

    Freshsales to Custom Audience, mapped.

    Signals reads the customer segments from your Freshsales deals and lifecycle stages; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    Signals reads the customer segments from your Freshsales deals and lifecycle stages; 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 Freshsales deals, contacts, and lifecycle stages.

    Sales teams running Freshsales who need lookalike seeds and suppression lists that track your live customer base out of Freshsales deals and lifecycle stages.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Freshsales, reading only your Freshsales deals and lifecycle stages, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.

    2. Map

      Columns from your Freshsales deals and lifecycle stages 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 Freshsales deals and lifecycle stages 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 Freshsales deals and lifecycle stages, delivered as records change.

    Always-current lookalike seeds and exclusions out of your Freshsales deals and lifecycle stages, 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 Freshsales deals and lifecycle stages.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /customaudiences source=freshsales.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 68,012 · num_invalid_entries -251
    5. audience_id "1694674" · session "upsert"
    6. ✓ accepted match=75%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Freshsales

    Freshsales to Google Customer Match

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

    Learn more

    from Freshsales

    Freshsales to TikTok Custom Audience

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

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

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

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

    NEXT STEP

    Freshsales to Meta Custom Audience, in production this week.

    Talk to our team All Freshsales use cases