CONNECTIONS / WooCommerce / WooCommerce to LinkedIn Offline CAPI
From WooCommerce orders to LinkedIn account-revenue reporting.
Signals reads your WooCommerce orders through scoped API access to WooCommerce, reading only your WooCommerce orders, then reports closed B2B deals so LinkedIn optimizes on account revenue so LinkedIn sees offline conversions without an export.
- ● woocommerce → linkedin.capi :: live
- > read closed_deals rows=20,974
- hash sha256(email,phone) consent=filtered
- route linkedin deliver
- ✓ delivered · 17,199 matched
WHAT THIS ENABLES
WooCommerce to LinkedIn Offline CAPI
LinkedIn Offline CAPI for WooCommerce: Signals reports closed B2B deals so LinkedIn optimizes on account revenue straight from your WooCommerce orders, hashed and consent-screened as orders complete.
- Signals reports closed B2B deals so LinkedIn optimizes on account revenue, reading your WooCommerce orders as orders complete.
- Account revenue attached to the sourcing campaign, with no export step out of your WooCommerce orders.
The click, the conversion, and the credit.
The conversion happens off LinkedIn, away from any pixel. Here is how WooCommerce closes the loop.
Built for the teams that own the number.
WordPress merchants running WooCommerce who need pipeline revenue tied to the LinkedIn campaigns that sourced it out of WooCommerce orders.
From kickoff to verified events.
-
Connect
Scoped API access to WooCommerce, reading only your WooCommerce orders, mapped to LinkedIn's Conversions API and tuned for long B2B attribution windows.
-
Map
Columns from your WooCommerce orders align to LinkedIn's Conversions API in the visual mapper, hashed as each order syncs and checked for long B2B attribution windows.
-
Deliver
As orders complete, Signals reads your WooCommerce orders and reports closed B2B deals so LinkedIn optimizes on account revenue, sends only the orders that changed, with long B2B attribution windows watched in the debugger.
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 WooCommerce records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /conversionEvents source=woocommerce.closed_deals
- conversion "urn:lla:llaPartnerConversion:40076"
- conversionHappenedAt 1783903076000
- user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
- ✓ accepted · conversionValue 32872 USD
Adjacent moves on the same stack.
from WooCommerce
WooCommerce to Google OCI
Google Offline Conversions for WooCommerce: Signals reconciles closed-won revenue to the…
Learn morefrom WooCommerce
WooCommerce to Google Store Sales
Google Store Sales for WooCommerce: Signals matches in-person transactions to Google…
Learn more
same use case
ActiveCampaign to LinkedIn Offline CAPI
ActiveCampaign to LinkedIn Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
LinkedIn Offline CAPI
Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed…
Learn moreAsked on almost every call.
How often does the WooCommerce LinkedIn Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly WooCommerce sync of your WooCommerce orders into LinkedIn. Since Signals sends only the orders that changed, pipeline revenue tied to the LinkedIn campaigns that sourced it keeps pace and WordPress merchants running WooCommerce watch long B2B attribution windows. One scoped connection sets it up, cadence adjustable later.
What match rate should a WooCommerce-sourced LinkedIn Offline CAPI batch expect?
Match rate follows identifier coverage in your WooCommerce orders, which WordPress merchants running WooCommerce control, not WooCommerce 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 WordPress merchants running WooCommerce tune against.
NEXT STEP