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

    CONNECTIONS / Backblaze B2 / Backblaze B2 to Google Store Sales

    From Backblaze B2 files to Google Store Sales matching.

    Connect Backblaze B2 and point Signals at your Backblaze B2 files; it matches in-person transactions to Google accounts as store-sales conversions each time a new file lands, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    backblaze -> google-store-sales :: live

    1. ● backblaze b2 → google.sales :: live
    2. > read closed_deals rows=25,135
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 19,857 matched

    WHAT THIS ENABLES

    Backblaze B2 to Google Store Sales

    Backblaze B2 to Google Store Sales: your Backblaze B2 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.

    • Offline and in-store sales from your Backblaze B2 files activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
    • Counter and showroom revenue inside the same ROAS view as online orders, drawn from your Backblaze B2 files by teams archiving exports to Backblaze B2.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in Backblaze B2 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, with the records already in Backblaze B2 buckets and object prefixes.

    Teams archiving exports to Backblaze B2 activating Google Store Sales matching straight from Backblaze B2 files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only application key scoped to the Backblaze B2 bucket you name to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      Signals picks up your Backblaze B2 files, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.

    3. Deliver

      On each run, Signals pulls your Backblaze B2 files, matches in-person transactions to Google accounts as store-sales conversions, and processes only the newly dropped file, with the store-sales match rate 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 Backblaze B2 records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=backblaze.closed_deals
    3. transaction_time 2026-07-21T06:43:05 · transaction_amount_micros 18811000000
    4. currency_code USD
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=79%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Backblaze B2

    Backblaze B2 to Google OCI

    Backblaze B2 to Google Offline Conversions: your Backblaze B2 files, hashed and…

    Learn more

    from Backblaze B2

    Backblaze B2 to Meta Offline CAPI

    Backblaze B2 to Meta Offline CAPI: your Backblaze B2 files, hashed and consent-checked,…

    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 Backblaze B2 Google Store Sales sync run?

    The pace follows your Backblaze B2 files: Signals sends changes from Backblaze B2 to Google Ads each time a new file lands. Because it processes only the newly dropped file, counter and showroom revenue inside the same ROAS view as online orders stays current while teams archiving exports to Backblaze B2 keep the store-sales match rate in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Backblaze B2 files decides it, and teams archiving exports to Backblaze B2 own that inside Backblaze B2. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the store-sales match rate, which teams archiving exports to Backblaze B2 then raise inside your Backblaze B2 files.

    NEXT STEP

    Backblaze B2 to Google Store Sales, in production this week.

    Talk to our team All Backblaze B2 use cases