Paid Strategy

How to Set Up UTM Parameters for B2B Paid Campaigns

By The Tofu team · · 8 min read

B2B companies should tag paid campaigns with five parameters (source, medium, campaign, content, term) using a fixed lowercase naming convention and each platform's dynamic tokens, then capture the values into hidden form fields that write to Salesforce or HubSpot, storing both first-touch and last-touch so pipeline reports by channel, campaign and creative.

Key takeaways

  • Use only five UTM parameters for B2B paid media: source, medium, campaign, content and term, each with a fixed naming rule.
  • LinkedIn and Google Ads let you set a tracking parameter once at the account or campaign level, while Meta's URL parameters field sits on each individual ad, so dynamic tokens there cut typing but don't remove the need to tag every ad.
  • UTM values only help pipeline reporting once they're captured into hidden form fields and mapped to the Lead, Contact and Opportunity in Salesforce or HubSpot.
  • Store first-touch and last-touch UTM values on separate fields; one shows what created demand, the other shows what closed it.
  • LinkedIn Lead Gen Forms don't load your landing page, so standard UTM capture scripts can't reach them; use LinkedIn's native lead fields and CRM sync instead.

Most B2B teams tag LinkedIn, Google and Meta campaigns with UTM parameters, then can't answer the question that matters: which campaign and creative produced the opportunities in Salesforce or HubSpot. The fix is building the parameters backwards from the CRM report you want, then capturing them onto the lead, contact and opportunity record before the data reaches a dashboard.

Below is the exact parameter schema, the dynamic tokens each ad platform supports, the capture step most teams skip, and the mistakes that quietly break reporting after launch.

What each UTM parameter should hold in a B2B paid program

A UTM parameter is a tag appended to a destination URL that tells your analytics tool and CRM where a click came from. Five parameters cover a B2B paid program; don't invent more.

ParameterWhat it holdsB2B example
utm_sourceThe ad platformlinkedin, google, meta
utm_mediumThe paid channel type, not just "cpc"paid-social, paid-search, display, paid-social-retargeting
utm_campaignA slug that matches the campaign name in the ad platform, not a free-text description2026-q1-demandgen-series-b-funding
utm_contentThe specific ad or creative variant, so you can tell two carousels apartcarousel-v3-roi-stat, image-logo-wall
utm_termThe audience segment or keyword that triggered the admatched-accounts-revops, kw-forecasting-software-exact

The test for every value: could someone in marketing ops filter a Salesforce report by this field and get a clean answer, with no manual cleanup. If the answer is no, the value is too vague or too specific.

Build the naming convention before you build a single campaign

A naming convention is a fixed set of rules for how each parameter value is written, so the same campaign never shows up as two different rows in a report. Agree on these four rules before anyone launches a campaign:

  • Lowercase everything. utm_source=LinkedIn and utm_source=linkedin are two different values to most CRMs and reporting tools, which splits your data for no reason.
  • Hyphens, not spaces or underscores, inside a value. Spaces get URL-encoded to %20 and make campaign names unreadable in reports.
  • A fixed token order. Put date, funnel stage and segment in the same position every time, for example [quarter]-[funnel-stage]-[segment]-[offer].
  • One owner for the list of approved values. New utm_source or utm_medium values get added to a shared sheet before they go live, not invented ad hoc inside the ad platform.
FieldRuleExample
utm_campaign[year]-[quarter]-[funnel stage]-[segment]-[offer]2026-q1-mofu-rev-ops-roi-calculator
utm_content[format]-[variant]single-image-v2, document-ad-v1
utm_term[audience type]-[segment name]matched-company-named-accounts

Dynamic UTM tokens in LinkedIn, Google Ads and Meta

Typing a UTM string into every ad is slow and error-prone. LinkedIn and Google Ads let you set a tracking parameter once at the account or campaign level and have it populate per click. Meta works differently: the URL parameters field sits on each individual ad, so dynamic tokens there cut typing but don't remove the need to tag every ad.

LinkedIn Campaign Manager

According to LinkedIn's Campaign Manager help center, you can add both static and dynamic URL tracking parameters to a campaign's destination URL. Static parameters hold any value you type, such as utm_source=linkedin. Dynamic parameters pull from a fixed list: ACCOUNT_ID, ACCOUNT_NAME, CAMPAIGN_GROUP_ID, CAMPAIGN_GROUP_NAME, CAMPAIGN_ID, CAMPAIGN_NAME and CREATIVE_ID, written in all caps inside double curly brackets, for example campaign_id={{CAMPAIGN_ID}}. LinkedIn began rolling dynamic UTM parameters out globally in English by the end of March 2024, according to Social Media Today's coverage of the launch, so if your account predates that you may need to re-check the setting. Set utm_content={{CREATIVE_ID}} once at the campaign level and every ad in it tags itself correctly without manual entry per creative.

Google Ads

