UTM Campaign ID Export Crosswalk

Tie supplied landing-link campaign IDs to reporting exports while preserving conflicting source values. Preparation only, not an account action.

What to provide

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

How it works

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.

The output

link_id | raw_utm_id | roster_id | export_row | source_medium | match_status | hold

Worked fictional example

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.

Checks and limits

Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.

More marketing workflows · How-to guides

Method: reviewed source. Demand lead: 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. Checked October 8, 2026.