# Social Label Rename History Crosswalk

Link a renamed campaign label to historical exports without silently merging namesakes.

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

## Inputs
Label IDs, rename history, workspace ID, dated exports and campaign definitions.

## Workflow
1. Use stable IDs and workspace boundaries to join versions.
2. Keep a rename of one ID separate from a new label with an old name.
3. Preserve the original export label beside the current name.
4. Return an auditable mapping; no relabeling or attribution change.

## Output contract
workspace | label_id | old_name | new_name | effective_time | historical_match | unresolved

## Fictional acceptance test
Fictional label L1 changes Spring to Summer. New L2 is named Spring. Historical L1 rows stay L1; they do not become L2 because the old name matches.

## 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://help.planable.io/hc/en-us/articles/21715363601052-Labels

Checked October 11, 2026. Oct11 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude35, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia98. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.