Tracking Vanity URLs & Forwarded Domains for Clients

How do agencies track a client's vanity URL in Google Analytics?

Point the vanity URL at a redirect that appends UTM parameters to the destination, and Google Analytics will attribute the traffic instead of dropping it into "direct." A vanity URL (yourclient.com/spring) is only a branded doorway; on its own it hands GA4 nothing about where a visitor actually came from. The UTM tags on the redirect target are what carry the source, medium, and campaign back into the client's reporting.

That distinction is the whole job when you deliver this for clients. Agencies get asked to "just make the short link trackable," and the client assumes it works out of the box. It doesn't, and if you set it up wrong, a meaningful share of print, radio, or QR-code spend shows up as unattributed direct traffic and the client quietly concludes the campaign flopped. Getting the plumbing right is what separates a clean attribution story from a reporting fire drill three weeks into the campaign.

Forwarded domains vs. vanity URLs: what you're actually delivering

These are two different tracking problems, and clients conflate them constantly. Sort out which one you're solving before you touch a setting.

Scenario	What the client wants	What you actually configure
Forwarded domain	An old or secondary domain (example.com) redirects to the live site	Tracking on the destination; the source domain arrives as a referral unless you tag the redirect
Vanity URL	A branded short link (client.com/promo) for a specific campaign	A redirect that appends UTM parameters so GA4 attributes source/medium/campaign
Microsite / separate domain	A standalone campaign or product site on its own domain	Embedded tracking code on the microsite, with cross-domain data trade-offs to flag

A forwarded domain passes the original domain name through as the referral source, so if example.com forwards to newdomain.com, GA4 records example.com as the referrer. That's usually harmless, but it's also why a client's "direct" bucket looks weird after a domain consolidation or rebrand, old domains leaking through as self-referrals. When you're delivering across a book of clients, standardizing on one approach per scenario keeps the reporting legible.

The delivery workflow: vanity URL tracking, step by step

Here's the repeatable sequence to run for a client campaign. Treat it as a checklist you can hand to a junior team member and QA in ten minutes.

1. Confirm the vanity URL and destination. The vanity URL is the branded short link (client.com/promo); the destination is the real landing page. Get both in writing from the client so you're not guessing which page should convert.
2. Build the tagged destination URL. Use UTM parameters, as HubSpot's guide to Campaign URL Builder basics describes, to append tags to the destination. Example: client.com/landing-page?utm_source=vanity&utm_medium=print&utm_campaign=spring_sale.
3. Set the redirect to the tagged URL. Point the vanity URL's redirect at the full tagged destination, not the bare landing page. This is the step teams skip, a redirect to the clean URL strips your attribution.
4. Test before it goes live. Visit the vanity URL and confirm it lands on the destination with the UTM string intact. Watch it appear in GA4 Realtime under the right source and medium.
5. Document it in the client's tracking sheet. Record every vanity URL, its destination, and its UTMs so the next person on the account isn't reverse-engineering last quarter's campaign.

The order matters. Most attribution gaps we're asked to debug trace back to step 3, the redirect points at the untagged page, or a UTM casing mismatch, since utm_source=google and utm_source=Google are counted as two different sources.

UTM parameters: the tagging convention to standardize across clients

Standardize your five UTM parameters into one house convention and enforce it across every client, or your cross-client reporting turns to mush. The parameters themselves are simple; the discipline is what you're really selling.

Parameter	What it captures	Example
utm_source	Where the traffic originates	vanity, summer-mailer
utm_medium	The marketing channel	print, email, qr
utm_campaign	The specific initiative	spring_sale
utm_term	Paid keyword (optional)	hubspot-onboarding
utm_content	Differentiates variants/creatives	banner-a

Lock down lowercase, decide once whether spaces become hyphens or underscores, and keep a shared naming key. When you manage this for a dozen clients, a value like Email on one account and email on another means every roll-up report double-counts. A one-page tagging standard, applied identically across the portfolio, is a small deliverable that saves hours of reconciliation later.

