Advanced Source Filters

Advanced Source Filters help you move from block-level inventory to exact block-instance evidence. Open View sources for a block, show advanced filters, then filter by indexed block content, class token, ID or anchor, attribute path/value, or compact query syntax.

Run a full scan after upgrade #

Run a fresh full scan before relying on advanced source filters. The filters use the normalized attribute index created during scan work and do not rescan post content while you browse source lists.

Filter modes #

Block content Use Block Content when one repeated block type contains multiple wording variants and only one copy fragment, CTA, placeholder, or disclaimer should stay in scope.
Sources modal showing search, filters, export controls, and source rows in DXM Block Toolkit.
Class token Use Class when you need an exact class token match, such as a block instance carrying hero without matching unrelated words that only contain those letters.
Sources modal filtering core paragraph sources by a class token in DXM Block Toolkit.
ID or anchor Use ID or Anchor when cleanup depends on a specific anchor, id, or compatible indexed id-like attribute.
Sources modal filtering core heading sources by an ID or anchor in DXM Block Toolkit.
Attribute path and value Use Attribute Path with Attribute Value for scalar block attributes. Top-level attributes use their key, while nested scalar values use dot paths such as style.elements.link.color.text.
Sources modal filtering core paragraph sources by an attribute path and value in DXM Block Toolkit.
Attribute query Use Attribute Query for compact power-user filters such as class:hero, id:intro, attr:data-variant=dark, or attr:style.color.text~=blue.
Sources modal filtering core paragraph sources with compact attribute query syntax in DXM Block Toolkit.

How matching works #

  • All active source-level filters must match together.
  • Block-content filters match indexed block content so you can isolate one wording variant before cleanup or replacement work begins.
  • Class filters match exact class tokens.
  • ID filters match anchors, ids, and compatible indexed id-like attributes.
  • Attribute path/value filters use exact matching by default, with contains matching available for bounded text attributes.
  • When block-content or attribute filters are active, source rows count matching block instances rather than every instance of that block in the source.

When block-content filters are the better fit #

Use block-content filters when the block name alone is still too broad. They are especially useful when one shared block type contains multiple wording variants, disclaimers, CTA copies, or similar content patterns and only one of them should stay in scope for review, updating, or replacement.

  • Use them to isolate outdated copy, campaign text, or disclaimer language inside repeated blocks.
  • Combine them with source-type or status filters when the same wording appears across editorial and theme-level sources.
  • Carry the same filtered scope into Refactor when the reviewed rows should become a previewed replacement batch.

Examples of content-first workflows #

Common examples include cases where the block name is already known and you want to isolate one wording variant or another content-level pattern. The filtered result can then support review, updates, replacement planning, QA, handoff, or Refactor preparation.

  • Find legacy CTA text still embedded in repeated button, paragraph, or group blocks.
  • Isolate disclaimer or compliance wording before editorial review, QA, or handoff.
  • Separate one campaign, locale, or placeholder variant from the rest of a shared block type before Refactor.

Compact query limits #

Compact queries use space-separated tokens. Use the dedicated fields when an attribute value needs spaces or when the scope depends on block content rather than attribute tokens. Quoted values, wildcards, and regular expressions are not supported in the current Refactor-aware workflow either.

Exports keep the active filters #

Source CSV exports follow the active source-level filters, including block-content filters and advanced attribute filters, so the downloaded evidence stays aligned with the view you filtered.

For inventory context, return to Blocks & Sources . For handoff, continue with Exports . For replacement work based on the same filtered scope, continue with Refactor .