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

    CONNECTIONS / BigQuery / BigQuery to LinkedIn Leads CAPI

    From BigQuery datasets to LinkedIn lead-stage optimization.

    Point Signals at the dataset behind a read-only service account, and it reports deal-stage progress so LinkedIn favors opportunities that advance on the cadence your scheduled query already keeps.

    Talk to our team Explore the setup

    bigquery -> linkedin-leads-capi :: live

    1. ● bigquery → linkedin.capi :: live
    2. > read crm.lead_stage_history rows=53,978
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 43,722 matched

    WHAT THIS ENABLES

    BigQuery to LinkedIn Leads CAPI

    BigQuery to LinkedIn Leads CAPI: A scheduled query reads the qualified-lead and pipeline signals in your BigQuery tables, and Signals reports deal-stage progress so LinkedIn favors opportunities that advance, hashed and consent-checked whenever the scheduled query reruns.

    • Signals reports deal-stage progress so LinkedIn favors opportunities that advance, reading your BigQuery tables whenever the scheduled query reruns.
    • LinkedIn focus on the deals that actually advance, fed by analytics engineers running BigQuery scheduled queries.

    WHAT FLOWS WHERE

    BigQuery to Leads CAPI, mapped.

    A scheduled query hands the qualified-lead and pipeline signals to Signals, which hashes and consent-filters each row before LinkedIn's Leads Conversions API logs the lead conversions for opportunity-stage weighting.

    A scheduled query hands the qualified-lead and pipeline signals to Signals, which hashes and consent-filters each row before LinkedIn's Leads Conversions API logs the lead conversions for opportunity-stage weighting.

    WHO THIS IS FOR

    Built for the teams that own the number.

    B2B advertisers whose LinkedIn forms fill faster than they qualify, with the numbers already modeled in BigQuery tables and GA4 exports.

    Analytics engineers running BigQuery scheduled queries who need LinkedIn focus on the deals that actually advance.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only service account with dataViewer on the one dataset you nominate to feed LinkedIn's Leads Conversions API, sized for opportunity-stage weighting.

    2. Map

      A scheduled query reads your BigQuery tables, and its columns map to LinkedIn's Leads Conversions API in the visual mapper, hashed and checked for opportunity-stage weighting.

    3. Deliver

      Whenever the scheduled query reruns, Signals reports deal-stage progress so LinkedIn favors opportunities that advance, scans only the rows the query changed, with opportunity-stage weighting watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    LinkedIn focus on the deals that actually advance on every run, since Signals scans only the rows the query changed.

    Campaign focus on the deals that advance, delivered whenever the scheduled query reruns without BigQuery slot cost climbing.

    Each run returns a match report on opportunity-stage weighting from LinkedIn's Leads Conversions API, read from your BigQuery tables whenever the scheduled query reruns, at flat BigQuery slot cost.

    ON THE WIRE

    What Leads CAPI actually receives.

    signals :: bigquery.linkedin-leads-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=bigquery.crm.lead_stage_history
    3. conversion "urn:lla:llaPartnerConversion:65064"
    4. conversionHappenedAt 1783970064000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "b19e04…" }]
    6. ✓ accepted · conversionValue 3336 USD
    RELATED USE CASES

    Adjacent moves on the same stack.

    from BigQuery

    BigQuery to Meta Conversion Leads

    BigQuery to Meta CAPI for CRM: A scheduled query reads the qualified-lead and pipeline…

    Learn more

    from BigQuery

    BigQuery to Google EC for Leads

    BigQuery to Google EC for Leads: A scheduled query reads the qualified-lead and pipeline…

    Learn more

    same use case

    ActiveCampaign to LinkedIn Leads CAPI

    ActiveCampaign to LinkedIn Leads CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    LinkedIn Leads Conversions API

    Datahash sends CRM lead events to LinkedIn server-side, so campaigns optimize toward…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the BigQuery LinkedIn Leads CAPI sync run?

    The scheduled query sets the pace: rebuild the qualified-lead and pipeline signals nightly and delivery to LinkedIn is nightly, or refresh hourly for an hourly feed. Each run only reads the rows the query changed, so LinkedIn focus on the deals that actually advance stays current for opportunity-stage weighting while BigQuery slot cost barely moves.

    What match rate should a BigQuery-sourced LinkedIn Leads CAPI batch expect?

    Coverage in your BigQuery tables decides the rate, not BigQuery. A row with a current hashed email or phone matches; one missing both cannot, however the query is tuned. The first run's report from LinkedIn's Leads Conversions API sets a baseline, the number B2B advertisers whose LinkedIn forms fill faster than they qualify weigh against opportunity-stage weighting.

    NEXT STEP

    BigQuery to LinkedIn Leads CAPI, in production this week.

    Talk to our team All BigQuery use cases