Unassigned is a reporting outcome, not a diagnosis of where visitors came from. Replacing every unknown source with a campaign name may make the chart prettier while destroying evidence. Start with the underlying acquisition fields, their scope and the landing journey, then repair the specific convention or collection issue you can reproduce.
Make this useful for your client. Follow the worksheet, or use the ready-to-copy task with your connected data.
Try this task in 1ClickReport → · See the product workflow →Evidence → Decision → Review
How to run the investigation
Choose the acquisition scope
Compare session-level fields with session-level outcomes when reviewing visits. Keep first-user acquisition and event attribution separate. Record the property, dates and report configuration so a difference between scopes is not mistaken for missing tracking.
Inspect the underlying rows
List source, medium, campaign, landing page and host for the Unassigned segment. Group recurring combinations and distinguish missing values from custom values that do not fit a channel rule. A large unknown bucket may contain several unrelated problems.
Test the tagged journey
Follow representative campaign links through redirects, consent screens and cross-domain transitions. Confirm whether parameters survive. Ask the implementation owner to inspect collection when necessary; a report alone cannot prove which browser step dropped a value.
Repair the right layer
Use consistent future campaign tags where the issue is naming. Consider a documented custom channel rule when a legitimate source needs classification. Do not rewrite historical business conclusions as if a label change discovered the visitor’s true origin.
Decision worksheet
Use these rows to turn the investigation into an action. Add the actual account, date range, evidence and owner before sharing it with a client.
| What you find | Interpretation | Next move |
|---|---|---|
| Custom medium present | Channel rule may not match | Review naming or a documented classification rule. |
| Source and medium missing | Collection or journey needs investigation | Reproduce the entry path before assigning a cause. |
| Only first-user and session reports differ | Scope can explain it | Compare like-for-like dimensions. |
Download this worksheet (CSV) ↓
Worked example: an illustration, not a customer result
Imagine newsletter visits tagged with a novel medium such as “founder-message.” They may be collected but classified unexpectedly. Visits with no recorded source are a separate investigation. Changing a rule for the first group does not recover the origins of the second. Keep that distinction visible in the client report.
MAKE THIS YOUR NEXT CLIENT TASK
Run the review on your own data.
Start with one client in 1ClickReport. Connect GA4 and the relevant ad or commerce source, select the correct client and use the task below. The analyst keeps client-specific context as you work.
Read the ready-to-use task
Audit GA4 Unassigned traffic for this client. Use session source, medium, campaign, landing page and host on matched dates. Separate missing acquisition data from unmatched channel rules and scope differences. Identify representative URLs to test. Propose a tagging or classification repair with an owner; do not invent historical attribution.
3-day free trial · No credit card required.
- Copy the task, then create your account in the new tab.
- Finish setup and connect the relevant client data.
- Return to this page and open the task in AI Analyst ↗. Review the prompt before sending.
Missing order, CRM or application evidence must be provided by its owner. No cross-system match is assumed.
A question worth asking
Is Unassigned the same as direct traffic?
No. They are different reporting classifications. Inspect the underlying acquisition fields and definitions before combining them. A missing or unusual value does not establish a direct visit.
References and method
Reviewed November 12, 2026. The decision process and worksheets are 1ClickReport’s editorial recommendations. Examples are hypothetical, not customer results. Platform behavior and access can vary; use the current native account view to verify settings.