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

    CONNECTIONS / Tencent COS / Tencent COS to Meta Custom Audience

    Tencent COS objects into Meta, built for Meta lookalike and suppression seeds.

    Connect Tencent COS and point Signals at your Tencent COS objects; it keeps Meta audiences synced as adds and removals so lists never drift each time a new file lands, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    tencent -> meta-custom-audience :: live

    1. ● tencent cos → meta.audience :: live
    2. > read segments rows=13,757
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 10,730 matched

    WHAT THIS ENABLES

    Tencent COS to Meta Custom Audience

    Meta Custom Audience for Tencent COS: Signals keeps Meta audiences synced as adds and removals so lists never drift 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 Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
    • Lookalike seeds and suppression lists that track your live customer base, drawn from your Tencent COS objects by teams running Tencent Cloud COS.

    WHAT FLOWS WHERE

    Tencent COS to Custom Audience, mapped.

    Signals picks up the customer segments from your Tencent COS objects; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    Signals picks up the customer segments from your Tencent COS objects; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, with the records already in Tencent Cloud COS buckets and objects.

    Teams running Tencent Cloud COS activating Meta lookalike and suppression seeds 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 Meta's Custom Audiences API, sized for audience refresh cadence.

    2. Map

      Signals picks up your Tencent COS objects, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.

    3. Deliver

      On each run, Signals pulls your Tencent COS objects, keeps Meta audiences synced as adds and removals so lists never drift, and processes only the newly dropped file, with audience refresh cadence in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Tencent COS objects and processes only the newly dropped file.

    Always-current lookalike seeds and exclusions from your Tencent COS objects, with transfer overhead steady because Signals processes only the newly dropped file.

    A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Tencent COS objects.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: tencent.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=tencent.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 13,757 · num_invalid_entries 408
    5. audience_id "1665303" · session "upsert"
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Tencent COS

    Tencent COS to Google Customer Match

    Google Customer Match for Tencent COS: Signals projects your segments into Google Ads as…

    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 Meta Custom Audience

    ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Custom Audience

    Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Tencent COS Meta Custom Audience sync run?

    The pace follows your Tencent COS objects: Signals sends changes from Tencent COS to Meta each time a new file lands. Because it processes only the newly dropped file, lookalike seeds and suppression lists that track your live customer base stays current while teams running Tencent Cloud COS keep audience refresh cadence in view. Delivery needs no export and no manual upload.

    What match rate should a Tencent COS-sourced Meta Custom Audience 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 Meta; neither, and it will not. First-run feedback flags audience refresh cadence, which teams running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

    Tencent COS to Meta Custom Audience, in production this week.

    Talk to our team All Tencent COS use cases