Owner, trigger and scope
Marketing operations owns the procedure, the taxonomy of allowed values and the link register. The requesting marketer owns the request: the destination, the channel, the campaign and the date the link is needed. Marketing operations can refuse a request that does not fit the taxonomy, and proposes the nearest valid values instead.
The trigger is any need for a tagged link pointing into the site from outside: a paid ad where auto-tagging is not used, an email, a social post, a partner placement, a QR code on print, an influencer brief or a newsletter sponsorship. Which traffic needs a manual tag and which should rely on auto-tagging is set out in the comparison of UTM parameters and auto-tagging. Links within the site are out of scope and should never be tagged.
The procedure covers requests, building, testing, logging and sharing. Designing or changing the taxonomy itself is a separate governance task described in the data operations and taxonomies guide. How tagged traffic is grouped into channels and credited is covered by the measurement guides and is not changed by this SOP.
Before you start: inputs and access
| Input | Owner | Notes |
|---|---|---|
| Request form | Marketing operations | Destination URL, channel, source, campaign, content variant, needed-by date |
| Taxonomy of allowed values | Marketing operations | Approved sources, mediums and campaign name pattern |
| Link register | Marketing operations | Shared sheet or tool listing every issued link |
| Link builder | Marketing operations | A template or tool that enforces lower case and allowed values |
| Link shortener, if used | Marketing operations | Branded domain where possible |
| Analytics access | Analytics owner | Real-time or debug view to confirm the tag |
The rules for naming, case and separators come from the naming conventions and UTMs guide. Keep it open; the taxonomy check is a comparison against it.
The procedure
Submit the request
The requesting marketer fills in the form with the final destination URL, the channel and placement, the campaign the link belongs to, any content variant to distinguish, and the date it is needed. Requests by chat or email are redirected to the form. Ask for links as early as possible; a link needed within the hour is the one most likely to be built wrong.
Check against the taxonomy
Marketing operations compares each value with the taxonomy. Source and medium must be from the allowed list; the campaign name must follow the pattern; content values must be descriptive and lower case. Search the register first: if a matching link already exists, reissue it rather than building a near-duplicate. Any new value is added to the taxonomy deliberately, never invented for a single link.
Build the link
Build the link in the agreed builder from the approved values, so that case, separators and encoding are consistent. Check the destination URL is the final live address, not a redirect or a staging page, and that any existing query stringA key and value appended to a URL after a question mark, such as a filter, sort order, session or tracking tag, that may or may not change the page. on it is preserved correctly. Paste nothing by hand into the parameter string; typing is where most errors enter.
Shorten if needed
Shorten the link only where the channel requires it, such as print, QR codes or character-limited posts, using the team's shortener on a branded domain where available. Record both the short and the long link. Never shorten a link for a channel that displays the full address anyway; every redirect adds a point of failure and hides the destination from the reader.
Test the landing and the tag
Open the link in a private window. Confirm it lands on the right page, on a phone as well as a desktop, that the parameters survive any redirects and that consent banners do not strip them. Check that a session with the expected source, medium and campaign appears in GA4Google's event-based analytics platform. real-time or debug view. For a fuller verification of events and conversions, use the tracking verification checklist.
Log in the register
Add a row to the register with the date, the requester, the channel, the full and short links, every parameter value, and the test result. The register is the single place anyone can look up what a value means, which campaign a link belongs to, and whether a link already exists. A link that is not in the register does not officially exist.
Share with the requester
Send the requester the tested link with a reminder of where it may be used. If the same campaign needs links for several placements, issue them together with distinct content values. Ask the requester to confirm before launch that they used the issued link exactly, without editing or re-shortening it, and close the request.
A webinar campaign tagged across four placements
Ledgerwren Payroll, an invented payroll software company, needs links for a webinar promoted in a partner newsletter, a LinkedIn post, an email to customers and a printed flyer. Marketing operations finds an existing campaign value in the register, issues 4 links with distinct content values, and shortens only the flyer's link for a QR code. Testing shows the partner's newsletter tool appends its own parameters, which are stripped before sending. At month end all 4 placements report under a single campaign row, with the partner newsletter producing 212 of the 530 registrations, and no sessions fall into unassigned.
QA checks
If any check fails, rebuild the link from the request rather than editing the failed version, and test again. A quick fix to a broken link is the most common way a second error is introduced.
Before a link is shared, marketing operations confirms:
- Every value is from the taxonomy, in lower case, with the agreed separator.
- No duplicate link already existed in the register for the same placement.
- Destination is the final live URL, with no redirect chain.
- Parameters survive redirects, consent banners and shortening.
- Analytics shows a test session with the expected source, medium and campaign.
- Short link, if used, resolves to the full tagged link.
- Register row is complete, including the test result.
Hand-offs and records
The tested link is handed to the requesting marketer, who becomes responsible for using it unchanged. If the link feeds a paid campaign, the campaign manager receives it as an input to the launch procedure. For links that drive enquiries, the team running the inbound lead handling playbook needs the campaign values too, so that source information carries through to the CRM and lead routing.
The register is the lasting record and also the basis for AttributionAssigning conversion credit to touchpoints. questions later: when a report shows an odd value, the register says who requested it and why. Marketing operations reviews the register against analytics each month, looking for tagged traffic that does not match any register entry. Each mismatch is a link built outside the SOP and a reason to talk to the team that built it.
When links already in circulation have produced a tangle of variants, the diagnosis of inconsistent campaign names and UTM tags shows how to measure the drift and which source to fix first.
Common mistakes
Every one of these produces the same symptom: campaign traffic split or unassigned in reports.
- Mixed case. Analytics treats differently cased values as different. Enforce lower case in the builder.
- Tagging internal links. It overwrites the original source of the visit. Tag only inbound links.
- Building links in chat. Values drift. Route every request through the form.
- Inventing a source for one link. New values fragment reports. Add them to the taxonomy deliberately.
- Skipping the test. A redirect that strips parameters looks fine to the requester. Test every link.
- No register. Without it, the same link is rebuilt repeatedly with small differences.
- Requesters editing issued links. A changed character breaks the match. Ask for a new link instead.
