---
title: Guide to dynamic tags
description: Dynamic tags are a powerful tool used throughout the Centercode platform to automatically pull and insert relevant information from the Centercode data engine into your content, email templates, and integrations.
---

[Skip to content](https://help.centercode.com/en/guide-to-dynamic-tags#main-content)

[![New\_Centercode\_Logo.png\]](https://help.centercode.com/hs-fs/hubfs/New_Centercode_Logo.png?height=35&name=New_Centercode_Logo.png)](https://centercode.com/)

- [Help Center Home](https://help.centercode.com/)
- [Starter & Delta Edition Help](https://learn.centercode.com/)

Open main navigation

Close main navigation

- [Help Center Home](https://help.centercode.com/)
- [Starter & Delta Edition Help](https://learn.centercode.com/)
- [Report an Issue](https://centercode.com/issue)

[Report an Issue](https://centercode.com/issue)

 How can we help?

- There are no suggestions because the search field is empty.

1. [Help Center](https://help.centercode.com/en?hsLang=en)
2. [Centercode Basics](https://help.centercode.com/en/centercode-basics?hsLang=en)
3. [Guides](https://help.centercode.com/en/centercode-basics?hsLang=en#guides)

# Guide to dynamic tags

## Insert live user, feedback, and project data into emails, integrations, and content across Centercode

 

*This article applies to* ***All*** *editions.*

 Dynamic Tags let you pull data from the Centercode Data Engine and insert it into emails, integration payloads, and content. If you've ever needed an email to address each tester by name, or a Jira integration to automatically populate ticket fields from Centercode feedback, Dynamic Tags are how you do it.

This guide covers what Dynamic Tags are, the available data sources, where you can use them, how to insert them, and common mistakes to avoid.

#### **What Are Dynamic Tags?**

 Dynamic Tags are placeholder variables that resolve to real data when content is rendered or sent. You insert a tag in your email template or integration config, and Centercode replaces it with the actual value for each recipient or each feedback ticket.

**For example:** An email template with a "First Name" Dynamic Tag will display "Hi Sarah" for one recipient and "Hi Marcus" for another, all from the same template.

#### **Dynamic Tag Data Sources**

 Dynamic Tags draw from three core data objects in the Centercode Data Engine. The tags available to you will depend on the context where you're inserting them.

### **User Data**

Tags that pull information about individual users, including profile data, participation history, and account details.

- **User Account**: First name, last name, full name, email address, username, and other account-level fields
- **User Participation**: Login history, activity counts, project membership, team assignments
- **User Profiles & Surveys**: Responses from profiling forms and surveys, including demographic, technographic, and custom fields you've configured

### **Feedback Data**

Tags that pull information from feedback submissions, including tickets, issues, ideas, and discussions.

- **Feedback Type**: Ticket title, description, status, priority, category, creation date, and all form fields within the feedback type
- **Submitter User Account**: The account details of the user who originally submitted the feedback
- **Feedback Metadata**: Ticket ID, submission date, last modified date, vote count, duplicate count, and other system-tracked fields

### **Project & System Data**

Tags that pull information about the project or community context.

- **Project**: Project name, codename, dates, URLs, and configuration details
- **External Data**: Data captured from external systems via listeners and webhooks, stored as custom fields as Boolean, Date/Time, Integer, or String data types

💡 **Ted Tip:** Not sure which data source has the tag you need? If the data came from a *person*, look under User. If it came from a *submission*, look under Feedback. If it came from *outside Centercode*, look under Web Services or External Data.

### **Where can I use dynamic tags?**

Dynamic tags are available wherever the dynamic tag panel appears in the editor. If the panel is not there, that area does not support them.

You can use dynamic tags in:

- Email templates and notifications
- Content and Resources articles
- Macros and notices
- Test plan feature and activity descriptions
- Menu items
- Report elements
- External destinations and integrations

##### **Where they are not available**

Survey and feedback question text does not support dynamic tags. You cannot insert a participant's stored profile information, such as their name or address, into the wording of a question.

If you need someone's saved details to appear in front of them, put that content somewhere that does resolve tags. A Content page, a test plan activity description, or the email that delivers the survey will all render the value.

 

#### **How to Insert a Dynamic Tag**

 The process for inserting a Dynamic Tag is the same across the platform, whether you're working in an email template or an integration configuration.

1. Place your cursor where you want the dynamic data to appear
2. Locate the **Dynamic Tags** insertion panel (typically on the right side of the editor or within the configuration interface)
3. Select or search for a **data source category** (e.g., User Account, Feedback Type, Web Services)
4. Browse or search for the specific field you need
5. Double-click the field name to insert the Dynamic Tag at your cursor position

### **Plain Text vs. HTML Dynamic Tags**

When inserting Dynamic Tags, you'll often see an option to use the **Plain Text** version of a tag. This distinction matters:

- **Plain Text Dynamic Tags** strip all formatting and return raw text values. **Use these for integrations** (Jira, webhooks, API payloads) to prevent HTML code from being sent to external systems.
- **Standard Dynamic Tags** may include HTML formatting. **Use these for email templates** and other contexts where rich formatting is appropriate.

💡 **Ted Tip:** If you're seeing raw HTML code showing up in your Jira tickets or Slack messages, you're probably using a standard Dynamic Tag where you need the Plain Text version. Switch to Plain Text and the problem will go away.

#### **Common Use Case Examples**

### **Example 1: Personalized Status Update Email**

**Scenario:** You want to automatically notify a feedback submitter when their ticket status changes to "Needs More Information."

Set up a macro triggered by the status change, and build an email template like:

> Hi **\[First Name\]**,
> 
> Thank you for submitting **\[ID\]** titled: **\[Summary\]**. Our team has reviewed your submission and we need a bit more detail before we can move forward.
> 
> Please revisit your submission and add any additional context that might help us reproduce or understand the issue.

Each Dynamic Tag in the template resolves to the correct value for each recipient and their specific feedback ticket.

 ![](https://t.gyazo.com/teams/centercode/3a010234aab471d3ba222bbbf98d1236.png)

### **Example 2: Jira Integration Field Mapping**

**Scenario:** You want Centercode feedback to automatically create Jira tickets with the submitter's details and feedback content.

In your Jira integration JSON configuration, replace static placeholder values with Dynamic Tags:

- **Summary** field → Feedback Title Dynamic Tag
- **Description** field → Feedback Description Dynamic Tag (Plain Text)
- **Reporter display** → Submitter Full Name Dynamic Tag
- **Priority** → Feedback Priority Dynamic Tag

### **Example 3: Discord Notification with Feedback Context**

**Scenario:** You want your team's Discord channel to receive a notification whenever new feedback is submitted.

In your webhook POST body, inject Dynamic Tags for the feedback title, submitter name, and feedback type so each Discord message includes the specific details of the submission that triggered it.

### **Can I use a dynamic tag for a value I update each phase, like a build number?**

No. There is no dynamic tag that holds one central value you edit in a single place and have update everywhere it appears. Tags resolve per recipient from that person's own data, so there is nothing to point at a value you maintain centrally.

Distributed Values are the closest feature and they do not solve this either. A distributed value resolves to the specific value handed to that person, and editing the type's value list does not change what anyone already holds. After you update the list for a new phase, everyone who received the previous build number still resolves to the previous build number.

The workable approach is to keep the value in one place people go to rather than pushing it into every message. Put the build number on the Content or Release page, and point your announcements at that page. Updating the page then updates what everyone sees, with nothing to reissue.

#### **Best Practices**

- **Preview before activating:** Send a test email or trigger a test webhook to verify your Dynamic Tags resolve correctly before going live.
- **Use Plain Text tags for integrations:** Any time data flows to an external system (Jira, webhooks, Slack, Discord), use the Plain Text variant to prevent HTML from appearing in your payloads.
- **Match tags to context:** A Feedback Type Dynamic Tag won't resolve in an email that has no feedback context (e.g., a general community announcement). Make sure the data source matches the trigger.
- **Keep templates readable:** When a template contains many Dynamic Tags, it can become hard to scan. Use clear formatting and whitespace so collaborators can still understand the template at a glance.
- **Don't forget External Data tags:** If you've set up external listeners or webhooks that capture data from third-party systems, that data becomes available as Dynamic Tags too. You're not limited to Centercode-native fields.

#### **Notes**

- Dynamic Tags are available wherever the Dynamic Tags insertion panel appears in the platform. If you don't see the panel, that area does not support Dynamic Tags.
- The available tags depend on your context. Email templates triggered by feedback macros will show Feedback-related tags; templates triggered by user macros will show User-related tags.
- External Data fields captured via webhooks and external listeners become accessible as Dynamic Tags after they've been stored. See the [Guide to Simple External Listeners](https://help.centercode.com/en/centercode-guide-to-simple-external-listeners?hsLang=en) for setup instructions.
- For a deeper understanding of the data objects behind Dynamic Tags, see the [Data Engine Overview](https://help.centercode.com/en/what-is-the-centercode-data-engine-cde?hsLang=en).
- For integration-specific usage, see the [Jira Integration Guide](https://help.centercode.com/en/centercode-jira-integration-guide?hsLang=en), [Guide to Simple Webhooks](https://help.centercode.com/en/centercode-guide-to-simple-webhooks?hsLang=en), and [Guide to Integrating with Discord](https://help.centercode.com/en/integrate-centercode-with-discord?hsLang=en).
- If the dynamic tag panel is missing from an editor listed above, your community may not have the feature enabled. Contact your Centercode Implementation Manager to check.
- A Distributed Value used as a dynamic tag in an email arrives as plain text, even when a URL value is set. It renders as a link on the Content or Release page itself. See the [**Guide to Distributed Values**](https://help.centercode.com/en/guide-to-distributed-values?hsLang=en).

- [Centercode Basics](https://help.centercode.com/en/centercode-basics?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/centercode-basics?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/centercode-basics?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/centercode-basics?hsLang=en#faqs)
- [Community Administration](https://help.centercode.com/en/community-administration?hsLang=en#main-content)

    - [Community Administration](https://help.centercode.com/en/community-administration?hsLang=en#community-administration)
    - [Overviews](https://help.centercode.com/en/community-administration?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/community-administration?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/community-administration?hsLang=en#faqs)
- [Project Administration](https://help.centercode.com/en/project-administration?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/project-administration?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/project-administration?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/project-administration?hsLang=en#faqs)
- [Features & Test Planning](https://help.centercode.com/en/features-test-planning?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/features-test-planning?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/features-test-planning?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/features-test-planning?hsLang=en#faqs)
- [Resources & Surveys](https://help.centercode.com/en/resources-surveys?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/resources-surveys?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/resources-surveys?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/resources-surveys?hsLang=en#faqs)
- [Recruiting](https://help.centercode.com/en/recruiting?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/recruiting?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/recruiting?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/recruiting?hsLang=en#faqs)
- [Feedback](https://help.centercode.com/en/feedback?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/feedback?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/feedback?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/feedback?hsLang=en#faqs)
- [Dashboards & Reporting](https://help.centercode.com/en/dashboards-reporting?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/dashboards-reporting?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/dashboards-reporting?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/dashboards-reporting?hsLang=en#faqs)
- [Integrations](https://help.centercode.com/en/integrations?hsLang=en#main-content)

    - [Overviews](https://help.centercode.com/en/integrations?hsLang=en#overviews)
    - [Guides](https://help.centercode.com/en/integrations?hsLang=en#guides)
    - [FAQs](https://help.centercode.com/en/integrations?hsLang=en#faqs)

- [What's New?](https://whatsnew.centercode.com/)
- [System Status](https://status.centercode.com/)
- [Starter & Delta Edition Help Center](https://learn.centercode.com/)
- [Report an Issue](https://centercode.com/issue)

[![Centercode logo](https://help.centercode.com/hubfs/images/logos/Centercode-Logo.svg "Centercode logo")](https://centercode.com)

Copyright © 2027, Centercode