This checklist is for marketing teams that run several channels for the same hospital or group: search ads, Meta ads, YouTube, email, WhatsApp broadcasts, partner listings and print QR codes. If your monthly report has a long tail of sources such as "Google", "google", "goog" and "(not set)", the problem is naming and capture, not analytics software.
The aim is narrow. Every enquiry should arrive in the CRM with a source you can trust, a campaign you can read, and, where the platform provides one, the click identifier that lets you send a later outcome back. That needs three things: a naming convention that people follow, a mechanism that keeps the values alive from the first landing page to the form submit, and hidden fields that carry them into your lead record.
This article covers those three. It does not cover what to do with the data afterwards. For stage definitions and channel credit, see the companion piece on closed-loop attribution by CRM stage.
Why the convention matters more than the tool
Google's guidance on custom campaign URLs states that parameter values are case sensitive, so utm_source=google and utm_source=Google are different values. It also warns that leaving out relevant parameters leads to (not set) values in reporting. Both are in the URL builder documentation, which is worth reading once as a team.
In a hospital, tagging is usually done by several people: the in-house marketer, two agencies, the doctor's PA who sends a broadcast, and a vendor who prints a QR code. Without a rule everyone invents their own. The cost shows up three months later when you cannot tell whether a spike came from a campaign or from a typo.
The convention: five rules
1. Lower case only, hyphens for spaces, no spaces or punctuation beyond hyphens and underscores. Write joint-replacement, not Joint Replacement or joint_replacement.
2. A closed list for source and medium. Do not allow free text. Publish the list and treat anything else as an error.
| utm_source | utm_medium | Used for |
|---|---|---|
| cpc | Search and Performance Max ads | |
| youtube | video | YouTube ads |
| meta | paid-social | Facebook and Instagram ads |
| organic-social | Posts, bio link, stories | |
| broadcast | Campaign messages to opted-in contacts | |
| newsletter | Opted-in email | |
| gbp | organic-local | Google Business Profile links |
| partner | referral | Insurer, TPA or corporate pages |
| qr | Hoardings, brochures, OPD desk |
Ads that Google auto-tags are a special case, covered below. The table is for everything you tag by hand.
3. A fixed campaign pattern. One that works: dept-service-city-objective-yyyymm, for example ortho-knee-replacement-pune-consult-202612. The month suffix stops last quarter's name being reused for a different offer.
4. Use utm_content for creative and utm_term for keyword or audience only. Keep creative names short and unique, such as video-doctor-explainer-v2. Do not put a doctor's name in a free-text field if the doctor has not agreed to it.
5. Never put personal data in a URL. Google's guidance on avoiding PII in Analytics says the URL path and parameters must both be free of PII, and that campaign parameters are included. A link in a broadcast that carries a patient's phone number or name is a data protection problem and a reporting problem. Use a campaign code, never an identity.
Keep the convention in one shared sheet with a URL-builder tab that outputs the final link. The sheet should have a validation list for source and medium so that nobody types them. Version it, date it and name an owner.
Auto-tagged ads and click IDs
Paid platforms add their own identifiers when you click an ad.
Google's click identifier, the GCLID, links a click to a later conversion. Google's help page on importing conversions from ad clicks explains that a click ID must be present for a file-based offline import to match, and that a GBRAID is used for aggregate measurement on iOS and Safari. The same page calls the file-based method legacy and recommends enhanced conversions for leads for new setups.
Meta's equivalent is the fbclid query parameter. Meta's documentation on fbp and fbc parameters describes how the _fbc value is built from the fbclid, in the form version, subdomain index, creation time and the fbclid itself. It notes the fbclid is case sensitive and should not be altered, and it recommends storing the _fbc cookie with a 90-day expiry.
Two practical consequences follow.
First, do not strip or rewrite these parameters in redirects. A well-meaning redirect from an old URL to a new one that drops the query string will silently erase your click IDs. Test every landing page URL with a dummy click ID appended and confirm it survives to the final page.
Second, keep hand-tagged UTMs on links where the platform auto-tags only the click ID. Auto-tagging and UTMs can sit together. The click ID is for the ad platform; UTMs are for your own analytics and CRM. Make sure your final URL template for Meta ads carries your UTMs, for example through the platform's URL parameter field, rather than relying on the fbclid to describe the campaign.



