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

    CONNECTIONS / Tencent COS / Tencent COS to Google Customer Match

    Tencent COS objects into Google Ads, built for Google Customer Match.

    Connect Tencent COS and point Signals at your Tencent COS objects; it projects your segments into Google Ads as Customer Match lists each time a new file lands, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    tencent -> google-customer-match :: live

    1. ● tencent cos → google.match :: live
    2. > read segments rows=63,984
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 56,306 matched

    WHAT THIS ENABLES

    Tencent COS to Google Customer Match

    Google Customer Match for Tencent COS: Signals projects your segments into Google Ads as Customer Match lists straight from your Tencent COS objects, hashed and consent-screened each time a new file lands.

    • Customer segments from your Tencent COS objects activated for Google Ads, as Signals projects your segments into Google Ads as Customer Match lists.
    • Customer Match lists that add joiners and drop lapsed members each sync, drawn from your Tencent COS objects by teams running Tencent Cloud COS.

    WHAT FLOWS WHERE

    Tencent COS to Customer Match, mapped.

    Signals picks up the customer segments from your Tencent COS objects; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    Signals picks up the customer segments from your Tencent COS objects; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Growth teams feeding Google audiences from governed first-party data, with the records already in Tencent Cloud COS buckets and objects.

    Teams running Tencent Cloud COS activating Google Customer Match 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' Customer Match API, sized for the serving-size threshold.

    2. Map

      Signals picks up your Tencent COS objects, and its columns map to Google Ads' Customer Match API in the visual mapper, hashed and checked for the serving-size threshold.

    3. Deliver

      On each run, Signals pulls your Tencent COS objects, projects your segments into Google Ads as Customer Match lists, and processes only the newly dropped file, with the serving-size threshold in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync on every run, as Signals reads your Tencent COS objects and processes only the newly dropped file.

    Lists that self-maintain across syncs from your Tencent COS objects, with transfer overhead steady because Signals processes only the newly dropped file.

    A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Tencent COS objects.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: tencent.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=tencent.segments
    3. operation ADD · user_list "segment_60635"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 63,984 · members_matched 56,306
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Tencent COS

    Tencent COS to Meta Custom Audience

    Meta Custom Audience for Tencent COS: Signals keeps Meta audiences synced as adds and…

    Learn more

    from Tencent COS

    Tencent COS to TikTok Custom Audience

    TikTok Custom Audience for Tencent COS: Signals delivers first-party segments to TikTok as…

    Learn more

    same use case

    ActiveCampaign to Google Customer Match

    ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Google Customer Match

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Tencent COS Google Customer Match 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, Customer Match lists that add joiners and drop lapsed members each sync stays current while teams running Tencent Cloud COS keep the serving-size threshold in view. Delivery needs no export and no manual upload.

    What match rate should a Tencent COS-sourced Google Customer Match 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 serving-size threshold, which teams running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

    Tencent COS to Google Customer Match, in production this week.

    Talk to our team All Tencent COS use cases