What Is Conversion Tracking?

    Quick answer

    Conversion tracking records valuable actions, such as form submissions or booked calls, and connects them to the ad, campaign or source that led to them.

    Conversion tracking is the process of recording the actions a business treats as valuable and linking each one back to the campaign, ad or source that led to it. In B2B, conversions typically include demo requests, contact form submissions, booked meetings, content downloads, trial sign-ups and, later in the funnel, qualified opportunities and closed deals. Tracking can happen in the browser, through tags such as the Google tag, the LinkedIn Insight Tag or the Meta Pixel; on a server, through integrations such as Meta's Conversions API; and through CRM or offline conversion imports that send later sales stages back to ad platforms. UTM parameters and hidden form fields carry source and campaign details into the CRM. Conversion data serves two purposes: it tells the business which activity produces results, and it gives ad platforms the signals they use to optimise delivery.

    Reviewed by the Growleady team · Updated 26 September 2026

    How Conversion Tracking Is Set Up

    Setting up conversion tracking starts with deciding which actions count and at which stage, then defining each event consistently across the website, ad platforms and CRM. Browser tags record on-site actions, server-side and CRM integrations can add events the browser cannot see, and deduplication stops the same action being counted twice when both methods are used. Source data such as UTM parameters should be captured on the form and stored on the lead record so it survives into reporting. Several dependencies shape what is possible. The consent framework decides whether and when tags can fire, browser privacy features and ad blockers limit browser-side data, and the website platform, CRM and technical environment determine which integrations are practical. Because of these limits, platform-reported conversions and CRM results rarely match exactly, so B2B teams usually treat the CRM as the reference for qualified pipeline and review tracking whenever forms, sites or consent settings change.

    Key Points

    • Conversion tracking records valuable actions and connects each one to the ad, campaign or source that led to it.
    • B2B conversions range from form submissions and booked meetings to qualified opportunities and closed deals.
    • Methods include browser tags, server-side integrations such as Meta's Conversions API, CRM or offline conversion imports and UTM source capture.
    • Consent settings, browser privacy features, ad blockers, the website platform and the CRM all limit what can be tracked.
    • Platform-reported conversions and CRM results rarely match exactly, so many B2B teams treat the CRM as the reference for pipeline.

    Conversion Tracking Example

    A B2B company runs Google, LinkedIn and Meta campaigns to a demo request page. When a visitor consents to tracking, the platform tags record the form submission, and hidden fields store the UTM source and campaign on the new CRM lead. The Meta Conversions API sends the same event from the server with an event ID so Meta can deduplicate it. When sales marks the lead as qualified, and later as an opportunity, those stage changes are imported back to the ad platforms that support it, so reporting and optimisation reflect sales progress rather than form fills alone.

    Related Terms

    Paid MediaMeta AdsLanding PageCRM AutomationLead Routing

    Want the work done for you? See our Paid Media services.

    Learn More

    Conversion Tracking FAQs

    Straight answers to common questions.

    What counts as a conversion in B2B?

    It depends on the funnel. Early conversions include form submissions, content downloads and booked meetings. Later conversions include qualified leads, opportunities and closed deals, which usually come from the CRM rather than the website.

    What is the difference between browser-side and server-side conversion tracking?

    Browser-side tracking uses tags that run in the visitor's browser. Server-side tracking sends events from a server or CRM directly to the ad platform, which can capture actions the browser does not see. Many setups combine both and deduplicate events.

    How does consent affect conversion tracking?

    Where consent is required, the consent framework controls whether and when tags can fire and what data can be sent. Some platforms offer modes that adjust tag behaviour based on consent choices. The business remains responsible for its consent decisions and privacy obligations.

    Why do ad platform numbers not match the CRM?

    Platforms use their own attribution windows and models, can only see actions their tags or integrations record, and may be affected by consent choices and browser privacy features. The CRM records what sales actually works. Differences are normal, so teams agree which source they use for each decision.

    What are UTM parameters used for?

    UTM parameters are tags added to a URL that record the source, medium, campaign and sometimes content or keyword. When a form captures them and stores them on the lead record, the CRM can report which campaigns produced each lead.