GA4 Unassigned does not automatically mean your UTM parameters disappeared. A source and medium can be present while their combination fails to match the default channel rules. Inspect the underlying acquisition dimensions before changing the campaign or installing another tracking script.
Start with the row, not the channel label
Open the affected acquisition report and note its exact dimension. Session acquisition and first-user acquisition answer different questions. Keep the scope consistent while adding source, medium and campaign as supporting dimensions.
Google's default channel definitions explain that Unassigned represents traffic without a matching channel rule. It is not the same as the "(other)" row used for reporting cardinality. A missing value and an unrecognized combination also deserve separate investigation.
Export a small set of affected rows with dates and counts. Do not export visitor identifiers or personal URL parameters into an unrestricted spreadsheet. The source and medium strings are usually enough to start the classification diagnosis.
Use a controlled campaign example
Suppose a fictional partner email was tagged with source newsletter_partner and medium partner_blast. The label communicates something to your team, but it does not guarantee that the default Email channel recognizes it. Compare the actual values with Google's current rule definition.
For a future email placement, use an agreed medium that describes email traffic, and retain the partner detail in the source or campaign name. Do not label a paid advertisement as email merely to force a preferred report category.
| Evidence |
Interpretation |
Next action |
| Intended source and custom medium present |
Classification may be the problem |
Compare exact channel rules |
| Source or medium absent unexpectedly |
Collection or redirect path may be wrong |
Inspect the actual landing journey |
| Different scope gives different numbers |
Reports describe different acquisition moments |
Align the comparison scope |
| Historical campaign remains Unassigned |
New links did not rewrite old visits |
Annotate the change and evaluate future data |
Convention: Source, medium and campaign agreed. Future link: Accurate medium for the placement. Landing path: Parameters reach the destination. Processed report: Compare the same session scope. Explanatory checklist, not a customer test result.
Repair the campaign convention, not the history
Document one source, medium and campaign convention before updating future links. Google's tagging guidance is a useful reference for consistent campaign parameters. Keep redirects from stripping legitimate attribution, but avoid placing UTM tags on ordinary internal navigation.
If the business intentionally needs a category outside the default taxonomy, evaluate a custom channel group with a clear definition. Keep it distinct from Google's default channel and document the reporting scope. A custom label should explain traffic, not conceal an implementation failure.
Confirm the next real reporting period
Test the destination URL and parameter preservation with a controlled visit under the site's actual consent rules. Do not force consent to make analytics appear. Check processed reports after the applicable reporting delay and compare the same session-scoped dimensions.
If the problem instead begins after payment, follow the WooCommerce payment referral guide. For attribution troubleshooting, share the redacted landing URL, exact dimension names and affected dates. That evidence distinguishes a naming problem from a lost acquisition signal.
References reviewed October 14, 2026. Examples are explanatory, not customer test results.