iAdvizeDocs

AI Storefront

Publish your site's AI Storefront, a page we host with your brand where shoppers talk to your assistant and shop, and share its link. It serves the agent that answers on your site.

Your AI Storefront is a page we host for your site, outside your own storefront, where shoppers talk to your assistant and shop. It lives at https://iadvize.ai/s/<site-key> and anyone with the link can open it: no iAdvize account, no dashboard access. Share it in a newsletter, a social bio or a campaign, or send it to a prospect as a working demo.

Each site has one AI Storefront, and it serves the agent that answers on your site. To put the assistant on your own storefront instead, use the web tag: publishing the AI Storefront doesn't gate the tag, and the tag doesn't need it.

Publish your AI Storefront

Make sure an agent answers on your site. You choose it from the agent itself: open it under Agents and use Go live. See Put an agent live or take it offline.

Open the site's Site settings → AI Storefront tab, the last tab of Site settings. The card names the agent your AI Storefront serves, with a Change in Agents link.

Turn on Publish your AI Storefront, then click Save at the top right of the page. The switch stays disabled while no agent answers on the site. If the agent that answers has no Live version left, Save fails with "This site has no live agent yet. Make one go live in Agents first." Put a version live with Go live, then save again.

Once saved, the link appears under the switch. Copy link puts it on your clipboard and Open shows it in a new tab.

Changing which agent answers changes what the AI Storefront serves, at once. You don't need to reshare the link.

To take the page offline, turn the switch off and save. That pauses the link without discarding the key: publish again and the same link works again.

Only members whose role can edit sites see the switch. Everyone else sees whether the AI Storefront is published, the agent it serves, and the link once it's live.

Publish it from the MCP server

An MCP client connected to your dashboard can do the same with set_site_hosted_page: it switches the page on or off for a site and reads the link back. It needs the same permission as the dashboard (Sites: Edit), applies at once and has the same condition: an agent with a live version must answer on the site. The link is also on the hostedPage field of the site on the MCP server's list_sites and on the REST site: enabled, and link while the page is published.

Open it from the site menu

The site menu at the top of the sidebar (click the site's name) has a section for the site you're working in, above the list of sites:

  • Visit your site opens your own site's address in a new tab.
  • Open your AI Storefront opens the AI Storefront in a new tab, once it's published.
  • Set up your AI Storefront takes you to the AI Storefront tab instead, while it's not published. Only members who can edit sites see it.

There's no copy action in the menu. Copy the link from the AI Storefront tab.

Which language it opens in

A shopper who opens the link sees the AI Storefront in their browser language when your site offers it, otherwise in your site's default language. You set both on the site's Website tab.

To force a language for a link you're sharing in one market, add ?l= with a language code, for example https://iadvize.ai/s/<site-key>?l=fr in a French newsletter or on a French QR code. It only picks among the languages your site offers. A shopper who comes back to a conversation they already started keeps that conversation's language. See Choose the shopper's language for the shared rules.

The link is built from the site key, which also identifies your site to the web tag. If the link has leaked or you want a clean one, use Rotate key in the Site key card of the site's Site settings → Installation tab. Rotating takes effect at once:

  • every AI Storefront link you already shared (newsletters, bios, campaigns) stops opening;
  • the tag installed on your site stops working until you replace its key with the new one.

So rotating is not the same as unpublishing. To take the page offline for a while, turn Publish your AI Storefront off instead.

What visitors get

  • Chat only. The page reuses the same chat component as the dashboard playground, with no dashboard chrome, no conversation history, no version picker.
  • The agent's identity, shown at the right moment. Before the first message, the served agent's avatar and display name (set on its Public identity card) show above the welcome message (or a generic assistant icon and label if neither is set), but only when a welcome message is configured for the visitor's language. If not, the compact chat header keeps showing the identity throughout instead. Once the visitor starts typing or the conversation has a message, the identity moves into (or stays in) the header. The site's own logo never appears in the chat.
  • Friendly status messages, never raw tool calls. While the assistant is working (searching the catalog, comparing products, thinking through a reply), visitors see a short, plain-language status instead, like "Looking for the best products for you…" or "Thinking…", shown only while that step is in progress, and, when the assistant loads a conditional instruction block you gave an indicator message, that phrase in the visitor's own language. Once it finishes, only the result appears (a product carousel, comparison, detail card, or clarifying question), or nothing at all if there's nothing to show. This is fixed for the AI Storefront: there's no setting to show the raw tool name, its JSON, or the assistant's reasoning here. You can preview this exact display from the dashboard using the User view option in the playground's configuration panel.
  • The live version, always. The AI Storefront serves the live version of the agent that answers on the site. When another version goes live, the page starts answering with it immediately, so you don't need to reshare anything. No other version is reachable this way.
  • Every linked connector works, same as the playground. Whatever connectors are linked to the live version (Shopify, Custom, or any other e-commerce connector) run on the AI Storefront exactly like they do in the playground. There's no connector-type restriction: catalog search, cart/policy tools, and any Custom connector's tools all work the same way here as they do for your own team testing the agent.
  • Visitors can rate any response. Every assistant message has a thumbs-up/thumbs-down control that opens a short dialog (an optional issue category for a thumbs-down, an optional comment either way) rather than submitting instantly. Submitting shows a one-line notice that the feedback and conversation may be reviewed internally, shown only on this surface. A message that ends on a clarifying question gets no thumbs until the visitor answers, skips or closes it, or moves on by typing a message or tapping something else in the chat, since until then there's no reply to rate. See Rate a message for the full behavior.
  • Not indexed. The page and its API route are excluded from search engines (robots.txt and a noindex tag), so sharing the link is the only way anyone finds it.

Rate-limit protection

The AI Storefront and the embedded web tag share the same chat endpoint, and it's protected against abuse by two layers, both managed by iAdvize. There's nothing to configure on your side:

  • A per-visitor limit: 15 requests per 10 seconds. Tuned to stop a single abusive source (someone hammering the endpoint from one place) without ever affecting normal shopper traffic, even for a large merchant whose traffic naturally comes from many different visitors.
  • A per-organization ceiling: 1,200 requests per minute. Set deliberately high so it never throttles legitimate usage. It only trips on an unusual, distributed flood across many sources at once.

Regular traffic, however busy your storefront gets, won't come close to either.

The link itself is the access control

Anyone who has the link can chat with the assistant: there's no password or login on top of it. Don't share it anywhere public you wouldn't want a stranger to find (a public GitHub repo, an indexed forum post). If a link gets out, rotate the key, knowing the installed tag needs the new key too.

The link returns a not-found page (rather than an error) whenever it can't resolve to a live agent. This is by design, so a stale or guessed link never leaks anything:

  • The AI Storefront isn't published, or the key has been rotated.
  • No agent answers on the site, for example after the answering agent was taken offline. Put an agent live from Agents to bring the page back.

AI Storefront conversations show up in Conversations with AI Storefront as their conversation source (hosted in the API and the MCP server). You can review the transcript there like any other conversation.

On this page