Storefront language
Match visitors based on the storefront language they're currently browsing in.
Storefront language matches a visitor based on which published storefront language they're currently browsing your store in. It's only useful if your store has more than one published language — on a single-language store, every visitor matches the same language, so the rule wouldn't distinguish anyone.
Common uses: showing a market-specific promotion only to visitors browsing in a particular language, or restricting content that's only ready in certain languages so visitors browsing in an unsupported language don't see a half-translated experience.
Like most access rules (aside from the action-based ones such as Passcode, Secret link, Subscribe, and Confirmation prompt), Storefront language can be set to match If the visitor is browsing in the selected language(s), or Unless they are — inverting it to match every other language instead. See Combining rules.
Add the rule
Open Locks and create a new lock, or open an existing one to edit it.
Choose the content you want to protect. See Access rules overview for how rules fit into a lock.
Click the Unlock rules tab, then in the Condition type dropdown, select Storefront language.

Select one or more of your store's published languages to match against.

Choose If or Unless.
Click Save.
Example: Show a campaign page only on the French storefront
Suppose a campaign page has only been prepared in French and should not be available in the store's other published languages.
Select the French campaign page as the content to protect.

Add Storefront language, choose If, then pick French from Available languages.

Leave the rule's Redirect URL empty.
Set the Access denied message to:
This campaign is only available on the French storefront.

Click Save.
Result on the storefront
A visitor browsing the French version of the storefront can open the page normally. If the visitor switches the storefront to English or another language, the rule no longer matches and the page displays the message above.

Related docs
Last updated
Was this helpful?