With the “Page” element, you publish your own web pages directly from your campaign, with no hosting of your own. You upload the finished files, for example a landing page you built with an AI tool like ChatGPT, Claude or Lovable. Quentn then serves them on your own domain.
Your page can include a form. When a visitor signs up there, Quentn creates the contact and starts the campaign for them. This connects your page directly to your marketing.
At a glance:
- Your own design: You build the page with HTML, CSS and JavaScript, using an AI tool or by hand. You’re not tied to the Quentn layout.
- No server needed: You upload the files and Quentn serves them.
- Form that starts your campaign: New contacts go straight into your campaign.
- AI prompt template: You get a ready-made guide for your AI tool so the page follows all technical rules.
Requirement: your own domain
Pages built from your own HTML run only on your own domain (e.g. go.example.com), never on a Quentn domain. The reason: such a page has no Quentn legal notice and no Quentn footer, so it belongs on your domain.
- Set up your domain in Domain Management (you can find a guide here).
- Wait until the domain is live.
Note: As long as no domain is live, the “Page” element shows the message “Connect your own domain first” with a “Set up domain” link.
If a domain later becomes unreachable (e.g. because the DNS settings have changed), the element lets you know. Have the DNS settings corrected or choose a different domain.
What you use the element for
- You’ve built a page with an AI tool or by hand (HTML, CSS, JavaScript, images, fonts) and want to publish it without your own hosting.
- The page should have a form that visitors use to sign up and that starts your campaign.
- You want to react to visitor actions later using page events.
Setup in five steps
When you open the element, the dialog guides you through five numbered steps.
Step 1: Choose the page address
Choose one of your live domains and enter a path, for example webinar. The page is then available at https://go.example.com/webinar.
-
Home page: Leave the path empty if the page should be your domain’s home page. This only works if the domain doesn’t already have another home page (e.g. a static page at
/). -
Reserved paths: You can’t use paths that start with
_p,public,admorapi.
Next to the address, you’ll find these buttons:
| Button | Function |
|---|---|
| Copy | copies the address to the clipboard |
| QR code | copy as an image or download, e.g. for flyers |
| Change | changes the address |
If your page has a preview image for messengers and social media (og:image), you’ll see it there too.
Good to know: A changed address only goes live when you publish the campaign. Until then, the page stays available at the old address. The new address is already reserved for you, though.
Step 2: Configure the form
Answer the question “Does the page contain a form that adds contacts to this campaign?”
- No: The page is a content-only page.
- Yes: Select the contact fields the form may send (e.g. first name, email, phone or custom fields).
Required fields: Mark fields as required if they must be included in every submission. If a required field is missing, Quentn rejects the submission.
Important: The form always needs either the primary email address or a complete postal address.
Protection: Under “Protection”, you can set the following:
| Option | Effect |
|---|---|
| Flood protection | no more than 20 submissions per IP address in 60 minutes. We strongly recommend turning it on. |
| Spam protection | checks the IP address against a spam database |
Even without flood protection, a fixed limit of 300 submissions per IP address in 60 minutes applies.
What happens on submission: Quentn...
- creates the contact or updates an existing one,
- adds an entry to the contact history,
- starts the campaign for the contact from this element (trigger “Form on page submitted”).
Note: Your page shows the success message after submission itself. Quentn doesn’t provide a thank-you page or redirect here. The page handles that itself.
Step 3: Build your page with AI
The “AI prompt template” button opens a guide with a ready-made template. Give it to the AI tool that builds your page.
The template contains:
- the rules every page in Quentn must follow (see “Technical rules for your page” below),
- your page’s address,
- your form’s fields and how the page sends them to Quentn,
- the names of your page events.
The guide also shows examples: build settings (e.g. for a Vite project), a finished HTML form and the values the form can send.
Tip: Set the address and form fields first (steps 1 and 2). Then the template can include them. If the form is turned on but no field is selected yet, the guide points this out.
Step 4: Upload files
Once you’ve given the prompt template to the AI of your choice, it will give you one or more files as a result. Drag these files, a folder or a ZIP file into the upload area or select them. A ZIP file is unpacked directly in your browser.
- Adding files: Uploaded files are added to the page. Files with the same path are replaced.
- New build: Check “Replace all files of the page (e.g. for a new build)” when you upload a completely new version. Files that no longer exist in the new build are removed too.
-
Required file: The page needs an
index.htmlat the top level. - File list: It shows all files with size and type. You can delete individual files.
-
Edit directly: You can edit the
index.htmlin the dialog (code editor, also full screen). This lets you create a simple page without uploading anything: paste HTML, done.
Allowed file types:
| Allowed | Not allowed |
|---|---|
| HTML, CSS, JavaScript, JSON, text, XML | Video and audio |
| Images: SVG, PNG, JPG, GIF, WebP, AVIF, ICO | |
| Fonts: WOFF, WOFF2, TTF, OTF | Archives (except for uploading as ZIP) |
| Scripts that run on a server (e.g. PHP) |
Embed videos from another service instead, for example YouTube or Vimeo.
Limits:
- no more than 2,000 files
- no more than 50 MB per file
- no more than 300 MB in total
Step 5: Preview your page
- Preview opens the current version on your domain in a new tab. This includes changes you haven’t saved yet.
- Use the preview QR code to open it on your smartphone.
- The preview link is valid for one hour.
Note: In the preview, the form doesn’t send anything and page events aren’t counted.
Draft, saving and publishing
This is how your page goes live:
-
Draft: Everything you change in the dialog (uploads, editing the
index.html, deleting files) goes into a draft first. - Save the element: Only when you save does the draft become a new version of the page.
- Publish the campaign: The live version is always the one in the published campaign.
More notes:
- If you haven’t saved a draft, the dialog asks you the next time you open it whether you want to continue with it or discard it.
- On the canvas, the element is named after its address. Without files, it shows “(no files yet)”.
- Each version takes its title from the
<title>of yourindex.html. You’ll also find the page under this title in the “Page event” element.
Good to know
- One page per element: Each “Page” element has exactly one page. If you copy the element or the campaign, the copy gets its own page.
- Deleting the element: If you delete the element, its page is deleted along with all versions.
- Deleting the domain: If you delete the domain, the page goes offline. Choose a different domain in the element.
-
Only one address: Quentn serves only the page’s own address. Subpages like
/webinar/detailsdon’t exist. Multiple views within the page work with hash addresses, for example#/details.
Technical rules for your page
These rules are also in the AI prompt template. If you use the template, your AI tool takes care of them. They still help you with troubleshooting.
- Static files only: Plain HTML, CSS and JavaScript are allowed, or a framework that generates static files (e.g. Vite with React, Vue or Svelte; Next.js only with static export). Nothing may run on a server: no PHP, no API routes, no server-side rendering.
-
Relative paths: Paths to your own files must be relative, i.e.
./assets/app.jsinstead of/assets/app.js. In Vite, setbase: './'for this. - Don’t hard-code anything: Don’t hard-code the domain, the address or IDs.
-
External files: You can load files from other servers (web fonts, videos, analytics) with a full
https://address. -
Link preview: For previews in messengers and social media, set
og:imagein the<head>.