外掛標籤
開發者團隊
原文外掛簡介
Vizzel brings AI storefront experiences to your WooCommerce shop. The plugin is a
single, extensible container: you connect it to your Vizzel workspace once, then
enable the widgets you want from one settings screen.
Widgets
Wall Preview — adds a “See it on your wall” button to the product page. A
shopper uploads a photo of their room, frames the wall, and Vizzel places the
product’s artwork on it, true to scale. Ideal for galleries and art sellers.
More widgets are added over time and appear on the same settings screen — no
plugin changes needed.
Widgets are rendered by the Vizzel widget bundle inside an isolated Shadow DOM, so
they never conflict with your theme. All display copy, usage caps and availability
are controlled from your Vizzel dashboard.
What you control in WordPress
Which widgets are on.
The button’s wording.
Where the button sits on the product page (five placements, with a live preview).
Which product categories to hide it on.
Button accent colour, shape and font.
The widget language, or automatic per shopper.
A Vizzel account is required. The plugin is the storefront half of a hosted
service — without a workspace and a publishable key it renders nothing.
External services
This plugin connects to Vizzel, a third-party service operated by Vizzel, to
generate product previews. It will not work without it.
1. Vizzel API — https://api.vizzel.ai
When your store’s admin saves a publishable key: the key is sent so Vizzel can
confirm it is valid before the plugin switches anything on.
When an admin opens the Vizzel settings screen of a connected store: a request
is made for the list of supported widget languages. No store or visitor data is
sent, and nothing is requested before the store is connected.
When a visitor uses a widget on your storefront (from their browser): the
publishable key, the WooCommerce product ID, the product title and image URL,
the chosen language, and the photo of their room that they upload are sent so
the preview can be generated. For a visitor who is not logged in, room photos
are used only to produce that preview and are deleted automatically after a short
retention window. An anonymous, randomly generated per-visit ID is also sent so
Vizzel can count widget usage; it is not derived from anything identifying and
contains no personal data.
When a logged-in customer uses a widget, and the Preview history widget is
enabled: an opaque per-customer token is also sent. The token is a random value
generated on your own site and stored in WordPress user meta; it is not their
email, name, or user ID, and Vizzel cannot resolve it back to a person. It lets
their previews be listed back to them under My account → Wall previews, which
means those room photos and previews are kept until the customer deletes them
rather than being deleted after the short window. Each customer keeps a limited
number of previews; older ones are removed automatically.
When a logged-in customer opens or deletes a preview: the same token is sent,
plus the preview’s ID.
When you export or erase personal data for a customer from Tools → Export/Erase
Personal Data: the token is sent so their previews can be listed or deleted.
When you have turned on Purchase attribution, and a shopper buys a product they
previewed: your store sends the preview’s opaque token, the product and variation
IDs, the quantity, the line total, the currency, and the order’s ID and status.
The request is signed by your own site so Vizzel can confirm it came from you.
No customer name, email, phone, billing or shipping address, order notes or
payment data is sent. This setting is off by default: no order information
of any kind leaves your store until an administrator turns it on, and turning it
off stops it again.
When such an order is refunded or its status changes: the same fields are sent
again so the earlier figure can be corrected.
2. Vizzel CDN — https://cdn.vizzel.ai
The widget JavaScript bundle is loaded from Vizzel’s CDN on product pages where an
enabled widget appears. While your store is connected, your server also requests a
small manifest file from this host twice a day to learn the current bundle version.
No store or visitor data is sent in either request. Neither request is made — and
nothing is scheduled — until an administrator has connected the store.
Nothing is sent to Vizzel, and no request of any kind is made, until an
administrator connects the store with a publishable key. Installing and activating
the plugin schedules no background work and generates no traffic. Disconnecting stops
all of it again. No visitor data is sent until a visitor actively uses a widget.
Vizzel’s terms of service: https://vizzel.ai/terms
Vizzel’s privacy policy: https://vizzel.ai/privacy
