Enter to send · Shift + Enter for a new line
Give your page a name. You can start editing it right away.
A page named this already exists in this project.
Links to this page on your site update by themselves, and the old address sends visitors here.
Connect this page to a collection to turn it into a template: a visitor lands on it through one item's own URL, and it shows that item's data. In each element's own Settings panel you can bind it to a field — not every element on the page needs to be bound.
Tokens: {{title}}, {{slug}}, {{collection}}, {{field.key}}.
Code here runs on the published page. Never paste passwords, API secrets or private tokens.
These settings apply to published pages. Secrets are write-only and are never included in your site files.
No cookies and no raw IP storage. Do Not Track is respected. Analytics is not gated by cookie consent.
Add ?pa_ignore=1 on your site to exclude your browser.
Your real contact details. Add them to any page from Elements → Business info (phone, email, address, hours, social links, WhatsApp) — published pages always show what is saved here. The AI uses them too when it builds pages, and search engines get them. Leave anything blank you don't want shown.
Social profiles: a full link or just the handle (@yourname).
With Cookie consent set to Opt in, these tags wait until a visitor accepts. With consent Off (or Notice only) they load for every visitor. Set this in the Cookie consent tab.
Code here runs on your published site for every visitor. Review it before publishing. Consent-gated snippets stay inert until consent is granted.
Things visible when the page opens show straight away. Better PageSpeed; effects lower on the page still play.
How one page changes into the next on your published site. It shows in Chrome, Edge and Safari; other browsers simply change page. Visitors who prefer reduced motion never see it.
The page glides when visitors scroll with a mouse wheel or trackpad, like most premium sites. Visitors who ask their device for less motion keep normal scrolling. Shows in Preview and on the published site.
Animations for each element are in the editor's Animate tab.
Analytics is cookieless and does not require consent. Tracking tags and tagged custom code are loaded only when their category is accepted.
Captcha and connected destinations are configured here. Secret values are saved separately and cannot be read back.
Each new submission is saved here first, then also sent to every app you turn on below. Keys and links are stored encrypted and can't be read back.
Supported: Generic webhook, Google Apps Script, Zapier, Make, Slack, Discord, Telegram, Mailchimp, Brevo, Kit/ConvertKit, Airtable, HubSpot, and Notion. Put webhook URLs, API keys, and tokens in the write-only secret JSON below. A webhook URL is saved as connector:id:webhook_url.
Honeypot, minimum fill time, link limits, captcha, and rate limits are checked by the server. Connector delivery runs after the submission is saved.
Click a card to view and edit its settings. Enabling either or both doesn't affect the other -- a Store cart or a Buy button set to Dynamic always needs Dynamic checkout on; turning it off is blocked while any such element still exists on a page.
Allowed link hosts: Stripe (buy.stripe.com, donate.stripe.com), PayPal (paypal.me), Flutterwave, Paystack (paystack.com). Links from other hosts are removed when you publish.
New payment products are created from an element’s Dynamic payment settings. Store products are managed in Build > Shop.
These older products have not been moved into the Store catalog yet. Moving them preserves their identifiers, so existing payment buttons keep working.
Collect up to 10 short text, choice, or checkbox values before hosted checkout. Do not ask for card details, passwords, or security codes.
Choose what the customer sees once they pay (or don't) and return from the hosted checkout page. The default keeps them on the page they started from and shows a popup message — pick a page instead to redirect them there.
Asked before every checkout and sent to providers that accept it (Flutterwave), so the buyer's real name shows there instead of whatever the provider falls back to on its own.
If you redirect to a success/failure page above, the popup message normally shows there too, on top of that page's own content. Choose No if your success/failure page already explains the outcome on its own and the extra popup feels redundant.
The messages above cover the two most common outcomes. Failure, cancellation, and other statuses each have their own default message below — only fill one in if you want to replace it.
Send signed order events to up to five HTTPS endpoints you control. Secrets are shown only when created or rotated. Verify the raw request body and timestamp within five minutes before processing; use the delivery ID for idempotency.
Only needed if your own server receives these webhooks. Every request is signed so your server can confirm it is genuine and was not forged or replayed. If you use Zapier or Make, you can skip this. The signature is lowercase hex HMAC-SHA256 over timestamp.body, prefixed with v1=. Use the exact raw body bytes.
const expected = 'v1=' + crypto.createHmac('sha256', secret).update(timestamp + '.').update(rawBody).digest('hex'); if (Math.abs(Date.now()/1000 - Number(timestamp)) > 300 || !timingSafeEqual(signature, expected)) reject();$expected = 'v1=' . hash_hmac('sha256', $timestamp . '.' . file_get_contents('php://input'), $secret); if (abs(time() - (int)$timestamp) > 300 || !hash_equals($expected, $signature)) { http_response_code(400); exit; }Emails the project owner about store order events. Customer receipts (Build > Shop) are separate and unaffected. Saved with the main Save settings button below, like everything else on this tab.
Which order outcomes should notify the store owner:
Group products so storefront grids can show a focused selection.
Manage products, prices, variants and checkout fields. Products remain drafts until you make them active. Existing Payment Buttons continue to work after moving legacy products.
Notify when a tracked product variant reaches or falls below this stock level. Alerts are sent once per low-stock period and reset after inventory is restocked above the threshold.
This is independent of order-event emails (Settings → Payments) and shares the same notification email -- set it here or there, either one updates both.
Cart totals, stock and discount use counts are recalculated on the server before checkout. Shipping rate amounts use your Payments tab's Default currency.
Used automatically by any Buy Now or Cart button that doesn't have its own Provider set.
Shoppers can't pay yet. Your cart and Buy buttons need online checkout: in the , turn on Dynamic checkout and connect a provider. Until then the published cart tells shoppers online checkout isn't available.
Order-event owner notifications (payment succeeded, failed, refunded, etc.) are in Settings → Payments. Low-stock alerts are above.
Turn off to stop charging this tax rate at checkout without losing your saved percent and country.
Payment keys are encrypted at rest using a separate payment-only encryption key. Payment functions decrypt a key only when they need to contact its provider. No person or screen can read it back, and keys are never included in published files. Key changes are logged below.
What we cannot protect against: if a provider key is leaked or misused, contact that provider and rotate it. Use restricted keys with only the permissions your checkout needs.
Finite retention deletes order records after the selected period, including paid sales records. Choose a finite period only if it suits your accounting and legal requirements.
Checkout email, name, and custom-field values are stored with the order. Deleting data for an email removes those customer details and custom fields while retaining the anonymized order total and status.
Use test keys first. Enable only the webhooks you need. Rotate keys if you suspect a leak.
Invite people to work on this project. Editors can make changes; Viewers can look around.
Connect a domain you already own, from any provider. Your site remains available at its ProtoAlly address too. Only the project owner can manage domains.
The AI reads this before every request, on any device. It keeps it up to date as you work; change or delete anything that's wrong. Clearing the conversation doesn't clear this.
Cookieless first-party analytics. Raw IP addresses are not stored.
Are you sure you want to delete ""? This can't be undone.
Create a reusable component in this project. Its instances stay linked so future master edits can update them together.
Components belong to this project. Insert from Assets or Elements. Shortcuts: Ctrl+Alt+K creates; Ctrl+Alt+R replaces; Ctrl+Alt+D detaches.