GA4 or the HubSpot portal: which tracking to recommend

Recommend GA4 with UTMs when the client just needs source attribution, and lean on the client's HubSpot portal when they need to tie the click to a contact record and downstream revenue. Both track a vanity URL; they answer different questions, and part of your value is steering the client to the right one instead of over-building.

For clients on HubSpot, the portal can also track a microsite or forwarded domain using embedded tracking code, though it comes with some data trade-offs you should flag up front rather than after the fact. In our delivery we've found HubSpot's reporting consolidates the pieces most clients care about (landing pages, analytics, and campaign KPIs in one dashboard) which is often an easier hand-off than teaching a client to live inside GA4's Explorations.

There's a pragmatic middle ground worth remembering when a client asks to track something GA4 handles awkwardly, like an asset download. As one of our team put it on LinkedIn: a PDF is just a URL, and Google Analytics can tell you whether someone actually opened that PDF, less detailed than HubSpot's native CTA data, but for many clients it's genuinely good enough. Knowing when "good enough" is the right call, versus when the client truly needs contact-level attribution, is the judgment clients are paying an agency for.

One more reason to build clean UTM habits now: Google Analytics 4 has added a dedicated AI Assistant channel that classifies referral traffic from ChatGPT, Gemini, and Claude, according to a 2026 Semrush report. As more of a client's discovery happens inside AI answers, disciplined source tagging is what lets you separate that emerging channel from the "direct" catch-all.

Scoping and packaging analytics work without eating the margin

Scope tracking setups generously, because "just add tracking" almost always uncovers integrations and data-source connections that weren't in the original brief. This is where agencies quietly lose money on analytics work, the task sounds like a 20-minute favor and turns into a half-day project.

Our own delivery numbers make the point. A standard GA4 setup initially scoped for 12 hours required 16 hours to complete once the additional integrations and data-source connections surfaced. And a unified Looker Studio dashboard pulling from Google Analytics, Google Search Console, and HubSpot runs about 36 hours of integration work plus roughly 8 hours of ongoing monthly management. Vanity URL tracking rarely lives alone; it's usually the entry point to a broader reporting build.

That reality shapes how you package it:

• Pay-per-task for a single campaign's vanity URL and UTM setup: clean, defined, easy to quote.
• White-label retainer when the client wants ongoing tagging discipline, monthly reporting, and dashboard upkeep across campaigns.
• Reserved capacity for clients running enough concurrent campaigns that tracking hygiene is a standing job, not a one-off.

Building the standard once and reusing it across the book is what makes the per-task version profitable instead of a loss leader.

Reporting the results back to the client

Show the client the campaign, source, and medium breakdown their UTMs make possible; that's the payoff they can see, and it's what earns the next engagement. In GA4, the tagged traffic surfaces under the source/medium and campaign dimensions, with users, sessions, and events attached to each; custom Explorations let you shape that into a view the client actually understands.

Remember to monitor and analyze the data to make informed decisions rather than dumping raw GA4 screens on the client. And when you consolidate a client's old domains, keep the forwarding clean so retired URLs don't turn into 404 errors that quietly erode the SEO value the client built up, a broken redirect undermines the very attribution you set out to deliver.

Delivering vanity URL tracking under your brand

The mechanics of vanity URL and forwarded-domain tracking are learnable in an afternoon; doing it consistently, cleanly, and profitably across every client on your roster is the hard part, and it's exactly the work agencies hand to us. As the white-label partner behind other HubSpot and marketing agencies, Meticulosity delivers this kind of white-label digital marketing (analytics setup, UTM standards, GA4 and HubSpot reporting, and the campaign tracking underneath it) under your brand, so your clients see your name on the results.

If your team is stretched thin on the analytics and tracking side of client delivery, contact our experts and we'll slot in behind you.