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

    CONNECTIONS / Attio / Attio to OpenAI Offline CAPI

    Your Attio workspace lists, wired to OpenAI's Offline Conversions API.

    Connect Attio and point Signals at your Attio workspace lists; it reports downstream revenue as OpenAI's conversion measurement comes online as records change, hashed and consent-checked for OpenAI.

    Talk to our team Explore the setup

    attio -> openai-offline-capi :: live

    1. ● attio → openai.capi :: live
    2. > read closed_deals rows=61,632
    3. hash sha256(email,phone) consent=filtered
    4. route openai deliver
    5. ✓ delivered · 49,922 matched

    WHAT THIS ENABLES

    Attio to OpenAI Offline CAPI

    OpenAI Offline CAPI for Attio: Signals reports downstream revenue as OpenAI's conversion measurement comes online straight from your Attio workspace lists, hashed and consent-screened as records change.

    • Offline and in-store sales from your Attio workspace lists activated for OpenAI, as Signals reports downstream revenue as OpenAI's conversion measurement comes online.
    • A revenue feed ready the moment OpenAI's offline measurement expands, drawn from your Attio workspace lists by RevOps teams running Attio.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    OpenAI credits the campaign that sourced the conversion conversion happens off-platform Ad click on OpenAI CRM record sync recorded in Attio 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, with the records already in Attio records, lists, and workspace objects.

    RevOps teams running Attio activating OpenAI's Offline Conversions API straight from Attio workspace lists.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Attio, reading only your Attio workspace lists to feed OpenAI's Offline Conversions API, sized for the emerging OpenAI ad surface.

    2. Map

      Signals reads your Attio workspace lists, and its columns map to OpenAI's Offline Conversions API in the visual mapper, hashed and checked for the emerging OpenAI ad surface.

    3. Deliver

      On each run, Signals pulls your Attio workspace lists, reports downstream revenue as OpenAI's conversion measurement comes online, and sends only the records that changed, with the emerging OpenAI ad surface 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 Attio records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Attio

    Attio to Google OCI

    Google Offline Conversions for Attio: Signals reconciles closed-won revenue to the Google…

    Learn more

    from Attio

    Attio to Google Store Sales

    Google Store Sales for Attio: Signals matches in-person transactions to Google accounts as…

    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 Attio OpenAI Offline CAPI sync run?

    The pace follows your Attio workspace lists: Signals sends changes from Attio 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 RevOps teams running Attio keep the emerging OpenAI ad surface in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Attio workspace lists decides it, and RevOps teams running Attio own that inside Attio. A live email or phone matches into OpenAI; neither, and it will not. First-run feedback flags the emerging OpenAI ad surface, which RevOps teams running Attio then raise inside your Attio workspace lists.

    NEXT STEP

    Attio to OpenAI Offline CAPI, in production this week.

    Talk to our team All Attio use cases