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

    CONNECTIONS / GCS / GCS to Meta Offline CAPI

    Your GCS objects, wired to Meta's offline optimization.

    Connect GCS and point Signals at your GCS objects; it credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    google-cloud-storage -> meta-offline-capi :: live

    1. ● gcs → meta.capi :: live
    2. > read closed_deals rows=65,398
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 53,626 matched

    WHAT THIS ENABLES

    GCS to Meta Offline CAPI

    GCS to Meta Offline CAPI: your GCS objects, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands.

    • Offline and in-store sales from your GCS objects activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, drawn from your GCS objects by data teams landing exports in GCS.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta G File drop sync recorded in GCS S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in Google Cloud Storage buckets and objects.

    Data teams landing exports in GCS activating Meta's offline optimization straight from GCS objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only service account scoped to the one GCS bucket you name to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals picks up your GCS objects, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your GCS objects, credits dealer, branch, and phone sales to the Meta campaigns behind them, and processes only the newly dropped file, with Meta's 62-day event window 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 GCS records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: google-cloud-storage.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=google-cloud-storage.closed_deals
    3. event_name "Purchase" · event_time 2026-07-22T19:40:56
    4. value 45157.00 · currency AED
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-92256"
    6. ✓ accepted match=82%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from GCS

    GCS to Google OCI

    GCS to Google Offline Conversions: your GCS objects, hashed and consent-checked, feed…

    Learn more

    from GCS

    GCS to Google Store Sales

    GCS to Google Store Sales: your GCS objects, hashed and consent-checked, feed Google Ads as…

    Learn more

    same use case

    ActiveCampaign to Meta Offline CAPI

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

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the GCS Meta Offline CAPI sync run?

    The pace follows your GCS objects: Signals sends changes from GCS to Meta each time a new file lands. Because it processes only the newly dropped file, in-store and phone revenue joining Meta's optimization loop stays current while data teams landing exports in GCS keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.

    What match rate should a GCS-sourced Meta Offline CAPI batch expect?

    Coverage of hashed identifiers across your GCS objects decides it, and data teams landing exports in GCS own that inside GCS. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which data teams landing exports in GCS then raise inside your GCS objects.

    NEXT STEP

    GCS to Meta Offline CAPI, in production this week.

    Talk to our team All GCS use cases