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

    CONNECTIONS / GCS / GCS to LinkedIn Offline CAPI

    Your GCS objects, wired to LinkedIn account-revenue reporting.

    Connect GCS and point Signals at your GCS 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

    google-cloud-storage -> linkedin-offline-capi :: live

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

    WHAT THIS ENABLES

    GCS to LinkedIn Offline CAPI

    GCS to LinkedIn Offline CAPI: your GCS objects, hashed and consent-checked, feed LinkedIn as Signals reports closed B2B deals so LinkedIn optimizes on account revenue each time a new file lands.

    • Offline and in-store sales from your GCS 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 GCS objects by data teams landing exports in GCS.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off LinkedIn, away from any pixel. Here is how GCS closes the loop.

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn G File drop sync recorded in GCS 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 Google Cloud Storage buckets and objects.

    Data teams landing exports in GCS activating LinkedIn account-revenue reporting straight from GCS objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only service account scoped to the one GCS bucket you name to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      Signals picks up your GCS 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 GCS 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 GCS records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: google-cloud-storage.linkedin-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=google-cloud-storage.closed_deals
    3. conversion "urn:lla:llaPartnerConversion:51809"
    4. conversionHappenedAt 1784117809000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
    6. ✓ accepted · conversionValue 35714 USD
    RELATED USE CASES

    Adjacent moves on the same stack.

    from GCS

    GCS to Google OCI

    GCS to Google Offline Conversions: your GCS objects, hashed and consent-checked, feed…

    Learn more

    from GCS

    GCS to Google Store Sales

    GCS to Google Store Sales: your GCS objects, hashed and consent-checked, feed Google Ads as…

    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 GCS LinkedIn Offline CAPI sync run?

    The pace follows your GCS objects: Signals sends changes from GCS 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 data teams landing exports in GCS keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

    What match rate should a GCS-sourced LinkedIn Offline CAPI batch expect?

    Coverage of hashed identifiers across your GCS objects decides it, and data teams landing exports in GCS own that inside GCS. A live email or phone matches into LinkedIn; neither, and it will not. First-run feedback flags long B2B attribution windows, which data teams landing exports in GCS then raise inside your GCS objects.

    NEXT STEP

    GCS to LinkedIn Offline CAPI, in production this week.

    Talk to our team All GCS use cases