Target Tokens by Page, Menu Item, URL, Component, or Site Module

Every QCDR Token can be limited to the frontend locations where it is allowed to resolve. Page targeting is available for normal Token workflows, while component and site-module render targeting is a Pro-level capability.

Token targeting applies both when the placeholder is written directly into rendered content and when a Rule depends on that Token. If the Token is outside its allowed scope, QCDR treats it as unavailable rather than forcing a replacement.

Choose the Page Scope

In the Token editor, Pages and menu items provides three scopes:

  • All frontend pages: page/menu/URL targeting does not restrict the Token.
  • Only particular pages or menu items: the Token qualifies when the current Joomla menu item or the current URL/path matches one of your targets.
  • All pages except particular pages or menu items: matching targets are excluded and other frontend pages remain eligible.

Combine Menu Items and URL Patterns

  1. Select the desired frontend menu items when a stable Joomla menu context is the best target.
  2. Add URL or path patterns when a route needs to be matched independently of its menu item.
  3. Use * wildcards only where variation is expected, such as /products/*.
  4. Save the Token and test both a matching and a non-matching page.

Within a selected/excluded page scope, QCDR treats the selected menu items and URL/path patterns as alternatives: a match from either source counts as a page match. In an exclusion scope, either kind of match excludes the Token.

Target Component or Site-Module Output

Output created by extensions can be set to all render regions, only selected components/site modules, or all except selected components/site modules. This extension targeting requires Pro or higher.

QCDR identifies package-owned render boundaries in the final HTML so a Token can qualify for a component or a specific site-module region. Plugin output and Administrator modules are not exposed as isolated runtime targets. Content outside an isolated module region normally uses the current page component as its extension context.

All Token Gates Still Apply

Page and extension targeting narrow where the Token may run; they do not bypass its status, plan tier, audience, schedule, IP rules, technical conditions, or nested dependencies. All applicable gates must qualify for the current location.

If a directly authored Token is outside its scope, the literal placeholder is preserved. If a Rule depends on that Token at a location where it is unavailable, QCDR leaves the Rule's matched content unchanged.

A Practical Targeting Test

Start with the narrowest page/menu target that proves the Token's output. Then test a different menu item, a URL that should be excluded, and—when extension targeting is enabled—both the intended component/module region and unrelated output on the same page. Broaden the scope only after each boundary behaves as expected.

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.