Support

Omea Consent · Guides

LinkedIn Conversions API on WordPress (no code)

Send WordPress conversions to the LinkedIn Conversions API without code or a tagging server – matched by hashed email or click ID, sent with consent.

Updated · Omea Consent 1.0.2

On this page
  1. Set it up
  2. How LinkedIn matches conversions
  3. De-duplication and consent
  4. Check it

LinkedIn’s Conversions API sends conversions from your server to LinkedIn, so B2B leads still count when the Insight Tag is blocked. It’s especially useful for lead generation, where every form fill matters. On WordPress there has been no simple way to set it up – Omea Consent Pro does it without code.

Set it up

  1. Switch on the Insight Tag Under Omea Consent › Integrations, switch on LinkedIn Insight Tag and paste your Partner ID.
  2. Create a Conversions API data source In LinkedIn Campaign Manager go to Data › Conversions API, add a data source and copy its access token.
  3. Turn on the Conversions API In the LinkedIn card, switch on Conversions API, paste the Access token and click Save changes.
  4. Create conversions in Campaign Manager Under Campaign Manager › Conversions, set up a conversion for each goal that should use the Conversions API, and note its ID.
  5. Map them in WordPress Under Omea Consent › Conversions, edit each conversion and paste the LinkedIn Conversion ID in its LinkedIn row.

The same LinkedIn Conversion ID is used by the Insight Tag in the browser and by the Conversions API, so you only map it once.

How LinkedIn matches conversions

LinkedIn needs one of two identifiers to match a conversion to a member:

  • the visitor’s email address, SHA-256 hashed – for example from a WooCommerce order or a new account, or
  • the LinkedIn click ID (li_fat_id) from an ad click.

If neither is available, the event is skipped – LinkedIn couldn’t use it anyway. Names are never sent to LinkedIn.

  • Each event carries the same ID as the Insight Tag’s event, so LinkedIn counts each conversion once.
  • Events are sent only with Marketing consent, checked on your server. The Insight Tag itself has no consent mode, so it always waits for Marketing consent too.

Check it

The LinkedIn card shows Latest server events with Sent or Error for each. For more help, see Conversions API events missing.

Developers: the LinkedIn API version header can be changed with the omea_consent_pro_linkedin_api_version filter.