Forms & popups

The builder lives under Operations → Forms & popups. Beyond email and phone you can add your own fields — text, dropdowns, radio choices, checkboxes, dates, numbers, ratings — give each a width, make one appear only when another is answered, and split a long form into steps. A live preview shows exactly what the storefront gets, including the header image and layout.

Each form collects email opt-in, SMS opt-in, or both, with single or double opt-in per form. You can also wire it to a target segment and a welcome journey, so a confirmed subscriber lands in both with no further setup.

• Inline, on a page you choose. In the theme editor, add the Ezzeefy signup form block where the form should live and paste in the form's ID. It renders as part of the page, styled to match.
• As a popup, site-wide. Switch the form to popup mode and it is served by the Ezzeefy Popups app embed on every page that qualifies. A popup can carry the form itself, or be content-only — a heading, body, image and button for announcements that collect nothing.

Editing a form takes effect on the storefront as soon as you save. Neither delivery method needs a return trip to the theme editor.

• Triggers — after a delay, at a scroll depth, or on exit intent.
• Frequency caps— a dismissed popup stays dismissed for the window you set, and one marked “never after subscribing” never returns for a subscriber.
• Targeting — limit by page, device, visitor segment, campaign link, or a schedule. Page rules are enforced server-side, so a popup cannot leak onto an excluded page.
• Experiments — run variants against each other with a holdout, the same testing model campaigns use.

Only one popup shows per page view — if several qualify, the highest priority wins — and a hard cap stops an active store from ever stacking them. On small screens a popup becomes a bottom sheet rather than covering the page.

The submission is stored immediately. If double opt-in is on, nothing else happens until the confirm link in the email is clicked — an unconfirmed submission never becomes a subscriber.

Once confirmed (or immediately, for single opt-in), four things follow: consent is recorded against the channel, the customer joins the form's target segment, they are enrolled in its welcome journey, and they are synced to a Shopify customer carrying marketing consent. Campaigns and journeys then treat them like anyone else — including suppression, which always wins.

Answers to your custom fields are stored with the submission and are covered by the same data-request and deletion flow as everything else — a GDPR redaction removes them along with the rest of the customer's data.

Each form lists its submissions in the admin, with a CSV export, and tracks a simple funnel — views, submissions, confirmations — so a form that shows often but converts rarely is easy to spot.

A hidden honeypot field quietly discards bot submissions, so the list you see is people. Spam never reaches the segment or the journey.