Social Label Rename History Crosswalk

Link a renamed campaign label to historical exports without silently merging namesakes. Preparation only, not an account action.

What to provide

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

How it works

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.

The output

workspace | label_id | old_name | new_name | effective_time | historical_match | unresolved

Worked fictional example

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.

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: Oct 11 live AIS Search Console: marketing Copilot 37 impressions, Planable/Claude 35, Planable/ChatGPT24, campaignbrief 12, investoragent 19, MuseIndia 98. 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. Checked October 11, 2026.