Pages
The Pages card on the Targeting tab decides which pages of your storefront the stage is eligible to fire on. Two independent axes: page types (a checkbox list of known Shopware page types) and URL patterns (glob patterns to match arbitrary URLs).
Both are strict opt-in — empty matches nothing. You must pick at least one page type, or set at least one URL pattern, or the stage will not display anywhere.
Page types
Section titled “Page types”A checkbox list of known Shopware storefront page types. Pick the page types where the stage should display.
- Home page
- Category page
- Product page
- Search page
- CMS page
- Cart page
- Checkout pages
- Customer account
The current page’s type is computed server-side on every request and matched against this list during resolve.
URL patterns
Section titled “URL patterns”A text area where each line is a glob pattern. Patterns match the full request URL path:
*matches any characters except/.**matches any characters including/.?matches a single character.
Examples:
/sale/*— matches/sale/spring,/sale/winterbut not/sale/spring/details./sale/**— matches/sale/spring/detailsand any deeper path./product/?— matches/product/1through/product/9./checkout(exact) — matches only/checkout.
Empty matches no URL — same strict opt-in policy as page types.
Combining page types + URL patterns
Section titled “Combining page types + URL patterns”When both axes are set, the Pages / URL match operator decides how they combine:
- OR — match page types or URL patterns (default) — fire on any page that satisfies either axis. Most permissive; useful for “fire on all product pages OR on
/promo/*”. - AND — match page types and URL patterns — fire only when both axes match. Most restrictive; useful for “fire only on product pages within
/category/sale/*”.
The operator is hidden / ignored when only one axis is set — there’s nothing to combine.
Common patterns
Section titled “Common patterns”| Goal | Page types | URL patterns | Operator |
|---|---|---|---|
| Fire on every product page | ✓ Product page | (empty) | n/a |
Fire only on /promo/* regardless of page type | (none) | /promo/* | n/a |
| Fire on cart and checkout | ✓ Cart, ✓ Checkout | (empty) | n/a |
Fire on category pages within /sale/* only | ✓ Category page | /sale/* | AND |
Fire on home OR /welcome/* | ✓ Home page | /welcome/* | OR |
How it interacts with the rest of targeting
Section titled “How it interacts with the rest of targeting”The page filter is just one axis. A stage is eligible for the current request only when all of these pass:
- Active toggle on, schedule in range (Schedule).
- Sales channel matches (Audience).
- Customer group matches.
- Rules evaluate true.
- Page filter (this page).
- Other association filters (categories / products / manufacturers / streams / CMS pages, if set).
Failing any of them filters the stage out at resolve.
Where to go next
Section titled “Where to go next”- Audience — sales channels, customer groups, rules, categories, products, manufacturers, streams, CMS pages.
- Triggers — when on the page (page passes → trigger schedules).
- Storefront → How stages render — the resolve pipeline.