Create and Name a Reusable QCDR Token

A QCDR Token gives one reusable value a stable placeholder such as {site.company_logo}. The same Token can be typed directly into eligible frontend content or selected as the replacement source for a Rule; there is no separate “standalone” and “Rule” Token mode.

Create the Token in Draft first, choose a name you can keep, and enable it only after testing its output and targeting.

Create the Token

  1. Open Components > QC Dynamic Replacer > Tokens.
  2. Select Create Token.
  3. Enter the machine name in Token.
  4. Enter the required Friendly name and, optionally, a description.
  5. Leave Status as Draft while building and testing.
  6. Choose the Output type and configure its value.
  7. Set targeting only where the Token should be narrower than all frontend pages.
  8. Select Save or Save & Close.

Token Name Rules

The machine name is normalized to lowercase and must start with a letter. It may then contain lowercase letters, numbers, dots, underscores, and hyphens. QCDR accepts up to 189 characters under the current validation and requires each Token name to be unique.

Use a short namespace that communicates ownership or purpose, for example site.phone, brand.logo, or campaign.fall_cta. QCDR displays and resolves the placeholder with braces: {site.phone}.

Friendly Name vs. Token Name

Friendly name is the administrator-facing label in the library. Token is the stable machine name that appears inside braces in authored content and Rule configuration. Changing the friendly name does not change the placeholder; changing the machine name can break existing references, so treat it like an API identifier.

Choose an Output Type Deliberately

Plain text is available at Basic. HTML/formatted content, image/media, link/button, and URL output require Pro. Joomla dynamic data and PHP output require Max/All Access, and PHP also requires the separate Manage PHP Tokens permission.

Nested Token references require at least Pro and inherit the highest required tier of their dependencies. QCDR prevents a newly configured Token from silently bypassing those plan boundaries.

Use the Placeholder

After saving, manually place {token.name} in eligible visible frontend content, or edit a Rule and choose that Token as the replacement source. Current standalone resolution does not scan inside HTML tags/attributes or normally protected script/style/code/form/comment regions.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.