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

    CONNECTIONS / Tencent COS / Tencent COS to Google EC for Leads

    Tencent COS objects into Google Ads, built for Google Enhanced Conversions for Leads.

    Connect Tencent COS and point Signals at your Tencent COS objects; it sends down-funnel lead milestones matched to the originating Google click each time a new file lands, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    tencent -> google-ec-leads :: live

    1. ● tencent cos → google.leads :: live
    2. > read lead_pipeline rows=29,833
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 25,656 matched

    WHAT THIS ENABLES

    Tencent COS to Google EC for Leads

    Google EC for Leads for Tencent COS: Signals sends down-funnel lead milestones matched to the originating Google click straight from your Tencent COS objects, hashed and consent-screened each time a new file lands.

    • Qualified-lead and pipeline signals from your Tencent COS objects activated for Google Ads, as Signals sends down-funnel lead milestones matched to the originating Google click.
    • Lead-value bidding fed by the stages your pipeline actually reaches, drawn from your Tencent COS objects by teams running Tencent Cloud COS.

    WHAT FLOWS WHERE

    Tencent COS to EC for Leads, mapped.

    Signals picks up the qualified-lead and pipeline signals from your Tencent COS objects; Signals hashes and consent-screens each record before Google Ads' Enhanced Conversions API accepts the lead conversions for GCLID and hashed-email matching.

    Signals picks up the qualified-lead and pipeline signals from your Tencent COS objects; Signals hashes and consent-screens each record before Google Ads' Enhanced Conversions API accepts the lead conversions for GCLID and hashed-email matching.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Google lead-gen advertisers bidding past the first form submit, with the records already in Tencent Cloud COS buckets and objects.

    Teams running Tencent Cloud COS activating Google Enhanced Conversions for Leads 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' Enhanced Conversions API, sized for GCLID and hashed-email matching.

    2. Map

      Signals picks up your Tencent COS objects, and its columns map to Google Ads' Enhanced Conversions API in the visual mapper, hashed and checked for GCLID and hashed-email matching.

    3. Deliver

      On each run, Signals pulls your Tencent COS objects, sends down-funnel lead milestones matched to the originating Google click, and processes only the newly dropped file, with GCLID and hashed-email matching in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lead-value bidding fed by the stages your pipeline actually reaches on every run, as Signals reads your Tencent COS objects and processes only the newly dropped file.

    Lead-value signals matched to the paid click 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' Enhanced Conversions API on GCLID and hashed-email matching, straight out of your Tencent COS objects.

    ON THE WIRE

    What EC for Leads actually receives.

    signals :: tencent.google-ec-leads :: wire

    1. ● signals :: event payload
    2. > POST /conversion_action source=tencent.lead_pipeline
    3. gclid "Cj0KCQjw…" · conversion_action "sql_reached"
    4. conversion_value 8 · currency SAR
    5. hashed_email sha256 "9c41af…"
    6. ✓ accepted match=gclid+hashed_email
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Tencent COS

    Tencent COS to Meta Conversion Leads

    Meta CAPI for CRM for Tencent COS: Signals reports lead-stage progress so Meta bids toward…

    Learn more

    from Tencent COS

    Tencent COS to TikTok CRM

    TikTok CRM Integration for Tencent COS: Signals reports pipeline-stage changes to TikTok as…

    Learn more

    same use case

    ActiveCampaign to Google EC for Leads

    ActiveCampaign to Google EC for Leads: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Enhanced Conversions for Leads

    Datahash pushes hashed user data from your CRM back to Google Ads so lead-based campaigns…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Tencent COS Google EC for Leads 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, lead-value bidding fed by the stages your pipeline actually reaches stays current while teams running Tencent Cloud COS keep GCLID and hashed-email matching in view. Delivery needs no export and no manual upload.

    What match rate should a Tencent COS-sourced Google EC for Leads 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 and hashed-email matching, which teams running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

    Tencent COS to Google EC for Leads, in production this week.

    Talk to our team All Tencent COS use cases