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

    CONNECTIONS / Tencent COS / Tencent COS to Google OCI

    Tencent COS objects into Google Ads, built for Google Ads offline conversion import.

    Connect Tencent COS and point Signals at your Tencent COS objects; it reconciles closed-won revenue to the Google Ads click through GCLID each time a new file lands, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    tencent -> google-oci :: live

    1. ● tencent cos → google.oci :: live
    2. > read closed_deals rows=13,374
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 10,432 matched

    WHAT THIS ENABLES

    Tencent COS to Google Offline Conversions

    Google Offline Conversions for Tencent COS: Signals reconciles closed-won revenue to the Google Ads click through GCLID 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 reconciles closed-won revenue to the Google Ads click through GCLID.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, 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 Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, with the records already in Tencent Cloud COS buckets and objects.

    Teams running Tencent Cloud COS activating Google Ads offline conversion import 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' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals picks up your Tencent COS objects, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      On each run, Signals pulls your Tencent COS objects, reconciles closed-won revenue to the Google Ads click through GCLID, and processes only the newly dropped file, with GCLID coverage 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 OCI 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 OCI actually receives.

    signals :: tencent.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=tencent.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-18T18:20:40"
    5. conversion_value 44955 · currency_code AED
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Tencent COS

    Tencent COS to Google Store Sales

    Google Store Sales for Tencent COS: Signals matches in-person transactions to Google…

    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 OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Tencent COS Google OCI 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, Smart Bidding trained on booked revenue instead of a mid-funnel proxy stays current while teams running Tencent Cloud COS keep GCLID coverage in view. Delivery needs no export and no manual upload.

    What match rate should a Tencent COS-sourced Google OCI 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 GCLID coverage, which teams running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

    Tencent COS to Google OCI, in production this week.

    Talk to our team All Tencent COS use cases