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

    CONNECTIONS / OVHcloud / OVHcloud to Google Store Sales

    From OVHcloud Object Storage files to Google Store Sales matching.

    Signals reads your OVHcloud Object Storage files through a read-only S3 key scoped to the OVHcloud container you name, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    ovhcloud -> google-store-sales :: live

    1. ● ovhcloud → google.sales :: live
    2. > read closed_deals rows=51,593
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 44,370 matched

    WHAT THIS ENABLES

    OVHcloud to Google Store Sales

    OVHcloud to Google Store Sales: your OVHcloud Object Storage files, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions each time a new file lands.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your OVHcloud Object Storage files each time a new file lands.
    • Store visits reconciled to campaign spend, with no export step out of your OVHcloud Object Storage files.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in OVHcloud S Signals hash · dedupe Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, working out of OVHcloud Object Storage containers and objects.

    Teams on OVHcloud Object Storage who need counter and showroom revenue inside the same ROAS view as online orders out of OVHcloud Object Storage files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only S3 key scoped to the OVHcloud container you name, mapped to Google Ads' Store Sales Direct API and tuned for the store-sales match rate.

    2. Map

      Columns from your OVHcloud Object Storage files align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the file lands and checked for the store-sales match rate.

    3. Deliver

      Each time a new file lands, Signals reads your OVHcloud Object Storage files and matches in-person transactions to Google accounts as store-sales conversions, processes only the newly dropped file, with the store-sales match rate 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 Store Sales 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 OVHcloud records the event.
    ON THE WIRE

    What Store Sales actually receives.

    signals :: ovhcloud.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=ovhcloud.closed_deals
    3. transaction_time 2026-07-21T05:31:12 · transaction_amount_micros 13972000000
    4. currency_code AED
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=86%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from OVHcloud

    OVHcloud to Google OCI

    OVHcloud to Google Offline Conversions: your OVHcloud Object Storage files, hashed and…

    Learn more

    from OVHcloud

    OVHcloud to Meta Offline CAPI

    OVHcloud to Meta Offline CAPI: your OVHcloud Object Storage files, hashed and…

    Learn more

    same use case

    ActiveCampaign to Google Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the OVHcloud Google Store Sales sync run?

    You set the cadence, from near-real-time to a nightly OVHcloud sync of your OVHcloud Object Storage files into Google Ads. Since Signals processes only the newly dropped file, counter and showroom revenue inside the same ROAS view as online orders keeps pace and teams on OVHcloud Object Storage watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.

    What match rate should a OVHcloud-sourced Google Store Sales batch expect?

    Match rate follows identifier coverage in your OVHcloud Object Storage files, which teams on OVHcloud Object Storage control, not OVHcloud itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Store Sales Direct API pinpoints the store-sales match rate, the number teams on OVHcloud Object Storage tune against.

    NEXT STEP

    OVHcloud to Google Store Sales, in production this week.

    Talk to our team All OVHcloud use cases