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

    CONNECTIONS / Capsule / Capsule to Meta Custom Audience

    Your Capsule opportunity milestones, wired to Meta lookalike and suppression seeds.

    Connect Capsule and point Signals at your Capsule opportunity milestones; 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

    capsule -> meta-custom-audience :: live

    1. ● capsule → meta.audience :: live
    2. > read segments rows=54,418
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 40,269 matched

    WHAT THIS ENABLES

    Capsule to Meta Custom Audience

    Capsule to Meta Custom Audience: your Capsule opportunity milestones, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift as records change.

    • Customer segments from your Capsule opportunity milestones 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 Capsule opportunity milestones by small sales teams running Capsule.

    WHAT FLOWS WHERE

    Capsule to Custom Audience, mapped.

    Signals reads the customer segments from your Capsule opportunity milestones 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 Capsule opportunity milestones 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 Capsule contacts and opportunity milestones.

    Small sales teams running Capsule activating Meta lookalike and suppression seeds straight from Capsule opportunity milestones.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Capsule, reading only your Capsule opportunity milestones to feed Meta's Custom Audiences API, sized for audience refresh cadence.

    2. Map

      Signals reads your Capsule opportunity milestones, 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 Capsule opportunity milestones, 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 Capsule opportunity milestones and sends only the records that changed.

    Always-current lookalike seeds and exclusions from your Capsule opportunity milestones, 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 Capsule opportunity milestones.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /customaudiences source=capsule.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 54,418 · num_invalid_entries 248
    5. audience_id "1655661" · session "upsert"
    6. ✓ accepted match=74%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Capsule

    Capsule to Google Customer Match

    Capsule to Google Customer Match: your Capsule opportunity milestones, hashed and…

    Learn more

    from Capsule

    Capsule to TikTok Custom Audience

    Capsule to TikTok Custom Audience: your Capsule opportunity milestones, 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 Capsule Meta Custom Audience sync run?

    Delivery tracks Capsule, run by small sales teams running Capsule: a near-real-time or scheduled sync of your Capsule opportunity milestones feeds Meta on that cadence. Each run sends only the records that changed, 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 Capsule-sourced Meta Custom Audience batch expect?

    Match rate follows identifier coverage in your Capsule opportunity milestones, which small sales teams running Capsule control, not Capsule 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 small sales teams running Capsule tune against.

    NEXT STEP

    Capsule to Meta Custom Audience, in production this week.

    Talk to our team All Capsule use cases