Why does my LinkedIn Conversions API show 'Low Match Rate', and how do I raise it?

TofuAnswer by the Tofu team · checked

It means LinkedIn can't tie enough of your events to members, and the fix is more identifiers: a SHA-256 hashed email plus LinkedIn's li_fat_id click ID. LinkedIn recommends that pair "for the best matching," then first and last name, company, job title, country and IP address where you have them. Lowercase and trim emails before hashing, send events within a day, and check the conversion's status panel a few hours later.

Ask Tofu next

Pick a question and Tofu Ads Agent answers it in chat.

As of November 2026.

Before you start

  • Access to the ad account in Campaign Manager, to read the conversion's status panel.
  • Access to whatever sends the events: your own code, or a partner such as Google Tag Manager, HubSpot or Zapier.
  • A sample event, so you can see which fields each one carries today.
  • One caveat: LinkedIn's signal quality page says its check "is only applicable for conversions based on Direct API integration." If a partner sends your events, the partner decides which fields go out, so check its settings too.

Step 1: Find out which match rate is low

Go to Measure, then Conversion tracking, and click Active in the Status column. The panel shows details, including the match rate percentage. LinkedIn says event counts and match rate can take a few hours to fill in.

LinkedIn's developer FAQ describes two match rates:

Match rateWhat it measuresIf it's low
IdentityHow well LinkedIn can tie your events to LinkedIn membersSteps 2 to 6
AttributionOf the matched members, how many clicked or viewed an ad from the ad sets linked to the conversion, inside its windowStep 7

The "Low Match Rate" label is about identity. LinkedIn shows it under Active when the data you stream has "a low likelihood of successful event-to-profile matching." It matters because, as LinkedIn puts it, "we can only attribute conversions to members we successfully match," and only matched events feed optimization.

Step 2: Hash emails the way LinkedIn expects

Send email as SHA256_EMAIL:

  1. Convert the address to lowercase.
  2. Remove all whitespace.
  3. Hash it with SHA-256, without salt.
  4. Send the hex string (64 characters).

LinkedIn's FAQ says lowercasing first gives "better match rates." A salted hash, a stray space or capital letters produce a different string, which can't match. Hash one address you know yourself and compare it with what your system sends.

An email can be hashed perfectly and still miss. LinkedIn doesn't say which of a member's emails it checks for Conversions API events, and members can add several to their account. If a buyer's LinkedIn account doesn't carry the work address in your CRM, that email alone may not find them. That's where the click ID helps.

Step 3: Capture the li_fat_id click ID and send it

LinkedIn's FAQ says the click ID "helps increase match rates significantly." It's tied to the ad click itself, so it doesn't depend on which email the person used.

  1. Turn on enhanced conversion tracking. Go to Measure > Signals manager > Insight Tag, open the Manage Insight Tag menu, select Settings, check Enable enhanced conversion tracking and save. LinkedIn's two sources differ here: its developer docs say it's "enabled by default" for recently created tags, while its help pages describe it as a checkbox you turn on and mention no default. Check the box either way.
  2. Let LinkedIn add the click ID. From then on, LinkedIn adds li_fat_id to your landing page URLs when someone clicks an ad.
  3. Capture it on your site. Read it from the URL, or from the li_fat_id cookie if the Insight Tag is installed. Put it in a hidden form field so it's saved with the lead in your CRM.
  4. Send it with every event as LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID, including later MQL and SQL events.

The timing works for long B2B cycles. The cookie lasts 30 days from the most recent ad click, but LinkedIn stores the link between a click ID and a member for 365 days, so a click ID saved at form fill can still match an SQL sent months later, within that year. If you only parse the URL (no Insight Tag on the site), LinkedIn's developer docs say view-through attribution may be limited, and its help says view-through conversions aren't available that way, though sending other IDs, such as a hashed email, can help enable them.

Test it: click one of your own ads and check that li_fat_id is still in the URL after any redirects, and that it lands in the form field.

Step 4: Add names, company, title and country

The userInfo object adds what LinkedIn's schema calls "probabilistic user matching":

FieldRule
First and last nameBoth are needed if you send either. Plain text, or since API version 202609, hashedFirstName and hashedLastName: lowercase, no spaces or punctuation, UTF-8, then SHA-256
companyNamePlain text, optional
titlePlain text, optional
countryCodeTwo-letter code such as US, optional

LinkedIn's signal quality page calls job title, company and country "secondary identifiers." Email, click ID, IP address and third-party IDs are the primary ones.

Step 5: Add IP address and the other IDs you have

  • IP address. PLAINTEXT_IP_ADDRESS (added May 2026) or SHA256_IP_ADDRESS (added September 2026), IPv4 only. LinkedIn suggests it for upper-funnel events such as page views.
  • Lead Gen Form leads. If the lead came from a LinkedIn Lead Gen Form, send the form response ID in the lead field (urn:li:leadGenFormResponse:{id}). LinkedIn accepts it as an identifier on its own.
  • Third-party IDs. ACXIOM_ID (LiveRamp's identity graph) and GOOGLE_AID (Android devices, added May 2026).
  • Your own user ID. Send it in externalIds alongside the standard IDs. Once matched, LinkedIn keeps the link for one year and uses it across ad accounts in the same Business Manager, so later events can carry just that ID. Only one external ID per event counts.

LinkedIn's advice is to send the identifiers that fit each event type: IP for page views, hashed names for leads and offline events.

Step 6: Send events quickly and steadily

LinkedIn asks for events in real time, "or ideally within a day." Events with a timestamp older than 90 days fail validation. LinkedIn also says to keep event volume steady, since a sudden drop can mean tracking broke, and to review your setup regularly.

Step 7: If members match but conversions aren't credited

That's the attribution match rate. A matched member only counts if they clicked or viewed an ad from the ad sets attached to the conversion, inside the conversion window. Attaching the conversion to the right ad sets and checking the window are covered in why LinkedIn shows zero conversions. For longer windows on qualified leads, see how to send MQLs and SQLs from your CRM to LinkedIn.

Common problems

ProblemWhy it happensFix
CRM stage events (MQL, SQL) show Low Match RateThey're sent long after the click, and carry no click ID unless you saved it at form fillSave li_fat_id at form fill and send it with every later event, plus names and company
Match rate fell after a site changeA redirect or form rebuild dropped li_fat_id or the hidden fieldClick your own ad and trace the ID to the CRM
Correct emails don't matchCapitals or spaces before hashing, or a salted hashLowercase, trim, unsalted SHA-256
Request rejectedA first name sent without a last name, or a timestamp over 90 days oldSend both names; send events sooner
Partner setup matches poorlyThe partner may send only a hashed emailCheck which fields it can share and turn on the rest

Contact list uploads have their own match rate with different rules. If those match poorly too, see why only a small share of a contact list matches on LinkedIn.

Sources (9)

Related resources