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

    CONNECTIONS / Tencent COS / Tencent COS to LinkedIn Offline CAPI

    Tencent COS objects into LinkedIn, built for LinkedIn account-revenue reporting.

    Connect Tencent COS and point Signals at your Tencent COS objects; it reports closed B2B deals so LinkedIn optimizes on account revenue each time a new file lands, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    tencent -> linkedin-offline-capi :: live

    1. ● tencent cos → linkedin.capi :: live
    2. > read closed_deals rows=15,027
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 13,073 matched

    WHAT THIS ENABLES

    Tencent COS to LinkedIn Offline CAPI

    LinkedIn Offline CAPI for Tencent COS: Signals reports closed B2B deals so LinkedIn optimizes on account revenue 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 LinkedIn, as Signals reports closed B2B deals so LinkedIn optimizes on account revenue.
    • Pipeline revenue tied to the LinkedIn campaigns that sourced it, 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 LinkedIn, away from any pixel. Here is how Tencent COS closes the loop.

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn 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.

    B2B teams whose deals close long after the impression, with the records already in Tencent Cloud COS buckets and objects.

    Teams running Tencent Cloud COS activating LinkedIn account-revenue reporting 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 LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      Signals picks up your Tencent COS objects, and its columns map to LinkedIn's Conversions API in the visual mapper, hashed and checked for long B2B attribution windows.

    3. Deliver

      On each run, Signals pulls your Tencent COS objects, reports closed B2B deals so LinkedIn optimizes on account revenue, and processes only the newly dropped file, with long B2B attribution windows 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.linkedin-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=tencent.closed_deals
    3. conversion "urn:lla:llaPartnerConversion:65053"
    4. conversionHappenedAt 1784111053000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
    6. ✓ accepted · conversionValue 40381 USD
    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 LinkedIn Offline CAPI

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

    Learn more

    generic

    LinkedIn Offline CAPI

    Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed…

    Learn more
    FAQ

    Asked on almost every call.

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

    The pace follows your Tencent COS objects: Signals sends changes from Tencent COS to LinkedIn each time a new file lands. Because it processes only the newly dropped file, pipeline revenue tied to the LinkedIn campaigns that sourced it stays current while teams running Tencent Cloud COS keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

    What match rate should a Tencent COS-sourced LinkedIn 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 LinkedIn; neither, and it will not. First-run feedback flags long B2B attribution windows, which teams running Tencent Cloud COS then raise inside your Tencent COS objects.

    NEXT STEP

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

    Talk to our team All Tencent COS use cases