Jump to a popular page, or start typing.

    CONNECTIONS / Close

    Close + Datahash: turn call-driven pipeline into ad signals.

    Close tracks every call, status change, and opportunity your inside sales team runs, while ad platforms still optimize on the first form submitted. Signals reads lead status and opportunity confidence back into Meta, Google, TikTok, and LinkedIn so bidding follows what your reps actually close.

    close :: live

    1. ● close :: signals live
    2. > read leads status=qualified rows=3,180
    3. > read opportunities confidence>=70% value=$412,900
    4. hash sha256(email,phone) scope=leads.read
    5. route meta · google · tiktok · linkedin
    6. ✓ 4 destinations synced · match 79%
    WHAT FLOWS THROUGH CLOSE

    The signal Close yields, and receives.

    Every kind of signal that moves between Close 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
    A lead moving from Potential to Qualified posts as a conversion event, so campaigns optimize on a real sales signal instead of the first call booked.
    Lead conversions
    Opportunities marked won leave Close with their confidence score and deal value attached, landing as offline conversions with revenue intact.
    Custom audiences
    Lead and contact identifiers are hashed before they leave Close, so audience sync never puts a raw email or phone number on the wire.
    Lead generation inbound
    A custom field added to a lead or opportunity in Close shows up in the visual mapper the same day, with no engineering ticket required.
    USE-CASE LISTING

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

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

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

    From authorization to delivered signal.

    1. Authorize

      Connect Close with a scoped integration user, reversible from Close at any time.

    2. Map statuses

      Map lead statuses and opportunity stages to events in the visual mapper.

    3. Hash and consent

      Hashing and consent flags are applied the moment a record is read.

    4. Deliver

      Go live with per-destination delivery status and match rate reporting.

    FAQ

    Close questions, answered.

    Which Close stage changes can fire events?

    Any lead status or opportunity stage you choose can fire an event. Most Close teams map Qualified and Customer to conversions, leave earlier statuses out of the feed entirely, and route confidence-weighted opportunities to a separate audience so ad platforms see committed pipeline rather than every raw lead entering the CRM.

    Is customer PII stored by Datahash?

    No, Datahash does not store customer PII. Every identifier read from Close is SHA-256 hashed at the moment it is read, and Datahash Cloud holds no raw email addresses or phone numbers on its servers. Teams that cannot let data leave their perimeter at all run the same mapping on a self-hosted Core deployment instead.

    How fast do stage changes reach the ad platforms?

    Stage changes reach ad platforms in near real time, not on a batch schedule. A lead status or opportunity update in Close is read, hashed, and routed to every connected destination on the same pass, and the live debugger shows per-platform match feedback so you can confirm a change landed instead of guessing from the ads dashboard.

    NEXT STEP

    See your Close data working in every ad platform.

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