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

    CONNECTIONS / Tencent COS / Tencent COS to Snap Offline CAPI

    Tencent COS objects into Snapchat, built for Snapchat in-store conversions.

    Connect Tencent COS and point Signals at your Tencent COS objects; it reports in-store purchases against the Snapchat campaigns that reached the buyer each time a new file lands, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

    tencent -> snap-offline-capi :: live

    1. ● tencent cos → snap.capi :: live
    2. > read closed_deals rows=48,200
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 42,898 matched

    WHAT THIS ENABLES

    Tencent COS to Snapchat Offline CAPI

    Snapchat Offline CAPI for Tencent COS: Signals reports in-store purchases against the Snapchat campaigns that reached the buyer 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 Snapchat, as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer.
    • Physical-world sales counted inside Snapchat performance, 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 Snap, away from any pixel. Here is how Tencent COS closes the loop.

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap File drop sync recorded in Tencent COS S Signals hash · dedupe Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Retail and QSR advertisers whose Snapchat audience buys in person, with the records already in Tencent Cloud COS buckets and objects.

    Teams running Tencent Cloud COS activating Snapchat in-store conversions 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 Snapchat's Conversions API, sized for offline event timing.

    2. Map

      Signals picks up your Tencent COS objects, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.

    3. Deliver

      On each run, Signals pulls your Tencent COS objects, reports in-store purchases against the Snapchat campaigns that reached the buyer, and processes only the newly dropped file, with offline event timing 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 Offline CAPI 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 Offline CAPI actually receives.

    signals :: tencent.snap-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=tencent.closed_deals
    3. event_type "PURCHASE" · event_conversion_type "OFFLINE"
    4. hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
    5. timestamp 1784346807 · price 41838 · currency SAR
    6. ✓ accepted · match=true
    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 Google Store Sales

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

    Learn more

    same use case

    ActiveCampaign to Snap Offline CAPI

    ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Snap Offline CAPI

    Deliver offline conversions to Snap on a schedule that fits your operations.

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Tencent COS Snap Offline CAPI sync run?

    The pace follows your Tencent COS objects: Signals sends changes from Tencent COS to Snapchat each time a new file lands. Because it processes only the newly dropped file, physical-world sales counted inside Snapchat performance stays current while teams running Tencent Cloud COS keep offline event timing in view. Delivery needs no export and no manual upload.

    What match rate should a Tencent COS-sourced Snap Offline CAPI 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 Snapchat; neither, and it will not. First-run feedback flags offline event timing, which teams running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

    Tencent COS to Snap Offline CAPI, in production this week.

    Talk to our team All Tencent COS use cases