Email capture

Collect email addresses from your page, choose where each signup is delivered, and export the list — with consent recorded and no marketing ever sent by Maska.

Email capture is the form at the bottom of your public page. A guest types their address, presses your button, and you have a subscriber — with the moment they consented recorded against the address.

It is the one block on the page that collects something from a guest rather than sending them somewhere, so it works differently from a link: you decide the copy, and you decide where each signup is delivered.

Turn it on and write the copy

The Email capture block sits at the bottom of the Links tab. Turn its switch on to show the form on the public page, then open it with the pencil to edit three pieces of copy:

Heading — the line above the field, for example Get the drop first.
Description — an optional sentence under it explaining what they’re signing up for.
Button label — the text on the submit button.

Leave the heading or button blank and the page falls back to sensible defaults. Everything autosaves; the form changes for guests on your next Publish.

Where signups go

Under Where signups go there are two delivery channels. They are independent — set either, both, or neither, and a single signup fans out to whichever you’ve configured.

Notification email — an address of yours. Maska emails it every time someone new signs up, so a manager sees the address arrive without opening the console.
Webhook URL — an https:// endpoint. Maska posts each signup to it, which is how you wire the form into Google Sheets, Mailchimp, Zapier or a CRM.

The collapsed Email capture row summarises what you’ve chosen — emailed to you, sent to webhook, or both.

CSV export is always there

Every signup is stored whether or not you set up a channel, and the collapsed row reads exports to CSV when neither is configured. That is the fallback, not a lesser option: with no notification email and no webhook, you simply collect the list and download it when you want it.

The export lives on the Analytics tab under CSV export, and needs the manage permission. It gives you one row per address, oldest first, with three columns — the email, when they consented, and when the signup was captured. See Analytics.

Submitting the form is the consent. Maska stores the address together with the moment it was given, and that timestamp travels with the record into the CSV — so if you are ever asked to show that a subscriber opted in, you can.

Only the address and those two timestamps are kept. Nothing else about the visitor is recorded.

If the same address is submitted again on the same page, the second submission succeeds quietly and changes nothing — you get one record per address per page, never a duplicate, and the guest is never told they’re already on the list.

Spam protection

The form carries a hidden field a human never sees and never fills in; a submission that fills it is discarded. On top of that the API rate-limits submissions per page, and a visitor who trips that limit is told plainly to wait a moment and try again.

There is no CAPTCHA — your guests are never asked to identify traffic lights to join your mailing list.

What Maska does not do

Maska never sends marketing email from this list. The only message Smartlinks sends on your behalf is the per-signup notification to the address you set, and that goes to you, not to your subscriber. Sending to the list is entirely yours to do, in whatever tool you deliver the signups into.

Taking a page offline does not touch the list. Unpublishing keeps every captured address, and republishing carries on where you left off — see Create and publish a page.

Note: the signups figure printed on the collapsed Email capture row in the editor is a placeholder and always reads 0. Read your real numbers from the Email signups card on the Analytics tab.