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

    CONNECTIONS / MySQL / MySQL to LinkedIn Leads CAPI

    From MySQL tables to LinkedIn lead-stage optimization.

    Signals reads your MySQL tables through a read-only database user scoped to the MySQL tables you name, then reports deal-stage progress so LinkedIn favors opportunities that advance so LinkedIn sees lead conversions without an export.

    Talk to our team Explore the setup

    mysql -> linkedin-leads-capi :: live

    1. ● mysql → linkedin.capi :: live
    2. > read lead_pipeline rows=73,236
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 57,856 matched

    WHAT THIS ENABLES

    MySQL to LinkedIn Leads CAPI

    MySQL to LinkedIn Leads CAPI: Signals reads your MySQL tables and reports deal-stage progress so LinkedIn favors opportunities that advance, hashed and consent-checked each time the read runs.

    • Signals reports deal-stage progress so LinkedIn favors opportunities that advance, reading your MySQL tables each time the read runs.
    • Campaign focus on the deals that advance, with no export step out of your MySQL tables.

    WHAT FLOWS WHERE

    MySQL to Leads CAPI, mapped.

    Signals reads the qualified-lead and pipeline signals from your MySQL tables each time the read runs, hashes and screens each record, and posts the lead conversions to LinkedIn's Leads Conversions API, keeping opportunity-stage weighting in view.

    Signals reads the qualified-lead and pipeline signals from your MySQL tables each time the read runs, hashes and screens each record, and posts the lead conversions to LinkedIn's Leads Conversions API, keeping opportunity-stage weighting in view.

    WHO THIS IS FOR

    Built for the teams that own the number.

    B2B advertisers whose LinkedIn forms fill faster than they qualify, working out of MySQL tables and views.

    Application teams on MySQL who need LinkedIn focus on the deals that actually advance out of MySQL tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MySQL tables you name, mapped to LinkedIn's Leads Conversions API and tuned for opportunity-stage weighting.

    2. Map

      Columns from your MySQL tables align to LinkedIn's Leads Conversions API in the visual mapper, hashed as the read runs and checked for opportunity-stage weighting.

    3. Deliver

      Each time the read runs, Signals reads your MySQL tables and reports deal-stage progress so LinkedIn favors opportunities that advance, reads only the records changed since the last run, 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 from your MySQL tables, delivered each time the read runs.

    Campaign focus on the deals that advance out of your MySQL tables, delivered each time the read runs without read load on the database climbing.

    Match feedback on opportunity-stage weighting from LinkedIn's Leads Conversions API each run, tied back to your MySQL tables.

    ON THE WIRE

    What Leads CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from MySQL

    MySQL to Meta Conversion Leads

    MySQL to Meta CAPI for CRM: Signals reads your MySQL tables and reports lead-stage progress…

    Learn more

    from MySQL

    MySQL to Google EC for Leads

    MySQL to Google EC for Leads: Signals reads your MySQL tables and sends down-funnel lead…

    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 MySQL LinkedIn Leads CAPI sync run?

    Delivery tracks MySQL, run by application teams on MySQL: a near-real-time or scheduled sync of your MySQL tables feeds LinkedIn on that cadence. Each run reads only the records changed since the last run, so campaign focus on the deals that advance holds up on opportunity-stage weighting. The live debugger confirms every delivery inline.

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

    Coverage of hashed identifiers across your MySQL tables decides it, and application teams on MySQL own that inside MySQL. A live email or phone matches into LinkedIn; neither, and it will not. First-run feedback flags opportunity-stage weighting, which application teams on MySQL then raise inside your MySQL tables.

    NEXT STEP

    MySQL to LinkedIn Leads CAPI, in production this week.

    Talk to our team All MySQL use cases