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

    CONNECTIONS / Tencent COS / Tencent COS to Google Store Sales

    Tencent COS objects into Google Ads, built for Google Store Sales matching.

    Connect Tencent COS and point Signals at your Tencent COS objects; 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

    tencent -> google-store-sales :: live

    1. ● tencent cos → google.sales :: live
    2. > read closed_deals rows=62,762
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 52,092 matched

    WHAT THIS ENABLES

    Tencent COS to Google Store Sales

    Google Store Sales for Tencent COS: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your Tencent COS objects, hashed and consent-screened each time a new file lands.

    • Offline and in-store sales from your Tencent COS objects 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 Tencent COS objects by teams running Tencent Cloud COS.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in Tencent COS 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 Tencent Cloud COS buckets and objects.

    Teams running Tencent Cloud COS activating Google Store Sales matching straight from Tencent COS objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Signals picks up your Tencent COS objects, 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 Tencent COS objects, 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 Tencent COS records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=tencent.closed_deals
    3. transaction_time 2026-07-20T04:55:09 · transaction_amount_micros 17413000000
    4. currency_code USD
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=83%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Tencent COS

    Tencent COS to Google OCI

    Google Offline Conversions for Tencent COS: Signals reconciles closed-won revenue to the…

    Learn more

    from Tencent COS

    Tencent COS to Meta Offline CAPI

    Meta Offline CAPI for Tencent COS: Signals credits dealer, branch, and phone sales to the…

    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 Tencent COS Google Store Sales sync run?

    The pace follows your Tencent COS objects: Signals sends changes from Tencent COS 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 running Tencent Cloud COS keep the store-sales match rate in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Tencent COS objects decides it, and teams running Tencent Cloud COS own that inside Tencent COS. 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 running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

    Tencent COS to Google Store Sales, in production this week.

    Talk to our team All Tencent COS use cases