LinkedIn Conversion Tracking: Insight Tag, Website Actions, and CAPI in 2026
Set up the Insight Tag and Website Actions for web outcomes, and CAPI or CSV for CRM stages — with Qualified Lead as the lifecycle category to favor and rules associated to campaigns.
Updated July 22, 2026.
LinkedIn conversion tracking has three current source families: website conversions through the Insight Tag or Microsoft UET, server/CRM outcomes through Conversions API, and offline outcomes through CSV. The conversion rule is not operational until it is associated with the ad sets that should use it.
Verification boundary. This guide was checked against official LinkedIn Marketing Solutions advertiser help, developer documentation, and release notes available on July 22, 2026. It does not rely on agency blogs, community posts, or third-party tutorials. Interface labels can differ during account-level rollouts. Where the official documentation describes a pilot, gradual rollout, regional limit, or incomplete availability, the guide says so rather than assuming access.LinkedIn’s create-conversion help page was updated July 15, 2026. This guide uses Qualified Lead as the preferred current lifecycle category because LinkedIn’s 2026 API release notes deprecate older MQL/SQL categories in favor of Qualified Lead.
Current conversion sources
| Source | Best for | Key limitation |
|---|---|---|
| Insight Tag manual website conversion | URL rules or event-specific tracking on a website | Requires correct tag coverage and a rule/event that represents completion. |
| Website Actions | Automatically observed page visits, button clicks and form submissions | Actions must populate after the Insight Tag runs; sensitive-data restrictions apply. |
| Microsoft UET website source | Eligible Microsoft UET-based website tracking inside LinkedIn’s current source options | Confirm availability and source mapping in the account. |
| Conversions API | Website/server and CRM lifecycle events | Requires an approved direct, partner or GTM path and a conversion rule attached to ad sets. |
| CSV conversion | Periodic offline or CRM events | Upload cadence and timely data materially affect optimization. |
| CRM Sync | Automatic creation/mapping where an eligible CRM integration is connected | Availability and field mapping depend on CRM partner and account. |
Step 1: Install the Insight Tag
- Open Campaign Manager and select the correct ad account.
- Open the data/conversion area and select the Insight Tag setup.
- Choose the official installation method available: direct code, tag manager or supported partner.
- Install one governed Insight Tag across the intended website. LinkedIn recommends one tag per website.
- Use Campaign Manager’s status view to confirm receipt. Allow for the processing interval described in the account.
- Verify that the tag does not transmit sensitive data through page URLs, titles, form fields or custom parameters.
The Insight Tag supports conversion tracking, retargeting and Website Actions. Do not install a second tag merely to create a second conversion; conversion rules sit on top of the same website source.
Step 2: Create a conversion rule
- In Campaign Manager, open Measurement and Conversion tracking.
- Choose Create conversion.
- Select the source: website, Conversions API, CSV or another source displayed in the current account.
- Name the conversion and select the closest current category.
- Choose value behavior: fixed value, dynamic value where supported, or no assigned value.
- Set click-through and view-through windows offered for the category.
- Select the attribution model shown in the current workflow.
- Define the source-specific rule or mapping.
- Associate the conversion with the ad sets that should track and optimize toward it.
Current official categories include: Key page view, Video view, Register event, Sign up, Download, Lead, Book appointment, Contact, Qualified Lead, Submit application, Add to cart, Purchase, Other.
Step 3: Choose manual website rules or Website Actions
Manual website conversion
Use a manual website rule when a URL or explicit event represents the action reliably. Define the page or event condition, test all URL variants and confirm it does not fire on preview, edit or error pages.
Website Actions
Website Actions uses Insight Tag observations to surface button clicks, page visits and form submissions. LinkedIn says actions typically become available after the tag has been active and can take additional time to recognize new actions.
- Confirm the Insight Tag status is active.
- Open Website Actions and locate the observed page, form or button action.
- Review the URLs and element description carefully. Similar button text across the site can represent different business actions.
- Create a conversion from the selected Website Action.
- Set category, value, windows and attribution.
- Associate it with the correct ad sets.
- Retest after website redesigns or form-provider changes.
Website Actions is convenient, but observed interaction is not always confirmed success. For a critical lead, prefer an event or server/CRM outcome that confirms acceptance.
Step 4: Use the right category
| Business outcome | Current category | Guidance |
|---|---|---|
| Content download | Download | Use only after the asset is delivered or request accepted. |
| Web form lead | Lead | Separate from later Qualified Lead. |
| Meeting scheduled | Book appointment | Trigger on confirmed booking. |
| Sales-qualified or accepted lead | Qualified Lead | Preferred current lifecycle category; older MQL/SQL API categories are deprecated. |
| Application submitted | Submit application | Use for completed applications. |
| Order or paid transaction | Purchase | Send value and currency consistently. |
| Distinct action with no accurate category | Other | Document the business definition and eligibility. |
Step 5: Configure Conversions API
LinkedIn supports direct CAPI, approved partner integrations and an official Google Tag Manager path. The server event does not replace the need to create a LinkedIn conversion rule and associate it with ad sets.
- Create the conversion rule using the Conversions API source or follow the current sequence in Campaign Manager.
- Select the closest category, value behavior, windows and attribution model.
- Choose direct, partner or GTM setup.
- For a direct integration, use LinkedIn’s current Marketing API version and schema. Send the required conversion timestamp, conversion URN/rule reference and permitted user identifiers.
- For CRM stages, emit the event when the stage transition is authoritative, not when a dashboard report is generated.
- Test with a controlled record and inspect processing/diagnostics.
- Associate the rule with every ad set that should use it.
Browser and server together
LinkedIn’s official CAPI use-case guidance recommends browser and server sources where appropriate and describes duplicate handling. Keep separate conversion rules by data source when the official workflow requires it, and use the current deduplication fields and identifiers in LinkedIn’s schema. Do not assume that two rules with similar names automatically deduplicate.
Step 6: Upload CRM or offline events by CSV
- Create a CSV-source conversion in Campaign Manager.
- Select category, value, currency behavior, windows and attribution.
- Download the current template from the account rather than copying an old column list.
- Map the click/member/customer fields permitted by the current template and your consent basis.
- Use a conversion timestamp that reflects when the business event occurred.
- Ensure currency values match the ad account’s requirements.
- Upload a small test file and resolve row errors.
- Schedule repeat uploads. LinkedIn recommends timely, recurring qualified-lead data; do not wait until quarter-end.
- Associate the conversion with the relevant ad sets.
LinkedIn’s current help supports common click/view windows and longer windows for selected categories such as Qualified Lead, Lead, Purchase, Add to Cart and Submit Application. Use only the options shown for the category in your account.
Step 7: Build a B2B event ladder
| Stage | Event source | Bidding treatment |
|---|---|---|
| Landing-page engagement | Insight Tag / Website Actions | Reporting or retargeting; rarely the core conversion. |
| Form lead | Website event | Primary only when it correlates with quality and volume is needed. |
| Booked meeting | Website or scheduling backend | Stronger optimization event when reliably captured. |
| Qualified Lead | CRM via CAPI/CSV/CRM Sync | Preferred downstream signal when volume and upload speed support it. |
| Opportunity | CRM custom/Other or supported lifecycle mapping | Use as high-value reporting or optimization based on eligibility. |
| Closed revenue | CRM purchase/revenue event | Use real value for revenue measurement and eligible optimization. |
Step 8: Associate and audit ad sets
Association is a recurring failure point. When creating or editing an ad set, confirm the intended conversion rule is selected. When adding a new conversion after campaigns are live, audit existing ad sets; do not assume they inherit it automatically.
QA checklist
- One correct Insight Tag covers all intended pages.
- Website Actions are reviewed for actual success rather than ambiguous clicks.
- Conversion category uses current terminology, including Qualified Lead rather than deprecated MQL/SQL categories.
- Fixed or dynamic value reflects a documented business value.
- Click and view windows match the sales cycle and available category options.
- CAPI/CSV timestamps use the actual event time.
- Customer identifiers are permitted, normalized and mapped correctly.
- Browser and server sources follow LinkedIn’s current duplicate-handling design.
- Every intended ad set is associated with the conversion.
- Campaign Manager totals reconcile with website, CRM and order records.
Common failures
| Failure | Cause | Correction |
|---|---|---|
| Conversion receives no campaign credit | Rule was never associated with the ad set | Attach it to current and future ad sets. |
| Website Action counts intent, not completion | Generic button click selected | Use confirmed form success or server/CRM event. |
| MQL/SQL naming persists in API build | Old schema/category assumptions | Migrate to Qualified Lead per current 2026 release notes. |
| CSV optimization is stale | Monthly or quarterly uploads | Send qualified events on a consistent, timely cadence. |
| Two sources inflate totals | Separate browser/server rules without correct duplicate design | Follow current LinkedIn CAPI use-case and schema guidance. |
| Sensitive values leak in URLs | Forms or pages put user data in query strings | Remove sensitive data and review Insight Tag restrictions. |
Implementation blueprints
Website-first B2B program
| Action | LinkedIn category | Source | Use |
|---|---|---|---|
| Pricing or case-study view | Key page view | Insight Tag / Website Actions | Secondary and audience signal |
| Demo form accepted | Lead | Manual website event or confirmed Website Action | Initial primary |
| Demo booked | Book appointment | Scheduler success/backend | Higher-intent primary |
| Sales accepted | Qualified Lead | CAPI, CRM Sync or CSV | Downstream primary |
| Customer/revenue | Purchase or eligible rule | CRM/billing | Revenue reporting |
Each rule must be associated with the ad sets that should use it. Add this association check to campaign duplication and bulk-edit QA.
Native Lead Gen Form program
Map the native lead ID, form, campaign/ad-set metadata, consent fields and submission time into the CRM. Reconcile native leads with website leads under one contact-merge policy. The Qualified Lead event should reference the accepted CRM record, not a separate spreadsheet maintained by the media team.
Conversion-rule governance
- Use one current category per business stage.
- Prefer Qualified Lead for current lifecycle mapping rather than deprecated MQL/SQL API categories.
- Record click and view windows by rule.
- Record whether value is fixed, dynamic or absent.
- Record data source and upload cadence.
- Audit ad-set association whenever a rule changes.
Release acceptance criteria
- Insight Tag is active and does not expose sensitive URL data.
- Website Actions have been observed and manually validated.
- CAPI/CSV test event processes with the actual conversion timestamp.
- Qualified Lead mapping matches the CRM definition.
- Every intended ad set has the rule attached.
- Native and website lead duplication is quantified and explained.
Verification record
Technically verified: July 22, 2026
Official-source rule: Every platform-specific instruction and feature statement in this article is grounded in an official LinkedIn source. The implementation recommendations are editorial guidance from The Ad Spend and are labeled as such.
Known limits at publication
- Website Actions requires observed activity and can take time to populate or recognize new actions.
- CRM Sync and Microsoft UET source availability can vary by account and integration.
- Longer attribution windows are category-specific.
- API versions and schemas are versioned; direct integrations must use the current supported version.
Official sources consulted
- Create conversions in Campaign Manager
- LinkedIn Insight Tag
- Website Actions
- Conversion categories
- Set up conversions with CSV
- Upload conversions with CSV
- Set up Conversions API
- Conversions API overview
- Conversions API use cases
- Marketing API recent changes
Related conversion tracking references
The Ad Spend
B2B conversions are decided in the CRM long after the click, which is exactly where the record breaks. The Ad Spend keeps the operating record around changes, timing, and decisions, giving analysts cleaner context when they interpret what a test or model is actually measuring. See History.