Signup Manager v1.0

Part of CloudWizard Email Suite

Signup Manager builds self-hosted opt-in forms — full page, popup, embed, or iFrame — with double opt-in confirmation, GDPR consent logging, spam protection, and built-in Bayesian A/B testing. Confirmed signups can route directly into an Audience Manager list, or run fully standalone.

Requirements

Step 1 — Install the Controller

Signup Manager runs inside the CloudWizard Controller. The controller handles authentication, shared database config, and module detection. Install it first.

public_html/CW/
  bootstrap.php
  config_path.php
  index.php          ← sends /CW/ to the admin login
  vendor/            ← bundled PHPMailer, shared across every module
  admin/
    index.php
    login.php
    logout.php
    settings.php
    setup.php
    style.css
    ...

Step 2 — Install Signup Manager

public_html/CW/SignupManager/
  module.php
  signup.php
  confirm.php
  embed.js.php
  popup_preview.php
  bootstrap.php
  admin/
    _bootstrap.php
    forms.php
    signups.php
    ab_tests.php
    embed.php
    index.php
    style.css

Step 3 — Activate your license

Overview

Signup Manager → Overview shows six stat cards — Total signups, Confirmed, Pending, Suppressed, Forms, and Active A/B tests — followed by the Signup funnel and Recent Signups (the last 8 across all forms).

Signup funnel

The funnel shows, for each form and for all forms together, how many people went from seeing the form to becoming a confirmed subscriber, so you can see which form actually works. Use the 7, 30 and 90 day buttons to change the period.

Building your first form

From Signup Manager → Forms, click + New form. Every form is built from three pieces: global settings (name, type, status, language detection), the fields you want to collect, and a settings-and-content table with one column per language.

Form types

Get the exact embed code for a form from Forms → Embed. Preview any form — including how a popup will actually appear — from Forms → Preview before publishing it.

Adding a form to your website

What you paste depends entirely on the form's type. Every code snippet is generated for you on the Forms → Embed page for that specific form — copy it exactly as shown rather than retyping it, since it includes your form's real slug and domain.

Full page

You get a single URL:

https://yourdomain.com/CW/SignupManager/signup.php?form=your-slug

Nothing to embed — link to this URL from an ad, a newsletter, a QR code, or your site's own navigation. Visiting it shows the complete signup page.

JS embed

Two snippets, both required, pasted into your own page's HTML:

1. Place a marker <div> exactly where you want the form to appear on the page:

   <div data-cw-form="your-slug"></div>

2. Add this script once, anywhere before the closing </body> tag:

   <script src="https://yourdomain.com/CW/SignupManager/embed.js.php?form=your-slug"></script>

The script finds the div by its data-cw-form attribute and renders the form inside it, inheriting your page's own fonts and surrounding layout.

Headline, sub-text, and image — any form type

Every form, regardless of type, can show a headline, sub-text, and an image above the fields — set once per language under Headline & image in the settings table. On a full-page form these render centered above the card; on a popup, above the fields inside it.

Background — full page and iFrame

Under Visual style, set a Background color or image URL. On full-page and iFrame forms, this fills the entire page behind the card as a cover-fit backdrop — independent of, and stackable with, the Image URL above (you can have a full-page background image and a small logo above the card at the same time). JS embed forms ignore this setting, since an embedded form shouldn't override the host page's own background.

Back link — full page only

A full-page form automatically shows a small "← Back to [site]" link above the card whenever the visitor arrived from a real referring page — clicking a link on your own site, for instance. It's never shown for a direct visit, a bookmark, a popup, or an embedded form, since there's nothing to accurately point back to in those cases.

iFrame

One block, works anywhere iframes are allowed — including email builders and page editors that block JavaScript:

<iframe src="https://yourdomain.com/CW/SignupManager/signup.php?form=your-slug"
  width="100%" height="520" frameborder="0"
  style="max-width:500px;border:none;display:block">
</iframe>

Adjust height if your form has more fields than fit in 520px — there's no auto-resize, so a tall form (many fields, a popup-style image) may get clipped or scroll inside the frame.

Popup

A single script tag, pasted before </body> — no div needed:

<script src="https://yourdomain.com/CW/SignupManager/embed.js.php?form=your-slug&mode=popup"></script>

It fires once per browser session according to whichever triggers you enabled on the form (scroll, timer, exit intent — see Form types), and remembers a dismissal in the visitor's localStorage so it won't reappear and annoy someone who already closed it that session.

