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

    CONNECTIONS / AWS S3 / AWS S3 to Meta Offline CAPI

    S3 exports into Meta, built for Meta's offline optimization.

    Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket you name, then credits dealer, branch, and phone sales to the Meta campaigns behind them so Meta sees offline conversions without an export.

    Talk to our team Explore the setup

    aws-s3 -> meta-offline-capi :: live

    1. ● aws s3 → meta.capi :: live
    2. > read closed_deals rows=31,235
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 25,925 matched

    WHAT THIS ENABLES

    AWS S3 to Meta Offline CAPI

    Meta Offline CAPI for AWS S3: Signals credits dealer, branch, and phone sales to the Meta campaigns behind them straight from your S3 exports, hashed and consent-screened each time a new file lands.

    • Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your S3 exports each time a new file lands.
    • Campaign learning fed by real-world purchases, with no export step out of your S3 exports.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta A File drop sync recorded in AWS S3 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, working out of S3 objects, prefixes, and export drops.

    Data teams landing exports in S3 who need in-store and phone revenue joining Meta's optimization loop out of S3 exports.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only IAM key scoped to the one S3 bucket you name, mapped to Meta's Offline Conversions API and tuned for Meta's 62-day event window.

    2. Map

      Columns from your S3 exports align to Meta's Offline Conversions API in the visual mapper, hashed as the file lands and checked for Meta's 62-day event window.

    3. Deliver

      Each time a new file lands, Signals reads your S3 exports and credits dealer, branch, and phone sales to the Meta campaigns behind them, processes only the newly dropped file, with Meta's 62-day event window 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 AWS S3 records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: aws-s3.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=aws-s3.closed_deals
    3. event_name "Purchase" · event_time 2026-07-21T10:55:33
    4. value 47704.00 · currency USD
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-46333"
    6. ✓ accepted match=83%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from AWS S3

    AWS S3 to Google OCI

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

    Learn more

    from AWS S3

    AWS S3 to Google Store Sales

    Google Store Sales for AWS S3: Signals matches in-person transactions to Google accounts 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 AWS S3 Meta Offline CAPI sync run?

    You set the cadence, from near-real-time to a nightly AWS S3 sync of your S3 exports into Meta. Since Signals processes only the newly dropped file, in-store and phone revenue joining Meta's optimization loop keeps pace and data teams landing exports in S3 watch Meta's 62-day event window. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your S3 exports, which data teams landing exports in S3 control, not AWS S3 itself. A record with a current hashed email or phone matches for Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number data teams landing exports in S3 tune against.

    NEXT STEP

    AWS S3 to Meta Offline CAPI, in production this week.

    Talk to our team All AWS S3 use cases