Why it happens
The rule is not attached to ad sets
The rule is not attached to ad sets
Same failure as the Insight Tag: an unattached rule credits nobody. LinkedIn only tracks conversions attached to an ad set.
Events cannot be matched to members
LinkedIn matches events on identifiers like a hashed email or the LinkedIn click ID. Events that carry neither are received and attributed to nothing.
Events arrive late or with the wrong time
Conversions are credited by when they happened. A batch sent days later with the send time instead of the conversion time lands in the wrong place or outside the window.
Double counting with the Insight Tag
The same sign-up sent by the tag and the API without a shared event ID counts twice.
How to fix it, step by step
Create the rule
In Campaign Manager, go to Measure, then Conversion tracking, then Create conversion, and choose Conversions API.
Configure it
Name it, pick the category, set a value, choose the click and view windows and the attribution model, then continue.
Pick the source
Choose Direct API if your developers will send events from your server, or a partner such as Google Tag Manager, HubSpot or Zapier for a lighter setup.
Send identifiers
Include a SHA-256 hashed email and the LinkedIn click ID when you have it, plus the time the conversion actually happened.
Deduplicate with the tag
If the Insight Tag tracks the same event, send the same event ID from both so LinkedIn counts it once.
Attach ad sets and watch
Associate the rule with every relevant ad set. Check Conversion tracking for Active status and incoming events after a day.
Steps checked against LinkedIn Help articles: Set up a Conversions API integration in Campaign Manager; Conversions API setup in Campaign Manager best practices; LinkedIn Conversions API.
Sprites fixes this
Or let Sprites fix it
Sprites does the Campaign Manager side: the rule, its settings, the ad sets. Your server, CRM or partner sends the events.
What Sprites does
- Creates the Conversions API rule with the right category, attribution model and click and view windows. You approve it first.
- Attaches the rule to the ad sets that should be credited.
- Checks the Insight Tag on your site, so the browser and server sides cover the same events.
- Reads conversions by ad set once events flow, so a feed that stops shows up as a drop.
What it doesn't do
- Send Conversions API events from your server or CRM
Questions
Do I need a developer for the LinkedIn Conversions API?
For Direct API, yes. Partner integrations like Google Tag Manager, HubSpot or Zapier need little or no code.
Does the Conversions API replace the Insight Tag?
No. Keep the tag for website events and retargeting. Add the API for conversions the browser misses and for offline outcomes like qualified leads.
How do I stop double counting?
Send the same event ID from the Insight Tag and the Conversions API for the same conversion. LinkedIn keeps one.
Can I send CRM stages like SQL or closed deal?
Yes. Create a Conversions API rule per stage you care about and send the event when the record reaches that stage.
Does Sprites send the events for me?
No. Sprites creates and configures the conversion rules and attaches them to ad sets. The events come from your server, CRM or integration partner.
Let Sprites fix it
Connect the account. Sprites finds the cause, stages the change and waits for your approval.