Marketing · Pages
Every block measured. No cookies.
A sales page, a sign-up page or a page for your business, built from blocks by you or by your agent. It shows how far each visitor scrolled and which button they clicked, and it alerts you when a destination stops responding.
One sign-in for every dashboard in the line. A code arrives in your email; you paste it once. The dashboard is in Portuguese for now.
Why this exists
A button that leads to a dead page makes no
NOISE.
The checkout moved, the video and the form went offline, and the page keeps sending people there. Here every destination is checked on publish and every 6 hours, and you find out before the next campaign.
- The visit that arrived and no one knows how far it scrolled
- The cookie banner that shows up before the promise
- The page only one person on the team knew how to change
The whole path
Start, build, connect, publish, measure.
And every block tells you how much it did.
1 · Start
From a template picked by goal, or from blank.
Templates are organized by what the page needs to do. Each one comes with its blocks in an order that persuades; you change the text and the images. Your account keeps its own templates and blocks for next time.
Sell a course Grow a list Event and sign-up Present the business includes bio links Local businesses and services Clinic and office Portfolio and résumé Show results Blank header, promise, action and footer
2 · Build
Eighteen block types, and no code to write.
A page is a list of blocks, built in the visual editor. All text is plain text, and each button points to a URL, an email, a phone number, another page or a block on the same page.
header · hero · content · features · grid video · stats · testimonial · logos · team pricing · cta · faq · compare · form embed · integrations · footer button https:// · mailto: · tel: · /page · #block
3 · Connect
The form, the video and the checkout you already use.
Paste the code or the URL from the tool you already have. Pages checks what you pasted and rebuilds the page from it: loose scripts, http and IP addresses are left out.
form the code from any tool video the video URL checkout the link or code of your checkout refused loose script · http · IP
4 · Publish
Each publish is a version. Going back is one click.
The page becomes static HTML served at the edge. Each publish keeps a version that never changes; going back to an earlier one means switching which one is live. Changing the address of a published page leaves the old one pointing to the new one.
https://pages.mymarketing.click/<account>/<address> publish a new version that never changes go back the previous one is live again new address the old one answers 301 taken down 410
5 · Measure
How far they scrolled, which button they clicked, how many submitted.
A small script measures the whole page block by block: visits, how many got past the fold, which block they reached, clicks on each button and submissions of the embedded form. Bots and app previews are counted separately.
visits by page, day, version and device fold how many got past the first screen reach which block they reached clicks on each button submissions from the embedded form under 50 the dashboard says "Coletando" (Collecting)
Model Context Protocol
The agent builds and publishes. Taking a page down needs you.
Four tools do everything the dashboard does, through the same API: the agent reads the guide, reads, creates, edits, publishes and generates or rotates the key. It builds the page, suggests text for a block, checks the destinations and publishes. The whole catalog costs the agent less than 3,400 characters before the first word.
The server's limits
- Deleting, revoking or canceling only after your yes, in the conversation: the first call only asks and shows what will happen.
- Approving what the agent requested is always yours, in the dashboard. The agent reads the request and tells you.
- The pgk_ key is refused by the MCP server. It is for systems, through the API.
The account comes from the token and never from an argument. The published version shows the agent that built it and the person who approved it.
The yardstick
What It Does, and Where It Stops
The limits, stated before you have to ask.
What it measures
Every block
Visits, fold, reach per block, clicks per button and submissions of the embedded form. Bots and app previews counted separately.
Destinations
Checked
If a button leads to a place that went down, you find out. Pages checks every exit and alerts you when one stops responding.
Cookie to measure
None
The day's visitor is a hash with a daily salt. The IP goes into the calculation and is not stored.
Who visited
Not stored
Neither who visited nor who sent the form: the submission goes to the form's tool.
A/B testing
Does not exist
Each page has one live version at a time, and the numbers are kept separate by version.
Checkout and video
From your tool
Pages does not charge payments or play video: it embeds what you already use and checks that it keeps responding.
Agent
Builds and publishes
Through the MCP server, with four tools that do what the dashboard does. Taking down and deleting only after your yes, in the conversation.
Pricing
1, 3, 9 or 99 pages
Free to start
1 live page, measured block by block.
What changes between plans is how many pages the account keeps. Visits, clicks and MCP are in every plan, with no plan limit. Prices are in Brazilian reais (BRL), charged by Stripe. No card, and the free plan never expires. The yearly plan costs ten months.
FAQ
The Questions, in the Order They Come Up
Does your page need something that is not here?
Talk directly to the person who wrote the code. A real case changes the design.
Marketing · Pages
Every block measured. No cookies.
A template picked by goal, the tools you already use, every destination checked, and the agent on the draft, never on the publish.