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

    CONNECTIONS / Close / Close to OpenAI Offline CAPI

    Close smart-view opportunities into OpenAI, built for OpenAI's Offline Conversions API.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, then reports downstream revenue as OpenAI's conversion measurement comes online so OpenAI sees offline conversions without an export.

    Talk to our team Explore the setup

    close -> openai-offline-capi :: live

    1. ● close → openai.capi :: live
    2. > read closed_deals rows=19,763
    3. hash sha256(email,phone) consent=filtered
    4. route openai deliver
    5. ✓ delivered · 16,996 matched

    WHAT THIS ENABLES

    Close to OpenAI Offline CAPI

    Close to OpenAI Offline CAPI: your Close smart-view opportunities, hashed and consent-checked, feed OpenAI as Signals reports downstream revenue as OpenAI's conversion measurement comes online as records change.

    • Signals reports downstream revenue as OpenAI's conversion measurement comes online, reading your Close smart-view opportunities as records change.
    • Measurement in place before the surface scales, with no export step out of your Close smart-view opportunities.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off OpenAI, away from any pixel. Here is how Close closes the loop.

    OpenAI credits the campaign that sourced the conversion conversion happens off-platform Ad click on OpenAI CRM record sync recorded in Close S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Early advertisers on OpenAI inventory measuring revenue from day one, working out of Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need a revenue feed ready the moment OpenAI's offline measurement expands 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 OpenAI's Offline Conversions API and tuned for the emerging OpenAI ad surface.

    2. Map

      Columns from your Close smart-view opportunities align to OpenAI's Offline Conversions API in the visual mapper, hashed as the sync runs and checked for the emerging OpenAI ad surface.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and reports downstream revenue as OpenAI's conversion measurement comes online, sends only the records that changed, with the emerging OpenAI ad surface watched in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Offline CAPI reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Close records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: close.openai-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=close.closed_deals
    3. event_name "Purchase" · event_time 1784579844
    4. em sha256 "2b9d64…" · value 19780 · currency AED
    5. ✓ accepted · row_status delivered
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Close

    Close to Google OCI

    Close to Google Offline Conversions: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to Google Store Sales

    Close to Google Store Sales: your Close smart-view opportunities, hashed and…

    Learn more

    same use case

    ActiveCampaign to OpenAI Offline CAPI

    ActiveCampaign to OpenAI Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    OpenAI Offline Conversions API

    Datahash uploads offline and in-store conversions to OpenAI with hashed identifiers, so…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Close OpenAI Offline CAPI sync run?

    The pace follows your Close smart-view opportunities: Signals sends changes from Close to OpenAI as records change. Because it sends only the records that changed, a revenue feed ready the moment OpenAI's offline measurement expands stays current while inside-sales teams running Close keep the emerging OpenAI ad surface in view. Delivery needs no export and no manual upload.

    What match rate should a Close-sourced OpenAI Offline CAPI batch expect?

    In Close, match rate tracks the email and phone quality your Close smart-view opportunities carry. Clean identifiers land for OpenAI; blank ones never will. The first Offline Conversions API report shows inside-sales teams running Close where the emerging OpenAI ad surface needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to OpenAI Offline CAPI, in production this week.

    Talk to our team All Close use cases