You have a product that is not ready, a course that opens next month or an event without a date, and you want to start collecting interested people now. You need three things: a page that explains what is coming, a form that keeps the e-mail, and a way to know whether the page works. Without coding, hiring anyone or a spreadsheet someone copies by hand.
This is how it works with Pages and Forms, from the Marketing line (by Ciro Cesar Maciel, who writes this).
Two pieces
-
Pages builds the page from blocks, publishes it at
https://pages.mymarketing.click/<account>/<address>and measures it without cookies. - Forms receives each sign-up, keeps bots out, stores consent with proof and delivers the response wherever you want.
The page does not store who signed up; the response goes to the form. That keeps the list in one place even if the same form sits on several pages.
Step 1: the form
Create a form in Forms. To publish, it needs an E-mail field. For a waitlist you usually need e-mail (required), a short text for the name, an optional single choice ("for me" or "for my team"), and Hidden fields that fill themselves with utm_source and utm_campaign.
If you will write to the list later, turn on the consent checkbox. It is never pre-checked, and each acceptance stores the text version, time, page and form version: the technical proof that the person agreed.
Bots are kept out without a captcha: a hidden honeypot field, a minimum of 3 seconds to fill it in, and 5 submissions per hour per address.
Step 2: the page
Create a page from a starter template; templates are organized by goal, including one to collect sign-ups for a list. A structure that works: a header with what is coming and for whom, three benefits, the form block with the Forms embed code, and an FAQ (when it opens, what it will cost, how to leave the list). Pages parses the embed before publishing: it refuses inline scripts, non-HTTPS addresses and IPs, and rebuilds the HTML from what it parsed. Each publish is a version that never changes; going back is switching which one is live.
Step 3: know whether it works
Pages measures every page without cookies: visits, how far the page was read, how many people reached each block, clicks on each button and form submissions. If many reach the header and few reach the form, the problem is in the middle. Under 50 visits, results show as "Collecting", with no per-block numbers. On publish and every 6 hours, Pages also checks that every link and embed still answers.
Where sign-ups go
Each response becomes a signed event for the destinations you pick: your automation's webhook, People for a record per person, or another system. Delivery is not lost: when a destination refuses, the response waits in a queue and is resent with the same id, without duplicating. A confirmation e-mail can go out through Messages.
Honest notes
- Forms has no conditional logic or file upload; Pages has no A/B tests, store or payments. A double opt-in newsletter is the Newsletter product.
- No site needed: the page lives at a Pages address, and the form has a ready link of its own.
- Pages and Forms have MCP servers; an agent can build both, show you the draft and publish after your yes.
- Free: 1 page and 1 form, no card, no expiry. The dashboards are in Portuguese for now.
Top comments (0)