How to Shorten a UTM Link Without Losing Campaign Tracking

Tag the landing page first

Start with the final page, then add a consistent set of campaign parameters:

https://example.com/guide?utm_source=customer_newsletter&utm_medium=email&utm_campaign=launch_guide&utm_content=hero_button

Google's custom campaign URL guide documents utm_source, utm_medium, and utm_campaign as the core fields. It recommends consistent, case-sensitive naming and describes utm_content as a way to distinguish creatives or links within one campaign.

Keep values lowercase and record them before publishing. Do not place names, email addresses, customer IDs, or other personal information in campaign parameters. URLs may be copied, logged, forwarded, and displayed outside your analytics account.

Save the whole tagged URL

1. Open the long destination directly and confirm the landing page works.
2. Check every UTM name and value against your campaign register.
3. Create a dynamic link in the GhostQR URL shortener.
4. Paste the entire URL, including everything after the question mark.
5. Name the record for its channel and placement, then save it.
6. Open the returned short link and inspect the final browser address.

GhostQR stores the destination as one complete URL. Its public link resolves that value and issues a temporary HTTP 302. The campaign query string in the example remains part of the Location destination. GhostQR does not provide a native GA4 connection; your destination site still needs a correctly configured Google tag.

Put the parameters in the saved destination, as shown above. Do not append them to the public short address. A request such as ghqr.au/em1001?utm_source=customer_newsletter still resolves the destination stored for em1001; GhostQR does not copy that incoming query string onto the target. Save the tagged example.com URL in the record instead.

Use separate links when attribution should stay separate

Suppose the same guide appears in an email hero button and an organic LinkedIn post. Give each channel its own destination and short link:

These names and short links are illustrative. Two records let you inspect their request totals independently. If you paste the same short URL into both channels, GhostQR sees requests for one slug and cannot infer which placement produced each one. Distinct UTMs also keep the channels separate in GA4's session-scoped acquisition reporting.

Test more than the visible address

A neat-looking short link is only useful if the full route works. Test each published version in a private browser window and on a phone. Confirm that:

• the short link uses HTTPS and opens the intended host and path;
• the final address still contains the expected UTM values;
• any redirect on your own landing site preserves the query string;
• the Google tag loads under the consent choice being tested; and
• the exact campaign value appears in GA4 before a large send.

Google says tagged campaign values are available through session source, medium, and campaign dimensions in Reports → Acquisition → Traffic acquisition. Correct the campaign URL rather than renaming report rows after inconsistent tags have split one launch into several values.

Edit carefully after publishing

A dynamic short link is useful when a landing page changes after an email or post is already public. Edit the saved destination and keep the same short address. Include the complete query string again. Changing from a tagged destination to an untagged one ends campaign tagging for later visits through that link.

GhostQR uses temporary redirects because destinations are editable. Its resolver is cached briefly at the edge, currently about 30 seconds, so a recently used link may show the previous destination until that cache entry expires. Read the short-link editing walkthrough for the full before-and-after workflow.

Read the resulting report at the right scope

Use GA4's Traffic acquisition report for session campaign analysis. Google distinguishes it from User acquisition: Traffic acquisition is scoped to sessions, while User acquisition describes how new users were first acquired. Its report comparison guide warns that metrics differ with those scopes.

Short-link requests and GA4 sessions will not match one for one. Automated previews can request a public link, while consent, browser blocking, connection loss, or an incomplete page load can prevent destination measurement. See why request and session totals differ before treating the gap as lost traffic.