Fields & custom data

Available fields: email (always on), first name, last name, full name, phone, company, website, message. Each active field gets its own label row in the settings table, translatable per language.

Multi-language forms

The settings table has one column per language. The default (EN) column is always present; click + Language to add another. Every content row — labels, messages, confirmation email content, the post-confirm page, GDPR text, popup headline/subtext, redirect and webhook URLs — can be set per language, or left as "Same as default" for settings that don't vary (opt-in requirements, spam protection, triggers, visual style).

The language a visitor signs up in is saved with their signup record, so the confirmation email and the page shown after they click the confirm link — days or weeks later — both render in the same language they started in, not whatever language happens to be active when they click.

Use ↻ Translate from default on any language column to auto-fill it from the English content via CloudWizard's translation API. Review and edit the result — machine translation is a starting point, not a final copy.

Double opt-in & GDPR

Enable Double opt-in under Audience in the form editor to require email confirmation before a signup counts. Enable GDPR required to show a consent checkbox using the GDPR text you configured (leave GDPR text blank to omit the checkbox entirely).

Every confirmed opt-in is logged with a timestamp, the visitor's IP address, and the form identifier — a real audit trail rather than just a status flag. Confirmed signups routed to an Audience Manager list carry that consent record with them.

What the visitor sees, in order

Spam protection

These are on by default and require no CAPTCHA, so there's no added friction for real visitors.

Audience Manager routing

Set Target AM list per language column to route confirmed signups from that language variant into a specific Audience Manager list — useful for running the same form in two languages into two separate lists with separate senders.

A/B testing

Signup Manager includes built-in A/B testing scoped specifically to form and popup variants, measured against confirmed opt-in — not arbitrary page elements.

Creating a test

What counts as a conversion

A conversion is a confirmed signup. Without double opt-in it is counted when the visitor submits the form. With double opt-in it is counted when they click the confirmation link, and it is credited to the variant that person saw, once. Signups from addresses on the suppression list, and from bots, are never counted.

Saving

Save test settings saves only the test's own settings: name, confidence threshold, minimum sample size and Auto-declare. Each variant has its own Save variant button, so editing a variant doesn't need a second save on the test. A Save button is grey until you change something in its form, and the note beside it says "Unsaved changes" when it is ready.

How the probability is calculated

Each variant's conversion rate is modeled as a Beta distribution (alpha = conversions + 1, beta = visitors − conversions + 1). A Monte Carlo simulation draws 10,000 samples from each variant's distribution and counts how often each variant comes out ahead — that share becomes its "probability of being best". This is the same approach used by tools like GrowthBook, and it's more intuitive for non-statisticians than a traditional significance threshold.

With few visitors the number stays modest on purpose: two signups out of two visitors doesn't make a variant "best", it gives it about a 70% chance against a variant with two out of three. As a rule of thumb, a clear difference needs dozens of visitors per variant, and a small one (for example 5% against 6%) needs several thousand before the probability passes 95%.

Signups & export

The Signups page lists every signup across all forms, filterable by form, status (pending / confirmed / suppressed), and email search. Each row shows email, name, form, status, source URL, IP, and signup time.

Filter by a specific form first, then use ↓ Export CSV to download that filtered set — columns are id, form_id, email, name, status, ip, source, created_at, confirmed_at.

Select rows with the checkboxes and click 🗑 Delete to remove pending or suppressed entries — useful for clearing typos and abandoned confirmations. Confirmed rows can't be deleted from here — a confirmed signup is a real Audience Manager subscriber, and deleting only the log entry here would leave that subscriber intact but misleadingly absent from this list. To remove an actual subscriber, unsubscribe or erase them in Audience Manager instead.

Security

• Always use HTTPS. Signups carry personal data (email, name, IP) and consent records — never run this over plain HTTP.
• The controller admin is protected by your admin password. Use a strong password (the setup wizard enforces a minimum length).
• Keep spam protection enabled — honeypot and time check catch the majority of bot submissions with zero cost to real visitors.
• Restrict admin access by IP if possible. In Nginx, inside the location block for your CW directory:
  

  allow 1.2.3.4;
  deny all;

• Review your GDPR text and consent settings with your own legal judgment — Signup Manager logs what it's told to log, but the wording and requirement (checkbox on/off) are yours to configure correctly for your jurisdiction.

Troubleshooting

CloudWizard Email Suite — Signup Manager v1.0
cloudwizard.eu — support@cloudwizard.eu