Use Pipeline → Tags to maintain the labels used across leads and playbooks. These operations can update many records and automatic rename rules, so administrative access and a clear intended change are prerequisites. Review the affected tags and playbooks before confirming a job.

What you’ll see

The Tags page, where you rename, merge or remove tags. Sort the list by Most leads or A–Z.

Review a tag change

  1. Search or sort the tag list and inspect each tag’s lead count. Use Show more when more rows are available; selected tags can be cleared with Clear.
  2. Open a tag’s actions and choose Rename, Merge, or Delete. For a bulk merge, select the source tags first and review the displayed selection limit.
  3. In the change dialog, enter the New name or choose the intended destination. If the new name already exists, the dialog explains that the tags become one. For deletion, review what should happen to leads carrying that tag.
  4. Review Keep doing this automatically carefully. It can retain a rule for future occurrences, beyond the current lead update.
  5. Wait for the playbook dependency check. Review referenced drafts or published rules and the offered update choices. Existing enrollments retain their original version; do not assume a tag rewrite changes those versions.
  6. Confirm only the reviewed operation and monitor its progress. A running job continues after the dialog closes; use the Tags page to inspect the result.

Confirm and recover

Recheck both the old and destination tags and any automatic rule. A timeout or unfinished job can leave some records already changed. The dialog explicitly advises reviewing confirmed updates before retrying. Stopping an automatic rename affects future additions and does not undo existing leads. Use support for an uncertain result rather than launching another overlapping rewrite.

Related: Leads, Playbooks.

Screenshots

The screenshot for this guide is shown above, under “What you’ll see”.