Use GA4’s Manual report, Manual Ad Content, and Manual Term dimensions without confusing manual-tagged campaign validation with every other acquisition question.
This page exists because teams often know that UTMs reached GA4, but still do not know which report answers which question. The safe move is to separate raw manual-tagged validation from broader acquisition interpretation, then test the route and scope in order.
It is the pre-made GA4 report for manually tagged campaign traffic, not a universal answer for every acquisition question.
utm_content and utm_term do show up in GA4.
Google documents them as the sources for Manual Ad Content and Manual Term dimensions.
Scope confusion causes fake diagnosis.
Teams often blame tracking when the real problem is using the wrong GA4 view for the question.
What the GA4 Manual report actually does
Google’s Manual report documentation says the report is a pre-made detailed report for manually tagged campaigns. It shows data when website clicks send UTM parameters correctly, or when an app sends the campaign_details event.
If the team is blaming the collection stack for what is actually a report-scope problem, reset the architecture boundary with server-side vs client-side tracking before rebuilding tags that are already landing cleanly.
Start here first
It is for manual campaign traffic
Use it when you want to check whether your tagged campaigns are being grouped the way your team intended.
It is not every campaign question
It does not replace Traffic acquisition, User acquisition, or custom explorations. It is just the pre-made view for manual-tagging analysis.
It only works when the tagging arrives cleanly
Broken UTMs, redirect loss, consent issues, or wrong report scope will still make the view look incomplete or misleading.
Which UTM fields appear in GA4 manual campaign reporting
Google’s manual tagging documentation confirms that utm_content and utm_term populate the Manual Ad Content and Manual Term dimensions, while utm_creative_format and utm_marketing_tactic are not currently reported in GA4 properties.
Field mapping
Core groupingutm_source, utm_medium, utm_campaign
Support detailutm_content, utm_term
Do not overpromiseutm_creative_format and utm_marketing_tactic are not currently surfaced in standard GA4 reporting
Manual source / mediumBest for the readable origin and traffic type that your team wants to compare later.Keep these fields governed and boring.
Manual campaignUse for the reporting concept, not every fast-moving platform detail.Readable campaign naming ages better than dynamic sprawl.
Manual Ad Content / Manual TermUse for creative, placement, audience, or query-style detail only when it genuinely improves analysis.These are support fields, not the place to rescue a broken base taxonomy.
Practical rule: manual reporting gets cleaner when the base fields stay stable and the support fields stay genuinely optional.
When to use the Manual report versus other GA4 views
The biggest mistake is asking one report to answer a different question.
Scope matters
Use the Manual report
When you are validating manual campaign structure
Did the manual UTM values land?
Is manual campaign traffic grouped the way we intended?
Do manual ad-content or term values look clean?
Use Traffic acquisition
When you need the broader session view
Use session dimensions for the current visit.
Best first stop when checking a tagged click path.
Custom breakdowns, support dimensions, and governance logic belong here.
Move into custom channel groups when the goal is classification, not raw validation.
Safe workflow for manual campaign reporting in GA4
Work forward from the link, not backward from the report screenshot.
Validation workflow
1
Build the final URL from governed inputs
Use the UTM Builder or your approved template so the tracking string is readable before a platform adds anything else.
The report cannot rescue a broken naming decision upstream.
2
QA the finished string
Use the UTM QA Checker to catch duplicates, malformed values, or overwritten fields.
Manual campaign reporting is only as good as the final URL you actually publish.
3
Check the live route
Use the redirect checker when a shortener, redirect, or cross-domain handoff sits between the ad click and the landing page.
Report confusion often starts with route behaviour, not the reporting layer.
4
Open the right GA4 view
Use the Manual report when the question is specifically about manually tagged campaign grouping. Use Traffic acquisition or the cross-domain guide when the scope is different.
Matching the question to the right report is part of QA, not an optional extra.
Primary docs and next routes
This page is grounded in current Google Analytics documentation and tied into the rest of the Shortlinkfix workflow.
Short answers to the points that usually create scope confusion, not just tracking mistakes.
FAQ
Does GA4 really have a Manual report?
Yes. Google documents a pre-made Manual report that shows how effective manually tagged campaigns were at driving traffic to your site or app.
Where do utm_content and utm_term appear?
Google says they populate the Manual Ad Content and Manual Term dimensions. They are support fields, not excuses to overload the base naming model.
Should we use the Manual report for first-user questions?
Usually no. Use it when the question is about manually tagged campaign traffic and grouping. Use the broader acquisition views when the question is session or first-user scope.
Why do manual-tagged clicks still look wrong sometimes?
Because the issue may be route behaviour, consent, malformed values, or simply checking the wrong GA4 report for the question you are trying to answer.
What should we check before opening GA4?
The finished URL, the QA output, and the live route. Clean reporting starts before the click lands.
Related reading
If you want cleaner network-specific tagging before the reporting layer, compare your setup with the Microsoft Ads tracking template.