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

    CONNECTIONS / FTP / FTP to OpenAI Offline CAPI

    Your FTP drops, wired to OpenAI's Offline Conversions API.

    Signals reads your FTP drops through read-only credentials scoped to the SFTP path you name, 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

    ftp -> openai-offline-capi :: live

    1. ● ftp → openai.capi :: live
    2. > read closed_deals rows=47,292
    3. hash sha256(email,phone) consent=filtered
    4. route openai deliver
    5. ✓ delivered · 39,725 matched

    WHAT THIS ENABLES

    FTP to OpenAI Offline CAPI

    FTP to OpenAI Offline CAPI: your FTP drops, hashed and consent-checked, feed OpenAI as Signals reports downstream revenue as OpenAI's conversion measurement comes online each time a new file lands.

    • Signals reports downstream revenue as OpenAI's conversion measurement comes online, reading your FTP drops each time a new file lands.
    • Measurement in place before the surface scales, with no export step out of your FTP drops.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    OpenAI credits the campaign that sourced the conversion conversion happens off-platform Ad click on OpenAI F File drop sync recorded in FTP 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 FTP and SFTP drop folders.

    Teams exporting nightly to SFTP who need a revenue feed ready the moment OpenAI's offline measurement expands out of FTP drops.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only credentials scoped to the SFTP path you name, mapped to OpenAI's Offline Conversions API and tuned for the emerging OpenAI ad surface.

    2. Map

      Columns from your FTP drops align to OpenAI's Offline Conversions API in the visual mapper, hashed as the file lands and checked for the emerging OpenAI ad surface.

    3. Deliver

      Each time a new file lands, Signals reads your FTP drops and reports downstream revenue as OpenAI's conversion measurement comes online, processes only the newly dropped file, 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 FTP records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from FTP

    FTP to Google OCI

    FTP to Google Offline Conversions: your FTP drops, hashed and consent-checked, feed Google…

    Learn more

    from FTP

    FTP to Google Store Sales

    FTP to Google Store Sales: your FTP drops, hashed and consent-checked, feed Google Ads 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 FTP OpenAI Offline CAPI sync run?

    You set the cadence, from near-real-time to a nightly FTP sync of your FTP drops into OpenAI. Since Signals processes only the newly dropped file, a revenue feed ready the moment OpenAI's offline measurement expands keeps pace and teams exporting nightly to SFTP watch the emerging OpenAI ad surface. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your FTP drops, which teams exporting nightly to SFTP control, not FTP itself. A record with a current hashed email or phone matches for OpenAI; one missing both cannot. First-run feedback from Offline Conversions API pinpoints the emerging OpenAI ad surface, the number teams exporting nightly to SFTP tune against.

    NEXT STEP

    FTP to OpenAI Offline CAPI, in production this week.

    Talk to our team All FTP use cases