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

    CONNECTIONS / MongoDB / MongoDB to LinkedIn Offline CAPI

    From MongoDB collections to LinkedIn account-revenue reporting.

    Signals reads your MongoDB collections through a read-only database user scoped to the MongoDB collections you name, then reports closed B2B deals so LinkedIn optimizes on account revenue so LinkedIn sees offline conversions without an export.

    Talk to our team Explore the setup

    mongodb -> linkedin-offline-capi :: live

    1. ● mongodb → linkedin.capi :: live
    2. > read closed_deals rows=20,370
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 17,111 matched

    WHAT THIS ENABLES

    MongoDB to LinkedIn Offline CAPI

    MongoDB to LinkedIn Offline CAPI: Signals reads your MongoDB collections and reports closed B2B deals so LinkedIn optimizes on account revenue, hashed and consent-checked each time the read runs.

    • Signals reports closed B2B deals so LinkedIn optimizes on account revenue, reading your MongoDB collections each time the read runs.
    • Account revenue attached to the sourcing campaign, with no export step out of your MongoDB collections.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn Scheduled read sync recorded in MongoDB 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, working out of MongoDB collections and aggregation views.

    Application teams running MongoDB who need pipeline revenue tied to the LinkedIn campaigns that sourced it out of MongoDB collections.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MongoDB collections you name, mapped to LinkedIn's Conversions API and tuned for long B2B attribution windows.

    2. Map

      Columns from your MongoDB collections align to LinkedIn's Conversions API in the visual mapper, hashed as the read runs and checked for long B2B attribution windows.

    3. Deliver

      Each time the read runs, Signals reads your MongoDB collections and reports closed B2B deals so LinkedIn optimizes on account revenue, reads only the records changed since the last run, with long B2B attribution windows watched 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 MongoDB records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: mongodb.linkedin-offline-capi :: wire

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

    Adjacent moves on the same stack.

    from MongoDB

    MongoDB to Google OCI

    MongoDB to Google Offline Conversions: Signals reads your MongoDB collections and…

    Learn more

    from MongoDB

    MongoDB to Google Store Sales

    MongoDB to Google Store Sales: Signals reads your MongoDB collections and matches in-person…

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

    The pace follows your MongoDB collections: Signals sends changes from MongoDB to LinkedIn each time the read runs. Because it reads only the records changed since the last run, pipeline revenue tied to the LinkedIn campaigns that sourced it stays current while application teams running MongoDB keep long B2B attribution windows in view. Delivery needs no export and no manual upload.

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

    In MongoDB, match rate tracks the email and phone quality your MongoDB collections carry. Clean identifiers land for LinkedIn; blank ones never will. The first Conversions API report shows application teams running MongoDB where long B2B attribution windows needs work, a data-quality task handled in MongoDB.

    NEXT STEP

    MongoDB to LinkedIn Offline CAPI, in production this week.

    Talk to our team All MongoDB use cases