Two different things in EDGR are called tags.
- A customer tag is a free-form label on a person:
nurture-q2, industry:fintech, priority:high. Use them to filter, to build dynamic segments, and to steer automation.
- A lead tag is a scoring signal on a product, not a label on anybody. It belongs to Scoring and lives in the product detail page.
Anything is a valid tag name except the bot: prefix, which the system reserves.
| Tag | Effect |
|---|
bot:disabled | The AI agent stops replying to this customer |
bot:disabled, and so does the set-bot-autoreply node. You rarely need to type it.
- Customer drawer → Profile → Tags, with autocomplete over tags that already exist.
- Tick rows in the customer table → bulk bar → add tags. Names that do not exist yet are created.
- A CSV
tags column, comma-separated. Missing tags are created.
- The
add-tag and remove-tag nodes inside a campaign. See Contact Nodes.
- The AI agent, which can tag a customer while handling their conversation.
Give tags a prefix and a consistent shape — industry:b2b-saas, stage:trial — and they stay sortable and filterable once there are a hundred of them.
/products → a product) and the lead-tags section asks what makes a good lead. Each entry describes a signal, sits in one of three groups, and carries a weight whose sign decides whether it raises or lowers the fit score. Sliders set how much each group counts.
These never appear on a customer. See Scoring for how they turn into a number and Leads for where that number shows up.