Page-type targeting

Targeting lives in the Page types card on the editor's General tab: five tiles, Home, Product, Category, Content and Blog, and below them a Show on every page instead switch.

Show on every page instead is the switch to reach for when you want a widget everywhere with no exceptions. Turn it on and the widget renders on every page type, full stop. It overrides the tiles completely: whatever's selected (or not) there stops mattering, and no page type, declared by your storefront or held by your site's pages, can exclude a page while this is on. While it's on, the tiles are greyed out with "Off while the widget shows on every page." and can't be changed; turning it back off makes them usable again with whatever page types were selected before. Nothing is cleared by toggling it either way.

There is no Checkout type: a widget cannot be kept off a payment page by page type.

Which page type a page hasCopy Anchor Link

A widget is matched against the effective page type of the page the shopper is on:

1. The type your storefront declares with iadvize('set', { customData }), when it is one of the five. A declaration always wins.
2. Otherwise, the type your site's Pages hold for the current address: the type from a read of the page, or the one guessed from the address until it is read. A page stored as Unknown counts as having none.
3. Otherwise, none.

This applies to the floating formats and to the inline ones, and to the starter-question chips they carry. A merchant who declares nothing now sees a widget targeted by page type follow the type of the page in Pages. Before, such a page had no type, so an allow-list could not exclude it. See When you declare nothing for how the tag looks it up.

Selected page types are an allow-listCopy Anchor Link

With Show on every page instead off, the page-type tiles work as an allow-list, not a simple filter, for both floating formats:

• No page types selected: the widget never renders, anywhere, even if it's online and published. You must explicitly select at least one page type, or turn on Show on every page instead, before the widget does anything. A new chat bubble or question bar never starts here: it arrives with Show on every page instead already on, so this state is only reached by turning that switch off without selecting anything.
• At least one page type selected: the widget renders on every page, unless the page has a type (declared, or held by your site's pages) that isn't on the list. A page with no type at all still shows the widget: the allow-list only has something to exclude once it knows what type the page is.

For example, selecting every type except Blog shows the widget everywhere except on blog pages: the ones you declare as blog and the ones your site's pages hold as Blog.

A widget or a question that had Checkout selected lost that value when the type was removed. A widget whose list held only Checkout is left with no page type, so it renders nowhere and the list shows it as Offline until you pick one.

Targeting is part of the draft, so a change here reaches shoppers when you go live, not when you save.

Starter questions carry a second page ruleCopy Anchor Link

A starter question has its own page scope, and the two rules are applied together: a chip shows on a widget only when the widget is allowed on that page and the question's own scope admits it. Neither overrides the other: a widget that shows on Home and Product carries a Product-scoped question on your product pages only, and a widget the targeting above excludes carries no chips at all.

On a page with no page type, neither rule has anything to match against: the widget renders (its allow-list can only exclude a type the page has) and it carries every enabled question with text in the shopper's language, capped at three. That is the same thing the panel does there, which is the point: a chip's job is to open the panel, so the two must not offer different questions on the same page.

Check it before publishingCopy Anchor Link

The preview's simulated page control, the first one above the scene, simulates the page a shopper is on, including Page type not declared: a page with no type. The preview opens on a page the widget targets, so you don't land on a scene that hides the widget you came to edit. It only simulates the page type you pick. It doesn't look up what your site's pages hold, so it can't show you the fallback described above. When your targeting excludes the simulated page, the scene says the widget is not rendered and names the page types it does target. The verdict comes from the same rule the tag applies, so the two can't disagree.