Google Ads calls its dynamic tokens ValueTrack parameters. Per Google Ads Help, useful values for B2B reporting include {campaignid}, {adgroupid}, {creative} (a unique ad ID), {keyword}, {matchtype} (e for exact, p for phrase, b for broad, or a for AI Max keywordless), {network} (g, s, d, ytv and others) and {device} (m, t or c). These go into the tracking template at the account, campaign, ad group or ad level, and the template must include a URL-insertion token such as {lpurl} or the landing page breaks. A typical template: {lpurl}?utm_source=google&utm_medium=paid-search&utm_campaign={campaignid}&utm_term={keyword}&utm_content={creative}.

If ValueTrack doesn't cover a value you need, Google Ads also supports custom parameters. Google Ads Help documents up to 8 custom parameters per level of the account (not at the account level itself), each with a name of up to 16 alphanumeric characters and a value of up to 250 characters, referenced inside the tracking template.

Meta Ads Manager

Meta has no auto-tagging equivalent to Google's, and nothing cascades between campaign, ad set and ad the way some teams expect. According to Terminus's guide to Meta UTM parameters, the URL parameters field lives on each individual ad, under Destination, and maps to url_tags on the ad creative object in the Marketing API rather than at the campaign or ad set level, which is why bulk automation of this field needs its own setup. The dynamic tokens Meta fills in at serve time include {{campaign.name}}, {{campaign.id}}, {{adset.name}}, {{adset.id}}, {{ad.name}}, {{ad.id}} and {{placement}}. Because nothing inherits, every ad needs its own URL parameters string, for example utm_source=meta&utm_medium=paid-social&utm_campaign={{campaign.name}}&utm_content={{ad.name}}.

Capture UTMs into hidden fields and push them to Salesforce or HubSpot

A UTM parameter only helps your pipeline reporting once it leaves the URL and lands on a record in your CRM. The step most teams skip is building that bridge.

According to Salesforce Ben, there are three common ways to get UTM values from the URL onto a Salesforce lead or contact: hidden form fields with prefill, which read UTM values out of the page URL at load time and submit them with the form; a tag manager plus a first-party cookie, which carries the values forward even if the visitor fills out a form on a different page than they landed on; or a dedicated capture tool, which does the same cookie-based capture and also classifies traffic that never carries a UTM, such as organic search and direct, into a channel field.

Map the captured values to fields on the Lead object (or Contact, once converted) and, critically, to the Opportunity. A campaign only matters once it's tied to pipeline, and if utm_campaign lives only on the Lead, it disappears the moment that lead converts unless a workflow or flow carries it forward.

Store first-touch and last-touch on every record, not just one

A contact can click three different ads across two platforms before they ever fill out a form. If you only store the most recent UTM values, you credit the last ad and erase the ones that built awareness earlier in the cycle. If you only store the first, you miss the retargeting ad that actually drove the conversion.

HubSpot's default contact properties already solve this at the platform level. Per Hublead's breakdown of HubSpot Original Source, Original Source is a first-touch property that records how a contact first found you, with Drill-Down 1 and 2 adding the specific campaign or referring detail, while a separate Latest Source property tracks the most recent interaction. If you're building this in Salesforce or a custom HubSpot property set, replicate the same pattern deliberately: a set of "first touch" fields that never overwrite once populated, and a parallel set of "last touch" fields that update on every new session. Report pipeline against both. First touch tells you what originally created demand; last touch tells you what pushed a deal into the pipeline.

Governance: who owns the taxonomy

UTM reporting breaks less from bad platform settings and more from nobody owning the rules. Assign these explicitly:

  • One owner for the approved values list, usually marketing ops. Every new utm_source, utm_medium or campaign slug gets added to a shared sheet or CRM picklist before it goes live, not typed fresh into the ad platform by whoever is launching that week.
  • Enforce lowercase and hyphenation at the point of entry. As Salesforce Ben points out, inconsistent casing, such as utm_source values of Facebook, facebook and fb for the same channel, shows up as three separate rows in a report instead of one.
  • Decide how auto-tagging and manual UTMs coexist on Google Ads. The tracking template requires a URL-insertion token such as {lpurl}; per Google Ads Help, leaving that out, or layering a conflicting template on a landing page with its own URL expansion rules, breaks the landing page URL entirely.
  • Know what LinkedIn Lead Gen Forms won't pass through. Lead Gen Forms submit natively inside the LinkedIn app or feed using the member's existing profile data and never load your landing page, so a UTM string on the ad's destination URL has nothing to attach to; use LinkedIn's native lead fields and a CRM sync for that ad format instead.
Before a new campaign launches, run its tagged URL through a link checker and confirm the parameters survive any redirect, including vanity domains and marketing automation tracking links. A 301 redirect that doesn't forward the query string strips every UTM you set.

What the resulting paid media dashboard should show

