Jump to a popular page, or start typing.

    CONNECTIONS / Capsule

    Capsule + Datahash: get a small CRM talking to ad platforms.

    Capsule keeps a sales pipeline simple, with opportunities moving through tracks and contacts organized by tag. Signals reads that activity and turns pipeline movement and contact lists into conversion events and audiences on every platform you advertise on.

    capsule :: live

    1. ● capsule :: signals live
    2. > read opportunities track=sales stage=won rows=964
    3. > read parties tag=customer
    4. hash sha256(email,phone) scope=opportunities.read,parties.read
    5. route meta · google · tiktok · snap
    6. ✓ 4 destinations synced · match 74%
    WHAT FLOWS THROUGH CAPSULE

    The signal Capsule yields, and receives.

    Every kind of signal that moves between Capsule and the platforms, through one hashed, deduplicated route.

    What flows Every platform Offline conversions Lead conversions Custom audiences Lead generation Signals hash · dedupe· route Google Meta Snap TikTok LinkedIn OpenAI
    Offline conversions
    An opportunity reaching the won stage of its track posts as a conversion event, so campaigns optimize on a closed sale rather than a form fill.
    Lead conversions
    Closed-won value attached to the opportunity reaches the ad platform as a valued offline conversion tied to the campaign that sourced it.
    Custom audiences
    Contact tags leave Capsule hashed and become scheduled audience segments, so a tagged list stays live instead of a one-time spreadsheet export.
    Lead generation inbound
    Custom fields on a Capsule opportunity or contact travel with the event, so a detail specific to your setup still lands where you need it.
    USE-CASE LISTING

    Pick your platform. Every use case for it, in one place.

    Every way Capsule data moves, grouped by platform and ranked by how many use cases Capsule supports.

    Google 5 Meta 4 Snap 4 TikTok 4 LinkedIn 3 OpenAI 1
    HOW IT CONNECTS

    From authorization to delivered signal.

    1. Connect

      Connect with a scoped Capsule API token, revocable any time.

    2. Map tracks

      Map opportunity tracks and contact tags to platform events in the visual mapper.

    3. Hash and consent

      Identifiers are hashed and consent flags applied before anything leaves Capsule.

    4. Deliver

      Delivery runs on a schedule, with per-destination match reporting.

    FAQ

    Capsule questions, answered.

    Capsule is simpler than most CRMs we've connected. Is that a problem?

    No, a smaller object model is usually faster to map, not harder. Capsule's opportunities, tracks, and parties cover the same conversion signals a larger CRM would, and the mapper works the same way regardless of how many custom objects a system has. Most Capsule setups take less time to configure than a CRM with dozens of custom fields.

    How does Capsule's tagging system map to audiences?

    Any tag applied to a party in Capsule can be pointed at an audience segment in the mapper, and membership updates as tags are added or removed. That means a manually curated list, like past customers or newsletter subscribers, turns into a synced audience without a recurring export step.

    Do you support multiple pipelines, or just one track?

    Capsule supports multiple tracks per account, and Signals maps each one independently, so a sales track and a separate renewals track can feed different events or the same one. You choose the mapping per track during setup, and it can be revised later without disrupting what is already live.

    NEXT STEP

    See your Capsule data working in every ad platform.

    Ready to enable a use case, or still mapping what Capsule data could do? Our team helps you find the right place to start.