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

    CONNECTIONS / WordPress / WordPress to LinkedIn Offline CAPI

    Your WordPress orders, wired to LinkedIn account-revenue reporting.

    Connect WordPress and point Signals at your WordPress orders; it reports closed B2B deals so LinkedIn optimizes on account revenue as orders complete, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    wordpress -> linkedin-offline-capi :: live

    1. ● wordpress → linkedin.capi :: live
    2. > read closed_deals rows=34,941
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 28,302 matched

    WHAT THIS ENABLES

    WordPress to LinkedIn Offline CAPI

    WordPress to LinkedIn Offline CAPI: Signals reads your WordPress orders and reports closed B2B deals so LinkedIn optimizes on account revenue, hashed and consent-checked as orders complete.

    • Offline and in-store sales from your WordPress orders 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 WordPress orders by content-led merchants on WordPress.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn Order sync recorded in WordPress 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 WordPress orders, users, and form entries.

    Content-led merchants on WordPress activating LinkedIn account-revenue reporting straight from WordPress orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to WordPress, reading only your WordPress orders to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      Signals reads your WordPress orders, 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 WordPress orders, reports closed B2B deals so LinkedIn optimizes on account revenue, and sends only the orders that changed, 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 WordPress records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from WordPress

    WordPress to Google OCI

    WordPress to Google Offline Conversions: Signals reads your WordPress orders and reconciles…

    Learn more

    from WordPress

    WordPress to Google Store Sales

    WordPress to Google Store Sales: Signals reads your WordPress orders 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 WordPress LinkedIn Offline CAPI sync run?

    Delivery tracks WordPress, run by content-led merchants on WordPress: a near-real-time or scheduled sync of your WordPress orders feeds LinkedIn on that cadence. Each run sends only the orders that changed, so account revenue attached to the sourcing campaign holds up on long B2B attribution windows. The live debugger confirms every delivery inline.

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

    Match rate follows identifier coverage in your WordPress orders, which content-led merchants on WordPress control, not WordPress itself. A record with a current hashed email or phone matches for LinkedIn; one missing both cannot. First-run feedback from Conversions API pinpoints long B2B attribution windows, the number content-led merchants on WordPress tune against.

    NEXT STEP

    WordPress to LinkedIn Offline CAPI, in production this week.

    Talk to our team All WordPress use cases