---
description: Find why GA4 traffic shows as Unassigned, (not set) or Direct, and order the fixes
argument-hint: [report, dimension or symptom]
---

Use the ga4-unassigned-not-set-diagnosis skill for this task: $ARGUMENTS

Read martech-context/ first if it exists: stack.md, naming-rules.md and decisions.md.
If the request is empty or vague, ask for the report, dimension, metric, channel group, date range, the date the pattern changed and which key events matter.
Ask what access you have: GA4 reports, the Data API and the BigQuery export.
Follow the skill's procedure in order and meet every acceptance check. Do not skip the artifact and channel group checks.
Stay read-only. Stop for approval before changing anything in GA4, GTM, the consent banner or a server sender.
Hand back the incident record, the cause tree with evidence, the ordered fix list and the confirmation test plan.

If the ga4-unassigned-not-set-diagnosis skill is not installed, install it with: npx skills add https://www.martechdevs.com --skill ga4-unassigned-not-set-diagnosis -a claude-code
