# UTM Campaign ID Export Crosswalk

Tie supplied landing-link campaign IDs to reporting exports while preserving conflicting source values.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Exact landing URLs; approved campaign-ID roster; export campaign IDs and row IDs; source/medium taxonomy; version date.

## Workflow
1. Parse utm_id and retain the raw URL and decoded value; do not browse the destination.
2. Match exact campaign IDs to the supplied roster and export.
3. Keep missing IDs, repeated conflicting IDs and case differences distinct.
4. Return a proposed crosswalk and unresolved rows; never silently rewrite naming or infer clicks.

## Output contract
link_id | raw_utm_id | roster_id | export_row | source_medium | match_status | hold

## Fictional acceptance test
Fictional link uses utm_id=C 17 and export row uses C 18. Hold the mismatch even when both names say spring. A link without utm_id stays missing, not guessed from campaign name.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://support.google.com/analytics/answer/10917952

Checked October 8, 2026. Oct8 live GSC through Oct5: marketing copilot 37 impressions, Planable/Claude 33 and Planable/ChatGPT 23, campaign brief 12 and reports 11. Marketing/social topics follow these parent-query leads; other professions follow method-source workflow needs, not exact query measurements. Exact monthly volume is unmeasured.