LinkedIn promotions are generating clicks, and the website is receiving inquiries, but if sales records only “website” as the source, it is impossible to tell which posts, ads, and audiences brought in customers. Continuing to allocate budget based only on click volume can lead you to mistake traffic for lead generation results.
To track website inquiries generated by LinkedIn B2B promotions, connect links with UTM parameters, successful website form submission events, and CRM lead records: links identify the traffic source, events confirm that an inquiry was submitted, and the CRM helps determine whether the lead is qualified. First ensure that the source is captured in the customer record when the form is submitted; this is more important than simply installing tracking code.
A click on a form button is not the same as an inquiry. A user may fail to submit the form, submit it more than once, or simply open the contact page. We recommend defining a website inquiry as a form that has been successfully received in the backend and recorded as a lead. Track clicks on email, phone, and instant messaging buttons separately as contact intent, and do not count them directly as received inquiries.
Sales should then distinguish between spam, qualified inquiries, and sales opportunities. This makes it possible to answer two different questions: how many inquiries LinkedIn generated, and how many are worth following up on. Without this distinction, low-quality submissions may also be mistaken for successful promotion.
Ads, posts on the company page, and employee shares should not all use the same link if you need to distinguish between them. Create a UTM naming convention before publishing, and use lowercase English consistently to prevent the same source from being split into multiple entries due to differences in capitalization or spelling.
These values are naming examples, not a format mandated by the platform. The key is for the team to consistently follow the same rules and keep a record linking each campaign ID to its creative. Do not put personal information, such as customer names or email addresses, in URL parameters.
Before publishing, open the landing page using the final link and check that the parameters remain intact after URL shortening, redirects, and language switching. Do not add UTMs to on-site navigation, as this may overwrite the original external source.
The presence of UTMs in the address bar does not mean that the inquiry will automatically include its source. The website needs to read the parameters when the user arrives, store them for the configured retention period, and write them to the lead at submission through hidden fields or server-side logic.
We recommend retaining at least the first-touch source, the most recent non-direct source, the landing page, the submission page, the campaign ID, and the submission time. The first-touch source helps identify how customers initially arrived at the website, while the most recent non-direct source helps track touchpoints before submission. Do not let a direct return visit without parameters easily overwrite the existing source.

A user may arrive from LinkedIn on a product page, browse other pages, and only then submit a form. This path must be covered. For cross-subdomains, external forms, or booking pages, also confirm that the source can be passed to the final receiving system; the parameters on the initial landing page alone are usually not enough.
Parameter storage and tracking tags should comply with applicable privacy and consent requirements. Browser restrictions, users declining tracking, or switching devices may result in missing data, so it is not possible to guarantee that the source of every inquiry can be fully reconstructed.
Website analytics tools track the process from visit to submission, while LinkedIn conversion tracking is used to assess ad contributions. The two can be configured in parallel, but they should use consistent business definitions.
If you use both browser-side and server-side event reporting, deduplicate events using the method supported by the platform. Do not send the original form content or sensitive information in events without a valid reason.
Ad platform data and website records do not have to match exactly: a platform may count view-through conversions, while the website may recognize only visits from clicks with parameters. Attribution windows, time zones, and user consent status can also affect results. Confirm the measurement definitions before reconciling the data, rather than immediately assuming that one side is wrong.
When a form submission enters the CRM, write the inquiry ID and source fields to the record together to avoid relying on sales staff to select the channel manually. Sales should mainly add information on whether the inquiry matches the business, whether the lead is qualified, and whether it has progressed to a quote. Keep the promotional campaign ID traceable and do not change it when the follow-up status changes.
During reviews, compare visits, successful inquiries, qualified inquiries, and corresponding spend by campaign or creative. For paid promotions, “spend ÷ number of qualified inquiries” can be used to compare acquisition costs, but avoid drawing conclusions too soon if the leads have not yet been screened.
Because B2B sales cycles are longer, track sales progress over time by inquiry creation cohort. Do not divide this month’s new ad spend directly by all sales closed this month, as those sales may have come from earlier promotions.
If there are clicks but no visit records, first check redirects and tag loading. If a success event fires but there is no inquiry in the backend, first check the trigger conditions. If the backend has an inquiry but the CRM source is empty, first check the field mapping and storage logic. Fixing each break in the chain helps prevent effective promotions from being wrongly stopped before tracking is fully connected.
Related Articles
Related Products