Once UTMs are flowing into Salesforce or HubSpot and attached to the Opportunity, the dashboard stops being a spend report and becomes a pipeline report. At minimum, build rows for:

  • Spend, pipeline and closed-won by utm_source, so you can compare LinkedIn, Google and Meta on revenue, not just clicks or cost per lead.
  • Pipeline and win rate by utm_campaign, broken out by funnel stage, so a top-of-funnel awareness campaign isn't judged on the same conversion bar as a bottom-of-funnel retargeting campaign.
  • Opportunities by utm_content, so you can see which specific creative, not just which campaign, is attached to deals that actually closed.
  • First-touch source next to last-touch source, on the same row, so you can see when a campaign's real job is opening pipeline versus closing it.

This is the same spend-to-pipeline view a B2B attribution tool tries to automate, but a clean UTM schema and two or three CRM fields get you most of the way there without a separate platform.

Common mistakes that break this reporting

  • Manual typos. One person types utm_campaign=q1-demand-gen and another types utm_campaign=q1_demandgen for the same campaign. Both show up as different rows forever.
  • Redirects stripping parameters. Vanity URLs, URL shorteners and some marketing automation tracking links drop the original query string unless explicitly configured to forward it.
  • Untagged retargeting. Teams tag the prospecting campaign and forget the retargeting campaign built from the same audience, so every retargeting conversion gets misattributed to direct or to whatever the UTM was on the original click.
  • UTMs that live only on the Lead object. If the fields aren't mapped forward to Contact and Opportunity, the attribution data disappears exactly when it becomes useful, at the pipeline and revenue stage.
  • Treating dynamic tokens as a finished taxonomy. {{campaign.name}} or {{CAMPAIGN_NAME}} only report what someone typed into the ad platform. If your campaign naming convention is inconsistent, the dynamic token just automates the mess instead of fixing it.

Keeping this consistent across three ad platforms, a naming sheet and two CRM objects is itself a workload. Tofu Ads Agent builds campaigns directly in LinkedIn, Google and Meta and writes dynamic UTMs back to the CRM as part of launch, so tagging follows the same schema every time instead of depending on whoever built that week's campaign. Campaigns still stage into your ad account switched off, so nothing launches until someone on your team turns it on.

If your plans already start from CRM data, the UTM schema should mirror the same segment and funnel-stage names used to turn CRM data into a paid media plan, so reporting language matches planning language end to end.

Frequently asked questions

What's the difference between utm_medium and utm_source for paid ads?

utm_source identifies the platform, such as linkedin, google or meta. utm_medium identifies the type of traffic, such as paid-social or paid-search. Keeping them separate lets you group all paid social spend together in a report even when it runs across two different platforms.

Should utm_campaign match the exact campaign name in the ad platform?

It should match closely enough that a marketing ops person can find the campaign in the ad platform from the CRM record alone, but use a lowercase, hyphenated slug rather than the exact display name, since display names often include spaces, emojis or characters that break a URL.

Can I use dynamic UTM tokens instead of a manual naming convention?

Dynamic tokens like LinkedIn's {{CAMPAIGN_NAME}} or Meta's {{campaign.name}} save you from retyping values, but they only report back whatever was typed into the ad platform at setup. If campaign names in the platform are inconsistent, the automation just reproduces that inconsistency in your reports faster.

Why do LinkedIn Lead Gen Form conversions show no UTM data in the CRM?

Lead Gen Forms open natively inside LinkedIn's app or feed and submit using the member's existing profile fields rather than loading your landing page in a browser. A UTM string on the ad's destination URL has no page to attach to, so standard hidden-field capture scripts never run for that ad format.

Do I need both first-touch and last-touch UTM fields, or is one enough?

Use both. First-touch fields (HubSpot calls its default property Original Source) show which campaign first created awareness; last-touch fields show what immediately preceded conversion. Reporting on only one hides whether a campaign's real job is opening pipeline or closing it.

What breaks UTM tracking after a campaign has already launched?

The most common causes are redirects or URL shorteners that drop the query string, manual retyping that introduces casing or spelling differences for the same campaign, and retargeting campaigns that get built from an existing audience but never receive their own UTM tag.

How many UTM parameters does a B2B paid program actually need?

Five: utm_source, utm_medium, utm_campaign, utm_content and utm_term. Adding more parameters usually creates fields nobody filters reports by, while skipping utm_content or utm_term removes the ability to compare creative variants or audience segments inside a single campaign.

Sources

  1. URL tracking parameters in Campaign Manager · LinkedIn
  2. LinkedIn Adds Dynamic UTM Parameters to Campaign Tracking · Social Media Today
  3. Set up tracking with ValueTrack parameters · Google Ads Help
  4. Create custom parameters for advanced tracking · Google Ads Help
  5. Facebook Ads UTM Parameters: Track Every Meta Ad · Terminus
  6. Learn how to use HubSpot Original Source · Hublead
  7. How to Capture UTM Parameters in Salesforce · Salesforce Ben

Let an agent build your next campaign.

Tofu Ads Agent reads your CRM, plans the funnel, builds the audience and creative, and stages full campaigns across LinkedIn, Google and Meta for your approval.